Database Develop

** [GUIDE] FIX AND RESCUE YOUR VIBRICK + ODIN SUPPORT! N00b Friendly **

Fixing so-called "Bricks"/Odin Errors
This guide is open to contribution/editing/correcting
I DO REALIZE THAT MOST OF THESE LINKS ARE BROKEN, PLEASE SCAN THE THREAD TO FIND UPDATED LINK. I'M NOT VERY ACTIVE ANYMORE, SORRY!
-----------------------------------------------------------------------------------------------------
BOOT CYCLE
This is where you get the annoying Samsung Screen/Galaxy S screen.
DOWNLOAD REQUIRED (CREDITS TO Woodrube):
JFD ODIN Images from Samsung (PDA)
Stock JFD Image
512 PIT File (PIT Extract first!)
Stock 512Pit
ODIN
Odin3_v1.0.exe.zip
Click to expand...
Click to collapse
1. Get into Download Mode (WITH THE PHONE PLUGGED IN) by following the steps below
*Turn off the phone until you get to the charging battery screen (keep in mind, your phone is currently PLUGGED IN)
*Press volume up and down, and power all at once.
*As soon as the screen turns black, release your power button.
2. Unplug phone from USB
3. Open Odin (in Administrator if you're running W7 or Vista), try one of the ones I attached to this post, at least one of them is bound to work, some don't work for me, but works for others, some doesn't work for others, but works for me, whatever floats your boat
4. Load in the files into Odin that you have downloaded from above Just load in the files corresponding to the text field.
DO NOT CHECK REPARTITION.
5. Plug in your phone with the DL mode
6. Click start and wait for the magic
-----------------------------------------------------------------------------------------------------
NO-BOOT PHONES
This is where your phone does NOT turn on, no combo of buttons works and power button does nothing.
DO THIS ONLY WHEN YOU PLUG IN YOUR PHONE AND NOTHING SHOWS UP ON THE SCREEN!!! If else, follow the steps from above.
This method is basically same as above, EXCEPT the way you get into Download Mode as your phone is HARD BROKEN.
1. Download all the files required in the "BOOT CYCLE" section of this post.
2. Remove everything from your phone (SD card, sim, battery).
3. Plug your phone into your computer WITHOUT the battery, as you have already taken it out in the last step.
4. Press and HOLD vol. up and vol. down.
5. As you are HOLDING these buttons, reattach your battery.
6. You should be in Download Mode.
7. Unplug phone from USB
8. Follow steps 4-8 from the "BOOT CYCLE" section.
Troubleshooting:
-Odin stuck at some random process?
*Switch to another odin
*Make sure you did NOT check repartition, if you did, just repeat all the steps over again, except for the downloading parts, obviously.
-Phone not responsive?
*Try "NO-BOOT PHONES"section of this guide
-Phone stuck at Galaxy S logo screen?
*Put it in to DL mode, and run Odin again, it's just a bad install.
-All three ODIN is nonfunctional, stuck or giving "FAILED" errors?
*DO NOT CLOSE ODIN ONCE IT HAS FAILED!
*Unplug your phone
*Replug in your phone, get it into DL mode
* Unplug once it is in DL mode
*Replug and ODIN should recognize your phone
*Leave all the settings the same, then click "Start" again.
-Cannot get into download mode using the method I listed? Use the method(s) below:
Soldering Method
More methods coming soon
-----------------------------------------------------------------------------------------------------
I know how much of a pain posting in the Q/A section can be and the wait time is pretty bad, so if you need help regarding UNBRICKING and ONLY UNBRICKING feel free to post in here.
Hope you enjoy, this is my first guide, please don't flame. Any comments or suggestion is suggest, or if you have your own method I'll also post it
POST YOUR RESULTS!
-Steven
The only forums this guide should be posted on is XDA, DZ, and PHANDROID under the username DRAIKZ and EXPLOSIVE. If it helped you, feel free to donate a coke or two!
​

Nice Guide! One thing I noticed is that the color is overdone and instead of helping with reading it has the opposite effect. Made everything look semi-messy and crowded.

good guide..
one question though, the PIT file is the one for the Tmobile JFD file. would that affect any unlocked vibrant? I mean, would it lock the phone back to Tmo??
thanks for sharing,
Cheers

I thought there's no fix to a phone which is really BRICKED? oh well, everything's possible at this time.

Please be more descriptive in your terms of "brick(ed)". The term bricked is meant that your phone isb rendered COMPLETELY & UTTERLY USELESS, FOREVER! The phone will never get used again... Hence.... Brick!?
I like the guide just think it would better off with more descriptive details of what caused the phone to boot loop or not boot.

Ok let me fix up the terms when I get home. I don't think you can ever make the vibrant utterly useless haha. Android phones are nearly impossible to brick
Sent from my SGH-T959 using XDA App

angel6677 said:
good guide..
one question though, the PIT file is the one for the Tmobile JFD file. would that affect any unlocked vibrant? I mean, would it lock the phone back to Tmo??
thanks for sharing,
Cheers
Click to expand...
Click to collapse
I'm not too sure as I do not have an unlocked phone myself and was wrong the same thing a few days back.
Sent from my SGH-T959 using XDA App

Is there a fix for the brick where the phone does not turn on at all amd does not even respond to the usb in the phone like for example plugging in the phone a wall charger and not even a grey battery or a little circle symbol?
Sent from my SGH-T959 using XDA App

Yeah, read the info under the "HARD BRICK" section Good luck, it should work as that also happened to me, I had it fixed with the method I listed up there.
If you need help or some questions answered during the process, I'll be online for another hour or so, or just PM me

OP. Can you add the soldering option as well? Would be good to have it in here. Added this Guide to the WIKI.

swehes said:
OP. Can you add the soldering option as well? Would be good to have it in here. Added this Guide to the WIKI.
Click to expand...
Click to collapse
Will do and thanks for the add
Now off to find the soldering guide x]

what do you do when you use odin and it STILL boots back to the samsung screen??

If the black screen doesn't change after like 15 minutes, then just do the whole process all over again. It could just mean a bad install
Even programs messes up sometimes
Goodluck!

Remember, please post your results so I can see how I can improve this guide!

So, i think i have actualy made a brick. I was running macnut r12/a13 kernal for about a week and had some issues with the overclock so i figured i would just flash aver itself as that has fixed a few issues in the past. booted into clockwork, flashed the rom, no worries. Hit reboot system and it hung at the vibrant/i9k boot screen. At this point i was still not worried. Here is where it gets fun. My Phone will now not boot into recovery, i have been trying now for about 4 hours. I can boot into download mode, but i can not get odin to see my phone. On the same PC, odin sees other vibrants, just not mine. If i turn on the phone it just boot loops at the vibrant/i9k screen. My pc makes the usb plug/unplug noise as it boot loops turning on and off with the vibrant/i9k screen telling me that the drivers could not be installed. If i plug my gf's vibrant in, i have no issues and odin gives me a com port. Any suggestions?

THANKS dude only if if you posted this before when my vibrant was soft bricked... I sent it back I didn't know what to do hehe!
Also a question... if I do this.. will it remove root and everything also does my phone HAVE to be soft/hard bricked to use these methods because I might want to just use the soft brick Odin thing when I want to get back to normal without being soft bricked...
Sent from my SGH-T959 using XDA App

@ Adam, have you tried installing the drivers manually? If not, then I don't know what to say =/ But I'm SURE people around here can offer some help
@Rider, You're welcome, and yes it does remove everything, and yes it does work even when you're not stuck in bootloops

draikz said:
@ Adam, have you tried installing the drivers manually? If not, then I don't know what to say =/ But I'm SURE people around here can offer some help
thanks for your reply
If odin recognizes one vibrant( the working one, my gf's) and not the other(my bootlooping) do you still think its a driver issue.
Macnut is a amalgam of almost all the galaxy s's. when my phone booted it would startsaying vibrant, then flash i9k. i did install kies thinking it would have some drivers for the i9k. I will try monkeying with the drivers a bit and let you know.
Click to expand...
Click to collapse

Ok, try playing around with the USB cable, trying different USB ports, too.

No problem, remember to post your results once you try it

[Q] Pretty sure I bricked.

So the story goes I installed Assonance on my Captivate from Official 2.2. Started having problems with the phone being stuck in Landscape mode. This problem followed when I installed Firefly. So I decided to try to go back to JF6 and clear everything. Couldn't get into download mode so downloaded a CMW flashable zip of JH7 and after installing the phone just sits at the AT&T World Phone screen. Can't get into Download mode with volume down + power or volume up down + usb. Need advice to try to get phone fixed/replaced, i'm stuck using a BlackBerry Bold. Any help please?

Google usb jig
CM7

Figured
Yeah that's what I figured. The only thing I'm curious about is the landscape mode issue following me around on different ROMS. After I hopefully unbrick the phone do you think it would be worth taking it to ATT?

Go to radioshack, 99 cents, use the video below for reference. You need 3 100k OHM resistors, and they run .99 cents for 5 of them. Use that to kick it into Download Mode and reflash. As for returning it to AT&T, if the orientation problem continues, I would if this doesn't fix anything.
http://www.youtube.com/watch?v=D0aoabVtPJ8

What Kernel did you flash before everything went haywire? This is a classic sign of an i9000 kernel being flashed to a Captivate.
Forget download mode for the moment, can you get back into recovery?

It's true. But, theres no reason the kernel wouldn't flash over during CWM. Not to mention, if that were the case it would also almost certainly display other i9000 kernel issues, like external SD mounting and headphone logic. I think something else is the culprit here.

geokhentix said:
It's true. But, theres no reason the kernel wouldn't flash over during CWM. Not to mention, if that were the case it would also almost certainly display other i9000 kernel issues, like external SD mounting and headphone logic. I think something else is the culprit here.
Click to expand...
Click to collapse
Sounds like lagfix present in Firefly was not disabled before flashing to stock, hence an ext4/jfs file conflict. OP, please let me know if you can reboot to recovery.

clemmie said:
Sounds like lagfix present in Firefly was not disabled before flashing to stock, hence an ext4/jfs file conflict. OP, please let me know if you can reboot to recovery.
Click to expand...
Click to collapse
hmmmn I agree. too many bricked phones not disabling lagfix and clock default values in their kernel when flashing back to stock. seems many forgot that procedure. every dev always states here to disable lagfix when flashing new rom and set back default clock values in current kernel. the very first step neglected PITA to troubleshoot.

Before you go and buy anything, did you try this method (sorry, if you said you did)? It always works for me, especially at the "Phone--!--Computer" screen.
FROM: How to unbrick the totally bricked captivate. [Click the > after "Originally Posted by thekurrgan" for the full source.]
thekurrgan said:
So far this has been the only sure fire method I've found to 100% get around any brick situation regardless of firmware, etc. This only works for the captivate, not any other galaxy s variant.
Situations: phone-!-Computer / no download mode
Black Screen / RST_STATUS 0x0
Procedure:
1. Remove the battery, external SD card and SIM card.
2. Wait 10 seconds.
3. Open odin3
4. Connect usb cable.
5. Hold volume up + volume down + Power.
6. Insert battery.
7. Release POWER BUTTON ONLY.
Click to expand...
Click to collapse

If he was using odin one click it repartitions automatically. If full version as long as repartition is clicked odin gets rid of the lag fix.
My point is that as long as repartition is enabled the lag fix is not his issue
CM7

mcord11758 said:
If he was using odin one click it repartitions automatically. If full version as long as repartition is clicked odin gets rid of the lag fix.
My point is that as long as repartition is enabled the lag fix is not his issue
CM7
Click to expand...
Click to collapse
It says nowhere in the OP that he used one click; as a matter of fact:
jonp92 said:
Couldn't get into download mode so downloaded a CMW flashable zip of JH7 and after installing the phone just sits at the AT&T World Phone screen.
Click to expand...
Click to collapse
I've seen this many many times, and it is usually a result of a non-disabled lagfix or OC kernel. I've been down this road with a few people. He may be trying to use one-click now, but without being able to get into DL mode he's stuck. I'm trying to help him get into DL mode, as are other posters. Let's just focus on getting him to DL mode.

buy this:
http://cgi.ebay.com/ws/eBayISAPI.dl...69781&ssPageName=STRK:MESELX:IT#ht_623wt_1139

[Q] Captivate Soft Brick - Need a rooted Odin solution.

Hi
My brother (a no-geek) has a captivate, and lives in a different city (I donot have physical access to the phone). He visited me few weeks ago and I installed CM-7 on his phone, i know my bad. Some of his videos were not working, so i asked him to update to the latest CM-7 build. He download the build, saved it on int sd_card and used ClockWork Recovery to install the selected ROM. Upon reboot it entered in never-ending splash screen. I found couple of odin ROMs, and posted him link, we tried to flash them, but no good.
Status --
The COM ports are detected, but the process at times halts at <SET PARTITION> at times at <SET UP>... at times all thread completed successful would show up as soon as hitting START.
I dont have a captivate, can someone please suggest a sure shot solution and post me a link for ODIN, with a root rom. I am using Team Whiskey on my Vibrant, and I prefer stable modified ROM because of its features and power.
I can explain him the process on skype using desktop sharing, but the ROM should be good. Thankyou very much in advance.

if he can access recovery, try wiping everything thru recovery then start again

Phone is in Soft Brick state.
Phone is in Soft Brick state. So i cannot boot into the phone and go to CW recovery.

What he needs is just a stable usb connection that's how he got to this point, bad communication between the phone and computer. On cm7 I beleive you need the nexus s drivers installed. Also make sure it's plugged into a usb port that's attached directly to the motherboard (back of pc, port 1 on laptop)

@studacris
I think the drivers are already installed good. The connection is also good, as i can the COM port detection in the ODIN, with one of the boxes changing its colour from NO-COLOUR to YELLOW-COLOUR.
I think the ROM builds are not good. They go action-less during flashing, actually nothing (progress bar) comes on phone, it keeps showing the Downloading screen, endlessly. Odin usually is stuck at at <SET PARTITION> at times at <SET UP>...
Can someone post a link for a test one click odin. Well i would prefer one click.

You did try DG's JF6 one click, thats the only one I use, how are you establishing dowload mode on the phone or are you even doing this.

REMY4223 said:
I would suggest to Odin back to stock then update to Froyo via Kies.
Click to expand...
Click to collapse
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament

Ragin Caucasian said:
if you could do all that, why would you need to send back for a new phone ? If you could do any of that, the OP wouldn't be in a non-functioning predicament
Click to expand...
Click to collapse
+1 If you read the OP the problem is he can't flash back to stock he is having problems flashing anything period, @ the OP correct me if I'm wrong but I have a strong hunch that you are leaving out some pretty crucial steps, I have a feeling that you are not putting the phone into download mode, I also believe that you are gonna need to make a jig and pay a visit to your brother to help him out especially if its bricked the same way mine just was flashing with cm7 roms. But if you are getting a com port to show without having to put in download mode then you are farther along in the boot process. If this is the case you may be able to adb into recovery do a full wipe excluding /boot and reflash. Will the PC recognize the phone with it in its current boot locked state? If so then recovering should be somewhat of a breeze.
http://forum.xda-developers.com/showthread.php?t=829392 read this post it may help otherwise there are tons others

- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.

viveksharma2108 said:
- I am getting to downloading mode by
--- pressing the "vol +" and "vol -" buttons and then connecting the usb cable to the computer.
--- then removing the cable, after the phone enters the download mode. Then, start the odin and connect the phone through usb cable again. The odin detects the phone on one of the COM port.
- I havent tired wiping the phone through recovery. But i need to get to recovery first. I dont know in a soft brick state if i can get into recovery.
- regarding getting back to 2.1... i would like to flash to the latest version. Kies update is not an option for me, as i not in US.
This phone was purchased from craiglist, i used one click root method to root it and the same script an option to get the unlock codes. After that i experimented a lot on the phone with various scripts. Last i was using congnition on it. Then saw CM7, i liked it on my vibrant, so i flashed it on my captivate (which i got for my brother). Now i have to get back to some stable modified ROM... I am thinking about trying Srendipity or cog ROM... but before than i have to install a rooted stock ROM.
That is the story and issue... but thanks a lot for help. Any more suggestions.
Click to expand...
Click to collapse
Try putting the phone into download mode after you open Odin. Which version of Odin is this? Also, installing the nightly build of CM7 again often fixes the boot loop on the newer builds. I would try that if you can get to recovery.
Sent from my SGH-I897 using XDA Premium App

[Q] HELP PLEASE Bootloop problem

I was trying to install the Teamhacksung's ICS for Captivate but when i was trying to select the rom, it gave me the status 7 problem. So then i found the Q&A Post about the rom, in which it said that if i had that status 7 problem i should install a kernel that was linked there. So i download it, and as i read on another post, i flashed the kernel the same way I would do with any ROM. The problem came when, once it had finished, I rebooted the phone, and then, the initial screen which says GALAXY S and SAMSUNG below, then a screen that says GALAXY S and below Cyanogen Mod, and finally a quick screen that looks as if the clockwork recovery mod is doing something( impossible to read), and then it takes me to the initial screeen and it repeats over and over. Someone please please help me, I can't get into the recovery mode with the three button mode aswell, Help!!!

Can you get to download mode? If so, you can flash back to a stock rom and try again.
You may also want to check the items in the "Captivate connection issues" thread in my signature.

No, I can't get to download mode, I can't even get into the home screen, I only see the first screens that enter in loop, and that is as far as I get.
EDIT: Yes! At least i made it into the download mode thanks to your post. What's next ?

Look in the development section for the sticky referring to Odin and Heimdall one-clicks. Grab one of those (preferably a bootloader-free version) that has the same setup as you had before you flashed ICS (in other words, flash a Froyo one if you had froyo, Gingerbread if you had gingerbread).
That should put you back in a clean state where you can start again.
(You can also grab the Heimdall UCKH3 one in my signature if you were on Gingerbread - one less search step.)

Thanks for answering. Just a few things. First, the download link of the Heimdall UCKH3 on your signature is broken, but i found on this thread http://forum.xda-developers.com/showthread.php?t=1348392 the onelink.jar file. That's what you meant when you said to grab a 'Heimdall one-click' ? Also, I have entered download mode and it shows the android digging up. But now that i have to open the Heimdall before connecting the phone, should i pull off the battery to exit this screen, open the oneclick and then connect the phone to enter the download mode ?

Thanks for catching that - guess it went down with the whole Megaupload thing.
I would grab this one. It's Odin-based, but should do the same thing, and it's Captivate-specific.
I wouldn't get out of download mode just yet. Unhook your phone from the computer, start the one-click, and reconnect it. With luck, you should be able to flash. If not, then do your battery pull / restart to download and try again.

Thanks for the link. I've downloaded it, unhooked the phone(the download screen didn't changed), started the one click and reconeccted it. A message appeared that said:
ID:0/006 Added!
Then I touched start button, and three more messages showed,
Odin v.3 engine(ID:6), File Analysis, Setup Connection.. and is still there. Have I done it right ? Do you know how much time is estimated to take, or I should have done something else ? I am asking all these questions, because, as you may see, i don't understand most things. Thank you

Thank you so much jmtheiss it worked fine now i'm running the stock version.

Glad to hear it worked for you.

I was wondering if you could help me with a similar problem. My Cappy is operating just fine on a ROM I flashed about 6 months ago, but I am not wanting to flash back to Stock. When I plug my cappy in to the computer (I'm running Ubuntu 11.10), the computer recognizes it and I'm able to transfer files just fine; however when I enter the cappy into Download mode, the computer will not recognize it anymore. Any help is much appreciated.

Are your libusb drivers installed, and are you using heimdall?

[Q] OH NO! Another noob bootloop thread :p

Hello fellow captivate users, I need some help here!
I've just brought a 'bricked' at&t captivate off of trademe here in NZ (it's like ebay) and I'm having a little trouble recovering it.
With the help of a homemade JIG I was able to force DOWNLOAD mode, and have tried using ODIN to flash various all-in-one firmwares. However, it seems no matter which I use the phone always ends up in some sort of bootloop, either with just the at&t logo looping, the at&t plus either a samsung s i897 or i9000 screen looping or just the samsung screen looping (depending on one-click used).
So far I've tried these oneclicks-
I897UCJF6 with bootloaders
I897UCKK4 with bootloaders
Plus various other packages that use odin to flash the different parts of the filesystem etc...
I've also used different ports and cables on the computer (although download mode and connection to pc do not SEEM to be a problem)
I'm sure I'm missing something here, but I'm also sure I'm following each firmwares instructions to the 'T'!
I've flashed other android devices in the past with no issues, is there something the samsung requires that I'm missing or messing up? (It's probably the latter )
Any help would be greatly appreciated
Cheers XDA Gurus

I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with. Apex even has a Heimdall package that will put cwm on your computer.

ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
odin likes to lock up. if odin locks up durring bootloaders... well its the only REAL way to permanently brick a cappy... until you unbrick it..
do you need the jig? is the button combo not working? both volume + plug in usb to PC
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/showthread.php?t=1386924
heimdall is like odin but open source (more features and more stable), but it uses different drivers that it will install itself, but that usb port will be your heimdall port, all others will work with odin, unless you install the heimdall drivers on other ports too.
or...
try flashing a custom rom using the guide in my sig. it will quickly give you a custom kernel with cwm recovery, you can mount usb to pc from recovery menu, then transfer a rom to flash.
give that a shot...

Wow, quick replies guys, thanks.
I have had success using Heimdall when stuck in a boot loop before. It will change the drivers on your computer so you will have to deal with that (Odin won't recognize them) but this can be dealt with
Click to expand...
Click to collapse
I should have mentioned - I did try one Heimdall oneclick, but had same bootloop result.
ok well you HAVE gingerbread bootloaders... STOP FLASHING BOOTLOADERS. gingerbread bootloaders are good with any captivate rom. no need to flash again.
Click to expand...
Click to collapse
I figured that, just wanted to make sure the bootloaders weren't at fault - I'll make sure I use the non-bootloader oneclicks from now on.
do you need the jig? is the button combo not working? both volume + plug in usb to PC
Click to expand...
Click to collapse
Originally the jig was needed (the phone arrived bootlooping at&t with no button combos working). But since my original stock flash (I897UCJF6) this hasn't been needed.
if odin is seeing the phone (turning yellow) and "PASS" ing the flash(turning green) then you dont have usb port or cable problems.
Click to expand...
Click to collapse
Cool, so cable/ports are ok
Code:
but try this KK4 gingerbread heimdall package, with re-partitioning.
http://forum.xda-developers.com/show....php?t=1386924
Thanks, I'll give this a shot first. If no go I'll try using the cwm method from your sig. How does the sd need to be formated/partitioned for captivate - guess I'll just use a single fat32 parition to start.
To sum up, now that I've got stock GB bootloaders, I'll quit using oneclicks with bl's included. USB cables and ports are fine. I'll try the KK4 heimdall package that was linked, if still no go I'll flash a custom rom and use clockwork to install changes from then on.
Thanks again

I must be messing up - having trouble getting into recovery.
Here's what I did;
The links here: http://forum.xda-developers.com/showthread.php?t=1386924 are dead, so I went straight to method 2.
Downloaded speedmod kernel from here: http://forum.xda-developers.com/attachment.php?attachmentid=566807&d=1302623831
Used odin to flash (kernel selected under pda), this seems to have worked as I now have the samsung i897 screen show up after the at&t. BUT when I try to enter recovery via three button method I get nothing.
How long should I hold the 3 buttons down for? (How many bootloops?)
Should I let go of them at th at&t splash, the samsung s i897 splash or at the blank screen?
All of this was done after my last odin oneclick attempt (which was a KK4, re-part, bootloaders included flash from here on xda)
**edit
I've also tried using the heimdall package (i897-Speedmod-K13E-GBbootloaders-One-Click.jar) to install the kernel with no luck getting into recovery.

For button combo to get into recovery--release when u see 1st att screen.
Or
Have u tried Adb (Android Debug Bridge) to get into recovery ??
Sent by XDA Premium App

cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...

Yep, no adb on bootloop. Still no joy getting into recovery - it's a stubborn wee device! Gona try some different kernels today.
Am I right that there's no kernels available that will boot straight to cwm without button combos? (I'm thinking my power button may be iffy coz I have no problems getting into download mode)
Sent from my FUSIONideos using XDA

TRusselo said:
cant adb... bootlooping.. or ... does adb work durring boot? no .. right? never tried, cant now...
Click to expand...
Click to collapse
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Its pretty handy, you can push a framework-res you are messing with without having to make a zip, and if you broke it and it loops, you can push the original back, reboot and you're back in business

*removed double post

studacris said:
I've used adb during a loop plenty of times..on a couple devices.
My captivate, and my gf incredible.
Click to expand...
Click to collapse
How exactly? adb doesn't see the captivate because it's only connected for a second before it reboots,adb just tells me device not found or something to that affect.

You have to hit enter at the Right moment, it takes practice

Lol, lucky I've got plenty of patience then!
Strangely if I 1-click back to stock eclair (maybe froyo not in front of PC at mo, and I know I shouldn't be messing with bootloaders but ehhh) I am able to get into what I assume is samsungs recovery mode, but I have to hold button combo for maybe 3 or 4 bootloops. Sticky button(s) maybe?
Am I able to use adb from there to get an update.zip to internal sdcard?
How come if the Odin oneclick seems to work I still end up in bootloops? Something not doing its job right? Partitions not working or kernel or system or bootloaders? Looking through adb shell the system looks intact-but still looping away!
Also am I right in assuming that because it gets to download mode it is eventually fixable?
Sent from my FUSIONideos using XDA

Just an update - from the stock eclair recovery I'm unable to push to the internal SD, get a permission error. Unable to remount that either, comes back with a fairly generic remount not allowed error.
Looking through the forums most people seem to have trouble getting into download mode rather than recovery - doesn't seem any cwm kernel will let me into recovery. Phone is model 1007 if that helps.
Is it possible the internal SD is stuffed? Can't see why all oneclicks end in loop - shouldn't they be overwriting the entire internals?
Gona format a microSD from my tablet and see if that will help, should I leave it fat or use Ubuntu to ext4 it for stock Samsung?
Sent from my FUSIONideos using XDA

If a Internal or External SD card is fried, then no amount of formatting and flashing will help it.

Is there any way to tell if the internal is cooked though? Odin and heimdall both seem happy to flash to the phone, but I've yet to find a package that doesn't end with a bootloop.
There must be some hardware issue though, seems unusual that aside from stock eclair I'm unable to enter recovery. According to the guy I got it from, it simply died while he attempted to update firmware, but the fact that I'm able to flash from download mode would suggest that's not the issue.
I guess there's no way to tell if hardware is cooked other than to send to samsung, is it common for people to get stuck with bootloops from stock flashes? Should I give up and see what samsung would charge to fix (if they will/can) or keep attempting different oneclicks (without bootloaders of course )

How about a non one click?
I've heard some peoples phones bootloop with one clicks, but work fine with .tar packages and the full Odin flashing utility.

Worth a shot. Got to wait a few days for my net to reset though, hit my limit for the month and it's painfully slooow - damn NZ's overpriced adsl!
Sent from my FUSIONideos using XDA

Still not working unfortunately. Using packages with odin3 gets me the same results, bootloops and no access to recovery. I also downloaded the aio captivate package and used the heimdall that came with that to flash stock eclair, which ended with a kernel panic screen - though am able to access recovery. Recovery doesn't see my fat32 microsd though so unable to flash from there.
I don't know my adb shell commands well enough to try and mount or format internal sd and I get permission denied when trying to push update.zip to internal sd via adb.
Unless anyone has any other ideas I'm stumped for now.

When my internal sd got messed up from cognadaian bacon (ooooold dg ROM) i reformated it with my computer and it then let me Load another rom on it... don't remeber if fat 32 or not ....mabey someone else might know
Edit: mabey designgears remembers what fix it when cognadian bacon porked it
Sent from my SGH-I897 using xda premium