I attempting to get the phone to load the "Sammy 1.5" Rom. I have a Galaxy S Captivate I897.
I was not initially able to get Odin 1.85 to recognize my phone. So I used Heimdall to place it back to UCKB2.
Now Odin recognizes the phone. So then going back to the instructions for Sammy ROM:
http://forum.xda-developers.com/showthread.php?t=1486344
I fired up Odin 1.85, placed Cog Kernel Beta 2 in the PDA slot. And now the phone is stuck at:
"File Analysis.."
Its been there for over 25 minutes.
Any suggestions?
Note: I had KK4 working on the phone (small quirks: games suck) just prior to attempting this MOD.
I had this issue with my backup phone. It never seemed to like to take a flash on the first try. If I put it in download mode via a jig it seemed to work better.
One trick that worked for me was to pull the battery (Yikes! I know it soft bricks it) and I would then get the incomplete flash screen. I would then Odin from that screen and it would take.
Red_81 said:
I had this issue with my backup phone. It never seemed to like to take a flash on the first try. If I put it in download mode via a jig it seemed to work better.
One trick that worked for me was to pull the battery (Yikes! I know) and I would then get the incomplete flash screen. I would then Odin from that screen and it would take.
Click to expand...
Click to collapse
Via a jig? Are you saying that you dance a jig when you connect the phone? Just kidding. What kind of jig are you talking about?
A jig is a usb connector that has a 301k Ohm resistor on the 4th and 5th pin (the top and bottom pins next to the headphone jack.) Most if not all Samsungs android devices use this method to get in Download Mode.
Layman way to make one found here. Don't buy the usb plug he used since thats really expensive but you can understand the theory of it. You can buy one here if you like. Cheaper to just grab the resistors and buying some plugs else where, splicing a spare cable or just trying to hit the 2 pins in the port.
Here is an example of one you can buy if you don't want to build your own. They are all over amazon and ebay. This is not an endorsement for this particular seller/product. Just an example so you can see what we're talking about. For $10 or less they're great to have around and can be a lifesaver.
http://www.amazon.com/SainSonic-Don...73JQ/ref=sr_1_1?ie=UTF8&qid=1329842683&sr=8-1
Thank you. I do have a jig from when I bricked my first Captivate. I got Odin to recognize the phone. Now she is stuck at "Setup Connection"
I must be missing a step somewhere, or, I have something installed that Odin doesn't like.
Let me ask this?
If I installed kk4 with Heimdall, should Odin still recognize the phone in download mode?
Richdd said:
Thank you. I do have a jig from when I bricked my first Captivate. I got Odin to recognize the phone. Now she is stuck at "Setup Connection"
I must be missing a step somewhere, or, I have something installed that Odin doesn't like.
Let me ask this?
If I installed kk4 with Heimdall, should Odin still recognize the phone in download mode?
Click to expand...
Click to collapse
Yes. Odin and Heimdall don't care how you flashed to where you are - they only care if the phone is in download mode.
Ok, I reinstalled KK4. I get a screwed up multi color screen. Then the phone boots correctly.
It seems I've missed something. I'm going to have to figure out how to get Odin recognize the phone. To be able to install the ROM I want.
EDIT
I noticed that when my phone reboots, my live wall paper goes back to the phones default wall paper. Does not remember what setting I have placed on the phone.
It sounds like you might have a mismatch between your bootloaders (most likely you have froyo/eclair) and your Rom (a GB rom).
If Heimdall worked, grab one of the Heimdall one-click packages that has bootloaders (you may have to flash twice to get the "flash bootloaders" option). That should straighten you out.
Ok, I'm downloading one now. I'll try it in a few. Thanks again everyone for helping!!
Edit
I tried everything with Odin. Nothing worked.
Heimdall works. I installed Heimdall I897UCKK4 Stock, Wipe, with option to install Bootloaders, Param,and Repartition-Heimdall One-Click. The phone boots good. Everything except games seem to be working for now. Still have to figure out how to get Odin to work to load that "SAMMY 1.5" ROM.
Related
Hello all and thx in advance.
ATT Captivate batch 1010
I had Cognition 2.3 I think on my phone and it worked great however I wanted to try a different ROM so I attempted to restore my phone to stock using ODIN one click. I realized after that that I never disabled the voodoo lag fix or deleted my user data.
Now I am stuck in a boot loop that either shows the white ATT logo screen flashing every couple seconds or the phone off charge screen re starting every couple seconds.
I bought a USB Jig and it works great so I can get into D/L mode easily but I have tried flashing the stock firmware at least 6 times now using different machines, different ports, different versions of ODIN and I've searched around these forums and others for several hours trying to find a solution. It seems that I needed to erase my user data in recovery mode and removed the lag fix before I did this but it is what it is. I have tried to get to recovery mode to no avail. All I can get to is download mode.
Any ideas on what I should/can do?
any help will be greatly appreciated.
Rob
Aircraft123 said:
I realized after that that I never disabled the voodoo lag fix or deleted my user data.
Click to expand...
Click to collapse
Neither are necessary for Odin use.
ATT Captivate batch 1010
Click to expand...
Click to collapse
I think that you may need to use the Froyo Odin (JI6).
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
CM7
please help, i have the same problem, was flashing back to stock from a serendipit 5.12 so that i could get the 6.0 version... all went as planned until odin said "reset" which was my cue to unplug and that the process was complete.... i unplugged the phone and tried to reboot and now it does exactly as the first post described, at&t logo then black screen, then back to the at&t logo then black screen again... my computer doesnt recognize my phone none of the methods of getting to download screen will work... no matter how many times i pull the sd, sim, and batt, no matter the button combination i use or which order i use them in.... same result... i cant afford a new phone i need help, i will donate also... i knew this stuff was over my head, but "curiosity killed the cat" i guess...
I had the exact same problem. Try this method, it's the one that worked for me when all others failed... But remember to follow it EXACTLY.
1. Pull out the battery.
2. Hold Volume UP+DOWN (Don't let go of them until you see the download screen).
3. Stick in the USB (which is connected to the computer).
4. Put the battery back in.
If not, you might need to get a USB Jig.
That Froyo Odin link worked!
Thanks guys I flashed to Froyo and it worked!
I've since flashed clockwork recovery and gotten Serendipity 6.1
As far as getting into download mode I had to use one of the USB jigs.
I ordered one from the guy who does the rom reviews but you could make one as well.
On another note the new ROM seems to be discharging my battery really fast
Before I start investigating it as a problem I am going to charge it completely then let it discharge completely to calibrate it.
Thanks again guys
Rob
I just fixed mine last night, I had the exact same problem because of the exact same upgrade. What you need to do is get or make a usb jig. There's a couple resources around here for how to do it.
Here's a video showing how to make one:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
Once I got my phone into download mode, I used Darky's ROM Resurrection Edition ( http://forum.xda-developers.com/showthread.php?t=940671 ) to restore my phone. Just scroll down to where it says "Files Needed" and download the Captivate version. Once you have that downloaded, use the jig to put your phone into download mode and follow the directions in the Darky's video (jump to about 2:30 into the video). Once I had my phone booting, I used clockwork to install Serendipity 6.
Hope that helps you as much as it helped me!!
went to radio shack, got all the stuff to make a jig and i was able to get my phone into download mode! now to try darko...... thanks everyone!
odin doesnt reconize phone
which odin3 are you using? 1.7? or the one click to stock?
you mentioned you had the bootloop problem before, so you should be using odin 1.7 with 2.2 stock.
open odin
get phone into download mode with your nice jig
unplug jig and plug in computer
box in odin should turn yellow.
And make sure you have the correct drivers installed. CRUCIAL.
Multiupload links not working
I'm stuck in the same situation as the OP.
I've been trying to use the method mentioned in the quote below, but the multiupload links are not working for me. I've been trying for 2 days to get to these files.
Breakin' Ranh said:
**Another thing, read the whole thing before doing it! If you're not confident whatsoever about this process, don't do it**
1. Download the following:
I897UCJH2 Firmware
password: samsung-firmwares.com
http://www.multiupload.com/B5OFPPOJFZ
512 PIT
http://www.multiupload.com/I5WICSBFJ1
ODIN3
http://www.multiupload.com/DLS7TWUVPY
Click to expand...
Click to collapse
Here's a link to the thread for more clarification:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36I've
Would anyone happen to have these files and be willing to share them?
^
Have u tried the Odin or Heimdall One Clicks in the development stickied thread ??
Sent by XDA Premium App
Yep, tried the Odin one click - caught in a boot loop with the AT&T Logo. I have yet to try the Heimdall one.
UPDATE
Tried Odin and Heimdall One-Clicks - unsuccessful. I'm think I will need the stock Eclair firmware file with Odin and the pit file.
lllll Nova lllll said:
Yep, tried the Odin one click - caught in a boot loop with the AT&T Logo. I have yet to try the Heimdall one.
UPDATE
Tried Odin and Heimdall One-Clicks - unsuccessful. I'm think I will need the stock Eclair firmware file with Odin and the pit file.
Click to expand...
Click to collapse
You ever get this to work? - I'm in a similar situation. all flashes 'work' but get stuck at ATT on boot. Not sure Eclair is an option or not since mine is a refurbished phone that started on 2.2
ScruffMcG said:
You ever get this to work? - I'm in a similar situation. all flashes 'work' but get stuck at ATT on boot. Not sure Eclair is an option or not since mine is a refurbished phone that started on 2.2
Click to expand...
Click to collapse
If one-clicks aren't working, you might need to grab the full version of Heimdall or Odin and flash a full package. Some of the newer phone builds don't like one-clicks.
^ +1
See this thread...the original Stock i897ucKK4 thread... http://forum.xda-developers.com/showthread.php?p=19587108
Then see post #57 for the regular Odin to use and instructions on what to do with the firmware.
Sent from my SAMSUNG-SGH-I777 using xda premium
I'm on a warranty exchanged 1012 build Captivate. I initially decided to go ahead and flash a new ROM to it, and proceeded to do so using Odin 1-click like I had done so many times in the past with my old 1008 build Captivate. Odin hung for quite some time, and I feared the USB cable I was using was faulty to a certain degree. No biggie, just restart the process and all would be good.
That wasn't the case here though. It simply doesn't boot anymore. I believe it to be a soft brick as there is an image available on the screen. It's the wretched cellphone --- computer screen. I attempted to reboot into download mode like I had done using the VOL+/VOL- and USB insert method, but all that appeared was this symbol. I was simply trying to restore to stock 2.1, as this Captivate came with stock 2.2.
I've even built a JIG, a couple actually, using varying resistors. The first JIG I built before attempting the ODIN flash that killed my phone. Prior to flashing ODIN, the JIG appeared to work brilliantly. It put my phone into download mode about two seconds after contact. Now all it does is bring up that damn cellphone --- computer screen.
What is strange is that the phone, when plugged into the computer after I attempt to put it into download mode using my JIG(s), the computer will play that sound that it plays when it recognizes a USB device. In addition to that, if I plug it in when ODIN is open, ODIN recognizes the phone and displays a yellow block with "0:[COM11]" in it.
I went ahead and downloaded the necessary things from this thread:
http://forum.xda-developers.com/showpost.php?p=10056254&postcount=36
and began trying to flash to stock using his instructions. So far ODIN appears to be running, but is stuck at modem.bin.
Maybe its not making any progress at all, but I'd like to hope so. Does anyone know if the 1012 batch can get into download mode using a method outside of the normal key presses and JIGs? Any recommendations for me to revive this Captivate? I did enjoy the fact that it didn't shut down on me every 30 minutes. The GPS still sucked on it though. But I need to bring it back to life, just don't know what other options there are. As far as I know, if the screen presents you with an image of any sorts, its just a soft brick and CAN be recovered.
Can't use one click with your build number. You would need to use full odin. There are numerous articles here on how to do that.
mrhaley30705 said:
Can't use one click with your build number. You would need to use full odin. There are numerous articles here on how to do that.
Click to expand...
Click to collapse
Yeah, found out the hard way. I do wish there was a stickied post that broke down the build numbers and the various caveats of each build number, including tried and proven methods of restoring to stock and other things.
My situation was quite strange, as ODIN appeared to recognize the phone even though it only displayed the "cellphone --- computer" icon. I'm wondering if the failed flash screwed up the download mode graphic and replaced it with the "cellphone --- computer" graphic? Either way, it didn't "appear" to actually be in download mode, it was.
That screen only means that a flash was incomplete. Flashing anything even a modem successfully will get rid of that screen, granted your kernel/rom was broken so it wouldn't have booted properly but that screen would've went away, replaced by a bootloop. so to fix it completely to an up and running state an entire rom package is needed. Like you used.
Just informing you that, that screen isn't the **** your pants moment. that time comes when the phones does absolutely nothing, as long as there is ANYTHING you are 99% of the time ok. That 1% is when your usb port on the phone is broken, or your pc drivers just all of a sudden decide to extend their arms and give you the figner, or you try odin again with the same faulty connection that gave you the bad connection/incomplete flash and that time it hangs on the bootloaders and bricks it.
Odin recognizes my phone in all modes except completely off: booted, recovery, download and I just tested the phone...!...pc screen on purpose by yanking the chord during a kernel flash got that screen of coarse cause the flash was incomplete. But unless the phone is in download mode it doesn't initiate download protocol and odin will hang on setting up connection.
You can't really have a guide line for what works on what builds for any certainty because every phone of a certain build doesn't behave the same way.
I have 3 captivates I flash. 1, a 1010, and 2 are 1012s all of them have no issue whatsoever with odin one click. It's just the luck of the draw...
I recently had this EXACT issue. The way i fixed it was building a jig out of 3 100k 1/4w resistors and forcing my phone into download mode.
Studacris helped me out there!
if your still having issues, its http://forum.xda-developers.com/showthread.php?t=1079000
I also just went through this. I just had to keep trying. The jig is what saved me.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
So I was trying to go from serendipity 6.4 to 7...
I was following the directions on the serendipity site, got to the point where it was supposed to be flashing the new boot loader and gingerbread. Odin sat on "zImage" for about 15 minutes before i decided for some reason that it was frozen and that unplugging it and trying again might help...
now the only thing I can get from the phone is a black screen with red and green dots when i try to get to download mode.
any suggestions??
Elliot
zImage is the kernel. This should recoverable
Did it get passed boot.bin and sbl.bin? If so you've got the new boot loaders. vol down and power to get to DL mode. Since odin hung and was disconnected before completion the image for DL mode might not even be on the phone. Try that combo (or better yet a jig) then whatever screen it boots into hook it up to odin and try flashing just xcals gb kernel. If it's not in DL mode it will just hang on "setting up connection."
studacris said:
zImage is the kernel. This should recoverable
Did it get passed boot.bin and sbl.bin? If so you've got the new boot loaders. vol down and power to get to DL mode. Since odin hung and was disconnected before completion the image for DL mode might not even be on the phone. Try that combo (or better yet a jig) then whatever screen it boots into hook it up to odin and try flashing just xcals gb kernel. If it's not in DL mode it will just hang on "setting up connection."
Click to expand...
Click to collapse
Got it to what is now just a white fuzzy screen (not giving me the black with dots anymore) and the computer doesn't recognize im plugging anything in. about to head to radio shack to source a jig.
Assuming im not completely water-headed, there should be a screenshot of my odin attempt, for your viewing pleasure...
if thats the first fail, then the bootloaders were never flashed so try the old button combo... switch usb ports first of all no matter if you try the next peice of advice or not anytime odin fails you should swap usb ports(always making sure its on the back, no hubs or front ports)...open odin, hold volume buttons and plug in usb chord on your phone...
a jig is always a good idea... i made mine before i ever flashed anything so i knew i would have an out if things went sour.
studacris said:
if thats the first fail, then the bootloaders were never flashed so try the old button combo... switch usb ports first of all no matter if you try the next peice of advice or not anytime odin fails you should swap usb ports(always making sure its on the back, no hubs or front ports)...open odin, hold volume buttons and plug in usb chord on your phone...
a jig is always a good idea... i made mine before i ever flashed anything so i knew i would have an out if things went sour.
Click to expand...
Click to collapse
finally got it to download mode, but now im frozen at "param.lfs" after "firmware update start"...
Thank you so much for the prompt help studa, I really appreciate it
Hmmm...not your day huh? If it's frozen you have no choice but to disconnect. All the damage has been done. When you disconnect now you will most likely get the "clay" screen: phone....!.....pc and like I said before the download mode image might be missing. But this should still be recoverable
What version of odin is that? The earlier versions tend to freeze up more. go to this thread http://forum.xda-developers.com/showthread.php?t=979133 don't worry about the firmwares just at the bottom there is a few versions of odin. 1.7, 1.81 and 1.82 try one of those.
studacris said:
Hmmm...not your day huh? If it's frozen you have no choice but to disconnect. All the damage has been done. When you disconnect now you will most likely get the "clay" screen: phone....!.....pc and like I said before the download mode image might be missing. But this should still be recoverable
What version of odin is that? The earlier versions tend to freeze up more. go to this thread http://forum.xda-developers.com/showthread.php?t=979133 don't worry about the firmwares just at the bottom there is a few versions of odin. 1.7, 1.81 and 1.82 try one of those.
Click to expand...
Click to collapse
Fortunately, I am apparently allowed a few more tries... it keeps letting me go back to download mode after it inevitably freezes at either "param.lfs" or "zImage"...
I tried with 1.82, still no luck...
umm could be the usb chord...
ouch.... a usb cable.... but on the other hand, you are now my hero!
Thank you very much sir, donations ye shall receive
I rooted my cappy(cappy 1) and installed serendipity 6.4 on a clockwork kernel back in May for the first time based upon info I gathered here from all the experiences and advice. It went flawless. I odined back to stock and attempted to update the kernel to the one from the link on the serendipity 7 page and while it was doing the kernel flash it went into a boot loop that I apparently am not smart enough to recover from. Odin does see the phone for just a split second and starts but the phone restarts before it gets done. My wifes(cappy 2) came in the mail yesterday and she wanted freedom too so I rooted and tried to use a kernel I d/l from a site I recognized from everyones post and it said to use sgs kernel flash and I have had pretty much the same result in this phone too!! ??? whatsup?? I did it without fail the first time and now I am questioning myeslf. Neither will boot to recovery, neither will connect to pc via usb long enough to use odin. I am dumb about ADB. Clicked on the adb file and it flashes through really quick on my pc then closes. Tried to make the usb manual jumper with the resistors and I can't seem to have any luck with the technique. I ordered the jig for the usb connection for like 9.00 but I won't get it til next week. Any help would be appreciated...... I am at a total loss!!!
Are you using Odin from download mode? As long as you have a cappy with working button combos, start Odin (right click and run it as an administrator) without the phone plugged in. Pull the battery out, remove the SIM and external SD card if you have one, replace the battery and leave the phone off. With the phone off, hold both volume buttons and plug the usb cord in. The phone should turn itself on in download mode, at which point you can hit start in Odin.
If this is what you're already doing I'm not trying to talk down to you, I just couldn't tell from your post. If this is indeed what you are already doing, are you getting an error in Odin?
the three button was working on both before but now seems to no longer.... I can't for the life of me get to recovery or download mode.... I think I could revive both if I could just get that far. and had a good kernel file which I obviously am not getting or I am doing somthing way wrong. Neither are totally bricked... the try to come on but keep restarting themselves. BTW thanks for the help and I don't feel talked down to at all.... felling pretty silly/crappy about my abilities right now. Thought I had the whole root/kernel/rom thing figured out til now.....
as far as odin errors. my first phone would hook to odin and then lose the connection because the phone turned itself off. the second one will not eastablish a connection at all.... does that make sense??
I would shoot for download mode at this point. When you tried the resistors to build your own jig, was the phone off when you were trying to get it to work?
1whttcdreamer said:
as far as odin errors. my first phone would hook to odin and then lose the connection because the phone turned itself off. the second one will not eastablish a connection at all.... does that make sense??
Click to expand...
Click to collapse
If you're in download mode, your phone shouldn't turn itself off. What odin package are you using?
yes, phone was off and I had 4 resistors with a total value of just between 300K and 301K. I was in my opinion unsuccessful in touching the two pins correctly without the resistors touching. I may try to disect a usb cord tonight and solder my resistors to the black and green wires(think thats correct) and see if I have any better luck. To impatient to await the jig for 5 or so days. But at least i'll have it for later use. Then I guess go back stock and start over. but I gotta get D/L mode to work first. I think odin was version 3.1.7 I'm at work and don't recall exactly. I know I D/L'ed a odin console and a set of files to put in particular places as to direct odin what to use. It came as a complete D/L. I also have tried the one click odin files before(this is what I used the first time back in may) any and all help is greatly appreciated.
1whttcdreamer said:
yes, phone was off and I had 4 resistors with a total value of just between 300K and 301K. I was in my opinion unsuccessful in touching the two pins correctly without the resistors touching. I may try to disect a usb cord tonight and solder my resistors to the black and green wires(think thats correct) and see if I have any better luck. To impatient to await the jig for 5 or so days. But at least i'll have it for later use. Then I guess go back stock and start over. but I gotta get D/L mode to work first. I think odin was version 3.1.7 I'm at work and don't recall exactly. I know I D/L'ed a odin console and a set of files to put in particular places as to direct odin what to use. It came as a complete D/L. I also have tried the one click odin files before(this is what I used the first time back in may) any and all help is greatly appreciated.
Click to expand...
Click to collapse
I have never been successful in touching the pins without cutting apart a USB cord. With the cord, though, it's a piece of cake. You don't even have to solder them, just stick the plug in there and you can hold the resistors (as long as they're covered with something) to touch the right pins. I don't know that the color coding is consistent, but you can figure it out either with a multimeter or trial and error. I also think it's 3 resistors not 4, but your values are correct so that's probably what you were doing.
Once you get into DL mode, you have a couple of options:
1. Try Serendipity 7 again. I've done several installs from their instructions and they work perfectly, but there are a lot of steps and you need to be careful to hit them all in order (I've definitely ended up in your situation before because I thought I remembered what needed to do but missed something).
2. Flash a one click. You can find them all here:
http://forum.xda-developers.com/showthread.php?t=1300843
If you were going to go this route, what I would do is flash the one-click for KF1. This will give you Samsung gingerbread bootloaders which are both compatible with everything and will give you your button combos back for download and recovery modes. Once you flash this, you should only use bootloader-free packages and you will always have your button combos with no risk of a hard brick.
Once you have KF1, you can root it from here:
http://forum.xda-developers.com/showthread.php?t=1127249
then get CWM recovery, skip to step 13 in the S7 download instructions, and flash it in recovery.
Good luck!
Thanks Ever So Much!!
:cool Well long story short my jig worked. You were right, it was very easy to make. Soldered resistors to pins so now I have a working jig. My original phone is so totally fixed. Running rooted 2.3.3 Serendipity 7 with CWM. Thank you very much for the confidence building and advice on where to start and finish.
I have a Samsung Captivate which has been rooted and unlocked...it was running 2.3.5 uckk4
I believe I got a virus from downloading some app that was not on the market well long story short I tried to flash it back to a different version
I believe I put something in odin bootload that I wasnt suppose to it was an accident as you see I am a total noob at this then I use the 1 click unbrick now my phone keeps rebooting itself but i looked at the about phone which i get to for a few seconds before it reboots itself again and this is what it says
Firmware
2.3.3
Baseband
1879UCKF1
Kernel Version
1897UCKK414489
BUILD
gingerbreadUCKF1
I have tried a master reset since I could get it into debug just that it keeps looping and it worked in odin but not on my phone and this is what it generated
<?xml version="1.0" encoding="UTF-8" ?>
- <REFLASH>
- <UNIT>
<ESN>00000000000000 /0</ESN>
<TIMESTAMP>20120424002823</TIMESTAMP>
<RESULT>_20120424002823</RESULT>
<SOFTWARE_NAME>Downloader</SOFTWARE_NAME>
<SOFTWARE_VER>3.00</SOFTWARE_VER>
<OEM_NAME>SAMSUNG</OEM_NAME>
</UNIT>
</REFLASH>
PLEASE HELP ME....if you can get my phone operational again I WILL DONATE MONEY TO YOU!
I have tried EVERYTHING and searched FAR AND WIDE!!!! I almost forgot Odin does not display my device anymore...ie such as com4...I really have tried everything that's why I am willing to donate/ pay you if you can solve my problem....if odin recognizes my device then it gets stuck halfway through. As of today my computer recognizes my device but Odin does not!
I have read and tried everything here
http://forum.xda-developers.com/showthread.php?t=858765
and here
http://forum.xda-developers.com/showthread.php?t=731989
and alot of other things listed and not listed on this site
NEW IFO: now I'm stuck at ATT logo and can not get into download mode
This thread will selfdestruct in 5...4...3...2...1....
DANG IT wrong section? SORRY MODERATORS!!!! SORRY
Please dont delete please just move it please!!!!
oh goodness... No need for donation but all you need to do is download a stock package odin like kk4 which is the most recent. Flash in download mode. There a sticky at the top of the thread list with all the packages.
In the future post in the questions/help section.
diskjockee said:
DANG IT wrong section? SORRY MODERATORS!!!! SORRY
Click to expand...
Click to collapse
Ok I gave you the only warning in the PM. I have moved this thread. A word from the wise. Learn what you are doing before you do it. This is not something to be taken lightly. You could very easily mess something up beyond repair. Take a few hours to spend reading and researching.
ThisWasATriumph said:
oh goodness... No need for donation but all you need to do is download a stock package odin like kk4 which is the most recent. Flash in download mode. There a sticky at the top of the thread list with all the packages.
In the future post in the questions/help section.
Click to expand...
Click to collapse
I have tried that it doesnt work. thats was one of the 1st things I tried
try this
http://forum.xda-developers.com/showthread.php?t=1266172
Make sure you're using a usb port that is on the motherboard (back of computer). Before you plug in your phone to flash, set up Odin first. Put all the files you are going to flash in the right places. After Odin is fully set up, plug in the usb to the back of your computer, then to you phone. Make sure you are in download mode. If the usb still isn't working, try a different USB port that is on the back of the computer. Connecting the usb to the back of the pc is very important. Odin doesn't recognize my phone when it's plugged in the front, when the phone is in download mode. Only the back usb ports.
If Odin still doesn't recognize the phone, try a different USB cable. But do everything else the exact same way as I described.
Also make sure you fully setup Odin before you plug your phone in to the usb.
Sent from my Serendipity VII flashed Captivate using xda premium
Limitz Cash said:
Make sure you're using a usb port that is on the motherboard (back of computer). Before you plug in your phone to flash, set up Odin first. Put all the files you are going to flash in the right places. After Odin is fully set up, plug in the usb to the back of your computer, then to you phone. Make sure you are in download mode. If the usb still isn't working, try a different USB port that is on the back of the computer. Connecting the usb to the back of the pc is very important. Odin doesn't recognize my phone when it's plugged in the front, when the phone is in download mode. Only the back usb ports.
If Odin still doesn't recognize the phone, try a different USB cable. But do everything else the exact same way as I described.
Also make sure you fully setup Odin before you plug your phone in to the usb.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
I just tried that....it worked but now I'm stuck at the ATT logo
You probably have mismatch kernel and bootloader loader. Maybe you can try to wipe data / factory reset in recovery.
Sent from my Serendipity VII flashed Captivate using xda premium
If you continue to go into a bootloop then I recommend a USB jig for the galaxy s series. I had had that happen before, Nothing worked, couldnt get it into download mode, couldnt get into recovery, Until I got the USB jig, Fixed my problem right away, and I flashed back to stock. The USB jig is only 6 bucks on ebay. Ill link you if you are interested.
Limitz Cash said:
You probably have mismatch kernel and bootloader loader. Maybe you can try to wipe data / factory reset in recovery.
Sent from my Serendipity VII flashed Captivate using xda premium
Click to expand...
Click to collapse
I know you're trying to be helpful, but there is no such thing as a kernel/bootloader mismatch...
b-eock said:
I know you're trying to be helpful, but there is no such thing as a kernel/bootloader mismatch...
Click to expand...
Click to collapse
Are you sure? Becuz I tried to flash an overclock kernel on my rom, and kept getting a bootloop. Then after flashing a few different kernels, the kernel that came with my rom didn't even work. I had to go back to stock and reflash my rom.
Idk, maybe it was just me then. I apologize. thank you for correcting me, that's how we learn what's right, and what's wrong.
Sent from my Serendipity VII flashed Captivate using xda premium
noob advice
I'm a noob, so this comment might just serve to show how little I know, but whenever I find myself in a bootloop situation, I've noticed that the problem starts with the initial attempt of installing a rom via a kernel with an older version of CWM. During the post-install boot sequence, I'll see the AT&T splash screen, a CWM screen with script running, and then a reboot. Usually, accessing the CWM (now on a higher version) and reinstalling the rom will get it working. Not quite kernel / bootloader mismatch, but close.
whisky23 said:
I'm a noob, so this comment might just serve to show how little I know, but whenever I find myself in a bootloop situation, I've noticed that the problem starts with the initial attempt of installing a rom via a kernel with an older version of CWM. During the post-install boot sequence, I'll see the AT&T splash screen, a CWM screen with script running, and then a reboot. Usually, accessing the CWM (now on a higher version) and reinstalling the rom will get it working. Not quite kernel / bootloader mismatch, but close.
Click to expand...
Click to collapse
Ohh ok. That might have been my problem before. Thank you.
Sent from my Serendipity VII flashed Captivate using xda premium
Try this.
Buy a jig. Either off of Ebay or mobiletechvideos.com
That week get you into download mode.
Then find the HEIMDALL flasher for a build. (my favorite was the one click for saurom Kk4)
Install heimdall drivers, and flash. Boom. Functioning phone.