Database Develop

[Q] Trying to switch out my captivate and have a few questions

I'm having a lot of issues with my phone running horribly and whenever I plug it into my computer it tells me that my internal storage needs to be scanned and fixed. So either my card needs to be formatted or it's going bad. I'm assuming this could also be the cause of my phone some time taking ~10 minutes to turn on. So I have a few questions:
1) can I completely format my card and still have stock experience for exchanging it? *I went ahead and did this because I'm impatient. seems to be working and I'll keep testing it and go from there*
2) I did root and flash custom roms on it before but the rom i'm running now is a flash of the original rom on my phone but rooted. Then I updated to JH7 and it got rid of the root. When I went into the store previously and had issues with it, the guy mentioned that I had a different IMEI from what they had registered. I'm not sure if this is due to the fact of flashing or if it's from having to get the first captivate exchanged for another one. Are there any steps I can take to ensure that everything is in correct order and there's no way to see that anything has been tampered with.
Any other advice on things that should be done before going to a ATT warranty store would be greatly appreciated.

Mantu13 said:
I'm having a lot of issues with my phone running horribly and whenever I plug it into my computer it tells me that my internal storage needs to be scanned and fixed. So either my card needs to be formatted or it's going bad. I'm assuming this could also be the cause of my phone some time taking ~10 minutes to turn on. So I have a few questions:
1) can I completely format my card and still have stock experience for exchanging it? *I went ahead and did this because I'm impatient. seems to be working and I'll keep testing it and go from there*
2) I did root and flash custom roms on it before but the rom i'm running now is a flash of the original rom on my phone but rooted. Then I updated to JH7 and it got rid of the root. When I went into the store previously and had issues with it, the guy mentioned that I had a different IMEI from what they had registered. I'm not sure if this is due to the fact of flashing or if it's from having to get the first captivate exchanged for another one. Are there any steps I can take to ensure that everything is in correct order and there's no way to see that anything has been tampered with.
Any other advice on things that should be done before going to a ATT warranty store would be greatly appreciated.
Click to expand...
Click to collapse
1) yes
2) Flash back to 2.1 using ODIN and you should have everything stock including your IMEI. Not JH7 but JF6.

Hopefully you backed up your stick settings prior to flashing. Sine custom roms change your product code and imei. Flashing with ODIN will not fix the product code. I'd the imei is correct I highly doubt that the tech and the DSC knows about checking the product code but you never know. Search around XDA there has been plenty of posts surrounding this topic.
Sent from my SGH-I897 using Tapatalk

Fatal flashing addiction

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.

Warranty help

I flashed a few roms, and I have an efs backup for imei/product code, but for some reason they won't restore, my phone is running fine on stock 2.2 froyo (unrooted), but I was wondering if there is anyway to get a new phone, so I can have an actual imei and use kies.

If you have just flashed roms and not modified your imei I don't see why it would be incorrect. Mine has never altered throughout many flashes. There is definitely some good threads on restoring imei In tthe development forums but If you can't figure it out and really crave your factory imei mobiletechvideos.com has a imei restore service for $30.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

xijar said:
If you have just flashed roms and not modified your imei I don't see why it would be incorrect. Mine has never altered throughout many flashes. There is definitely some good threads on restoring imei In tthe development forums but If you can't figure it out and really crave your factory imei mobiletechvideos.com has a imei restore service for $30.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I tried the technique that mobiletech uses, but I lost my efs backup folder now, and it won't restore without that. I also cannot get the product code to stick. I want a new phone....warranty help please.

When I get home ill look more into imei restoring. With no backup it might be hard. I have an efs backup on my PC in thecase something were to happen to my internal memory. can never be too careful. Curious though, why did you modify your imei? Still not too clear as to why people do this.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

xijar said:
When I get home ill look more into imei restoring. With no backup it might be hard. I have an efs backup on my PC in thecase something were to happen to my internal memory. can never be too careful. Curious though, why did you modify your imei? Still not too clear as to why people do this.
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.
Click to expand...
Click to collapse
I didn't do it on purpose, for some reason a long time ago I must have performed a bad flash.

Upon further research I see what you mean. Looks like this happens with bad flashes and with no backup it looks like the hex editor method located herehttp://forum.xda-developers.com/showthread.php?t=881162 is your only hope. You say you have tried this on jf6 rooted and no success?
Sent from my i897 running MIUI 1.8.12 with TalonMTD kernel.

I took an /efs backup from my first capitvate. I ended up sending it back to amazon as I had that infamous problem with the first OTA bricking phones. When I got my second, an I9000 rom changed my product type in my nv_data.bin. I saw an /efs backup on my SD card, forgot it was from my first phone, deleted /eft and tried to recover from the backup. I ended up with the test IMEI
I flashed back to JF6, called samsung, told them my IMEI became corrupt from a firmware flash and they asked me to send them the phone. They paid shipping both ways and fixed my IMEI in a week (they simply changed out the mainboard which seems to be a common fix for them).
Provided that your indicator strips are still white and there is no physical damage, I would imagine they would do the same for you too.

z28james said:
I took an /efs backup from my first capitvate. I ended up sending it back to amazon as I had that infamous problem with the first OTA bricking phones. When I got my second, an I9000 rom changed my product type in my nv_data.bin. I saw an /efs backup on my SD card, forgot it was from my first phone, deleted /eft and tried to recover from the backup. I ended up with the test IMEI
I flashed back to JF6, called samsung, told them my IMEI became corrupt from a firmware flash and they asked me to send them the phone. They paid shipping both ways and fixed my IMEI in a week (they simply changed out the mainboard which seems to be a common fix for them).
Provided that your indicator strips are still white and there is no physical damage, I would imagine they would do the same for you too.
Click to expand...
Click to collapse
So should I flash back to stock JF6, and send them my phone?

Reboot & Wifi "error" after 2 weeks of using any ROM

Hi all,
I've been unable to find a post about this for quite some time so I decided to make a threat about it.
I have a recurring problem with my captivate. Usually after about 2 weeks of using a ROM my phone will have 2 issues pop up simultaneously. They seem to always happen together. It seems to happen after my phone shuts off and will not turn back on until I battery pull. Once I do that I am presented with these two issues:
1.) When I try and toggle Wifi it attempts to then simply says "error" underneath it. I have found a few threads about this but no answers
2.) Upon installation OR restoration of any app with Titanium Backup my phone does a soft reboot (goes to spinning CM logo or for ICS goes to the multicolored squares flying around).
Edit: On the newest MIUI it now says "insufficient storage available" instead of rebooting when I try to install an app after the issues crop up, wifi "error" is still the same
I've had these same 2 issues occur with CM7 Stable, RC, and many nightlies, MIUI, and TeamHacksung's ICS build. I believe it may have happened with cognition too but am not positive.
I do not restore any data with TB. Before each flash I wipe system, cache, dalvik, and do factory reset and still this issue occurs without fail after about 2 weeks on any ROM and the only fix I have is to flash a new one.
Nandroid backups DO fix the problem. If anyone is willing to look through logs or something and see what was different I would be eternally grateful and certainly send you something through PayPal
Any help is greatly appreciated and I am willing to try anything at this point. Thanks!

Sorry for the double post,
Is there a better forum to post this in?

spectralite said:
Sorry for the double post,
Is there a better forum to post this in?
Click to expand...
Click to collapse
Nah this is the right place. That's a very strange problem you're having though, and I don't know what the exact solution is, if there even is one for this. The only thing I can suggest is going back to stock, and then reinstalling CM7 or whatever you want
Sent from my lightning fast Glitched 1.3Ghz CM7 i897 Captivate

Thanks,
Well happened again on newest MIUI. Gonna go back to stock and start over. I'll update the thread if it does or does not happen again.

Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance

spectralite said:
Unfortunately after using Odin to go back to stock and rerooting/flashing it happened again on the most current build of MIUI. I'm currently at a loss for what to do. Has anyone heard of or seen anything like this?
Thanks in advance
Click to expand...
Click to collapse
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.

I had this same problem with my fascinate. I flashed 1.10.21 MIUI follwed by glitch 13.1. This combination used to work, or so I thought. I flashed back to stock, 1.12.1 then a different package of glitch 13.1 and my wifi started working again. I know the captivates and fascinates are somewhat different, but try this out and see if it works.

bobbylx said:
Just curious, have you tried leaving it stock and seeing if it happens on a pure stock ROM? If so it could be a defect with the phone?
If you flash back to pure stock and the issue doesn't come back, maybe try a custom ROM that's closer to stock, not a CM or MIUI or ICS build. I haven't seen this issue, just trying to suggest some solutions.
Click to expand...
Click to collapse
I guess I could try that, I just like CM7/MIUI so much. Another thing that happens is many different applications start FCing after the problems all begin.
I tried to restore to a nandroid backup I had made before it happened this time and I received an MD5 mismatch which I believe happened last time I tried to restore...

New info:
I have not realized this before but it seems that I start getting a message that says, "Google Talk Authentication Failed", around the same time. Also FCs happen much more frequently. Is there anything I could be doing to cause this?

New Info
Just going to keep this updated with things I have tried in case anyone ever searches for this that has this issue:
Full format of SD card and odin back to stock did not prevent the issue from cropping up on the DarkKnight3 ROM with Icy Glitch. At this point I can only assume it is somehow hardware relatedl

No signal on Jelly Bean

Hi,
First post so please go easy!
I am currently running CM10.1 on my I9000 and for some reason there is no signal but IMEI is intact. I can't understand why this is as when I flash back to stock GB I get strong signal. The only thing that I think may be affecting this is that I recently repaired my IMEI via SRS whilst running GB and so there may be something (e.g. file/setting) that is not passed on/incompatible with JB. I have tried a number of different JB ROMS as well as many relevant modems with no success.
Any help is very much appreciated as I really want to get JB running correctly on my phone, I can't go back to GB now haha!
P.S I have a backup of the EFS folder so any suggestions involving this are welcome.

pricey888 said:
Hi,
First post so please go easy!
I am currently running CM10.1 on my I9000 and for some reason there is no signal but IMEI is intact. I can't understand why this is as when I flash back to stock GB I get strong signal. The only thing that I think may be affecting this is that I recently repaired my IMEI via SRS whilst running GB and so there may be something (e.g. file/setting) that is not passed on/incompatible with JB. I have tried a number of different JB ROMS as well as many relevant modems with no success.
Any help is very much appreciated as I really want to get JB running correctly on my phone, I can't go back to GB now haha!
P.S I have a backup of the EFS folder so any suggestions involving this are welcome.
Click to expand...
Click to collapse
Hi,
I guess you could restore the EFS folder backup and reboot.
Hope you have a great time on XDA.