So basically I have a Samsung Galaxy S Captivate (i896) and it was running 2.1, so I decided to try and upgrade to the newest stock available for the captivate (which is 2.3.5). I had to use heimdall because I bought the phone used and it was rooted and possibly running a custom ROM so kies is not an option. When I put the phone in download mode the computer wouldn't recognize it (I'm on a Mac). I did alot of reading online and I couldn't find a solution. So I decided to flash a new ROM hoping that this would solve the problem.
So I flashed a random ICS ROM. But with this ROM I couldn't even access download mode. I tried a 3 button fix, I tried to use terminal to boot into download mode, and I tried to use ADB from my computer; nothing worked. So I figured I would flash another ROM (this time I used Hellybean) but when I tried to install it, a bunch of code ran on the screen and it said "installation aborted". Before attempting to flash this ROM I completely wiped the phone (i formatted the system from the mounts menu in CWM) and now the phone is showing the at&t logo, then going to black, then some code runs on the screen, then it goes black and starts the whole thing again.
I cant get to recovery or download mode.
Is it bricked? How do I fix this?
I don't know what I did wrong! any help would be appreciated.
P.s. I would really like to avoid building a jig because I feel like Im not too good at that kind of stuff....but if that's what it comes to...
Thanx in advance
All the information you need is already available:
Putting the Phone into Download Mode
How To flash ANY Captivate ROM from Stock
Val D. said:
All the information you need is already available:
Putting the Phone into Download Mode
How To flash ANY Captivate ROM from Stock
Click to expand...
Click to collapse
I've tried all of those methods except for using a jig. Is it possible that while flashing a ROM my phone somehow lost download mode?
Also if all of those combos didn't work is it likely that a jig will work?
Looks like you started reading after you messed up the phone. Update instructions say clearly that you need GB bootloaders before you proceed to ICS or JB. You provide no information what exactly ROM you started from, what GB ROM you attempted to flash (with or without bootloaders), what exactly ICS you flashed after, what "some code" runs on the screen now, etc. It's a lot of guessing here. If bootloaders are messed up, than you won't be able to fix your phone at home. I have never seen a problem you describe, so wait for someone with more experience to stop by.
I got it going! All it needed was a jig and then I was able to flash stock GB with bootloaders.
Thanks for the help.
Good news! :good:
I have a Cappy and gingerbread boot loaders come in three flavours i897, i896 and i9000 and they're backwards compatible with froyo and éclair roms. Don't mix froyo and gb boot loaders though you will hard brick your device. I have i896(Canadian) boot loaders and when I flash kk4 [email protected] Odin gingerbread my "i896" boot screen is garbled image of pixels until I flash the proper param.lfs file to match. Hope this helps. BTW I have a jig as well and for all galaxy devices it's a must.
Sent from a Borg powered Nexus 4
Related
Hey,
I'm new to android.
I thought I've read up on everything I'm doing. Making sure to read the threads carefully.
I've rooted my captivate and tried to put OCLF. It said it was successful, except now when my phone was rebooted it shows:
device name (samsung i896)
rogers screen
galaxy s screen
then it goes black and vibrates every so often
I've tried searching and can't seem to find what I need.
If anyone can help, I can boot my phone into recovery mode, but thats about it. Nothing works in there right now,
Can anyone help me get this fixed, or back to the stock rogers firmware that would be great
Thanks!
you can try to use key combination to get into the download mode and flash the stock rom.
if you cannot get into the download mode, my suggestion is to build a jig or buy one:
http://cgi.ebay.com/ws/eBayISAPI.dl...47234&ssPageName=STRK:MESELX:IT#ht_510wt_1139
you can try to use key combination to get into the download mode and flash the stock rom.
if you cannot get into the download mode, my suggestion is to build a jig or buy one just in case:
http://cgi.ebay.com/ws/eBayISAPI.dl...47234&ssPageName=STRK:MESELX:IT#ht_510wt_1139
I can get into download mode and recovery mode.
I'm kind of lost on flashing back to the stock rom. I'm looking at other threads on how to do so, but something isnt working when I try.
Someone please help!
I'm experiencing the same problem even after flashing Rogers stock (2.1 and 2.2) with Oden and Heimdall. All flashing indicates they were successful; however, I still get the black screen, lit touch icons, and vibrations after the three boot screens/animations.
EDIT: Problem was solved for me by flashing a stock file that contained dbdata.rfs and param.lfs with 512.pit and repartitioning. The Odin flashable Rogers 2.1 stock ROM I put together can be found here. Because it is complete, it will also remove the AT&T boot screen if you flashed an AT&T ROM.
im apparently having the same problem with ma GF's phone -
Vylle said:
im apparently having the same problem with ma GF's phone -
Click to expand...
Click to collapse
Have you tried flashing AT&T or Rogers stock?
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
tomween1 said:
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
Click to expand...
Click to collapse
For your daughter's Captivate , did you try rebooting the phone and getting back onto recovery mode to see whether it was just a weird recovery boot ? LOL idk , I never heard of that one , but it may be fixed through a simple reboot . IF that doesn't work , try flashing another kernel through Odin + Download Mode .
For your Captivate , once you get to download mode , flash DG's stock Captivate Eclair (It has the 3-button mode fix , just in case you might not have it or ... just in case) . If that goes great , then install Rom Manager to get CWM , then start flashing again .
Yeah I'm kinda skipping steps , but you said that you've flashed before , so it should be a piece of cake to fit in the pieces together .
There are also other methods like Master Clearing , flashing another stock ROM , etc. but the method I posted has always helped me in tight situations .
BTW , does your captivate have the 3-Button combo ?
dayloooo said:
For your daughter's Captivate , did you try rebooting the phone and getting back onto recovery mode to see whether it was just a weird recovery boot
Click to expand...
Click to collapse
Yes I tried several times. Always getting the same options, always excluding sdcard option.
dayloooo said:
IF that doesn't work , try flashing another kernel through Odin + Download Mode
Click to expand...
Click to collapse
Why would I flash a different kernel to stock Froyo?
dayloooo said:
There are also other methods like Master Clearing
Click to expand...
Click to collapse
This is where I was when the catastrophe hit!
dayloooo said:
BTW , does your captivate have the 3-Button combo ?
Click to expand...
Click to collapse
FYSA yes It does....did
tomween1 said:
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
Click to expand...
Click to collapse
flash the leaked odin froyo from designgears REV02. you should fine after that
Which can be found here: http://www.megaupload.com/?d=QL6NX702
1. Open that .exe found in the .zip in the link above. (Make sure you run the .exe!)
2. Put your phone into download mode.
3. Plug in the USB.
4. The program (Odin One-Click) should find the phone.
5. Basically follow the only option you get, and it'll be done for you automagically (apart from 'Master Reset', which you might want to do AFTER you finish resetting it back to stock).
tomween1 said:
I have been flashing for 4 months or so. During this time it has all been without incident. I have flashed 3 Captivates (mine being one of them, has been flashed 6-8 times) and one ARIA.
I recently flashed my daughters Cappy to Froyo 2.2. She is now wanting her phone to look like mine was (key word "was" more on this later) running Serendipity. I tried to flash v6.2 using CWM and found when I was in restore mode I was never given the option to load from sdcard. So here I'm stuck. Can the ROM actually be flashed from Froyo 2.2, simply?
My phone I went for the Serendipity v5.12 to v6.2 clear and reinstall. I had a major problem during the ODIN flash that flat-lined my phone. I've purchased a jig and am awaiting its arrival. I understand how the jig works, but don't really understand the next steps after getting into download mode! What steps do I take next? Do I start flash back to 2.1, do I just install Serendipity over what I had? Throughly confused!
Click to expand...
Click to collapse
I dont think anyone that responded actually understood what you were saying, possibly myself included.
First part(daughter), froyo 2.2 stock has 3e recovery that requires a signed update.zip. You need to root it to install the modded 3e recovery in the dev section that removes the signature verification. OR flash it back to 2.1 with oden(yes downgrade it to upgrade it). Im sure there are other methods, those are just 2 i can think of off the top of my head.
Then you can install cwm with a cwm update.zip that is floating around the captivate forums.
From there you can install any rom with the normal methods.
Second part(you), odin bricks phones. Its not talked about very much but its easy to do. Your usb cable was probably loose, or bad, and cause an error and your phone soft bricked. Once you get the jig, pop it in get into download mode - start odin - connect the phone to the pc - wait for odin to detect it - flash 2.1 - flash serendipity.
If im understanding your problems correctly.
venomio said:
(apart from 'Master Reset', which you might want to do AFTER you finish resetting it back to stock).
Click to expand...
Click to collapse
Meaning after a new rom is no longer wanted? It's already stock.
So what you want to do is to Master Clear the Stock ROM before you install the new custom ROM on to it. This will prevent any possible problem coming up while flashing. (Of course, it will clear all data in your internal SD).
whiteguypl said:
Your usb cable was probably loose, or bad, and cause an error and your phone soft bricked
Click to expand...
Click to collapse
You hit the nail on the head I was half way through Odin when my computer made the disconnect sound and then reconnected immidiatly I kinda figured I was [email protected]@k?$ at this point. This was different though, because I've been able to come out of soft boots befiore. No doubt I was playing w/ fire thoes times
Thats exactly why I wanted to get a jig before I started any of my ROM flashing. I had an issue when I started Recovery Mode would just prompt restart and other things off the bass menu, when I tried to back up.
I had to flash 2.1 Eclair and then master Wipe it. Then I was able to do anything to.
Sucks you bricked it. EVERYONE Bricks one time at least one electronic device.
<--PSP Bricker
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 had tried flashing the SlimBeam ROM (coming from Helly Bean, which worked great), but got the perpetual AT&T logo of death. This seemed to be an issue with several other users, as pointed out in the SlimBean thread.
To resolve this, I flashed back to stock with a Heimdall One-Click utility. Stock now boots great and the phone is functional (albeit now running a very old version of Android). I was looking to root again to go back to Helly Bean. However, I can no longer enter recovery mode with either the 3-button method or ADB. When the phone is told to enter recovery, it just hangs at the AT&T logo, just like when it was trying to boot SlimBean.
I can restart the phone into the stock ROM and I can also successfully enter download mode. Recovery just isn't happening.
Any ideas on what I can try at this point? I'm on a Mac but have access to a PC if necessary.
Have you tried flashing a stock rom with bootloaders? I hate suggesting that, but sometimes re-flashing the bootloaders makes a difference.
Just make sure you're careful to have a solid connection throughout the flash.
themilstead;30584149
To resolve this said:
Which stock did you flash back to? I've only done it (but lots of times) with Odin-one-click, not Heimdal but not all the one-click packages contain CWM.
You could try one of these:
http://forum.xda-developers.com/showthread.php?t=1300843
Click to expand...
Click to collapse
Ah, I don't remember if the Heimdall package came with a bootloader (I did this earlier today at the office, and I'm home now). When I was restoring earlier, Odin wouldn't recognize that my phone was connected in download mode...hence me using Heimdall. I'll give Odin another shot right now since I'm up and running with stock.
There are Heimdall packages with bootloaders, if you need it.
Just remember that Heimdall will write its drivers to the port you installed it to - if you plug in your phone to that port and try to fire up Odin, Odin won't see it.
I'm on a different computer than when I used Heimdall earlier, so Odin is now recognizing the phone.
New problem: The process won't get past "SetupConnection". I'm currently trying out "I897UCKJ3 Stock with BL".
Rah rah rah rah rah.
^
See this thread by jmtheiss for help with ur prob. --- Captivate Connection Issues and Download Mode Help
Well, I'll be damned: The Epilogue
Got it!
It was simply a matter of me continuing to try other USB ports (my computer has 4). I tried one that previously didn't work, and it suddenly did. Not exactly sure what changed, but persistence paid off! I suppose power tolerance is potentially different for each port? (...in the same vein of it's better to plug into the back of the computer rather than a keyboard. I digress.)
Anyway, after Odin both recognized my phone and got past the "SetupConnection" step, I proceeded to install "KI2 w/ Bootloaders & Boog's KernO". This included ClockworkMod built-in, so I thought it'd be a good option. Sure enough, I was finally able to boot into recovery without any sort of trouble, then proceeded to install the new CM10 nightly.
Everything works. Thanks for the replies and help, everyone!
I have searched for the last 24 hours on this site for any mention of this problem and found nothing. I apologize if it has been covered elsewhere and would appreciate a link if I should be there instead of here. I am new to this forum.
I have an AT&T Captivate that I bought used for my wife. It was rooted and running some version of non-official Gingerbread when I got it (so it had been messed around with).
I have never been able to get into RECOVERY mode having tried every conceivable button and timing sequence at least 1 million times (3-button neutered?). I also have Android SDK installed on my PC and can send the "adb reboot recovery" command but it locks up at the AT&T screen and won't go any further so the PC is talking to the phone but the phone refuses to obey. Yes I have tried different USB ports and cables, un/reinstalling drivers, etc. The weird thing is that I can get into DL mode easily with the batt out, vol+/-,USB cable trick.
I originally took the phone all the way back to a stock Froyo ROM via Odin which appeared to work fine (but still no recovery mode) and then flashed to GB 2.3.5 with Kernel 2.6.35.7-I897UCKK4-CL614489 via "kh3_heimdall_cwm-One-Click_GB_2_3_5.jar"
Phone works OK now but I still can't get into RECOVERY mode. Unless I am mistaken, there are no ROMS available later than GB that can be flashed via Odin- all of the later ROMs need to be installed from recovery mode. The point of all this is that I want to try upgrading to ICS or JB but can't figure out how to do it without a way to get into recovery mode.
So the question is: How can I get recovery mode to work?
And: How can I update the ROM with no way to get into Recovery mode? Is it even possible?
Returning the phone is obviously out of the question as it is "obsolete" and I am not the original owner.
Thank you for any helpful insights.
captivated hippo said:
I have searched for the last 24 hours on this site for any mention of this problem and found nothing. I apologize if it has been covered elsewhere and would appreciate a link if I should be there instead of here. I am new to this forum.
I have an AT&T Captivate that I bought used for my wife. It was rooted and running some version of non-official Gingerbread when I got it (so it had been messed around with).
I have never been able to get into RECOVERY mode having tried every conceivable button and timing sequence at least 1 million times (3-button neutered?). I also have Android SDK installed on my PC and can send the "adb reboot recovery" command but it locks up at the AT&T screen and won't go any further so the PC is talking to the phone but the phone refuses to obey. Yes I have tried different USB ports and cables, un/reinstalling drivers, etc. The weird thing is that I can get into DL mode easily with the batt out, vol+/-,USB cable trick.
I originally took the phone all the way back to a stock Froyo ROM via Odin which appeared to work fine (but still no recovery mode) and then flashed to GB 2.3.5 with Kernel 2.6.35.7-I897UCKK4-CL614489 via "kh3_heimdall_cwm-One-Click_GB_2_3_5.jar"
Phone works OK now but I still can't get into RECOVERY mode. Unless I am mistaken, there are no ROMS available later than GB that can be flashed via Odin- all of the later ROMs need to be installed from recovery mode. The point of all this is that I want to try upgrading to ICS or JB but can't figure out how to do it without a way to get into recovery mode.
So the question is: How can I get recovery mode to work?
And: How can I update the ROM with no way to get into Recovery mode? Is it even possible?
Returning the phone is obviously out of the question as it is "obsolete" and I am not the original owner.
Thank you for any helpful insights.
Click to expand...
Click to collapse
Since you have no problems getting into download mode I suggest you start by going to this link... http://forum.xda-developers.com/showthread.php?t=1300843 Go to the third post and download the Odin one click of KK4 with bootloaders.
After you do the one-click back to stock go to this link... http://forum.xda-developers.com/showthread.php?t=1294477&highlight=corn+kernel and get the odin flashable version of 7.06 or 7.0A and if you don't already have Odin you'll of course need that too. Get yourself back into download mode and flash that kernel and it should give you back your recovery via the 3 button combo.
Worked! (eventually...sort of...)
m1batt1 said:
Since you have no problems getting into download mode I suggest you start by going to this link... http://forum.xda-developers.com/showthread.php?t=1300843 Go to the third post and download the Odin one click of KK4 with bootloaders.
After you do the one-click back to stock go to this link... http://forum.xda-developers.com/showthread.php?t=1294477&highlight=corn+kernel and get the odin flashable version of 7.06 or 7.0A and if you don't already have Odin you'll of course need that too. Get yourself back into download mode and flash that kernel and it should give you back your recovery via the 3 button combo.
Click to expand...
Click to collapse
m1batt1,
Thank you sooo much! It ALMOST worked!
- DL'ed Odin 1-click KK4 w/BL's as suggested, ran it, it failed and semi-bricked my phone... (phone--/!\---comp). Doh!
-Figured you were on the right track so DL'ed "I897UCKK4 Odin One Click - Stock, CONTAINS Bootloaders, Re-partition, Full Wipe" from 4-2ndtwin's post further down the same thread.
-after much anxiety and messing about to get it to connect, it successfully flashed!
-For the FIRST TIME EVER, I can get into recovery mode!
-followed up with corn kernel 7.06 as suggested with no problems
-now that the phone works as advertised, time for JB!
The funny thing is, I went back to stock ROMs several times and recovery never worked until now... go figure...
^
...then it had to be that KK4 one click in that 3rd post that fixed the prob.
Sent from my SGH-I897 using xda premium
I'm glad it got you back up and running! Now get your JB flash on! There are plenty to choose from for our "ancient" captivates.
One word of advice though. Coming from the point you're at now any JB ROM you flash will likely knock you into a boot loop on the first flashing attempt. Nothing is wrong just three button into recovery and flash again.
Sent from my SGH-I897 using xda app-developers app
And back up the efs folder, just in case.
It contains the vital IMEI info. :thumbup:
Sent from my SGH-I897 using xda premium
Thanks a million guys! Slim bean 2.9 up and running!
It Works!
Got to Slim Bean 2.9 through Cyanogen 9.1 and installed the Slim_GApps.
4-2ndtwin: Thanks for the suggestion to back up the efs folder. I hadn't done that before and now I am feeling VERY lucky that my phone still works at all! It lowered my stress level appreciably plus it was good practice using SDK.
m1batt1: Thanks for the heads up on the double flashing of JB ROM! It saved considerable unnecessary panic (although it was still somewhat unnerving)!
Consider both your thank you buttons righteously whacked! :good: