This morning I updated to 2.2 JPK using ODIN. Worked perfect all day, rebooted device, would not load anything past "sgs" and "S" went to black screen, only thing active was the led for two bottom buttons. Tried rebooting, pulling battery, factory reset cleared cache. Before it crashed I received a message that said "internal sd removed" tried flashing it again, tried a few other newer versions of 2.2, even tried downgrading to 2.1. Now, whenever I connect to my pc the battery icon appears, then dissapears, then appears... I cannot put it in "Download" mode anymore either. If I pull battery then power on, it just shows first samsung i9000 screen then turns off. Any suggestions? Called samsung they were useless, said I would have to take back to the dealer, however It is a bell mobility phone, I unlocked it and have been using with Rogers for a month. I offered to pay for them to take the phone and load the stock firmware but rep at samsung said I would have to send it through a dealer. Am I better off just putting it on ebay and let someone else deal with the BS?
It sound like a broken sgs.
Some sgs(bell) tend to break the internal sdcard. The only solution for that is to send it to repair.
Sent from GT-I9000 jpo. My own kernel for z4mod and with 342MB Ram
So This morning I decided to give my phone a restart, when I am holding the button to turn the phone one and the samsung boot screen comes on (the white one thats says I896 and samsung in white) and then after that it just goes blank and you can here it play that noise that it would normally make with the samsung boot screen.
After waiting on the blank screen for a few minutes I touched the buttons and the button lights came on. I pulled out the battery and I was able to boot the phone in the recovery screen where i tried to clear all user data and clear the cache, this did't change anything.
This phone was on android 2.1 stock build for rogers, with z4root and oclf (oneclicklagfix) v2 or v2.2 i think. I bought this phone on sunday so it is pretty new.
I am wondering what I should do about this, I spoke to my friend and he said He should be able to fix it with odin and even put 2.2 on it. If anyone has ever had this happen to them or they know anything about it i would be happy to know.
Rather than having your friend void your warranty, why not just return it?
if he purchased it from a reseller such as craigslist or ebay, then he might not be able to take his phone in though. Odin1click to stock usually solves soft-brick like issues though..
The USB cord was removed from my phone in the middle of an Odin restore (it was stuck at factoryfs.rfs). Now the phone won't boot and it isn't recognized by my computer when plugged in. Did I find a way to brick this thing? Any help would be appreciated. This is my fourth Captivate and I'm sure AT&T is going to start to give me a hard time. Thanks.
build a jig or buy one on ebay. you need to get into download mode and reflash to sotck.
http://cgi.ebay.com/ws/eBayISAPI.dl...47234&ssPageName=STRK:MESELX:IT#ht_511wt_1139
http://forum.xda-developers.com/showthread.php?t=731989
Try all 3 methods to get into download mode first
yes, you can try the key combo first. but as i know, build 1010 or later wont work for the key combo.
Got it back to d/l mode. Now it's stuck at factoryfs.rfs-same as last time. I'm finished with this phone. AT&T can send me another. This is what happened to the past two phones. Stuck on a Odin restore and can't get it up again.
Edit: Just booted up. That's a relief. Thanks.
Thare187 said:
Got it back to d/l mode. Now it's stuck at factoryfs.rfs-same as last time. I'm finished with this phone. AT&T can send me another. This is what happened to the past two phones. Stuck on a Odin restore and can't get it up again.
Click to expand...
Click to collapse
If it had happened on more than one phone, you may consider looking at odin...maybe remove and reinstall our check your drivers or computer...just double check all of little stuff that might be so obvious that they are not obvious
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5 1200 mhz/100hz kernel
so if your potentially bricking the phones, what do you tell AT&T that happened? and do they not ever check or whats the deal?
As far as I know at the wareenty centers they check for physical and water if they do attempt to boot as long as nothing looks custom they wont bother with checking the recovery or key combos samsung takes care of the rest they just want functional hardware..oh dont mention anything about modding. If anything syncing crashed is the best explaination. Tested.
Sent from my replaced cappy XD
Just dont become a familair face or it might get flaged on your account. Study up before doing somthing new. Just crashed my test cappy writing this had to stop and reflash heh live and learn.
A tech here on the forums said they can tell if it has been modified in just "3 clicks".
Sent from my SAMSUNG-SGH-IDK?
noobfail said:
A tech here on the forums said they can tell if it has been modified in just "3 clicks".
Sent from my SAMSUNG-SGH-IDK?
Click to expand...
Click to collapse
Lol....uh huh....i also have a direct line to the white house
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5 1200 mhz/100hz kernel
Omg really?!
Sent from my SAMSUNG-SGH-IDK?
Just messin' around....what kind of tech? Att, samsung or other?
********
Sent from my Samsung Captivate using the XDA app
ROM: Paragon RC5 1200 mhz/100hz kernel
He said he was a manager of an actual at&t walk in tech support store.
I rooted a phone and flashed to stock and returned it with no problems.
Sent from my SAMSUNG-SGH-IDK?
Sorry I'm late getting back. My phone is up and running again. Got in to D/L mode and flashed back to stock. Got stuck on the AT&T logo, but used Odin one more time and it booted right up. The first time I brought in the phone, the tech took it to the display for 2 minutes and called the warranty dept for me. I think that it helped that the Chiefs playoff game was on. They didn't seem to want to be bothered! The phone rep asked about water and physical damage. No questions about modding. The second time I did it at home over the phone. Again, no questions about modding. I told the rep both times that I was trying to transfer music to the phone via Kies and it crapped out on me. It always help to play dumb and act like you don't know too much.
Thare187 said:
Sorry I'm late getting back. My phone is up and running again. Got in to D/L mode and flashed back to stock. Got stuck on the AT&T logo, but used Odin one more time and it booted right up. The first time I brought in the phone, the tech took it to the display for 2 minutes and called the warranty dept for me. I think that it helped that the Chiefs playoff game was on. They didn't seem to want to be bothered! The phone rep asked about water and physical damage. No questions about modding. The second time I did it at home over the phone. Again, no questions about modding. I told the rep both times that I was trying to transfer music to the phone via Kies and it crapped out on me. It always help to play dumb and act like you don't know too much.
Click to expand...
Click to collapse
I had the same exact problem when i was just starting to mess around with roms and my biggest issue was the sequence that it took to flash properly. i kept opening odin then putting my phone in download mode and THEN plugging it into use as opposed to how it should have been which is holding vol up and vol down pressed then plugging in usb.
bugity said:
I had the same exact problem when i was just starting to mess around with roms and my biggest issue was the sequence that it took to flash properly. i kept opening odin then putting my phone in download mode and THEN plugging it into use as opposed to how it should have been which is holding vol up and vol down pressed then plugging in usb.
Click to expand...
Click to collapse
That's the weird thing. I'm somewhat new, but have been flashing my Captivate since Sept. When the original Cognition came out I was flashing daily. I think my problem was, it took longer than usual to flash to stock, I got impatient and didn't realize I could get to D/L mode by taking the battery out, holding power and inserting battery. I always used the button combo. Live and learn.
same problem
Ok i have the same problem as the original post stated, running odin and disconnected right at the beginning of the rom flash! this phone wont power up, and my jig (which i have used before) will not work! Is it done for!?
Ur last hope lays in adams Am I bricked thread, where u'll find an app that checks what state ur phone is in (linux or ubuntu needed)
nevermind, I tried harder and the jig worked, its one of the homemade jigs, where you cut up your charger, and use resistors to create the circut . . . . jankety but i got it to work thanks anyway though
Glad you got it, but I would buy a jig and keep it in a drawer. Just in case.
Hi,
I am running a custom ROM (Darky's 9.5) on a rooted Galaxy S with Voodoo Fix. All has been fine for the past week since I changed to this ROM.
However, today, suddenly the phone switched off and then immediately turns on by itself and as soon as the Galaxy S screen appears it restarts again and the loop continues.
I removed the battery, but as SOON as I put the battery back in, it turns on by itself and resumes the on off sequence.
So its IMPOSSSIBLE to get into recovery mode, it doesnt work even though I have it enabled. I can get into Download mode but it lasts 5 seconds as the phone switches off and back on.
I can connect via USB to computer in download mode, but like I said it lasts 5seconds.
Is my power button jammed or is there something sinister going on? lol
Doubt I have warranty as I bought it off eBay many months ago...
Thanks for any advice!
Here we go again yet another Darky broke my phone post .
You have no warranty full stop as you flashed a custom rom ..
Usual fix for dead Deadlys rom is flash stock Froyo 2.2 rom via Odin with pit 512 and repartition checked .
However as you cannot get to download mode i would try first factory reset .
Second three button download recovery jig from .
http://forum.xda-developers.com/showthread.php?t=819551
You could always ask Darky .
jje
Thanks for your response.
Don't know why the ROM would behave like this a week after being ok, perhaps an app has caused the issue to surface.
I cannot do a factory reset, the phone is in a continuous loop off switching on then restarting within 5 seconds. It doesnt get past the initial Galaxy S boot screen.
I shall get my hands on a JIG in a couple of days. Not sure how that will stop the loop but worth a shot I suppose. If that dont work, this phones dead isn't it?
UPDATE: SOLVED.
It resolved all by itself. Basically, I got fed up and I left it to loop back and forth from the boot screen....and after a few minutes I returned to the phone screen to find it had booted up fully to the normal desktop.
Very strange. I might just have a dodgy phone.
So my phone was in a boot loop a while back and I fixed it by restoring my back up boot. I had never flashed a rom or a kernal to my device and ran very few root apps on my phone. So I was texting my woman a picture of two of her kids and my screen went black and my phone was unresponsive. I tried to boot into boot loader and nothing happened. My phone doesnt respond to anything. No boot loader, my pc cant find device, i cant turn it on, the charge light doesnt turn on (and i know my charger works). Is there any way to fix this problem? If not will AT&T honor my warranty? I heard the phone is a ***** to take apart and it doesnt have water damage or anything i have no clue what happened to it. Am I screwed or can I get them to replace this device. Any personal experience with my carrier would be amazing. Thanks so much guys. I'll be checking back frequently as I want to get the phone fixed ASAP.
Justkevin09 said:
So my phone was in a boot loop a while back and I fixed it by restoring my back up boot. I had never flashed a rom or a kernal to my device and ran very few root apps on my phone. So I was texting my woman a picture of two of her kids and my screen went black and my phone was unresponsive. I tried to boot into boot loader and nothing happened. My phone doesnt respond to anything. No boot loader, my pc cant find device, i cant turn it on, the charge light doesnt turn on (and i know my charger works). Is there any way to fix this problem? If not will AT&T honor my warranty? I heard the phone is a ***** to take apart and it doesnt have water damage or anything i have no clue what happened to it. Am I screwed or can I get them to replace this device. Any personal experience with my carrier would be amazing. Thanks so much guys. I'll be checking back frequently as I want to get the phone fixed ASAP.
Click to expand...
Click to collapse
If the device is still under warranty they should be able to give you a new one. Call att. tell them what happened they would probably send you a new charger at no cost. since you already know whats going on, all you gotta do is take it to a att repair shop. before you get the new charger of course.