Going to finally get around to taking my Captivate to an AT&T Device Support Center to get it replaced due to random shutdowns. Currently running Perception build 5, so I was going to flash to JF6, master clear, and then update to JH7.
Was wondering if there was anything else I should flash/clear/reset before going to get it replaced. Thanks.
Was it randomly shutting down on stock?
Yep. Have had random shutdowns on every single rom I've used: stock JF6, ota JH7, Cognition 2.1X, Cognition 2.2X, Darky's Raw Steel (multiple versions), Doc's (multiple versions), Perception (multiple builds).
Yep, that's a warranty. Getting back to JH7 should suffice. Good luck.
Hah. So I flash back to JH6, do a master clear, and start an ota update to JH7. Updater says the phone will reboot. It turns off, AT&T logo comes on, and the phones dies. I can get no response out of it whatsoever now, no power at all. Tried the jig also, no response. Shouldn't be any problems with the warranty tomorrow, just rather ironic that their update bricks the phone the night before I go to get it replaced.
Related
I see the update is failing for a lot of people on the Samsung Captivate. Mine was reflashed using Odin3, and the update failed like so many others. I reflashed using Odin3 again, tried the update, and the same exact thing happened. The update fails at 50%.
The first time around, I was rooted and lagfixed, I tried it that way, then unrooted and tried again.
The second time around, I made absolutely no changes to the phone whatsoever, except signing in to my google account, and upping the screen timeout to 30 mins.
Doubt that this information is helpful to anybody, but was hoping maybe these symptoms would point to a trend as to why so many people's Captivates can't update.
Also, how many of you that failed used an Odin3 reflash any time before it failed?
I just flashed back to stock using the Odin One Click program and my updated failed at 50%. I tried 4 different time with the same result. I even reflashed a second time, did a Master Clear, and a Factory Reset. Stil no joy.
This morning as soon as I saw the news of the release I immediately hit the software update in the settings menu. Downloaded and just before I went to install I decided maybe it would be smart to do a rom backup with rom manager. Did that, and went ahead and then attempted to install it. It got to 100% and then said update failed, rebooted, said the same thing, update wasn't successful. However, if you checked about phone, it said it was jh7, but none of the jh7 stuff was there. The phone was rooted, sideload enabled, clockwork installed, and bloat removed, that's it. Never flashed a rom or lag fix or anything like that.
At this point I decided to try using the odin one click to stock jf6. Installed it, and tried to update again. Now, I'm getting what most people are getting, update fails very quickly at 50%, the phone reboots with no changes.
So I decided to use my clockwork backup, and restore my phone back to what it was before all this started this morning. Of course, since I remembered to do the backup AFTER downloading and postponing the update, it's sitting there waiting to go. Decided to try it and see if it acted the same as this morning, and now it's doing what it did right after the jf6 one click, gets to 50% and then fails with no effect.
How complete a wipe/restore of the phone is using rom manager? Because the update behavior on mine is different now after messing with odin than it was before, even after restoring it with rom manager.
Rooted with Sideloading on JH2. Not much else done to my phone. It has always worked well.
I didn't even get a percentage when trying to install. Just reboots and says "Update Failed".
Same issue here. Flashed back to JF6 using Odin one click. Update fails at 50%.
Only thing i can think of its that, that particular fw in odin is not the original fw flashed on the phone when bought and it does some sort of checksum or some kind of check.
50%, puke, and now when I click on update it tells me no firmware which I think is funny.
has anyone tried the firmware from
http://forum.xda-developers.com/showthread.php?t=777291
?
I don't have a PC at work (or even a x86 Mac) to play with.
Mine did the samething. I've used the the one click reinstaller a few times after trying out different roms. Maybe the one click installer changes something and it's blocking the update from totally completing. I hate to reinstall everything again but maybe theres a better way to do a total factory restore so we can get the update.
I'd guess that if it's doing a difference update (just applying the new stuff, not a full ROM) it needs a checksum match to be sure it doesn't bork the phone. Failing that (i.e. anything different from a pure stock phone) it will abort at some point.
There is a pure JF6 stock rom linked somewhere here on the forum--I'll see if I can find it, but it was never stickied or anything. Some guy just uploaded it because the one-click wasn't "pure" so to speak.
I guess this is their way of saying "you don't like our firmwares in the first place, you don't get this one either!"
Mine did all the same as you guys , failed at 50%. So I just got a new phone from att , told them it keep failing update. Did update right in store on new phone and boom installed no problem. On top of that gps is dead on, on new phone with update. Didn't get to try with out update. Already made sure I can get into download mode, no problems there. Note just scared to flash any roms since gps is perfect lol.
Sent from my SAMSUNG-SGH-I897 using XDA App
Omg and no xda force close lol . Also rf cal date is 7/10/2010 , old phone rf cal date was 8/07/10
Gps couldn't lock to nothing.
Sent from my SAMSUNG-SGH-I897 using XDA App
I tried using the Samsung Kies program and it says "this device's version cannot be updated". I'm wondering if that one click installer is not what it should be. Maybe if we flash to a different Captivate firmware the Kies program will update it.
I agree, I just like the way the one click installer worked. I know there's other roms/kernels posted, and I guess I'll have to do some legwork here. Here's hoping.
Just reflashed back to stock for the third time using Odin3 One Click and now when I check for updates it It says No Updates Available. Prior to this, it would dwnload the updated and reboot the phone and fail at 50% while installing. Frustrating!
I never use the 1click odin, I always put the .pit and the JF6 file into the 'normal' odin and use that -- haven't seen if anyone has tried that yet anywhere? Maybe that'll work.
BTW I still have no update available even after calendar trick :/
Hey guys, I did root my captivate. My question is do I need to un-root the device to apply the gps update or it does not matter.
Just downloaded JF6
how would I flash this back to my phone?
sorry if thats a stupid question but I cant find an answere seraching
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
cellgeek said:
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
Click to expand...
Click to collapse
Let me know how that goes. (Have family up in FloMo, very great place btw).
cellgeek said:
I downloaded JF6 from Samfirmware.com. I'm going to back up my current ROM, then do an Odin w/Repartition and use the JF6 from Samfirware.com.
We'll see if that works. . . .
Click to expand...
Click to collapse
Tried this a little while ago. I went to run the update and now it's saying that no updates are available.
I spent about an hour on the chat window with ATT support and they can't seem to find a way to reset it to push again. The guy on the other end was knowledgeable as far as I could tell.
hell - he even mentioned froyo. He said they have ALOT of information on it for the captivate but no release date yet.
Hey all. So after 1 month without my phone, I finally got it back from Bell. It's good to have it back!! Before my internal memory died, I was running Docs Rom, and I was actually quite happy with it. Now that the phone is back, it has the stock firmware on it. Im debating if I want to put on Hardcore, or update to the new 2.2 bell and call it a day.
Are we seeing a good reason to use Hardcore's Kernel vs the Stock JL2 Rom?
For those I9000m users who had their phone die, did you mod again, or stay stock?!?
I got mine back with JK4 on it, so I updated it to JL2 right away via Kies. I'm running Hardcore's SpeedMod K12L kernel with the /data lagfix enabled for the last few days without any issue.
Thats exactly what I was planning.
Hope it works out! Thanks for the feedback, makes me feel not so crazy for hopping back into modding after losing my phone for a month!
Whats the worst thing thats gonna happen you get a new phone and $100 credit to your account ? Happy Flashing ;p.
Upgrade to JL2. Apparently fixes the SD card issue, and it's quite fast.
Been running a custom JL2 ROM for a few days and it's great; I'm quite impressed. I was running a custom JPY ROM on a previous phone before it died.
I'd like to flash to Cog 3.04 directly if possible without Odin'ing back to 2.1. Is it ok to flash directly to 3.04 and if so, what the best way to wipe everything first to start form as blank a state as possible? I'm without a windows PC right now...
Thanks!
hate to bump but if anyone can provide a quick answer... thx.
I flashed 3.04 over 2b8 without any problem.....
You can try that but no guarantee that it will work.you may run into problems and have to flash back to odin then you will be sol with out a computer
Sent from my SGH-I897 using XDA App
You should be fine flashing from one version to another. If you enabled lagfix I'd disable that first, and to be on the safe side do a CWM backup, but other than that you should be fine. I've been flashing another ROM back and forth without going stock many times without issue.
You can go and flash custom ROMs on top of each other and it might work, but don't be surprised if you boot into Cog 3.04 and have to deal with a bunch of force closes or other weird behavior.
I ALWAYS recommend people flash back to stock and Master Clear/GSM Master Reset. That gives you a blank slate to work with. It takes less than 10 minutes, but some just believe that's too much work/time for them.
Your call.
I've never had an issue flashing updates on top of Cognition. I'm pretty sure as long as your lag fix is the same between versions then there should not be any problems.
I flashed serendipity 5.0 over 4.3 last night with no problems. I just disabled lagfix before I did.
Sent from my SAMSUNG-SGH-I897 using XDA App
Thanks everyone for your helpful input.
Is it possible to master clear without going back to stock? I'd like for everything except the external sdcard to be cleared.
Hello. As you can see from the title, I am stuck at the sgh I897 bootscreen. No matter what rom I flash I still get stuck unless i flash ultimate 7 tims tweak which I don't want because TiBu keeps erroring. I've tried Odining a thousand times. Oh and did I mention i'm leaving for vacation in 3 hours? Yea so time is kinda a factor. I'm not freaking out if you get that tone from this thread, but i'm kinda aggrivated, as this is the last thing i need to worry about. Any help is appriciated, and if you have the time, throw in the name of the best battery life on what rom just in case I get stranded in the desert and my phone has been on for 24 hours lol.
You are going back to stock but other roms won't install
Yes. I odined and then I flashed some Roms from my SD like I always do and then it got stuck.
EDIT: I flashed continuum, darky's and serendipity and they got stuck. But I flashed Andromeda, and it worked.
How long are you getting stuck for because some roms take a little longer on the first boot due to file conversions and initial install.
Longer than normal. About half an hour before I lose patience.
Hello astute folks on XDA!! My name is Brian and i'm a flash-a-holic. I'd like to share with you my experience that ultimately lead to me fubaring my beloved captivate.
I've flashed everything under the sun on this phone from roms to different kernels to modems. You name it, i flashed it with great success (after researching, never flashed on a whim.) UNTIL... Yesterday.. lol.. I was running a leaked 2.3.4 gingerbread rom and i noticed the problem first starting while trying to connect my phone to my computer via usb. The two didn't communicate when for the last 6 months, every single time i plugged in, my computer and phone recognized each other every single time. So that was my first clue that something aint right. Next thing i did was power the phone off. Went to turn it back on and NOOOOPPPEEEEE!!! Nothing!!!!! Held all three buttons and the little grey circular icon came on (the one that is initially in the battery icon when the phone is powered off but it's plugged in) but immediately shut off. Nothing turned my phone back on, but i was able to get into download mode. So thats what i did. I used odin3 oneclick to go back to stock eclair thinking that that will start everything all over, erase the bad/corrupt files and so forth. Flash was successful. Got back to stock eclair and got stuck in MTP initialization (you know, the screen in which you get if your debugging mode wasn't checked.) But it hung on that screen. No buttons would allow my to exit so, I pulled the battery. Then, the same damn thing.. I could NOT get the phone to power back on. Lesson learned for me. (today i learned that going back to stock is NOT a fresh install.) Used odin again, but this time unplugged my cord BEFORE i got to the eclair boot screen. As i'm peering at this home screen, i noticed that my USB connecting notification was flashing on, off, on, off yet my cord was unplugged. At this point i called tech AT&T tech support because i knew i was screwed. (i told them i tried to update to the 2.2 they provided on website and the phone cut out, lol).. I spent an hour on the phone and got no where other than determining that my phone is farked and they are gonna send me out a replacement (which will take 4 to 6 days) because luckily it was under warranty still. Tech support couldn't get my phone to turn on, but i could, lmao.. So... here i am stuck with a phone where usb debugging mode is buggin out!!!!!!! To wrap this story up, what i did was got back into download mode and flashed gingerbread bootloaders and a kernel and voila!! So long as i don't turn my phone off, i have a fully operational phone until my new cappy arrives in the mail in 4-6 days. (Dicks.. If i had been ordering a new phone, i'd have the option for next day shipping but thats another story.)
TLDR: Flashing too much will get you in a bad situation. Stick with a rom/modem/kernel setup that suits your needs because your next flash could be your last depending on the components in your phone.
EDIT: MAKE IT KNOWN THAT I HOLD NO ONE RESPONSIBLE OTHER THAN MYSELF FOR THE FUBARING OF MY CAPPY!!!!!!!!!!
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Things break...and ppl make mistakes... I'm still trying to figure out which one happened in your situation.
Sent from my SGH-I897 using XDA Premium App
That's a common hardware issue with the captivate. Happened to me twice. Its just the USB port spassing out thinking tthe cable is constantly getting plugged in and unplugged and freezing tthe phone with its craziness. Both times it was replaced under warranty. I'm paranoid it'll happen again now that I'm out of warranty.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
speedy_11 said:
Ok!?! This is not a question, this should be in the general thread if anywhere.
Could a moderator please move this.
Click to expand...
Click to collapse
Oops, my bad!! It needs to be somewhere as a precaution to those that think flashing is completely harmless
EDIT: upon further contemplation, it really is a question of what went wrong
Sent from my GT-I9000 using XDA Premium App
I am a flash addict as well
i have flashed all froyo based roms on my cappy !
Can anyone confirm that excessive flashing may risk my phone?
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Thanks for the quick response....!
now i dont need to worry
xijar said:
Doubtful that excessive flashing had anything to do with this. Just be sure to do all necessary wipes and take all the required steps before you flash a rom and you SHOULD be okay. You are always taking a risk when you flash your phone regardless of how many times it has a positive outcome.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I'm 99% sure my board failed because of cheap, unreliable components. However, that 1% is still in the back of my mind that it could have been from something I flashed. I suppose I'll never know.
Sent from my fubared, soon to be replaced cappy running GT-I9000 gb rom using XDA Premium App
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Accidental post. Please delete.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
xijar said:
It is hard to tell from what you say that it was purely hardware. Definitely sounds like the issue locked up the phone more then it did mine the two times I experienced it but it definitely wasn't performance friendly to me either. It seemed to settle down for,me intermittently then act up again. I never lived with it for too long since there's a warranty center i can do a walk in exchange at less than a mile from my house.
PS. I would flash stock jf6 then update via kies if possible before you send iit in to avoid being charged $500 for voiding the warranty. If kies wont work flash jf6 and find the jh7_ota.zip file floating around the forums to flash stock jh7 In cwm then remove cwm. There is a zip file that restores stock recover. I can provide these files if you can't find them not sure if they still have active dl links.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
As I started before, the phone is fully functional with gingerbread other than the occasional usb flickering..Only problem I have with it really is if I turn the phone off, it won't turn back on unless I hold power and volume up, enter cwm and then select reboot now.
Before I send it back, I'll odin back to jf6 first with oneclick. Without cwm on the phone, lol, it absolutely won't turn on by just using the power button. I made sure of this before I even called the warranty department and explained my dilemma
The nice thing is that I can use the phone while I wait fire the new one to arrive AND I can flash and experiment with everything now without worries!!!
Sent from my fubared chappy running GT-I9000 GB rom using XDA Premium App
I am also a flash-o-holic and I think that if you flash with odin lots with repartition checked or are enabling/disabling voodoo lots, it can mess up your phone. Has happened to me twice, just sent my phone today for the second time. Both times this happened to me it happened when successfully flashing back to stock with 512.pit and repartition checked. On boot up it stalls at the "S" screen and never goes past it and in recovery I get some errors like:
error: can't mount /dev/block/mmcblk0p1
error: can't mount sdcard
I flashed many different firmwares with different pit files and different android versions but all conclude the same, stuck at the "S" boot screen.
I have determined that the partition tables were messed up and I tried to fix it by putting parted on my phone and trying to repartition it from the shell. Both times I get the "unable to write to /dev/block/mmcblk0 - I/O error!" Also, from CWM Recovery I try repartition sdcard but it also comes up with an error. The last time I sent it into Samsung repair they had to replace the main board to get it working properly again. Think it is definitely a good idea to find a rom / kernel / modem you are happy with and stick with it for a while.