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.
Related
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).
I recieved a replacement captivate today. It was a 1011 build. Recovery and download worked fine. It was running 2.2.
I used the one click odin to flash to stock 2.1 and now I can no longer get in download mode or recovery with any key combo.
What can I do to fix this? Kinda freaked out, been flashing roms for months and months with zero issues so I am not real sure how to resolve this one.
To clarify, I can use adb to get into download or recovery I am sure and thats what I am going to do. Then flash the 3 button combo fix with Odin that C3P0LOL put together.
My question is I never had this on my 1007 build. What did I do wrong and what can I do to prevent this from every happening in the future? If the fix works and I avoid the one click odin, I should be good to go from now on right? Sucks. I tested everything before I flashed one click to 2.1 which is kinda stupid I guess.
what about holding vol up and down and inserting usb?
maybe your 3button was killed by the odin 1 click... but it still shouldve rebooted...
try the steps in this thread...
http://forum.xda-developers.com/showthread.php?t=775911
B-Naughty said:
what about holding vol up and down and inserting usb?
try the steps in this thread...
http://forum.xda-developers.com/showthread.php?t=775911
Click to expand...
Click to collapse
That is what I was doing and does not work. On my old captivate, I couldnt even count the times I did this so it's not user error. Guess its good I had such good success for so long as this is the time you learn stuff! I really dont want to learn today I just want it to work?!!
gocats7 said:
That is what I was doing and does not work. On my old captivate, I couldnt even count the times I did this so it's not user error. Guess its good I had such good success for so long as this is the time you learn stuff! I really dont want to learn today I just want it to work?!!
Click to expand...
Click to collapse
yea it's a little wierd the odin finsihed and didnt reboot the phone... and now 3button won't work... some phones just wanna act wierd... ive done everything in the world to mine including yank the cord during a bad flash... never lost 3 button or download... 1011 build...
tried holding the vol buttons and hookin usb then insert batt? hope u get it goin... keep us posted...
Flashed back to stock using the loader I referenced earlier and now I have both download and recovery key combinations.
I am speculatiing that coming from 2.2 to 2.1 with the one click was a bad idea. All I had done was root the phone to that point. If anyone knows 100% what the deal was I would like to know. I went from 2.2 to 2.1 because I couldnt get clockwork to work and I read that was an issue on 2.2. I am sure there was a better way but thats what came to me.
I would guess that using the thread below to go back to stock from now on to not risk screwing up my 3 button combos would be the best idea, anyone?
http://forum.xda-developers.com/showthread.php?t=995143
One question, if I want to go back to stock 2.2 as the phone came with is there a thread for that? I looked and so far didnt find it. Probably need to just keep looking but thought what the heck, would ask since I came this far.
After upgrading to 2.3.3 on my captivate the three button fix was applied, is it hardbricked and needs to send to Samsung?
you didnt read instructions did you?
how do you go back to stock? ODIN ONE CLICK
THEN flash 3 button fix with odin3 flasher ONLY IF YOU NEED TO after 1 click (shouldnt need to)
WHY? well that was in the instructions too!
3button fix only has 1 of 2 original bootloaders.
is it hard bricked?... probab-****in-bly.... does it turn on? you tell us...
send back to samsung, yup but keep your mouth shut and play dumb (shouldnt be hard)
ALL YOU SAY: "it stopped working" and stick it to the back of a big speaker magnet for an hour. (take out your sim and sd card dummy!)
well that was an expensive lesson..
Haha yes you probably did brick. Is it really that hard to read instructions? I flash at least 3-4 times a week and have never even come close to bricking. If you do exactly what the devs tell you to do then its almost impossible to brick your phone. However you clearly didn't read. To answer your question, yes, you most likely did brick your phone.
Sent from my beloved Cappy running Continuum 5 RC3
Its not brick I did the same stupid thing but I was able to fix it whit a jig
Sent from my GT-I9000 using XDA Premium App
if you mix bootloaders, you are screwed.
Well I did. And it won't work whit the jig until I pull the battery out many times and reinstall drives
Sent from my GT-I9000 using XDA Premium App
reinstalling drivers has nothing to do with you phone bricking, so.. please just stop there,
but im not willing to thow out a 400$ brick just to prove you wrong... so fine you win! mix bootloaders all you want.
TRusselo said:
reinstalling drivers has nothing to do with you phone bricking, so.. please just stop there,
but im not willing to thow out a 400$ brick just to prove you wrong... so fine you win! mix bootloaders all you want.
Click to expand...
Click to collapse
lol backing up Tru here.. If you mess up with bootloaders, the ONLY way back is a JTAG.
If you can fix it with a JIG, your bootloaders are intact and have never been mixed/damaged.
There is no way around, that's just how it is..
J tag is no guarantee though, 99 % ya but it costs more than I paid for this phone...
And ya like I said no mixy de boot loaders
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 !
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