Database Info

Another bricked captivate thread

Alright, after spending hours upon hours researching multiple forums I can firmly say I'm stumped. As an FYI, I change ROM's frequently and have preformed these actions multiple times. So this isnt about me being a noob and doing something incorrect due to lack of knowledge (at least i hope not).
After multiple methods I can not find a single way to get into download mode.
Methods attempted:
1. cards and Battery out
waited up to 30 min with battery out,
battery in
hold volume buttons (tried to do this before the battery goes in as well)
usb plugged in (odin on in background of course)
I have gotten into download mode multiple times using this method, however, doing it now (and multiple variations, including holding only volume up or volume down, tapping power once and a bunch of random things people from various forums 'claim' to work) will result in only one thing; having the battery charging screen pop up and freeze on me. I know it is frozen as the progress timer is stuck at the 12:00 position and doesnt change, even if left there for an hour or two.
If the phone is allowed to power up normally (or i press the power button when trying to go into download mode) the phone will go to the standard ATT screen flash once then show up again and finally go into recovery mode. My research hasnt shown that i can do anything from recovery mode without having access to the internal SD.
upon further research, I came across only one other thread of e=people who had a similar problem, however the OP said he performed the download mode method mentioned above over and over and then it eventually worked. Which doesnt make a whole lot of sense to me, but nonetheless he said he got it within 40 times, I must have done this over 100 times now with the same frozen battery screen result.
I even tried ADB, which is something that was new to me. But after getting ADB to successfully work on the command line, it does not recognize that the phone is connected (my assumption is because in recovery mode, which is the only place i can be with the phone on besides the frozen screen, the internal SD isnt mounted for mass storage). So ADB didnt work either.
I am within my 30 day period, but of course, I would prefer to just fix this thing as opposed to going down to have 'the talk' about bricking my phone with ATT. Has anyone seen this issue? Anyone else have any ideas? Anything I can do from the recovery screen?
Thanks for your help

Adb should work in recovery mode.
Let me know 2 things: your batch #
What ROM you were using when it went out
Sent from my SAMSUNG-SGH-I897 using XDA App

PS don't tell att you modded your phone
Sent from my SAMSUNG-SGH-I897 using XDA App

Yea I had the same problem when i bricked my brothers captivate. I did all the 3 button method and i couldnt still go to download mode but i figured another way on how to get there =) thanks to me. But this method only works if your computer recognize your phone like if your stuck on atnt screen or galaxy s screen or even more if its all dark screen, but most importantly is that your computer recognize your phone and you have clockwork recovery. Here is the link of my post.
http://forum.xda-developers.com/showthread.php?t=842484

@fattire
1. Where do i locate the Batch #
2. It had just finished flashing into Cog 2.3b4. I had flashed to stock (like I normally do) before flashing to Cog. Looking at the screen, everything looked like it went fine and Cog was installed properly. After it finished it started restarting the phone, and this is where I am now.
P.S. Yeah, that goes without saying just so much of a hassle with the ATT people....
P.P.S. I didnt know if this was normal or not, but in recovery mode the computer can see the phone's drive but it (the phones drive) is not mounted so I can not access any of the files on it. From all that I have read ADB is working correctly and have confirmed it in the command line. I have the correct drivers ( and i know they are the right ones bc Ive done this before on the same computer with the same USB port). Odin also recognizes the phone and says it is connected but upon trying to flash to stock or anything else it just hangs, again my assumption is bc the internal SD is not mounted correctly...
@G1
Thank you for your suggestion, unfortunately it appears the phone is not being mounted correctly on my comp to recognize it properly. So your method will not work.
But keep the ideas coming!! Anyone else?

There's a solderless procedure to go in download mode.
http://forum.xda-developers.com/showthread.php?t=841512

@Silver
I attempted the procedure and it only resulted in the phone booting up to the att screen then going into recovery mode.
After this procedure, performing method 1 to get into download mode does not result in a stalled battery screen, it now goes into recovery mode. Maybe I fried something....
Oh well off to att tomorrow.....

madpuma13 said:
@fattire
1. Where do i locate the Batch #
Click to expand...
Click to collapse
Under your battery 100? number

madpuma13 said:
@Silver
I attempted the procedure and it only resulted in the phone booting up to the att screen then going into recovery mode.
After this procedure, performing method 1 to get into download mode does not result in a stalled battery screen, it now goes into recovery mode. Maybe I fried something....
Oh well off to att tomorrow.....
Click to expand...
Click to collapse
If you can get to recovery mode then your fine well it depends if you have clockwork recovery. Clockwork have an option that will take you to download mode.
Sent from my T-Mobile G2 using XDA App

Bricked... Read nearly every post available.

Is it possible to perm brick your phone? My phone got stuck somewhere in the middle of an Odin flash and I had to pull the plug. Since then I have been stuck at the "Phone...!....Computer" picture.
I can get the downloading "Do not turn off Target!!!" section with the cable plugged in and no battery. I also have it recognized by Samsung PSLite, but when I'm trying to flash the stock rom back on through PSLite it disconnects as soon as it goes to 0%.
Will it make a difference that I have Win7 64bit and the VIA drivers say 32bit on them? I'm pretty sure I have every other driver that's needed.
Any help is GREATLY appreciated. I'm a sad panda without my new phone :-(

Go to the dev section of this forum.
http://forum.xda-developers.com/showpost.php?p=14147928&postcount=3
Follows these directions exactly. Will recovery your phone for you.
Good part is, you are not bricked.

Yeah, I've been following a couple of forums that all show nearly the exact same directions. Been getting stuck on the same area...
I have very little knowledge of any of this other than following instructions (obviously not that well) but something tells me it has to be a driver issue.
The VIA drivers I installed say 32bit and my machine is Win7 64. Also, when I plug the phone in it is recognized by my computer with no errors. Once I start the install and it gets to "VIA download" I get the error - then my computer tells me the device was not recognized. I have to do a full reboot to get my computer to recognize my phone again.
Thanks for the directions

Hey man, if that isnt working for you (which I dont see how.) You can always call tech support and say your phone is not booting, even after you pull the battery out. Just say it stays stuck on the samsung screen. They will send out a new phone. Just saying but it should work regardless. Also try another USB port, see if that solves your issue and make sure you are using the OEM usb cable.

I'm assuming this will work for you. It did for me. I had the same screen.
Download first file.
Odin 1.82
Open Odin then hook up your phone and put into download mode with the battery out. Crucial part here. Put the battery back in. After flash the first file I linked you to but make sure you check the PDA option and do it through PDA only.
Should fix it I do believe.

If you follow that exactly like is says. from start to finish. forgetting that you have ever tried anything before. And still follow it. You will be fine. download everything it says download, and follow the instructions exactly.

Thanks for all the feedback everyone.
I've been trying everything suggested on here except getting a newer version of Odin. When I get in tonight I'll keep trucking along with different tweeks.
The good news is I accepted defeat (Grrr!) and have a warranty replacement on the way. It kills me that I couldn't get this on my own.
I've even installed everything on my laptop with the exact same results. As soon as I get to the downloading portion where it shows 0% the phone disconnects and my computer tells me it is no longer recognized. This was in PSLite. Odin simply says FAIL when I try to flash that method.
I have a week to return the first phone. I'll use that time to get all my drivers in order and get this figured out.

After you put the phone into download mode when it was hooked up to the computer did you put the battery back in? I had the same screen as you and when I tried to use Odin it would just say it failed every time. Put the battery back into your phone after it is in download mode before you try to flash with Odin.

Also for PSLite I had to plug in the phone (in download mode) before starting PSLite (opposite of ODIN).

Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...

mikepic said:
Odin... OdinOdinOdinOdin!
That was my problem. I was using silly PSLite instead of Odin.
Thanks again everyone for the help! Now to see if I can break her again...
Click to expand...
Click to collapse
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.

elucid said:
Actually PSLite worked for me and not ODIN, but for others ODIN worked. I guess it is good to try both. Too bad both seems so flaky! Rooting on the OG droid was a breeze compared to the charge. The OG droid was indescructible.
Click to expand...
Click to collapse
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.

dragonstalker said:
Then go back to the OG Droid. It takes literally 10 min to root a Droid Charge. If you follow the instructions like we tell you to, its not hard at all.
Click to expand...
Click to collapse
I agree rooting was really easy. Several people have had issues where they needed to restore using and ODIN and it complete fails (this is after using ODIN successfully to flash ROMS, recovery, kernels). See the end of this thread:
http://forum.xda-developers.com/showthread.php?t=1108115
You can blame it on user error, but I can assure you that I didn't do anything that should have caused my /data partiion to not mount. Sometimes things happen and the last thing you want is ODIN failing to flash when you have a brick on your hands.

Hope you fix your phone :] It always pains me to see one of these posts where someone has a bootloop or even a dreadful brick.

[Q] [HELP] Stuck on CWM screen, frozen!

Hey everyone!
So I flashed a ji6 tar through SGS kernel flasher to get 2e recovery. I think it managed to do so successfully because now I have CWM when I boot into recovery. HOWEVER, when recovery pops up it goes to the CWM screen and FREEZES! I cannot select any options including reboot system. I also now cannot startup my phone normally! What can I do? I have ODIN but it won't detect my phone when it's connected (tried this about 20 times). I'm running a mac so I guess there aren't very many options. The only way out of anything int his mess is to pull the battery. SOMEONE PLEASE HELP! My phoen is now useless for all purposes. I tried factory reset, etc. On normal bootup my phone is stuck on the startup screen and never progresses past. Help please!

well odin doesnt run on mac.
search for heimdall. (same thing but for all OS) [PROGRAM] Heimdall - Open-Source Cross-Platform Flashing Suite ...
heimdall / odin use download mode not recovery, you know that right? hard to tell by your message.
Instructions for download mode:
plug USB cable into computer
have phone shut off
hold both volume buttons
plug USB into phone
let go of buttons when you see an android digging "down"
Click to expand...
Click to collapse
or get VMware or another virtual machine and install windows. http://www.utorrent.com http://torrentz.eu/search?f=vmware http://torrentz.eu/search?f=windows+7

THanks for the tips.
I've been using (or trying to) Odin in Download mode but it will not detect my device. Recovery in CWM freezes, 2e recovery leading to the CWM screen is fine but when I hit'reboot now' or startup regularly using the power button, it's stuck on the boot up logo page. But I'm investigating Heimdall hopefully that helps or I am totally at my wit's end! Been working on this for a couple hours using everything I can think of! (And Google and XDA forums of course!)

Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!

NewbDroid said:
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
Click to expand...
Click to collapse
Any chance you have access to a Windows based system? I've never used Heimdall, so I can't help you there.
Are you 100% sure you're in Download mode? Yellow shovel guy. Were you using Odin with VMware Fusion or something similar? Try different USB ports if it's a G5 or something, doesn't apply if a Macbook.

Heimdall is open source and it works on all platforms...
It's BETTER!

studacris said:
Heimdall is open source and it works on all platforms...
It's BETTER!
Click to expand...
Click to collapse
I don't doubt that at all. I flash to stock so seldom now that using Odin once ever 3 or 4 months doesn't bother me.

NewbDroid said:
Gave Heimdall a whirl, it just says failed to confirm end of PIT file transfer. HELP!!!
Click to expand...
Click to collapse
unfortunately i know nothing about heimdall, even though im the one that suggested it. studa! help a man out! i gave you your 900

here is a link to a 1 click heimdall package, which also has a prerooted version i suggest you get that as this a transitory os and rooting is part of the process of getting 2e recovery WITHOUT flashiing a stock kernel that will make your phone unbootable.
if you have connection issues refer to THIS THREAD
once that is completed, refer to THIS THREAD to MANUALLY replace 2recovery.
then to make sure it wasn't a wonky cwm file you had that made it freeze(actually now that i think about it you could use adb to push this to the root of /mnt/sdcard FIRST to see if its the cwm file. adb should work in recovery) grab the attached update.zip

Had a similar situation and had to order the USB jig to get out of it. It is pretty easy to make or if you want an easy (and clean) option, order one. Once you have that, remove the battery, SIM and SD. Reinsert the battery and then insert the USB jig. It will go right into download mode and then from there use Odin to flash it back to stock.

Question regarding odin (solved)

Ok I have looked at thread after thread and saw some similar issues but no real solution that has worked for me. Long story short, my brother tried updating his SGS4G and "says" the cable came out during update. Basically phone was stuck in communication with pc screen. After tons of trial and error button combos, jig, etc. I was about to give up as I couldn't get it into download mode. Well got bored so tried again and somehow got Odin to recognize the phone and started to flash the K1. Unfortunately, it failed before completing and now I can get the phone into DL mode but Odin nor the PC will recognize it. It sort of boot loops a couple times then loads up to home screen for a few seconds during media scanning then trips right back to Galaxy S 4g screen and starts the boot loop deal over again. I was able to check before it cut off and it has unknown baseband. Is there any other way to get Odin to recognize while in download? I have done all the steps then plug in phone etc. Odin just sits there and PC said usb not recognized. Tried 3 different PCs with XP, Linux, and Win 7. Is the baseband the issue for getting it recognized now? If I can ever get Odin to recognize I was hoping to manage a full backup to stock and then worry about the baseband issues but for now I am stuck and would have pulled all my hair out by now but I am bald. Any advice or pointing in the right direction would be great.
Edit: Thanks for the help. After tons of attempts I got Heimdall to recognize and got it flashed back to stock.. Still isn't recognizing all the time but hopefully it will enough to allow me to root it before I give it back to him. Thanks again I read and read and tried all sorts of stuff multiple times.

If you can get into download mode. Just start ODIN whether it recognizes phone or not and see what happens. And double check your settings are correct in ODIN. Make sure u have latest version as well. Or try Heimdall.
EDIT: Go ahead and tell us whether you were on FROYO or GB. And why were you flashing K1? And what is K1? KC1?
Are you using FB's GB Ext4 Starter Pack?

Odin can sometimes be a pain. If the computer gives you the "un recognized device" keep trying. Tried different cable and USB port and reinstalling drives and such? Lots of others have had luck using the one click.. Heimdel package. But, I'm an Odin fan... If you get any sign of life from PC while it loops, that's a start.
if you have adb loaded, have you tired to spam the reboot download command while the phone loops?? Its another way to see if it does/can get into download mode..

Did you get it working? If so mark the the title [SOLVED].

[Q] Can Someone Help? I'm Stuck In Recovery<3e>

​I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420

Did you try clicking flash in Heimdall, sometimes it looks like it doesn't see the phone, but you click flash and it works. Also, have you tried clearing user data and cache? (I know you said you had factory reset at one point but now that you are stuck might be worth a try.) Looks like a boot loader issue, not sure why Heimdall doesn't see the phone, I've had good luck in the past with it.
I'm tempted to tell you to format the internal sd and try heimdall again, but maybe someone with more experience would have a better idea.

khkaiser13 said:
​I hope there is a way for me to fix this. I am a noob but, I have been successful flashing things a few times in the past (and not so lucky a few times). This time I had flashed my Infuse back to stock 2.2 Froyo UCKD5 after having Zues w/ Aries HellFire running for a couple weeks. I decided to try another ROM because I was bored. Then I screwed something up thinking I knew more than I do. As I was trying to clean things up in my files to get ready to do a back-up,something happened and about half of my apps,factory and 3rd party had no files or ?? They didn't show any MB in cache / data,in TIBU or App Mgr, only "computing...", and obviously things didn't work right. So I hit the phone's Factory Reset,went into Odin3 thinking I would try doing something I never tried before,stupid me, and installed through the PDA button, zimage root tar file, success, saw the Fugu fish and then reset Odin, turned off/ on. Pulled battery from phone, usb jig to download mode, because three button method wasn't working. I thought it had something to do with the residual kernel or bootloader from Zeus. The kernel that was running is 2.6.32.9 and I don't know what that is. Any way I thought I would install KF1 .tar Odin3 installed it but it got stuck on the Samsung power-up screen,black background white Samsung letters. I usb jigged into download mode , thinking maybe I had the wrong drivers possibly and did the Heimdall Zadig driver install, nothing changed. So, I thought that I better just reflash to stock using GTG's Ultimate Unbrick, used the UCKD5 tar and it passed. Then I unplugged the phone when it shut off to reboot, it booted into blue recovery and I hit reboot and it came right back into blue recovery. I am able to get into download mode or into the ever looping blue recovery<3e>,but nothing else. No programs,Odin, Kies, Heimdall,GTG's, recognize the phone,the laptop does and says the device may not work correctly..., but I did notice what the fails were in the recovery boot-up. So I snapped pics with my Captivate and uploaded them and I will paste them here (I think XDA lets idiots like me paste in this area?). they are readable, but if I need to type everything out I can, but not until someone asks so as to keep this already lengthy story a bit shorter. Thanks in advance,KK13/khkaiser13. sent in using my Rooted Captivate on APEX12 through XDAPremium View attachment 899419
View attachment 899420
Click to expand...
Click to collapse
Before you go any further,
Read my how to..click on the first link on my sigs.
Read through several times.
There is a BIG difference b/t download mode and recovery.

Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13

khkaiser13 said:
Thanks, I did clear Data/Cache. I also did format the sd as a last resort but, it didn't help. I don't know if you looked at the screenshots I posted but, it says Checksum Fail and Movinand Checksum Fail. I dont know what either of those are but, willing to bet if someone knows it might be repairable. Thanks Again, to both, enochpc and qkster for the helpful info which I did not know before. khkaiser13/ kk13
Click to expand...
Click to collapse
Put your phone in download mode. Odin or heimdall back to stock and start over.
Don't worry about anything else as long as you can get into dl mode

Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.

khkaiser13 said:
Hey, thanks for responding. I know the difference b/t recov. and dload. I am stuck in recovery<3e> blue, it just returns the recovery screen no matter if I press reboot, clear cache, or clear data, or try install zip. But if I usb jig it, it goes into download mode. Thats it. What I have and don't know what or how to fix is during the reboot attempt (you can read it if you click on my screenshots) it says Checksum Fail, Movinand Fail, and lfs undone. I'm gonna try to find out more about those files ( I guess thats what those would be ???) Thanks Bro.
Click to expand...
Click to collapse
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.

qkster said:
You borked something in the ROM. That's why it won't boot. Files mismatch and don't add up. That's why you're in blue recovery.
You've to get into dl mode and flash a stock ROM img. Then start over.
Click to expand...
Click to collapse
Just to add this to what qkster said! I know you said you know the difference but be sure to have proper drivers installed I personally used GTG’s Ultimate Unbrick with 100% success. If there is any doubt about bad drivers I would also suggest reinstalling them there is a very easy to use Utility called usbdeview that lets you uninstall drivers and start fresh.