Related
DID I JUST BRICK MY PHONE??
tried flashing the i9000 rom... got messed up sometime after flashing csc and pda.... now i can boot to recovery menu and get odin to recognize but im getting an error
copy_multi_carrier from: ATT
multicsc : can not acces to /system/csc/ATT/system/
copy_common_data
then it stalls.. my power button doesnt work to reboot system now...
Even though odin recognizes i hit start and nothing happens..
can anyone help.. i will donate and make it worth your time..
No you didn't brick your phone, you need to follow the I9000 guide in the stickied threads. You need to load a Captivate kernel before fully rebooting your phone.
First off get your phone back into download mode. Pull battery and usb cable, restart Odin, then follow this method to get you into download mode, put in battery, hold down both volume buttons, keep holding them and plug in the USB cable.
First when you flash a I9000 rom make sure you uncheck autoreboot on Odin.
When this done when you flash the Rom it will say Restet in Odin. At that time pull your battery and USB cable.
Restart Odin and load the Captivate kernel. Put you battery in, hold both volume buttons, keep them held and plug in the USB cable, should go into download mode. Start Odin, and it should be fine to let it autoreboot.
I missed something it will be in the stickied thread.
Sent from my SAMSUNG-SGH-I897 using XDA App
can you clear something up is Android System Recovery the same as download mode??
ok this thread can be deleted.. im a noob.. kjpdx throw me a link to donate.. i figured it out by myself but atleast you replied..
Two different modes. Download mode shows an Android holding a shovel and Recovery mode is where you would install update.zips.
Needs to be in Download mode when installing roms and kernels with Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dont worry about it, glad i could help.
Sent from my SAMSUNG-SGH-I897 using XDA App
Hi:
I have the same problem of my Galaxy S. It is stuck in this screen saying
copy_multi_carrier from: ATT
multicsc : can not access to /system/csc/ATT/system/
etc. etc.
I boot it to the download mode as instruction, but the Kies always shows connecting device, and it never gets connected. The Odin shows no com port or device for me to load the firmware. Can anyone help? Any help will be appreciated.
uehsgerg said:
Hi:
I have the same problem of my Galaxy S. It is stuck in this screen saying
copy_multi_carrier from: ATT
multicsc : can not access to /system/csc/ATT/system/
etc. etc.
I boot it to the download mode as instruction, but the Kies always shows connecting device, and it never gets connected. The Odin shows no com port or device for me to load the firmware. Can anyone help? Any help will be appreciated.
Click to expand...
Click to collapse
You can't have Kies and Odin running at the same time =P
^lol that solved my problem too! thanks!
Zilch25 said:
You can't have Kies and Odin running at the same time =P
Click to expand...
Click to collapse
Will try it later. Thanks
It is fixed. Thank you for the help. I just need to lauch Odin first prior to plug-in my phone. Now, I don't have bricked Galaxy anymore. Thanks
KJPDX said:
No you didn't brick your phone, you need to follow the I9000 guide in the stickied threads. You need to load a Captivate kernel before fully rebooting your phone.
First off get your phone back into download mode. Pull battery and usb cable, restart Odin, then follow this method to get you into download mode, put in battery, hold down both volume buttons, keep holding them and plug in the USB cable.
First when you flash a I9000 rom make sure you uncheck autoreboot on Odin.
When this done when you flash the Rom it will say Restet in Odin. At that time pull your battery and USB cable.
Restart Odin and load the Captivate kernel. Put you battery in, hold both volume buttons, keep them held and plug in the USB cable, should go into download mode. Start Odin, and it should be fine to let it autoreboot.
I missed something it will be in the stickied thread.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Thanks! I couldn't get download mode and this is the only thread online to help. I received this error when trying to install the voodoo lagfix while running cognition 2.2 beta 7. (for some reason, my cognition did not have the lagfix built in)
cliffgardner said:
Thanks! I couldn't get download mode and this is the only thread online to help. I received this error when trying to install the voodoo lagfix while running cognition 2.2 beta 7. (for some reason, my cognition did not have the lagfix built in)
Click to expand...
Click to collapse
That reason is that voodoo doesn't work with 2.2
For the sake of your wallet, I would read the threads more carefully before flashing new roms if I were you. I'm not trying to be a ****, but this issue was addressed many times in the cognition thread. I'm all for learning from others on this forum after they make the mistakes
I've read and searched as much as I can but haven't seen anyone else have this problem.
I flashed Froyo XWJP6 using Kies and changing the registry entries and I am generally happy with the rom but I've seen others posted I wanted to try out. My problem is that I have so far been unsuccessful getting odin to connect when I go into the rom download screen (down+home+power). Odin and kies both connect when on the home screen.
I understand that since its Froyo with e3 recovery that update.zip files need to be signed so odin is needed to either install a new rom, install clockworkmod or install a kernel that has e2 recovery.
Is there any way I can get odin to connect or downgrade to e2 recovery without going through odin? Or any other solution to downgrade to 2.1 and start again?
It feels like i'm missing something but I don't have the experience to figure out what it is.
Any help would be much appreciated.
Pete
This happens to me every now and then as well.What I would do is to re-install the samsung usb driver in my laptop. After that, odin sees my phone again in DL mode.
Sent from my GT-I9000 using XDA App
Make sure you're connecting in the right sequence for odin.
- start odin with phone unplugged
- boot phone into d/l mode
- connect phone to pc via usb
thanks very much for replying. I tried a different computer and it seems to be a dodgy usb port/driver problem on my works computer I had tried originally.
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
I accidentally installed a capitvate i897 firmware (Android 2.3.4, AT&T branded) on my i9000. It looks like an US firmware, mine should be German.
Since installation of the new firmware I can't use the usb-connection anymore - some seconds after plugging the phone resets and stops working until I unplug the cable again. The 3-button-trick doesn't work anymore either, probably because the captivate hardware is quite different.
So... now I am desparately looking for any help or hints how I can get my phone rootet. I think that would help a lot to install a proper firmware again (via mobile odin).
Any hints?
Gingerly said:
I accidentally installed a capitvate i897 firmware (Android 2.3.4, AT&T branded) on my i9000. It looks like an US firmware, mine should be German.
Since installation of the new firmware I can't use the usb-connection anymore - some seconds after plugging the phone resets and stops working until I unplug the cable again. The 3-button-trick doesn't work anymore either, probably because the captivate hardware is quite different.
So... now I am desparately looking for any help or hints how I can get my phone rootet. I think that would help a lot to install a proper firmware again (via mobile odin).
Any hints?
Click to expand...
Click to collapse
You wouldn't really be going wrong by flashing back with Odin. I'd recommend flashing stock JW4 which is the latest European Gingerbread and rooting with the JW4 CF-ROOT.
I would have flashed already if I knew how to do it USB doesn't work, and entering recovery mode (if it is available, which I doubt) doesn't work either because I can't press the right buttons.
Gingerly said:
I would have flashed already if I knew how to do it USB doesn't work, and entering recovery mode (if it is available, which I doubt) doesn't work either because I can't press the right buttons.
Click to expand...
Click to collapse
u need to download 3 file odin from here http://www.hotfile.com/dl/150483619/708026d/I9000XXJW4_I9000OXAJW4_XEU.zip.html
and u will need also odin program from here http://www.filecrop.com/Odin-1.85.html after u download the firmware extract it and open odin
then put code in pda box modem on phone box an csc on csc box after that push vol down+home+power for download mode conect your phone to the computer and wait for yellow light in the program after thet press start good. luck btw if its only one file firmware put it on pda only
and if download mode not work with 3 button comb try jig device
Thanks for your detailed answer. But the 3-button-combo doesn't work. My guess is that the phone expects the captivate combo (volume up + volume down + power) which isn't possible on an i9000 device.
A jig might be worth a try, though I am worried, because the phone crashes always as soon as it get's power via usb (phone-pc or phone-power suppy, in both cases the phone crashes).
Is it possible to root the phone via wifi or right on the phone via app or some weird linux command line stuff?
You could try z4root? I don't think it will work but worth a try
Sent from my GT-I9000 running remICS-UX using XDA premium
Gingerly said:
Thanks for your detailed answer. But the 3-button-combo doesn't work. My guess is that the phone expects the captivate combo (volume up + volume down + power) which isn't possible on an i9000 device.
A jig might be worth a try, though I am worried, because the phone crashes always as soon as it get's power via usb (phone-pc or phone-power suppy, in both cases the phone crashes).
Is it possible to root the phone via wifi or right on the phone via app or some weird linux command line stuff?
Click to expand...
Click to collapse
Yes, I think it's worth a try, to download a SGS Kernel and try the App "SGS Kernel Flasher" (Search in Playstore, can't post a link) Maybe it works! I think you won't be able to boot your system after that, but maybe you can use the 3 button combo after that.
But first you have to find a way to root the phone... i can't find a app for that atm, maybe someone else found one?
------------------------------------------------------------------------------
EDIT
------------------------------------------------------------------------------
If you get root working, you can safely use this to flash the right firmware for your phone: http://forum.xda-developers.com/showthread.php?t=1347899
It's Odin on your mobile, so you can copy the files via an ftp or something like this and flash them to solve ur problem.
The other method I listed is a bit unsafe i think...
Actually, you can press Volume Up and Volume Down at the same time on a SGS. I tried it, because CM9 has the feature to change ringer mode this way.
nahum05 said:
u need to download 3 file odin from here http://www.hotfile.com/dl/150483619/708026d/I9000XXJW4_I9000OXAJW4_XEU.zip.html
and u will need also odin program from here http://www.filecrop.com/Odin-1.85.html after u download the firmware extract it and open odin
then put code in pda box modem on phone box an csc on csc box after that push vol down+home+power for download mode conect your phone to the computer and wait for yellow light in the program after thet press start good. luck btw if its only one file firmware put it on pda only
and if download mode not work with 3 button comb try jig device
Click to expand...
Click to collapse
Hello, More or less had the same problem.
To tell you the history: updated my samsung galaxy S I9000 to ICS, was not happy with it and f*cked up after that.
Wanted to install older firmware over ICS, telephone dead and than came on this forum and used
stockrom of I896 from developer TRusselo : http://forum.xda-developers.com/showthread.php?t=979133
now phone thinks he is a canadian I896.... Tried the above steps on PDA... unpacked ok but now phone keeps rebooting after it shows the samsunglogo....
did i miss a final step or did i do something wrong?
Thanks for your help in advance...
@calumn96: I tried z4root, it doesn't work..
@coroner21: wow! I always thought the both volume buttons would exclude each other. Now I can enter CWM.
Is there a way to root the i9000 in CWM? Or even better, to install a stock i9000 firmware?
Current situation: i897-firmware (2.3.4 uckh3) - I guess I need a root patch for this firmware.
Gingerly said:
@calumn96: I tried z4root, it doesn't work..
@coroner21: wow! I always thought the both volume buttons would exclude each other. Now I can enter CWM.
Is there a way to root the i9000 in CWM? Or even better, to install a stock i9000 firmware?
Current situation: i897-firmware (2.3.4 uckh3) - I guess I need a root patch for this firmware.
Click to expand...
Click to collapse
If you get a rooted i879 kernal you could try flashing that in cwm? You could try flashing a custom gb ROM from it (put files on a as card then in phone so not to use USB)
Sent from my GT-I9000 running remICS-UX using XDA premium
Gingerly said:
@calumn96: I tried z4root, it doesn't work..
@coroner21: wow! I always thought the both volume buttons would exclude each other. Now I can enter CWM.
Is there a way to root the i9000 in CWM? Or even better, to install a stock i9000 firmware?
Current situation: i897-firmware (2.3.4 uckh3) - I guess I need a root patch for this firmware.
Click to expand...
Click to collapse
Go into download mode
for i9000 it's volume down + home + power
for i897 it's both volume keys, and with the usb cable into the phone + power.
If you see the yellow triangle with and android and a shovel that's it!
Then get a stock firmware for i9000 on www.smafirmware.com and flash it through odin with the .pit + 3 files (PDA + MODEM + CSC).
@calum96: I will give it a try.
@-m3ta- : USB doesn't work, so any tips involving a usb-cable won't help :/
Another thing I realized is that recharging is barely possible...
Odin and Samfirmware is the way to go
Sent from my GT-I9300 using Tapatalk 2
Gingerly said:
@calum96: I will give it a try.
@-m3ta- : USB doesn't work, so any tips involving a usb-cable won't help :/
Another thing I realized is that recharging is barely possible...
Click to expand...
Click to collapse
I don't understand why 3 combo key, USB won't work. I had flash a captivate firmware onto the i9000 and the regular trick worked
@MrAndroid12: I don't understand it either. But the phone crashes as soon as the usb is plugged. Recharging didn't work at all, the phone just got hot and that's it.
@calum96: thank you! I flashed dmore 3.3 and so far it looks good. No usb-crashes anymore and the phone acts as it should. There is still an AT&T-brand, but that's still better than a useless phone
Gingerly said:
@MrAndroid12: I don't understand it either. But the phone crashes as soon as the usb is plugged. Recharging didn't work at all, the phone just got hot and that's it.
@calum96: thank you! I flashed dmore 3.3 and so far it looks good. No usb-crashes anymore and the phone acts as it should. There is still an AT&T-brand, but that's still better than a useless phone
Click to expand...
Click to collapse
You might be able to change the brands thing in build.props? Not sure tbh
So is it on i9000 firmware now? or is it just rooted? And is USB working now?
Sent from my GT-I9000 running remICS-UX using XDA premium
Everything works like a charm now
i9000 firmware (slim ics right now), usb works, recharging works and people can finally call me again (didn't work before either)
Thanks again for all your help, guys!
Glad to hear try remics its really good smooth with a Samsung feel
Sent from my GT-I9000 running remICS-UX using XDA premium
i have a att samsung captivate sgh-i897 and i flashed kit kat on it. it was working fine until one day it booted up to recovery and i couldnt get the phone to boot up. so i decided to flash back to a stock of gingerbread (i used the odin3 to do this) and that was successful. the only thing was my internal and external sd are no longer being detected and when i needed to reboot the phone it would continuously boot loop. ive looked every where for solutions. i just wanted to get everything back to normal so i tried to flash a what i believed was stock 2.2 froyo to it through hiemdall (SamsungCaptivate-SGHi897-UCKB2-NoRoot-One-Click) because i read it was the safest way to flash. after doing so i either get a black screen after boot or in boot loop and i can still get into download mode but when i try to run odin it wont detect the phone at all. can anyone help me get everything back to stock and get my phone usable again and possibly get my external sd card working again?
p.s. ive tried to wipe the cache and factory reset wipe too.
^
Go here... Stock I897UCKK4 Android 2.3.5 One Clicks *Heimdall and Odin*
If u want to use the Heimdall version that I linked, then use the same USB port that u used to flash the other heimdall one click that u mentioned.
If u want to use the Odin version, then use a different USB port, Because the heimdall usb drivers are installed only to the one specific usb port that u r using at the time of the install. That is more than likely why the computer is not recognizing ur phone when u r trying to use odin.
Here is another thread that may help as well... Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
Sounds like failing internal memory to me.
ok
4-2ndtwin said:
^
Go here... Stock I897UCKK4 Android 2.3.5 One Clicks *Heimdall and Odin*
If u want to use the Heimdall version that I linked, then use the same USB port that u used to flash the other heimdall one click that u mentioned.
If u want to use the Odin version, then use a different USB port, Because the heimdall usb drivers are installed only to the one specific usb port that u r using at the time of the install. That is more than likely why the computer is not recognizing ur phone when u r trying to use odin.
Here is another thread that may help as well... Captivate - PC Connection Issues, Download Mode and Recovery Mode Help
Click to expand...
Click to collapse
i downloaded the heimdall with no bootloaders and no difference. im still getting boot loops. should i try it with bootloaders and see that works?
Val D. said:
Sounds like failing internal memory to me.
Click to expand...
Click to collapse
is there anything i can do to boot it up if thats the case?
I'm not 100% sure this is the case, but failed internal memory issue happens to Captivate phones and the symptoms are same to what you describe. The phone can't read part of the memory and reboots constantly no matter what ROM you attempt to flash. Search the forum for internal/external swap methods. I never had to deal with this issue and have no experience with workarounds.