Related
Recently, I had a very long discussion with some helpful users regarding how my market disappeared in the Android Themes section. After never recovering my stock market application, I finally just flashed to the cognition rom that is built for 2.1.
This was a huge risk for me because for some reason my phone is not found in Odin when it is in download mode. I have already tried everything to get it recognized, but nothing was able to get it recognized. If I were to brick my phone, I don't think I could fix it. I soft bricked it during the problem with the Market, but luckily I was able to get the phone working again through recovery.
I am thinking of flashing to the new cognition so that I can get my phone running on a 2.2 based rom and then quit flashing until I get a better phone or figure out my Odin problems.
I just have a few questions. I know a lot of people recommend flashing to stock first (which I can't do), while others don't flash stock. I should be able to just disable Voodoo and hopefully flash successfully to a new rom, correct? Also, what are the chances of a permanent brick? As long as I could get into recovery I could probably get the phone back up again without the use of Odin, right?
Well, first, this belongs in Q&A but...
It sounds like you have nothing to lose at this point. A lot of people flash roms without going back to stock, myself included. Disabling lagix is recommended though. I've seen a few people have issues going from 2.2.1 to 2.2 so keep that in mind if you're currently running 2.2.1.
As far as bricking your phone, it's always a possibility. Proceed with caution.
As a side, did you try to battery pull method to get Odin to recognize your phone?
lrs421 said:
Well, first, this belongs in Q&A but...
It sounds like you have nothing to lose at this point. A lot of people flash roms without going back to stock, myself included. Disabling lagix is recommended though. I've seen a few people have issues going from 2.2.1 to 2.2 so keep that in mind if you're currently running 2.2.1.
As far as bricking your phone, it's always a possibility. Proceed with caution.
As a side, did you try to battery pull method to get Odin to recognize your phone?
Click to expand...
Click to collapse
Is 2.2.1 the same as 2.1update-1? Thats what I have...
What is the battery pull method? I may have tried it, but I can't remember.
yentlequible said:
Is 2.2.1 the same as 2.1update-1? Thats what I have...
What is the battery pull method? I may have tried it, but I can't remember.
Click to expand...
Click to collapse
Sounds like your running eclair. Do this to get into download mode.
Open stock Odin.
Power off the phone.
Remove the battery.
Connect your phone to your computer via USB.
While holding down the volume up and down buttons simultaneously re-insert the battery.
Odin should now recognize your phone and allow you to flash back to stock.
I haven't done that in a while.
Sent from my liberated Captivate via XDA App.
lrs421 said:
Sounds like your running eclair. Do this to get into download mode.
Open stock Odin.
Power off the phone.
Remove the battery.
Connect your phone to your computer via USB.
While holding down the volume up and down buttons simultaneously re-insert the battery.
Odin should now recognize your phone and allow you to flash back to stock.
I haven't done that in a while.
Sent from my liberated Captivate via XDA App.
Click to expand...
Click to collapse
Ok, ill try this out.
Also, I apologize for making this in the wrong forum. I got confused and thought that it would be a good place if I was discussing a roms.
yentlequible said:
Ok, ill try this out.
Also, I apologize for making this in the wrong forum. I got confused and thought that it would be a good place if I was discussing a roms.
Click to expand...
Click to collapse
Good luck . Their friendly in q&a too
Sent from my liberated Captivate via XDA App.
lrs421 said:
Good luck . Their friendly in q&a too
Sent from my liberated Captivate via XDA App.
Click to expand...
Click to collapse
Wasn't recognized....
Ill go take this over to the Q&A section...
So I did just brick a 1008 phone and have a new one coming, so what should I be aware of with these newer versions of phones before I flash?
I did learn that one-click odin and the 3-button fix are big no-no's. BIG. It's a shame too, because the GPS on this fixed model was as good as my girlfiend's tomtom. So anyway, can someone point me in the right direction?
Maybe get an Inspire 4G? Seriously though, the button combos are still the biggest pita to me I have a 1010 build and the one click odin will soft brick it in a heartbeat. full odin seems to work best for me.
i was surprised, it wasn't the one click that killed it, it was the 3-button fix. I had successfully gone back to JF6 and master cleared (even though it came with JH7 stock) without issue. Just that last thing killed me when I couldn't get into download and I was reckless. Oh well. I won't be screwing that up again!
Aron1980 said:
i was surprised, it wasn't the one click that killed it, it was the 3-button fix. I had successfully gone back to JF6 and master cleared (even though it came with JH7 stock) without issue. Just that last thing killed me when I couldn't get into download and I was reckless. Oh well. I won't be screwing that up again!
Click to expand...
Click to collapse
Hmph. That's just weird. I have a1008, and while I did soft-brick it once using Odin 1-click, using the 3-button fix wasn't a deal. I generally don't use 3-button now, though; just reboot into recovery from the menu screen when the phone is on, once I've flashed back, master-cleared, etc. Guess I'll be a bit leery about using 3-button in the future, though.
Well it was a reconditioned phone from AT&T. I think it had all the new software and updated hardware. So that may have been the reasoning. I'll be using ADB to get some stuff done for sure in the future
Here's a copy/paste of a reply I made on another forum. ODIN-1-CLICK bricked this guy's phone.
"
I think your original problem (and mine; same issue) was due to using ODIN-1-CLICK on a batch 1010 or 1012 phone. The trick is to ONLY use ODIN3 (NOT 1-CLICK) with the 1010/1012 phones. So far, I've flashed my 1012 phone this way at least 6 times and everything has worked fine.
[PROGRAM] AIO Captivate Toolbox 3.0 NOW LIVE *Smaller, Faster, + More Automation* - xda-developers
The above is a GREAT program/toolbox for flashing phones. It includes both ODINs and will allow you to flash, root, flash customs, all in one place.
The other thing that I've become semi familiar with is "ADB". If you're not familiar with it do some research on it. You can get ADB with the SDK Tools for Android - Basically what I use it for is to VERIFY communication between the phone and the computer, prior to using ODIN3. This will help to ensure that things are getting started off correctly.
The last thing I *****HIGHLY***** recommend is spending the $10 on a jig. I did a flash to stock today and it had some partition problems and I had to use the jig to get back to Download Mode. As far as I'm concerned - If you flash at all, you need one - for $10, buy one now and have it on hand for later.
Anyway, glad to see you got another one - Hopefully your first experience will not discourage you from flashing ROMs. I was hesitant at first for fear that my phone would go 'dead' again, but using the above techniques has really proved itself as reliable to me."
Most totally disagree with me, but this is the Odin I've used on my 1012 build with ZERO problems.....
http://forum.xda-developers.com/showthread.php?t=731989
Keep in mind, though, that I've only used it once when I went from Cog back to stock so I could flash Serendipity.
do you have 3 button working on it after using odin 1 click?i have a 1012 build used odin 1 click lost my 3 button into recovery and cant use it to get into download mode had to use odin 3 to get it back.
Maybe I'm missing something here but I don't even know if my 1012 build Cappy has the 3 button stuff on it or not.
If I want to go to recovery, I use the extended power options, OR adb, or CWM for that matter.
Download mode? ODIN will usually take me there automatically if plugged in to USB - or my jig - or adb again, or the ext power options.
I don't need/care about the 3 button crap - should I?
Dante04SRT said:
Here's a copy/paste of a reply I made on another forum. ODIN-1-CLICK bricked this guy's phone.
"
I think your original problem (and mine; same issue) was due to using ODIN-1-CLICK on a batch 1010 or 1012 phone. The trick is to ONLY use ODIN3 (NOT 1-CLICK) with the 1010/1012 phones. So far, I've flashed my 1012 phone this way at least 6 times and everything has worked fine.
[PROGRAM] AIO Captivate Toolbox 3.0 NOW LIVE *Smaller, Faster, + More Automation* - xda-developers
The above is a GREAT program/toolbox for flashing phones. It includes both ODINs and will allow you to flash, root, flash customs, all in one place.
The other thing that I've become semi familiar with is "ADB". If you're not familiar with it do some research on it. You can get ADB with the SDK Tools for Android - Basically what I use it for is to VERIFY communication between the phone and the computer, prior to using ODIN3. This will help to ensure that things are getting started off correctly.
The last thing I *****HIGHLY***** recommend is spending the $10 on a jig. I did a flash to stock today and it had some partition problems and I had to use the jig to get back to Download Mode. As far as I'm concerned - If you flash at all, you need one - for $10, buy one now and have it on hand for later.
Anyway, glad to see you got another one - Hopefully your first experience will not discourage you from flashing ROMs. I was hesitant at first for fear that my phone would go 'dead' again, but using the above techniques has really proved itself as reliable to me."
Click to expand...
Click to collapse
I certainly won't be deterred (sp?) from flashing again. Just going to do a little more research in the next two days, so I can flash the new one when it arrives. I am a little familiar with ADB and the standalone ODIN. I think I will be spending more time using them. I actually bricked using the AIO toolbox, so I think I will just stick to doing it myself. Not that it was that programs fault, but I believe it made me a little less cautious because of the ease of using it. But still a fantastic thing for many users.
Aron1980 said:
I actually bricked using the AIO toolbox, so I think I will just stick to doing it myself. Not that it was that programs fault, but I believe it made me a little less cautious because of the ease of using it. But still a fantastic thing for many users.
Click to expand...
Click to collapse
The toolbox just incorporates the individual programs and some of the ADB scripts all into one package - The ODIN versions used in the AIO toolbox are the exact same as the standalone ones. Just FYI.
I don't use ODIN 1-CLICK anymore (except for Master Clear use). I have actually encountered a soft brick situation 2 times using the ODIN3 - For some reason, my phone sometimes hangs on the Partition section during a flash. When it does, it results in a soft brick with the computer-!-phone. The jig always gets it back into download mode, no problem.
sethjamto said:
Most totally disagree with me, but this is the Odin I've used on my 1012 build with ZERO problems.....
http://forum.xda-developers.com/showthread.php?t=731989
Keep in mind, though, that I've only used it once when I went from Cog back to stock so I could flash Serendipity.
Click to expand...
Click to collapse
It's not a matter of disagreeing... it's the fact that many phones in the 1010, 1012, AND 1008 series take ODIN 1-click badly. Sort of takes the opinion aspect out of the discussion.
if youre worried about getting into download mode get a usb jig gets any captivate into download mode
kevalin said:
It's not a matter of disagreeing... it's the fact that many phones in the 1010, 1012, AND 1008 series take ODIN 1-click badly. Sort of takes the opinion aspect out of the discussion.
Click to expand...
Click to collapse
Yikes. I hosed up my 1008 this past weekend doing something I had no business doing. Odin3 1-click was what worked. I guess I'm lucky. I have a VERY old G5 Mac, so Odin, Kies, and the SDK won't run on it (no Intel chip, so no windows or SDK on the PPC Macs).
I borrowed a friend's laptop and loaded up Odin3 1-click. At first it wouldn't work. I installed the drivers from Samsung, but Odin3 would only recognize the phone when it was on. It let me do a Master Clear. But if I put it in DL mode and connected it, Odin3 never saw it.
Strangely enough, I tried putting Kies Mini on it to see if I could get the stock Froyo. It installed a bunch of drivers, but I could never get it going. Every time I connected the phone, Kies Mini would quit itself. In a last-ditch effort, I tried Odin3 one more time and it recognized the phone. I can only guess it liked the drivers or whatever else it was that Kies Mini put on there.
BUT NOW, I don't have the 3-button recovery option. My Captivate came with JH7 and I always got the 3-button recovery. But now that I flashed back to JF6, it doesn't let me enter recovery mode. Grrrrr.
I'm going to try to do the OTA update to JH7 over wifi at work and see if that brings back my recovery mode...I hope it's still available. Booooo!
Long story short: 1008 Cappy + JF6 = I need to buy a new computer.
KreepyKen said:
Yikes. I hosed up my 1008 this past weekend doing something I had no business doing. Odin3 1-click was what worked. I guess I'm lucky. I have a VERY old G5 Mac, so Odin, Kies, and the SDK won't run on it (no Intel chip, so no windows or SDK on the PPC Macs).
I borrowed a friend's laptop and loaded up Odin3 1-click. At first it wouldn't work. I installed the drivers from Samsung, but Odin3 would only recognize the phone when it was on. It let me do a Master Clear. But if I put it in DL mode and connected it, Odin3 never saw it.
Strangely enough, I tried putting Kies Mini on it to see if I could get the stock Froyo. It installed a bunch of drivers, but I could never get it going. Every time I connected the phone, Kies Mini would quit itself. In a last-ditch effort, I tried Odin3 one more time and it recognized the phone. I can only guess it liked the drivers or whatever else it was that Kies Mini put on there.
BUT NOW, I don't have the 3-button recovery option. My Captivate came with JH7 and I always got the 3-button recovery. But now that I flashed back to JF6, it doesn't let me enter recovery mode. Grrrrr.
I'm going to try to do the OTA update to JH7 over wifi at work and see if that brings back my recovery mode...I hope it's still available. Booooo!
Long story short: 1008 Cappy + JF6 = I need to buy a new computer.
Click to expand...
Click to collapse
That's odd, because after I soft-bricked my phone using ODIN3 1-click, then finally got it to let me get back into download mode (I don't remember exactly what I did to manage that, though I know I hunted around the forums until I found some workable instructions), I used the non 1-click ODIN3 to get 3-button back.
I swear to God, these Captivates are pickier than cats with a food choice.
Hey guys, hope you be able to help. I have a cappy and is dead, no screen at all, no response on any button combination or even when i plug it in none at all..
I got the phone like this (for free a friend gave it to me) what are my options?
Would a jig help or JTAG is the only solution? (which i've been told is not 100% full proof that will revive the phone)
Any reply is much appreciated.
JiroPrinz8 said:
Hey guys, hope you be able to help. I have a cappy and is dead, no screen at all, no response on any button combination or even when i plug it in none at all..
I got the phone like this (for free a friend gave it to me) what are my options?
Would a jig help or JTAG is the only solution? (which i've been told is not 100% full proof that will revive the phone)
Any reply is much appreciated.
Click to expand...
Click to collapse
Yahh look for the unbrickable mod, contact AdamOutler or Connexion2005 i think!
b-eock said:
Yahh look for the unbrickable mod, contact AdamOutler or Connexion2005 i think!
Click to expand...
Click to collapse
Thanks! i have a jig on the way, will try that first (HOPEFULLY it will.do.the trick), if no luck then will try unbrickable mod.. last option is jtag.. well last option is to chuck it in my toilet really.. LOL..
Sent from my XT720 using XDA App
JiroPrinz8 said:
Thanks! i have a jig on the way, will try that first (HOPEFULLY it will.do.the trick), if no luck then will try unbrickable mod.. last option is jtag.. well last option is to chuck it in my toilet really.. LOL..
Sent from my XT720 using XDA App
Click to expand...
Click to collapse
Try the jig, see if Odin recognizes it.
Don't do Jtag, it's a pay each time thing while the unbrickable mod is forever, my phones on the way back from getting it done!
I've tried using both Odin methods, even using sdk tools, through command prompt with adb. Nothing is working. My Captivate gets to the download screen, and that's as far as it gets. I've watched numerous videos about this, and haven't come across this problem before.
I'm not an idiot, i've flashed a few roms before, but i'm using phoenix 6.0 with a basic speedmod kernel, no under/over clocking.
Can someone please help me with this, it's extremely frustrating. Thank you
wow
wow, ok, now I still can't get back to stock with odin, nor can I get back the first boot screen past the AT&T World Phone screen
Are you either able to do download with the Vol Up & Down and insert USB and have ODIN recognize?
More details, how did you get here, what have you tried?
Sent from my Captivate using XDA Premium App
mcord11758 said:
More details, how did you get here, what have you tried?
Sent from my Captivate using XDA Premium App
Click to expand...
Click to collapse
I dont mind helping... easier way is IM tho.... google talk.... i'll IM my gmail....
lovethegame0204 said:
I've tried using both Odin methods, even using sdk tools, through command prompt with adb. Nothing is working. My Captivate gets to the download screen, and that's as far as it gets. I've watched numerous videos about this, and haven't come across this problem before.
I'm not an idiot, i've flashed a few roms before, but i'm using phoenix 6.0 with a basic speedmod kernel, no under/over clocking.
Can someone please help me with this, it's extremely frustrating. Thank you
Click to expand...
Click to collapse
When I first decided to flash to stock using Odin I had all kinds of issues. Everything from nothing happening to it only flashing halfway through. My problem turned out to be the cable. I was using a cheap microUSB cable at work. When I got home, I used the original cable that came with the device and had no issues.
Things you can try;
- Using a different microUSB cable
- Making sure you have the samsung drivers installed. If they are, uninstall and reinstall
- Try different USB ports with the microUSB cable. Some people say they had problems using the front ports while others the back ports. Worth a shot
- Try using a different version of Odin either newer or older
- If you have access to another PC, try flashing from there as well
Hope this helps
i've tried using both odins, the 3 click, and the one click. I've gone in with "AIO Captivate Toolbox" and also through the command prompt with adb.exe. It starts flashing and puts my phone into download mode, where Odin has it recognized, then it gets removed, but it never comes back like its supposed to.
for b naughty my google name is [email protected]
B-Naughty said:
Are you either able to do download with the Vol Up & Down and insert USB and have ODIN recognize?
Click to expand...
Click to collapse
I can get into download mode, but after that, odin stops recognizing my phone, and it never comes back to odin. I just have to unplug and reboot it.
ok guys, a couple people said re install the drivers, and that worked. Thank you very much, you saved me from owning a brick. Apparently it didn't install them properly the first time. Thank you to those that helped, I really appreciate it, truly. This is a great site, and the devs, and other members are awesome
lovethegame0204 said:
ok guys, a couple people said re install the drivers, and that worked. Thank you very much, you saved me from owning a brick. Apparently it didn't install them properly the first time. Thank you to those that helped, I really appreciate it, truly. This is a great site, and the devs, and other members are awesome
Click to expand...
Click to collapse
I too am having huge driver issues... I uninstalled the ones that work perfectly, and installed the ones in the aio tool... now huge driver issues... took me an hour to go to stock and load another rom... fixin to load cyanogen so gotta use the nexus s drivers... hopefully those will work better...
lovethegame0204 said:
I can get into download mode, but after that, odin stops recognizing my phone, and it never comes back to odin. I just have to unplug and reboot it.
Click to expand...
Click to collapse
Make sure Odin is up and running prior to going into download mode.
Will not fully reboot after flash back to stock ROM
Just flashed back to stock Rogers with Odin. Everything went OK untill reboot. It gets stuck at the ROGERS screen, then just shuts off!! and ideas?
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
Sorry for the long read, this is half rant and half question.
Alright, I got a captivate a long time ago (about a year and 3 months ago), loved it, rooted it and installed cyanogenmod as soon as I got home, changed roms and kernals constantly, did whatever I wanted to do.
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
-Pirate said:
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
Click to expand...
Click to collapse
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
-Pirate said:
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Click to expand...
Click to collapse
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
-Pirate said:
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
Click to expand...
Click to collapse
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
U def don't need a jig. If it's booting it's not bricked. Try removing battery, start Odin, hold down power and down, plug in and put battery in. This should bring u to download mode.
prbassplayer said:
If you would have actually searched you would have known it was a bug in the glitch. There are atleast 40 pages about that.
Click to expand...
Click to collapse
I did start to see a few people with the problem, however many people do not follow up with what fixes their problem, and I did what a few people had said to do.
prbassplayer said:
If you flashed ICS you should know it takes 2 flashes for it to work first time. Having a jig around is always a good idea as well.
Click to expand...
Click to collapse
I should of mentioned that I did flash a few times, 3 total I think, it was getting stuck at boot.
prbassplayer said:
Stuff doesn't work as intended. Keep in mind everything is still in dev and not all devices are the same. But you should have searched a little more and it would have ran =/
Click to expand...
Click to collapse
I understand that **** happens but honestly my old captivate could always get into recover mode and download mode no matter what, it's extremely frustrating that something changed with the newer models. One of my questions was what caused the brick? I did nothing wrong from what I see and it was running perfectly until I tried to restart/boot into recovery.
Oh and mbc663, thanks but download mode doesn't work at all, nor does recovery obviously.
I can't say exactly what you are doing. Best advice I can do Re download your .zips Flash back to stock GB and try again.
-Pirate said:
About 3 months ago my screen stopped working.. So I take it in and they give me a refurb captivate, looked brand new so I didn't mind. However, when I tried to get into recovery it didn't work, the 3-button-method just wouldn't work at all, period, so I try to get it to work, gets stuck in bootloop.. pretty much every time I try to flash a rom something goes wrong and I get stuck in a bootloop but I can usually get into recovery or download mode because I had CWM.
So I'm on maxq's rom and it's working great for the past 2 months, decide not to mess with kernals or anything, however today I decided to try ICS, load it up, everything's fine, then I realize my soft keys aren't working, search for awhile, can't find anything, finally just manually start looking through the rom pages, and someone said that if you have the problem to just odin back to stock and try again.
I odin back to stock, but now 3 button combo doesn't work.. So more searching, find that I can run the 3e fix by TRusselo, doesn't work because I need root, more searching on how to root without recovery, find "SuperOneClick", root with superoneclick, then run 3e fix, everything is working fine, I check my email and load the ICS files onto SD card, go to restart and go into recovery mode.. Bricked, stuck in a bootloop, won't go to recovery, won't go to download, nothing.
Why the **** was I able to do anything I wanted with my old captivate, but if I even root this one it bricks? And what did I do to even brick it? I only ran the 2 programs and both of them worked flawlessly.
I guess my only option is to usb jig it, but honestly now I'm convinced that the phone is just faulty, I want to run the thing over.
Click to expand...
Click to collapse
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Sounds like you got one of the refurbs that is missing the SBL. Have you looked at this thread? http://forum.xda-developers.com/showthread.php?t=1129821
I've not had this problem myself but it sounds like that might help. If I remember reading correctly, once this is flashed it should stick as long as you don't flash any other bootloaders on top of it.
Its not missing the sbl. The sbl it has doesn't respond to key combos. Derpa sherpa moment for samsung I guess?
Rofl yeah...if it was missing the sbl it would be fuggin bricked!
studacris said:
Kangi...if you flash a firmware package without bootloaders, you won't have to do the 3 button fix every time. And if you keep a copy of the update.zip on your pc you don't have to even root, let alone bother with side loading ROM manager.
Cezar has a no boots jf6 and after you run that, you can still use master clear in one click.
Click to expand...
Click to collapse
I know, thanks. I'm such a creature of habit, I started doing it like this a bit over a year ago, and has worked flawlessly for me(just jinxed myself!) so I never saw a reason to "fix what aint broke".
I'll take a look at Cezar's thanks!
Yeah, missing SBL was a poor choice of words. My bad.
kangi26 said:
Last year, I had issues with my original Cap, and got a "new" one. I learned that the bulk of the Caps going out as replacements are referbs. The one I got was a 1008 build, and does not have 3 button recovery. There are minor differences with each and every Cap that's out there. That's why some have issues with ROM's and some don't, some can over clock like crazy, and some can't at all. My guess is you have a 1008 as well, but that really doesn't matter. You just have a different device and as you seem to already have learned.
It sounds like there is more research you need to do. Even though the devices are a bit different, if you are having issues with ROM's loading, then I would say it's more of a procedure issue, than one with your device.
My procedure, is,
Remove SD/Micro SD
Odin1 Click to Stock JF6, and Master Clear(This will erase EVERYTHING)
Root with One-Click Root
Use Sideload Wonder Machine to install ROM Manager, copy update.zip and 3buttonFix to my SD, then reboot into recovery
Once in recovery I install the 3buttonFix, and install my new ROM
For me this has proven to be a very good method versus going from one ROM to another. The Master Clear cleans EVERYTHING off of your SD, so there is no chance for anything to corrupt your new install. Anytime I read a post of a install gone FUBAR, USUALLY a Flash To Stock/Master Clear (FTS/MC) fixes it
Before using Odin 1 Click, check your devices build number!! If it is higher than 1012, I would NOT recommend using 1 click, there is a higher chance of hard brick on the newer devices
Click to expand...
Click to collapse
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
kangi26 said:
3buttonFix to my SD, then reboot into recovery
Click to expand...
Click to collapse
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
-Pirate said:
I didn't think anyone else was going to reply to this thread, whoops.
Thank you for helping me, but I'm still having trouble.
Rom manager doesn't show up in Market, Sideload wonder machine tells me [INSTALL FAILED OLDER SDK] with any apk of Rom manager I find.
How do you reboot into recovery when 3buttonfix hasn't been applied yet?
This sucks and is extremely frustrating, I feel like my captivate is just trolling me.
Click to expand...
Click to collapse
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
kangi26 said:
When I get home later tonight I'll link you everything you'll need. Again, VERY important, what is your build number? If it's 1012 or higher, don't use Odin 1 click
Sent from a autonomous device
Click to expand...
Click to collapse
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
-Pirate said:
Ok, finally got it working, I did exactly what you said, I found the rom manager 3.00.002 or whatever and that worked with sideloader, it took some messing around with but I'm running ICS now, thank you so much man, you've helped me so much, and now I can change roms and keep up to date without worrying about constantly soft-bricking.
As for my build number, I'm not sure, the only thing I see under build number in settings is: "IML74k"
Click to expand...
Click to collapse
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
kangi26 said:
The build number is actually under your battery, and looks like 10.06, 10.07, 10.08 and so on. It is the production date
Edit** And as a side note, do NOT try to use the 3buttonFix with a GB ROM, it WILL brick your phone in a really bad way. ONLY use it with 2.1 or 2.2
Click to expand...
Click to collapse
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: deleted
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
-Pirate said:
Is it weird that I don't have a build number? It seems I can't post pictures without a few more posts, maybe this will work: imgurDOTcom/26sXGl.jpg
And thanks for the warning on the 3buttonfix, I'm going to have to read more about bootloaders though, I don't understand what you and studacris were talking about earlier in the thread, haha.
Click to expand...
Click to collapse
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
kangi26 said:
I havent seen that before, there doesnt seem to be a build#
Might want to pull that photo, it's not too good having your IMEI number publicly displayed
Click to expand...
Click to collapse
Maybe because it's a refurb? and whoops didn't think about that.
-Pirate said:
Maybe because it's a refurb? and whoops didn't think about that.
Click to expand...
Click to collapse
I'm not sure why, mine is a referb, and I have a sticker with mine on it. Ooh well, it is what it is
Sent from a autonomous device