Hardbricked even though ODIN said successful???? - Captivate Q&A, Help & Troubleshooting

I was flashing my phone back to stock tonight and even though ODIN said it completed successfully (passed all the steps, incl SBL.BIN), it is completely dead; won't turn on.
I'm assuming I'll need Connexion's debrick service now, but the big question is HOW DID THIS HAPPEN?
I can't figure out WTF went wrong even though ODIN went through 100% fine.........
Basically, the download mode status bar went to full and the software said successful, but the phone never rebooted.
Any help would be great.
-Brian

Which Odin did you use, and what were you on before you flashed Odin?
Also, check the Am I Bricked (see my sig) thread to know if you need jtag/unbrickable mod.

mrhaley30705 said:
Which Odin did you use, and what were you on before you flashed Odin?
Also, check the Am I Bricked (see my sig) thread to know if you need jtag/unbrickable mod.
Click to expand...
Click to collapse
I was using ODIN 1.81 (same as I'd used 2 days earlier and have used MANY times on this Cappy).
In was running Mosaic 6 (I think it was 6).
I haven't checked the thread you mentioned; I will. I've got a jig and that isn't working; Won't power on, nothing. Tried 3 button combo; nothing.

^ Was that the "3 button fix" Odin that u used to flash back to stock ??
If so, then it only flashes the sbl.bin and NOT the boot.bin file. And that would be the reason that you are now hard bricked. Because coming from Gingerbread bootloaders and flashing only the sbl.bin from the stock 2.1 eclair, you now have mixed bootloaders, which = brick.
But at least that brick can be fixed these days.

Dante04SRT said:
I'm assuming I'll need Connexion's debrick service now,
-Brian
Click to expand...
Click to collapse
If you do send it get Unbrickable Mod alot better then Jtag.
*Get Chance and Luck*

4-2ndtwin said:
^ Was that the "3 button fix" Odin that u used to flash back to stock ??
If so, then it only flashes the sbl.bin and NOT the boot.bin file. And that would be the reason that you are now hard bricked. Because coming from Gingerbread bootloaders and flashing only the sbl.bin from the stock 2.1 eclair, you now have mixed bootloaders, which = brick.
But at least that brick can be fixed these days.
Click to expand...
Click to collapse
That definitely sounds like what has happened. I didn't think much of the flash to stock because back in March/April when I was running CM7, I flashed back to stock using the same method and everything went fine; no issues.
If you do send it get Unbrickable Mod alot better then Jtag.
Click to expand...
Click to collapse
From everything that I read last night, that definitely seems to be the way to go.

Definitely is the way to go.
Dante04SRT said:
That definitely sounds like what has happened. I didn't think much of the flash to stock because back in March/April when I was running CM7, I flashed back to stock using the same method and everything went fine; no issues.
From everything that I read last night, that definitely seems to be the way to go.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App

UBM is definately the way to go. Where did you get the link to brick your device? We need to get it removed. Post it here.
I can do the UBM for you. Send me a pm. But for sure we need to get this link pulled. Its bricking a lot of devices lately.

AdamOutler said:
UBM is definately the way to go. Where did you get the link to brick your device? We need to get it removed. Post it here.
I can do the UBM for you. Send me a pm. But for sure we need to get this link pulled. Its bricking a lot of devices lately.
Click to expand...
Click to collapse
Link? I simply used Odin to attempt to flash back to stock from 2.3.4 Mosaic

How about a link to the Odin you used. I have to agree with Adam. If it's causing a lot of problems lately.

Dante04SRT said:
Link? I simply used Odin to attempt to flash back to stock from 2.3.4 Mosaic
Click to expand...
Click to collapse
which odin? there are lots now that we can make our own oneclicks, and non-click packages. what thread exactly did you get it from?

Actually, I was using the Odin v1.81 that came with my copy of All in One Toolbox - Funny thing is, this is the version that I downloaded back in March; it'd been working fine for months. This was the first issue I'd ever had with it.

I'm going to take a shot in the dark and say this was also the first time you used this coming from gingerbread.
Pretty sure the aio contained the "3 button fix" which very irresponsibly only contains one bootloader.

I wish aio would die.
People defend it because its a helpful program. I'd like to remind everyone reading this. Aio is and always be closed source. The developer lost the source. The program is unmaintained. The program is a one-click nuker. The program is responsible for a lot of bricks
I fought the battle to have it removed from the site. I lost. Its time for others to step up and report that program. Aio captivate toolbox is a captivate deathtrap.

AdamOutler said:
I wish aio would die.
People defend it because its a helpful program. I'd like to remind everyone reading this. Aio is and always be closed source. The developer lost the source. The program is unmaintained. The program is a one-click nuker. The program is responsible for a lot of bricks
I fought the battle to have it removed from the site. I lost. Its time for others to step up and report that program. Aio captivate toolbox is a captivate deathtrap.
Click to expand...
Click to collapse
I'm having it removed/unstickied at the moment. Reinbeau - great mod!
EDIT: Reinbeau ended up changing the TITLE to {froyo only}
not sure how much that will help.... (sad panda)

4-2ndtwin said:
^ Was that the "3 button fix" Odin that u used to flash back to stock ??
If so, then it only flashes the sbl.bin and NOT the boot.bin file. And that would be the reason that you are now hard bricked. Because coming from Gingerbread bootloaders and flashing only the sbl.bin from the stock 2.1 eclair, you now have mixed bootloaders, which = brick.
But at least that brick can be fixed these days.
Click to expand...
Click to collapse
Where is this "3 button fix" Odin........just want to make sure I avoid it when in a hurry ??
EDIT: Nix that, found it !

Related

Build 1010 Will Not Go Into DL Mode!!!

Few days ago I rooted and put Serendipity 2.0 on my Build 1010 with no problems.
I want to try Cognition 3.01.
So I followed the SAME method used in the MobileTechVideos and I cannot figure out how to get it into download mode
I have tried the 3 button method several times and it just takes me to the battery charging icon.
------
Would I be able to just pull up Odin3 (I897UCJF6-final-OCD-REV0) .exe as administrator, plug in USB, turn on phone, and go to DL mode through the phone via that way? Would it recognize it on my computer so I can just go back to stock and do the entire process over again for a ROM?
Or is this easier: http://forum.xda-developers.com/showthread.php?t=818439
Would going to download manager through my phone while having Odin3 pulled up on the computer and my USB of course plugged in, work???
Please, someone, anyone!!! Wanting to try a new ROM so bad!!!
I would flash back to stock and start fresh
Have you used odin before?
I can get you into download mode and going with odin if your phone is working and recognized by your computer but with your build you don't want to use the odin you linked I am pretty sure.
crupp said:
I would flash back to stock and start fresh
Click to expand...
Click to collapse
That's what I'm trying to do!!! I just need to get into download mode first. My phone is not bricked or anything; it's working great. I just need to get into download mode so I go back to stock and put a new ROM on!!!
I think it's because of my build, 1010.
Can anyone confirm C3POs (Odin3) method works?
xThe Enforcer said:
Few days ago I rooted and put Serendipity 2.0 on my Build 1010 with no problems.
<snip>
Would I be able to just pull up Odin3 (I897UCJF6-final-OCD-REV0) .exe as administrator, plug in USB, turn on phone, and go to DL mode through the phone via that way? Would it recognize it on my computer so I can just go back to stock and do the entire process over again for a ROM?
Click to expand...
Click to collapse
You would probably end up with a brick.
See: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
And, BTW, there is no need to flash stock before flashing Cognition, but it's still good to find a reliable way in case you ever have a real need to do so. Also, I'm pretty sure Cognition still includes and sbl.bin that will fix your button combos (that's not normally a good thing, but in your case it is).
xThe Enforcer said:
That's what I'm trying to do!!! I just need to get into download mode first. My phone is not bricked or anything; it's working great. I just need to get into download mode so I go back to stock and put a new ROM on!!!
I think it's because of my build, 1010.
Can anyone confirm C3POs (Odin3) method works?
Click to expand...
Click to collapse
I also have 010 and have flashed half a dozen rooms and used 3 button for all of them including Cog 3
opcow said:
You would probably end up with a brick.
See: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
And, BTW, there is no need to flash stock before flashing Cognition, but it's still good to find a reliable way in case you ever have a real need to do so. Also, I'm pretty sure Cognition still includes and sbl.bin that will fix your button combos (that's not normally a good thing, but in your case it is).
Click to expand...
Click to collapse
Thanks for the link.
So bottom line; just use a different Odin3. Just like I originally posted:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
Same concept.
crupp said:
I also have 010 and have flashed half a dozen rooms and used 3 button for all of them including Cog 3
Click to expand...
Click to collapse
Every phone is different. I've read of someone with 1008 not having 3 button.
opcow said:
You would probably end up with a brick.
See: http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
And, BTW, there is no need to flash stock before flashing Cognition, but it's still good to find a reliable way in case you ever have a real need to do so. Also, I'm pretty sure Cognition still includes and sbl.bin that will fix your button combos (that's not normally a good thing, but in your case it is).
Click to expand...
Click to collapse
And also, I disagree. Every ALWAYS says to flash to stock no matter what...
xThe Enforcer said:
And also, I disagree. Every ALWAYS says to flash to stock no matter what...
Click to expand...
Click to collapse
Not everyone. It's apparently mainly confined to the Captivate forums and not universally recommended even here (Darky's instructions say nothing about it, for example). There is no benefit to doing so, believe it or not. Of course I don't care how anyone does it. It's up to you. If you tell people it's safer, however, you're misinforming people based on something that got started months ago and just became the status quo.
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
I believe this is what im looking for. I couldn't find the pit nor tar files any where. Im a vibrant owner so not to familiar with the files. Thanks. Will let you know.
Sent from my SGH-T959 using XDA App
Well bottom line, I think the easiest method for me to get into download mode every time I want to root/flash is by using the 99 cent jig. Thanks everyone for there info.
So I got into download mode by installing a 3buttonfix.zip via CWM.
I used Odin3 exactly like your supposed to. Went to stock, master cleared. Everything passed and completed.
My phone is now back to stock but still showing all files on my SD card. I even tried a factory reset and it still shows them.
Any ideas?
Blah, still no one?
*2767*3855#
This is the code you can enter in the dialer to wipe the phone internal memory. Does not ask for confirmation so make sure you have already done a backup of what you want.
newter55 said:
*2767*3855#
This is the code you can enter in the dialer to wipe the phone internal memory. Does not ask for confirmation so make sure you have already done a backup of what you want.
Click to expand...
Click to collapse
Outstanding. It worked and did actually delete everything on my SD card. It's odd how Master Clear and factory reset through the phone did not but this way did. Build 1010 is bipolar.
Appreciate all the help everyone!
(I gave you a 'thanks' Newter)

[Q] Brick

I am wondering how easy it is to brick my Captivate. Also, how easy is it to brick the phone, with the only solution being to use a JIG?
Is the only way to brick if you do something stupid? If you follow all instructions (flash to stock, etc.) is it even possible to brick it? I've upgraded my phone to 2.2 using Kies; does the fact that I've upgraded once make it muc less likely to fail and brick later?
I'm wondering this because all the ROM makers must flash constantly, so I'm thinking there must be a way to avoid bricks.
Thank you!
AmandeepG said:
I am wondering how easy it is to brick my Captivate. Also, how easy is it to brick the phone, with the only solution being to use a JIG?
Is the only way to brick if you do something stupid? If you follow all instructions (flash to stock, etc.) is it even possible to brick it? I've upgraded my phone to 2.2 using Kies; does the fact that I've upgraded once make it muc less likely to fail and brick later?
I'm wondering this because all the ROM makers must flash constantly, so I'm thinking there must be a way to avoid bricks.
Thank you!
Click to expand...
Click to collapse
Depends on your Captivate. In general, it's a bad idea to flash back to stock unless absolutely necessary. Bad Odin flashes are one of the biggest causes of bricked Captivates. Bad flashes through other methods (like CWM) usually leave you with boot problems, but working button combos for download mode. You should also check beforehand that your button combos work, since some Captivates are without them out of the box.
Also, wrong forum. This belongs in Q&A.
GGXtreme said:
Bad Odin flashes are one of the biggest causes of bricked Captivates.
Click to expand...
Click to collapse
Isn't the accepted way (as in the stickied thread) to always flash to stock?
GGXtreme said:
You should also check beforehand that your button combos work, since some Captivates are without them out of the box.
Click to expand...
Click to collapse
"Hold down both volume buttons and while holding them down plug the phone in." works for me
I have bricked my phone to the point of needing a jig 3 times now all because of odin. But the jig is 99 cents and is easy to use
sent from my captivate running a kitchen rom and hardcores 256hz k12n
kschumake83 said:
But the jig is 99 cents and is easy to use
Click to expand...
Click to collapse
Can you buy it, or do you have to make it from components?
Flashing back to stock is only needed when you have to, but no you do not have to flash to stock every time you flash a rom, a bad odin flash is usually the main cause in a bricked phone.. But as long as you can get to recovery or download mode, then its not bricked, you can usually get something flashed either way
existz said:
Flashing back to stock is only needed when you have to, but no you do not have to flash to stock every time you flash a rom, a bad odin flash is usually the main cause in a bricked phone.. But as long as you can get to recovery or download mode, then its not bricked, you can usually get something flashed either way
Click to expand...
Click to collapse
But the stickied thread says the exact opposite. I'm a little confused.
nbs11 said:
Here is the rule of thumb: if it does not specifically say anything about being able to not use ODIN in the original thread for the ROM you MUST you ODIN.
Click to expand...
Click to collapse
AmandeepG said:
But the stickied thread says the exact opposite. I'm a little confused.
Click to expand...
Click to collapse
Sometimes personal habit becomes the correct way to do something. For instance one teacher teaching how to count with pictures of apples and the other using oranges.
GGXtreme said:
Bad Odin flashes are one of the biggest causes of bricked Captivates. Bad flashes through other methods (like CWM) usually leave you with boot problems, but working button combos for download mode.
Click to expand...
Click to collapse
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
zelendel said:
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
Click to expand...
Click to collapse
Thanks! I'm gonna check if my Captivate has this 3 button recovery mode.
If it does, is the 3 button way just as effective as a JIG? And how effective is the 3 button and JIG at recovering from bricks (like I mean, how possible is it that they will not work)
AmandeepG said:
Can you buy it, or do you have to make it from components?
Click to expand...
Click to collapse
you can buy jigs online people sell for 20$ or so...but it's actually very simple to make and so cheap as well so buying one is slightly pointless. also, i have flashed too many roms i've lost track, my phone shutdown in the middle of an odin, etc etc, and i always manage to get out of it so i wouldn't be concerned. having 3button enabled helps tho
AmandeepG said:
Thanks! I'm gonna check if my Captivate has this 3 button recovery mode.
If it does, is the 3 button way just as effective as a JIG? And how effective is the 3 button and JIG at recovering from bricks (like I mean, how possible is it that they will not work)
Click to expand...
Click to collapse
I am guessing that you are concerned with bricking yours. You must be thinking about flashing a rom for the first time. I needed the jig yesterday for the first time. From what I understand, the jig method is almost a guarantee fir download mode, making the captivate nearly unbrickable. Can it be bricked... I am sure it can, but you are part of a community full of resources to keep you from doing so. You trepidation is not unique... I too was slow to flash my captivate. Now that I have, I have a phone that I love. I have been able to contribute to the community. And... I have a new found addiction.
Hi. My username is NunHugger and I am a flashaholic.
Sent from my SGH-I897 using XDA App
NunHugger said:
I am guessing that you are concerned with bricking yours. You must be thinking about flashing a rom for the first time.
Click to expand...
Click to collapse
You are completely right there!
I think I'll hold off doing my first flash until I can go out and get the parts for the jig, make and test it, so I can be sure nothing bad will happen
zelendel said:
Normally The bad flashes from odin are due to the fact the the phone being flashed did not have the 3 button combo by default. I personally have flashed ALOT and always odin and master clear before a new rom, the only time I bricked and needed a jig was when I had my old phone (got it replaced) that didnt have the 3 button and used the wrong odin.
Click to expand...
Click to collapse
Same here...corrupted data is corrupted data..and will cause problems...no matter how it gets loaded ...I've have been using Odin since I came to the Captivate..and is the only way I have been able to actually enjoy a new rom..A new rom...a fresh install..less problems for me.
Mac
A question about download mode:
I want to test if my captivate can get into download mode by the 3-button combo. However, I don't have any zips to update or anything to download or anything like that.
How do I enter download mode and then exit without making any modifications?
I thought I could just power the phone off, but in big letters it says "Do not power off target" (in videos I've watched).
AmandeepG said:
Isn't the accepted way (as in the stickied thread) to always flash to stock?
Click to expand...
Click to collapse
Accepted, yes.
Stupiud, yes.
You don't need anything to flash to get into DL mode
Just follow the instructions as it says and if it comes up you can just reboot the phone. Although you have to pull the battery. Although I've heard that holding just the Vol Up and Power for 10 secs also works. I've never tried it though
AmandeepG said:
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Click to expand...
Click to collapse
Depends on a lot of factors. It could be that your Captivate doesn't support flashing back to earlier than JH2 (JF6 one-click will brick), that your Captivate is already missing button combos (requires C3P0LOL's fixed Odin or AT&T's OTA JH7 update), a bad USB cable, problems with Windows, using the wrong USB port, etc. (all on top of user error). Lagfix won't affect Odin flashes.
AmandeepG said:
Do these "bad" flashes occur do to doing improper things, like pulling the cable mid-update, or forgetting to unlagfix before, or stuff like that? Or are they purely random?
Click to expand...
Click to collapse
I wouldn't say they are random. They are probably mostly caused by user error or some fault in the USB chain (port, cable, driver interactions). Whatever the root cause, from what I can see almost all bricks/semibricks are the result of using odin (I include cases such as where a cwm flash results in a boot loop and the user can recover because he used one-click and has no button combos).

[Q] Will the real ODIN please stand up?

I see several different versions of ODIN being mentioned in the forum and I'm wondering which is the gold standard and/or the most up to date stable version for use on the Captivate.
Here is what I've seen that confuses me:
- References to ODIN one-click and non one-click
- Versions 1.0 all the way up to 3.0
- Filenames such as ODIN.exe and I897UCJF6-final-OCD-REV0.zip
Can anyone assist in clearing up the confusion?
I agree it gets confusing. I can tell you that I use I897UCJF6-final-OCD-REV0 to flash my captivate back to stock before loading a ROM. That version makes my captivate just like it was when I first received it. It is the One-Click 1.0. The only thing I want it for is to wipe back to stock before loading a ROM and it works so I just have stuck with that one.
G.Hook said:
I agree it gets confusing. <snip> I have a Captivate that was manufactured in Oct 2007.
Click to expand...
Click to collapse
Uh. I don't think so.
Then I must have gotten wrong information from the android forums. What does the 1007 number mean under your battery? I read that it was month/date that the phone was manufactured?
edit: whoops it must have been July 2010?
I897UCJF6-final-OCD-REV0.zip is the one I have always used
G.Hook said:
I agree it gets confusing. I can tell you that I use I897UCJF6-final-OCD-REV0 to flash my captivate back to stock before loading a ROM. That version makes my captivate just like it was when I first received it. It is the One-Click 1.0. The only thing I want it for is to wipe back to stock before loading a ROM and it works so I just have stuck with that one.
Click to expand...
Click to collapse
Palmetto_X said:
I897UCJF6-final-OCD-REV0.zip is the one I have always used
Click to expand...
Click to collapse
+1
10 char
G.Hook said:
Then I must have gotten wrong information from the android forums. What does the 1007 number mean under your battery? I read that it was month/date that the phone was manufactured?
edit: whoops it must have been July 2010?
Click to expand...
Click to collapse
1007 mean year and month or 7-2010
Sent from my SAMSUNG-SGH-I897 using XDA App
I have the 1010 build and when I used odin one click or v.1 it bricked my phone I layer found out that I have to use Odin v.3 only when I had my first captivate build 1007 I could easily use Odin v.1 I switched from 1007 to 1010 because 1010 has better GPS
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks guys.
It seems like maybe the version of ODIN you use should be correlated with build date?
I'm on 1008.
sircaper said:
Thanks guys.
It seems like maybe the version of ODIN you use should be correlated with build date?
I'm on 1008.
Click to expand...
Click to collapse
Odin should be used only until 10.09 (correct me if i am wrong on this date). But it should never be used on 10.10 or later builds as it tends to brick them. There are separate threads detailing how to get them to stock. Since u said urs is 10.08, u should be fine.
diablo009 said:
Odin should be used only until 10.09 (correct me if i am wrong on this date). But it should never be used on 10.10 or later builds as it tends to brick them. There are separate threads detailing how to get them to stock. Since u said urs is 10.08, u should be fine.
Click to expand...
Click to collapse
Is that correct that the 10.08 mean 10 = 2010 and 08 = August?
I have a 1010 captivate, and I used Odin last night following the instructions located here:http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
It worked, took me back to stock so that I could flash Cog. 3.04. Hope that helps.
Good thread, I've been wondering about this myself. Three button download mode does not appear to work on my gf's phone but two button + usb does. Also I'm comfortable adb so adb reboot download is probably my best bet. Would I ever be so bricked that I wouldn't have access to adb?
Phone is a 1007, which version of ODIN do I need?
The other question I've seen asked often is,
"Will ODIN return MY phone to Stock ATT 2.1?"
People want to know if ODIN is going to return THEIR phone to the exact state and build it was in when purchased. I don't know the answer to this. From what I gather, ODIN is A stock 2.1 build gathered somewhere along the line, but not necessarily MY stock build.
Or, were all Captivate phones sold by ATT the same out of the box regardless of time or location of purchase? I know that there was a JH7 update, but is that the only thing that has changed on all Eclair builds for the Captivate or are other things different as well? What was the original source for ODIN? Was it a Samsung/ATT release of source code?
I also keep that I897UCJF6-final-OCD-REV0.zip for when i want to flash back to stock. works great. If i ever screw anything up. Just go back in time. Also keep root folder near as well.
Phateless said:
Would I ever be so bricked that I wouldn't have access to adb?
Click to expand...
Click to collapse
Yes, you could get to the point where you can't get it to fully boot and use adb. I can't get the three button or two button usb option to work, thus I haven't flashed any ROMs yet. Last thing I need is a $500 paperweight.
trekie86 said:
Yes, you could get to the point where you can't get it to fully boot and use adb. I can't get the three button or two button usb option to work, thus I haven't flashed any ROMs yet. Last thing I need is a $500 paperweight.
Click to expand...
Click to collapse
I can get the two button download mode to work. Is that a failsafe if I'm ever ALMOST totally bricked?
There is a version of Odin that fixes the 3 button recovery. It copies slightly different files to the phone.
Phateless said:
Good thread, I've been wondering about this myself. Three button download mode does not appear to work on my gf's phone but two button + usb does. Also I'm comfortable adb so adb reboot download is probably my best bet. Would I ever be so bricked that I wouldn't have access to adb?
Phone is a 1007, which version of ODIN do I need?
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
cdwhit said:
There is a version of Odin that fixes the 3 button recovery. It copies slightly different files to the phone.
Click to expand...
Click to collapse
Which version?
It is in the development section and the title says something like "odin one click w/3 button" sorry im on mobile but it shouldbe within the first few pages in development.
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Android 2.1 for captivate

where can i find the original 2.1 version of android for my captivate? Plz Help
concha214 said:
where can i find the original 2.1 version of android for my captivate? Plz Help
Click to expand...
Click to collapse
You can use Odin (search for it in the Captivate Forum) and that will get you back to 2.1
http://forum.xda-developers.com/showthread.php?t=731989
Here is Odin3 one click w/ drivers, if needed. USE ONLY IF YOUR BUILD NUMBER IS 1009 OR LOWER!!!! FAILURE TO DO SO WILL RESULT IN A BRICKED PHONE.
mrhaley30705 said:
http://forum.xda-developers.com/showthread.php?t=731989
Here is Odin3 one click w/ drivers, if needed. USE ONLY IF YOUR BUILD NUMBER IS 1009 OR LOWER!!!! FAILURE TO DO SO WILL RESULT IN A BRICKED PHONE.
Click to expand...
Click to collapse
Caps are like swear words use sparingly or they will become meaningless.
But yeah odin back to stock
Sent from my SAMSUNG-SGH-I897 using XDA App
mrhaley30705 said:
http://forum.xda-developers.com/showthread.php?t=731989
Here is Odin3 one click w/ drivers, if needed. USE ONLY IF YOUR BUILD NUMBER IS 1009 OR LOWER!!!! FAILURE TO DO SO WILL RESULT IN A BRICKED PHONE.
Click to expand...
Click to collapse
Mine is a 1010 all I have ever used is the one click version to go back to stock. On top of that my sister and her bf each have a 1012 used it on both of theirs no problem either. All if them have the 3 button fix still too...
Studacris,
Then why do most people here use the 1010 rule for one click?
Crystalhand,
Just wanted to show how important the info is. Point taken.
mrhaley30705 said:
Studacris,
Then why do most people here use the 1010 rule for one click?
Crystalhand,
Just wanted to show how important the info is. Point taken.
Click to expand...
Click to collapse
I've been wondering this for a while! Like I said no problems on this end. Only problem I ever had was odin not seeing it in dl mode, I got that fixed though, n no bricked phones or even lost 3 button fixes I've heard happening. But I don't wanna f anyones phone up if I'm just somehow an exception to the rule or something.
I understand.
i am so tired of people getting offended by CAPS. it is not anger / or yelling or offensive.
ITS TO STRESS A POINT, some times its needed as alot of people cant read what has been said 5 times in-front of their face. (not here but other situations)
other times why bother being all polite and writing an essay when you can give instructions in point form and stress the main points.
i use caps and people think im a jerk.
but they notice the important part or get the point.... its worth it.
YOU ARE NOT ALONE! IM WITH YOU BUDDY!!
"sticks and stones will break my bones but CAPITAL letters offend me...."
what a world...
How do I find the build number?
UNDER YOUR BATTERY!!!!
lol its a date 1007 - 1012 or 1101 up...
A-HA!! So it is. I must be blind. 1007. Well that sucks. I just flashed the official ATT 2.2 and borked everything.
studacris said:
I've been wondering this for a while! Like I said no problems on this end. Only problem I ever had was odin not seeing it in dl mode, I got that fixed though, n no bricked phones or even lost 3 button fixes I've heard happening. But I don't wanna f anyones phone up if I'm just somehow an exception to the rule or something.
Click to expand...
Click to collapse
Off topic, but how did you make ODIN recognize your phone? I never had problems with it until recently, but it started to not recognize my phone after flashing MIUI. I tried every possible fix besides using a different computer, and nothing worked. Finally used a spare laptop and it worked, but I'd like to be able to use my main for flashing stock.
OBatRFan said:
Off topic, but how did you make ODIN recognize your phone? I never had problems with it until recently, but it started to not recognize my phone after flashing MIUI. I tried every possible fix besides using a different computer, and nothing worked. Finally used a spare laptop and it worked, but I'd like to be able to use my main for flashing stock.
Click to expand...
Click to collapse
I restored my pc from a restore point I made 3 days before that **** started happening. I make one once a week, or anytime windows updates whichever comes first.
So if I cant use ODIN because my phone is an early build, what can I use to put back the stock 2.1 on there, or retry 2.2?
jmgelba said:
So if I cant use ODIN because my phone is an early build, what can I use to put back the stock 2.1 on there, or retry 2.2?
Click to expand...
Click to collapse
No, you CAN use odin because your phone is an early build, I was saying that I have 3 later builds that are supposed to be wonky with odin but haven't gotten any problems. And that is just about the one click odin anyway, you can always use the full odin, just the one click is supposed to cause problems with later builds.
1007 should be fine.
jmgelba said:
So if I cant use ODIN because my phone is an early build, what can I use to put back the stock 2.1 on there, or retry 2.2?
Click to expand...
Click to collapse
You aren't reading. Your 1007 will restore using Odin just fine. You need to be on 2.1 to be able to use the Kies Mini upgrade to 2.2.
Odin worked fine thanks guys, I needed it to be able to get the warranty on my phone back and get it replaced by att,
Sent from my GT-I9000 using XDA App

[Q] I think I hard bricked my Captivate

First off there is no section to Continuum so I'm simply posting in here rather than android development. I have read up and am going out later today to buy some resistors in order to test if I can get into download mode that way.
Okay so I 1 click odin'd back to stock from firefly 2.8. I then tried to use the button combinations to get back into download mode after flashing stock. I lost the button combinations after using odin. So I one click rooted, installed terminal emulator and was able to get into recovery and download mode using that method. I began the process of flashing continuum and flashed the gingerbread bootloaders. It went fine. I9000 flash screen popped up and it booted into eclair. Stupidly I used an older update .zip to flash cwm and then flashed a 3 button fix .zip in order to get the 3 button combo back before moving forward. After I choose to reboot in cwm. Nothing happened. Phone is completely unresponsive (button combos, power, won't charge). Complete paper weight right? I already have a replacement coming from att but I just wanted some input as to how much I messed it up and if ATT can go through my files after they jtag the phone I send them back.
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
studacris said:
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
Click to expand...
Click to collapse
lol anything out of the universe that could fix it?... OH YEAH I KNOW, I KNOW! A JTAG
Then again, go for waranty 1st. Studa is right, once you mess up with the bootloaders, there's nothing you can do about it. Your phone is bricked.
studacris said:
Bricked!! You DID NOT need the button fix on the new bootloaders, you had a working combo with the new ones its contained in the secondary bootloader its just a different series of buttons flashing the button fix mixed a gb primary bootloader and a eclair/froyo secondary= completely ****ed. No jig in the universe can save it.
Att won't be able to tell, they have to take it apart and flash it, thus erasing all evidence.
Click to expand...
Click to collapse
Sent from my GT-I9100 using XDA App
Studacris,
I'm not a noob. I am running continuum on my other captivate and have flashed many times. I did try the other key combinations NOT the standard ones. They still would not work. I understand that is bricked. I figured as much. The jig was in case any of you asked if I at least tried. AlI needed to know.
I sort of did the same thing
http://forum.xda-developers.com/showthread.php?t=944418&page=63
The last post here, the guy said he used the All-in-one tool to load Continuum 5, so I tried it. Woops. At least my contract is up, may look into the Inspire.
I have not tried a jig, since ever post I've seen, if it don't even flicker with the buttons, it's a waste of time.
Later
I recently bricked mine as well. I believe you can walk into an att device repair center located in your town and let them play with it for a few minutes. After they figure they cannot fix it they will give you a replacement.
Least thats what they did years back with my htc kaiser (at&t variant). I even took apart that kaiser and messed with the internals. They said "you know it's out of warranty cause the void sticker is damaged?" I said "What? No I didn't know I didn't do that." They replaced it anyway. They are pretty nice when it comes to these things.
I currently have a bricked cappy. Gonna take it in friday.
Where in any of the GB bootloader instructions on any of the ROMS does it say flash 3 button fix. Its says read over and over how to flash and follow to the T. You failed nice job. That is why the dev write the instructions so that you can read and follow.
Sent from my GT-I9000 using XDA Premium App
BWolf56 said:
lol anything out of the universe that could fix it?... OH YEAH I KNOW, I KNOW! A JTAG
Then again, go for waranty 1st. Studa is right, once you mess up with the bootloaders, there's nothing you can do about it. Your phone is bricked.
Click to expand...
Click to collapse
HEY STUDA!!! doesnt this sound familiar??? lol dumb ass!
didnt i say what you did?
and you said what bwolf did?
couple days ago...
teach you for making me look dumb!
and +1 for dingokevin!!
keepin an eye on you!
TRusselo said:
HEY STUDA!!! doesnt this sound familiar??? lol dumb ass!
didnt i say what you did?
and you said what bwolf did?
couple days ago...
teach you for making me look dumb!
and +1 for dingokevin!!
keepin an eye on you!
Click to expand...
Click to collapse
wait what?
oops nevermind that was bwolf doing that to me the other day... lol
damn short term memory...
wait what?
Since nobody can read. I ALREADY HAVE a replacement coming. I DID read the instructions and have successfully installed roms since cognition. Mods please lock thread because everyone likes to jump down peoples throats and assume rather than reading my explanation and how I knew it was bricked already. Thanks for nothing.
Sent from my GT-I9100 using XDA App
thread locked by op request.

Categories

Resources