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
Related
I had loaded the ginger clone rom and all was well. I then however wanted to swap kernels so i loaded up seitrons cwm 1.5.6 and proceeded to flash through cwm. this has now become the worst day of my life. the phone will not boot past the galaxy s screen. i cannot not get into recovery and both computers now say usb device not recognized when in download trying to flash odin. i am worried that something is corrupted on my phone because not matter how many times i uninstall and reinstall the drivers no luck. i think it is officially bricked and im sol. maybe some great minds can figure it out here.
It's not bricked - issue is trying to get your computer to recognize your phone when in download mode so you can flash it back.
What OS are you running? Also - where did you download the drivers from? Some seem to work better than others.
If you can get to the galaxy screen you might still be able to to get into recovery. pull out the battery and use the 3 button combo. Hold down both volume button then power and let go of the power button after it turns on. then just reinstall the rom
I'm willing to bet you can also get into Download Mode either with button combos, or a JIG. Once in Download, you can use Odin to restore to JF6, and have a working phone to flash around with again.
i can get into download mode no problem. and i think it is quite possible drivers are corrupted on the phone itself. my wifes phone works on the same exact setup. no usb device not recognized error. i have tried the drivers from here and samsung directly with no luck. 3 button combo does not work. sim out sim in battery out and in. but like i said it will just not register with the comp and hers will. so im going to att and seeing about replacing it. but i will see how that goes. ive done this lots of times with no issues ever.
download works
3 button combo does not so no recovery
usb device not recognized error
thanks for the help and keep it coming i will try everything if i haven't already.
Try current usb port
Sent from my SCH-I897 using XDA App
Think I'm in worse shape. Tried flashing just the kernel to get BLN working again (last ROM I put on somehow loaded a non-compatible kernel). Now the phone boots the white ATT screen and just sits there. Can't get it into D/L mode with 3-button and doesn't respond to computer I have been using to flash ROMs for a couple weeks now...
Am I hosed? ANY help would be greatly appreciated...
You could try to use a JIG to force your phone into Download Mode
Okay...well, got into D/L mode finally. Used Odin to get it back to factory. Used the One Click rooter again, except now it boots to recovery 3e, which doesn't let my power button work as the okay button Pulling the battery to reset it, but it will no longer go into D/L mode to use Odin again. It keeps booting to the recovery Utils, which I cant get out of...*sigh*
Thoughts?
at least your able to do something i still cannot get my phone into recovery or to be recognized by the computer. it is not the drivers so i have no idea. i can only think that something got funked up with the kernel flash.
if you are getting into 3e recovery then you are most certainly NOT using the JF6 one click stock
3e recovery comes on JI6 which is the FroYo leak....completely different builds and roms
have you tried a different usb cable? I was having this problem, and the stock samsung cable was B.O. and wasnt working... i tried my blackberry one and all was good
magnumrt562 said:
have you tried a different usb cable? I was having this problem, and the stock samsung cable was B.O. and wasnt working... i tried my blackberry one and all was good
Click to expand...
Click to collapse
i actually tried this yes. i had a blackberry cable from the storm (shivers) that was laying around. tried that but no luck with that or my wifes cable as well. but a good tip for others nonetheless
Pirateghost said:
if you are getting into 3e recovery then you are most certainly NOT using the JF6 one click stock
3e recovery comes on JI6 which is the FroYo leak....completely different builds and roms
Click to expand...
Click to collapse
I just want to quote this to stress the importance.
Thank you, didn't realize that (still sorta new to this)...
I downloaded a zip (I thought from here somewhere) that extracted into the 4 files. Anyone got a link to the JH6 set of files?
I also downloaded DG's "One Click Odin", but it doesn't seem to really do anything when I run it unless I manually load all the files. Also, I don't see a "Master Clean" like the post refer too
are you sure you downloaded the right odin? in the one click version, theres no option to load files at all. only a "start" and "master clear"
make sure the odin one click is open before you connect your phone.
http://forum.xda-developers.com/showthread.php?t=731989
You guys rock! I don't know how, cause I could have sworn I D/L'd it from that link before and I got the generic Odin, but it looks like I have the right one now! Thank you for your patience with us noobs as we start getting into this new world!
glad you got yours working. i have officially given up and receiving a new one on tuesday. i tried everything but somehow someway the phone is not recognized in download mode. oh well have to mess the with new one then lol
zippox180 said:
glad you got yours working. i have officially given up and receiving a new one on tuesday. i tried everything but somehow someway the phone is not recognized in download mode. oh well have to mess the with new one then lol
Click to expand...
Click to collapse
I was having the same problem. Have you tried powering off, start odin, hold both the volume up/down, then plug in the usb to your phone?
Introduction
I've put together a video on how to flash a rom. It includes Rooting, Backing up data, Flashing a kernel, Flashing a rom, and troublehooting bad flashes.
Warning
Before you go and flash a ROM for the ultra-fast speeds, kick-butt graphics and awesome sound upgrades... Realize that the risks are real, it is possible for you to black-screen-brick (hard brick) your phone. Here is a real-world example:phone won't turn on. At this point, only JTAG recovery will be effective. I will be posting a video on JTAG soon enough.
You may feel more comfortable stopping after rooting and titanium backup, and not installing a ROM at all, that's OK.
How-To
If you are installing a ROM, then select the ClockWork Mod flashable zip you want and copy it to your phone's internal memory before you watch the video. I did not cover this in the video as there are many options. Team Komin recommends Andromeda3, but you may select any Captivate ROM.
Here is the video which I have prepared on flashing a custom ROM.
Flashing Toolbox
Windows Drivers - select the proper driver for your setup
32 bit: http://www.mediafire.com/?0b45zo7o75rc5d5
64 bit: http://www.mediafire.com/?3dh4d6up72me9re
Files
*SuperOneClickV1.7 - http://files.teamkomin.com/Andromeda/Tools/SuperOneClickv1.7-ShortFuse.zip or http://www.mediafire.com/?kr649t97dd116cd
*Odin3 1.7- http://files.teamkomin.com/Andromeda/Tools/Odin3 v1.7.exe or http://www.mediafire.com/?dy2ix2icags19qr
*Ursa Minor - http://files.teamkomin.com/Andromeda/Tools/UrsaMinor.tar or http://www.mediafire.com/?a1i0boby6em54eo
*Andromeda3 - http://files.teamkomin.com/Andromeda/Andromeda3-Final.zip or http://www.mediafire.com/?vpu22j478j4542a
Recovery Software
*Odin3 one-click 1.0- use only in case of emergency, this can damage your phone -http://www.multiupload.com/XAZUYNXSC1
Tips, Tricks, Good to know
If you have a standard computer setup and you see your phone connected to a port higher then COM6, reboot your phone and your computer before flashing anything.
Phone--!--PC is just a download mode. If the computer does not recognize the phone, reinstall drivers, reboot and pull the battery out, then try again.
Odin is only used for initial and/or recovery modification. After using odin to flash a new kernel sucessfully, you will only need ClockWorkMod (CWM) to flash most kernels and ROMs. CWM is accessed by pressing and holding the 3 button combo.
If your phone displays Phone--!--PC and does not register a COM port on your computer follow the directions below
1. remove the usb cable, battery, sdcard, SIM.
2. wait 10 seconds, then insert the USB cable.
3. press and hold the 3 button combo while you insert the battery
4. continue to hold until phone's screen goes black twice and release power button.
5. timing is critical, it may not work the first time. Keep going until you see the COM port is connected properly.
Disclaimer: All materials presented are for informational purposes. This video is not an authorization, advertisement, nor a suggestion to flash your phone with custom firmware. In no event shall I be held liable for any direct, indirect, incidental, spcial, exemplary, or concequential damages, including but not limited to loss of data, business interruption or damage to equipment. This information is released AS-IS with no written or express warranty or liability.
Thanks for the guide adam, I'll be using this tonight. Could you possibly update this with a section on how to go back to a stock kb1 build? That would be great.
Sent from my SAMSUNG-SGH-I897 using XDA Premium App
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
AdamOutler said:
That's the link at the bottom. Odin3 1-click is a KB1 build. It will bring you back to stock KB1.
Click to expand...
Click to collapse
Thats JF6, not KB1.....
Stock 2.2 you get from the update using kies mini.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dead Links
Hey could you repost the download links because none of them work anymore? Thanks
Sorry, Team Komin's server is down right now, there are other sources on the internet. I will mirror on mediafire as soon as I can
In a boot loop - Moved from Andromeda thread
Hi Adam, Just to get up everyone where we are. I had a flashing issue with Andromeda which resulted in the phone continuously rebooting; i.e. white screen Ursa Minor screen disembodied voice which I now think says missing operation, it definitely doesn't say backup operation, I've listened to it soooooooo many times. . .anyway I put the phone in download mode as you said - BTW this phone with phone off vol+vol then plug in USB and download appears. Holding the power button takes you -when the phone isn't loopiing of course- into recovery mode. I had already restarted the computer, - not a VM - restarted Odin 3 and tried to reflash. Pass! Reset and unfortunately I'm still in that loop can't get to recovery mode.
I removed the battery and USB. Held down all three buttons and with the USB cable connected put the battery back. I held through 2 screen goes black circuits. Second time up the screen shows a gray battery then goes black then I get the ATT screen followed by Ursa Minor and my now less than favorite voice. Doing the same without the USB cable I don;t get the battery but I do get the ATT splash screen between the two black screen and then that darling voice again. So that's where I am. Ideas please
Personally I would One-Click back to Stock. ROOT. Install CWM using Rom Manager. And then install Andromeda via CWM. (I usually skip re-rooting and just install from CWM via the update.zip from ROM Manager) See if that doesn't work... If it does, finish up by installing Ursa Minor #2 (or is it just Ursa Minor now?)
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
^^ It can be tricky to get it into download mode, but there are several ways to do it on all phone. The important thing is that you get a sane COM port like COM8 or less on Odin3 1.7, and that you have download mode activated on the phone. Good to see that everything is working properly.
BWolf56 said:
Great Work Adam! This is surely gonna help alot of new users!
On a other note, I'm concidaring to try A3 and was wondering if it's not exactly what I'm looking, can I flash over it (as it is really stock based) or am I better using Odin 1.7 again and flash another ROM?
Thanks!
Click to expand...
Click to collapse
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
fireboss said:
Okay so I was writing this reply saying "I tried that first thing and have tried it several times in various ways since. It hangs, never got a progress bar" I had just tried it again (20 minutes of nothing) and was going to post the log out of Odin but I had closed it out so I thought what the heck I'll run it again. Danged if it didn't work this time.
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after. As I said the only way into download mode I've found with this phone is powered off hold vol+vol then plug in USB. This time Odin was waiting, found the port and when I clicked start it worked. Heaven only knows if that is a quirk or coincidence.
Now off to see if I can flash this rom.
Thanks
Click to expand...
Click to collapse
OK well I've confirmed that Odin One Click won't restore on this phone unless it is open on the Windows machine when I connect the USB port tot throw the phone into download.
I restored then went through the flashing process again. This time when when it rebooted it didn't loop but it wouldn't go into recovery. I used droid explorer to flip it to recovery mode. Inoted then that there was no adndromeda.zip package on the sd card. I assumed Ursa was supposed to pull that over because in the video it says to find it and install. In any case I drug it from the computer to Droid Explorer and then was able to find it and install the Rom. The unpack looked normal enough the system rebooted. I unplugged USB,gave it the three button fix roputine, and was back in the loop. No matter what I did it looped. The loop was slower this time and the voice clearly said Restore Operation. Not knowing enough to wander farther and unable to get into recovery now because Droid Explorer couldn't see the phone anymore I let Odin restore it. That's where I am now.
Suggestions?
AdamOutler said:
Get ursa minor on there and you can do anything!
The ursa minor kernel with ClockWork Mod flashed through Odin3 1.7 will support all ROMs designed for our phone. Some ROMs are not designed for our phone (Cyanogen Mod, MIUI) and have work-arounds supported by the developers. I skipped the portion of downloading a ROM because you can pick a ROM yourself, this video just gives you the tools to do so. You are more then welcome to use the "UrsaMinor.tar" file as a ClockWork Mod springboard to other ROMs or kernels, I just picked my own team's ROM for the video.
Click to expand...
Click to collapse
Thanks! I'll try that out once I get home from work. The only thing I can say is that I wish that would've been up when I got my 1st cappy - would've saved me the trouble of having to Odin3 1 click
Once again, Great work!!
EDIT: This should be Stickied!
fireboss: redownload all links above, it is possible that something went wrong with the download process and a bit is missing somewhere.
-copy the rom of your choice to your SDCard (Team Komin recommends Andromeda3, but any will work)
-put the phone into download mode and flash ursa minor tar file using Odin3 1.7
-let it run though it's operation until it boots normally.
-remove the usb cord, press and hold 3 buttons to reboot into recovery
-select zip from SDCard- Andromeda3.zip
i dont see a link, or file attachment or any mention of 3e recovery in OP
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Might already be in Ursa Minor? (correct me if I'm wrong Adam)
fireboss said:
I know this sounds odd but I think the difference was that I had Odin One Click running when I put the device into download mode instead of starting it after.
Thanks
Click to expand...
Click to collapse
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Trusselo said:
i dont see a link, or file attachment or any mention of 3e recovery in OP
Click to expand...
Click to collapse
Right Bwolf
No need to mess with 3e recovery. UrsaMinor.tar overwrites 3e recovery and gives you CWM so you can begin flashing immediately.
mxracer101 said:
You should always start odin BEFORE plugging the USB cable into your phone. I have never had an issue with odin on any of the phones I've flashed if I had it running before going into download mode. I also always restart odin between the initial flash and master clear if I'm going that far.
Click to expand...
Click to collapse
That works. The biggest thing is that you are in download mode and you have a sane COM port like COM5 or 6, not COM14. As shown in the video, COM14 lead to Phone--!--PC..
I may do this video again with heimdall. it worked well.
mxracer101, any chance you can generate a pit file? I'd like to make Andromeda3 into a full heimdall flash where you simply put the phone into download mode, select the files, hit start, and let the stock phone boot into Andromeda3.
So here't the full background, it's not long, please read:
http://www.darkyrom.com/community/i...-bricked-my-sgs-wonder-what-i-did-wrong.2032/
Long story short, it looks like I bricked my SGS when trying to flash with Odin, even though I followed the tutorial very closely. When I power up the phone, it just gives me the image with phone, exclamation mark and PC on it. It does, however, go into download mode when powered up with VolDown and center button.
How do I save it? Do I need the JIG (God, please say no! )
Have you tried reflashing with odin.
Jig is only needed when you cant get into download mode.
Also i just looked inside the darky rom topic.
Have you flashed the jvk rom first with the bootloaders?
Edit: as said below. If you gonna reflash, flash a stock rom. Not the darky rom. First priority is to make your phone work.
Sent from my GT-I9000 using XDA Premium App
Yeah, you have download mode.
Now, fire up Odin and load a few rom files into it, connect the phone and see if the PC still recognises it. (Do not flash, Just a test)
If so...
Flash a stock rom.
Somehow, I was able to flash it with Odin in Download Mode this time. Phew! I read somewhere that the flash might fail if You're using wrong USB port. At first I connected my phone to a eSATA/USB combo port, and for the second time (after brick) I tried a normal USB 2.0 port in my laptop. Maybe that's what made the difference, I have no idea.
Anyway, I'm running stock Samsung 2.3 rom and am trying to install Darky's 10.0 RC3 on it - I am running into some problems, but thankfully they're much less serious than the brick that I was able to fix.
Thanks for Your help!
I ran into similar problems last week. A rom wouldn't flash, so I gave it an hour and it proceeded nowhere. Had to pull the plug on it.
Sometimes it just takes a few times plugging and unplugging repeatedly until it just happens to get detected by Windows. Maybe just a bit of luck too
Congrats on your recovery.
Just wondering which stock 2.3 rom did you use and which Odin setting you used to get your phone up and working again.
Here is my post / problem, seems similar to yours
http://forum.xda-developers.com/showthread.php?t=1020223
Thanks
I had the same issue like warnec on my first darkyy flash, finally everything went fine...don't worry!
just try to reflash with odin (maybe going for a stock version first is a good idea), be sure to do everything as mentioned in the guides out there. and be sure your computer works stable, maybe you want to quit some tasks in the background (however it should work even without but something crashed my odin once...)
Reflash with Odin to make your phone work again. I suggest using a stock 2.2.1/2.3.3 ROM. It is important that it consists of the 512.pit file, a PDA file, a Phone file and a CSC file. The ROM must have bootloaders included!
Now, disconnect your phone and turn it off.
Start Odin and load all the files. Tick 'Repartition'.
Start your phone in Download Mode by pressing Vol-Down, Home and Power.
Connect it to your PC and wait for Odin to say 'Added!'.
Now hit Start, wait 2-3 minutes until it is done and your phone should succesfully reboot!
Sent from my GT-I9000 using XDA Premium App
Thanks I tried this and my phone just keeps flashing i9000m screen, then blank and then back to the i9000m screen. Looks like the phone is unusable.
chriszak said:
Thanks I tried this and my phone just keeps flashing i9000m screen, then blank and then back to the i9000m screen. Looks like the phone is unusable.
Click to expand...
Click to collapse
does not sound very good...could you solve your problem yet?
Had to take the phone into Bell. Waiting on return of it and currently using a loaner HTC Desire Z from Bell.
Hi,
I have done a lot of reading and searching, and I think I understand most of the basic pieces of what I am trying to do and how to do it. Let me explain.
Ultimately, I want to be able to install custom roms to my captivate.
Firmware: 2.2
Kernel: 2.6.32.9
Build: FROYO.UCKB1
I installed rom manager, but I see that with my hardware, I cannot install cwm recovery. It seems I need to downgrade my kernel using odin. Problem is, although I found the thread listing all of the kernels for download in zip format, I have no clue which one to use.
I found the instructions on how to reboot into cwm recovery, but without the new kernel, I cannot do it, at least that's what I gather.
Can you guys help me here? I know I am on the right track, but don't know what to do to go any farther. Also, I cannot get into recovery mode buy clicking the buttons. It seems I must now use adb. All I want to do at this point is reboot into cwm mode. Can that be so difficult.
Well, this is my first post. Thanks to all who reply.
Viper
3e recovery. Look in the stickies to fix that. OR flash another kernel (like Cog 4.x.x kernel) and flash a rom.
+1 to the above. Personally when flashing a custom ROM I just always start with JF6, the flash the green CWM update.zip file followed by the ROM, or if it's got an initial-kernel like many ROM's call for now days.
Quick stupid question...
Does the sim card need to be out to do this, or any of the other things I have been trying?
PghPittViper said:
Quick stupid question...
Does the sim card need to be out to do this, or any of the other things I have been trying?
Click to expand...
Click to collapse
It does not matter. The whole (remove SDCARD and SIM steps) in my opinion have always been false info. The only reason I'd remove anything would be the SDCARD if using a recovery that's untested to ensure it's not formatted or something like that.
error?
No matter what I try flashing with odin, I get this message:
<OSM> All threads completed. (succeed 0 / failed 1)
This indicates that the process failed. What gives?
Re-install your drivers. Then ensure the ODIN is open BEFORE connecting your phone in download mode. You can get the latest drivers in a package I made with ODIN here:
www.mediafire.com/?eyr42m5ilf03566
Edit: Also only use a genuine OEM cable when flashing. There are two many issues with non-oem cables and the usb data transfer they provide.
Need big time help now!!!!!!!!!!!!!! Possible Brick!!!
Now i have been playing with flashing roms. Now I have a real problem.
I flashed darky 10.2 i believe and now I am in a boot loop. It cycles between the white att screen and a colored pixelated screen.
I have been reading and researching for hours now. Present time 3:15 am. Research tells me that the cappy is pretty much un-brickable.
I KNOW I have to get into either download mode or recovery mode. I cannot do either.
I have researched this subject exhaustively, but my brain is fried now, and I work at 6:00 and need my phone.
What to do????
I emplore anybody up at this time to help.
TIA
PghPittViper said:
Now i have been playing with flashing roms. Now I have a real problem.
I flashed darky 10.2 i believe and now I am in a boot loop. It cycles between the white att screen and a colored pixelated screen.
I have been reading and researching for hours now. Present time 3:15 am. Research tells me that the cappy is pretty much un-brickable.
I KNOW I have to get into either download mode or recovery mode. I cannot do either.
I have researched this subject exhaustively, but my brain is fried now, and I work at 6:00 and need my phone.
What to do????
I emplore anybody up at this time to help.
TIA
Click to expand...
Click to collapse
What ROM were you coming from? Did you try all the 3 button combos? or battery pull/Vol+/- then plug in usb? Next best thing is a Homemade/bought Jig.
PghPittViper said:
What to do????
I emplore anybody up at this time to help.
TIA
Click to expand...
Click to collapse
Did you flash gingerbread bootloaders before flashing the ROM?
I am not amused by your phones performance
Did not flash gingerbread...
I apologize, my intent was not to amuse.
How now can I flash gingerbread if the phone wont stay powered on?
I ran home during my work break to check my replies.
Because I didn't flash gingerbread, I presume I was hasty in flashing darky becuause it seemed so great, is it possible to resurrect this phone?
I am feeling pretty discouraged.
Thanks and please continue to help.
As long as the phone shows any type of life its not Hardbricked and can be recovered with key combos or a Jig. Your fine. Get in to download mode and flash a clean stock and start over.
Entering recovery mode in my situation.
I am currently trying to hold the 2 button volume control and the power key.
The phone comes on to the att white screen, then goes black, then comes back on, etc...
I am very worried.
When I plug into the usb, it will connect to pc, then disconnect, then keep repeating this. I read that kies has an emergency recovery feature. But,, I can't connect to kies. Odin recognizes a port, but kies just says to connect your phone.
Any advice?
PghPittViper said:
I apologize, my intent was not to amuse.
How now can I flash gingerbread if the phone wont stay powered on?
I ran home during my work break to check my replies.
Because I didn't flash gingerbread, I presume I was hasty in flashing darky becuause it seemed so great, is it possible to resurrect this phone?
I am feeling pretty discouraged.
Thanks and please continue to help.
Click to expand...
Click to collapse
You don't need gingerbread BL for Darky 10.2. I've flashed Darky 10.2 before, his directions were pretty clear. I moved onto Fasty since his updates stopped. I suggest reading the stickies for making jigs or buying them as well. You can do it! & Good luck.
^what he said. You can try and taking out ur batter open odin, connect your phone hold Vol up and down insert battery. If that doesn't work you need a jig. Not hard to make, takes a little time though (if you peel a cheap cable for the plug that is)
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