Database Develop

Phone acting is up. Help?

Ok yesterday i got my i9000m. Rooted, and one click lag fixed. Stock 2.2 Froyo.
Today the phone would not wake up from sleep. Turned it off and on again and got past boot animation then just get a black screen (the buttons light up). Restarted a few times with same result.
Then i reformatted through recovery and rebooted. Got through to TouchWiz but it was very laggy and found no Google apps along with the phone saying there was no SDcard. So i reformatted again. Now the phone has the same problem, gets past boot animation but does not wake up.
Can someone please help me.

Do you know what build it was running? (JK4 or JL2)
If you got it through a store/Bell store, take it back and demand a new one on the spot. You've got symptoms of Internal SD card failure.
If you bought it off of eBay or some other source, you can try to take it in to Bell and hope they'll fix/replace it, or call up Samsung (1-800-726-7864) to send it in to them.
Best of luck.

I got mine today and right out of the box it was running JK4, the 1st phone they gave me was a boot loop, 2nd phone worked flawlessly, just return it if it's less than 2 week old they'll replace it on the spot

I bought it 2nd hand and im a rogers customer... :\ not sure if its JL2 or JK4
maybe a friend on bell can try and send it back for me?

Also I AM able to get into recovery and downloader mode. Suggestions?

You could try grabbing the official JL2 build and flash via Odin, if that doesn't help you could always call Samsung, they don't seem to care who you're signed up with and their turnaround time is apparently pretty fast.

got_milk said:
You could try grabbing the official JL2 build and flash via Odin, if that doesn't help you could always call Samsung, they don't seem to care who you're signed up with and their turnaround time is apparently pretty fast.
Click to expand...
Click to collapse
I agree you got nothing to lose..Flash stock and see how you go

Bricked. Like completely. Ugh...
Thanks anyways.

Disconnected from PC in the middle of Odin restore-phone wont' boot.

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.

[Q] Galaxys I 9000M sd card bricked ???

surprised it took this long, had counted myself one of the lucky ones.... even though i was one of the unfortunate saps whose phone came with the three button recovery disabled, (a two week trip to samsung for repair).... was running darky's rom 9.3 and various eaarlier versions since october with no problems... today google voice started force closing so i tried to reboot the phone and it would not boot up again... i went into recovery and tried a wipe, still no go.... then i tried to reinstall the rom, still no go.... when it is booting up it just keeps looping the loading screen and vibrates once, then pause, then three times... i can get into recovery and download mode.
anywhose my questions are this,
A) best way to determine that the SD is in fact bricked.....
B) best way to get a bricked SD card back to stock so i can send it back to samsung for warranty.
C) if i get it back fixed from samsung, should i try to off this piece of Sh*t phone that has given me, and others soooooo many problems. that is to say, has anyone who has had their phone fixed recently had their new SD card go corrupt again??
P.S. never buying anything samsung ever again, PERIOD!!, had a 30 inch monitor of theirs recently go bad as well, like i dont care if they cure cancer, bring peace to the middle east, and resurrect jesus!!! i still wouldnt buy a rememberance day poppy from them!!!!!!!

Sounds similar to mine when it bricked. The best solution is to use Odin and flash jl2 onto it and send it in for repair.
They were doing a replacement and compensation program through bell for a while but I think that's over now.
On the plus side, since my repair in December the phone has been amazing. No problems flashing different roms many times. The phone has been better than I expected! The number of phones dying from this issue have dropped significantly since the new year.
Sent from my GT-I9000 using XDA Premium App

is there a link you have to flashing this frimware with odin? never used it before....
hope the replacement and compensation is still going on, kinda pissed that bell didnt call me about it...

tried flashing JL2 with odin, when i have odin open and my phone in download mode, and i plug the phone in, windows does not recognize my device and thus does not install drivers for it and thus im pooched.... ergo vis a vis help please

i know im just talking to myself but just in case anyone wants to know, installed kies to get usb working, flashed JL2, gonna take phone in for repair now (2nd time) awesome!!!

Sorry it took me a while to reply. Forgot to check this thread. There are a bunch of threads about dealing with it. If you get a hard time there's a thread you can search for about filing a complaint to the ccts. That would get you the replacement and comp I think. Good luck!
Sent from my GT-I9000 using XDA Premium App

[Q] My Cappy DIED without a Reason

So... i've read a lot of topics about dead captivates, but it seems that all of them are related with something during a flash procedure.
Well, mine just died yesterday after a week using Darky 10.2 in perfect state.
It was charging in the morning, i remembered checking it once and it was with 62%, when i came back to check again to see if it was full, it was already off and just wouldn't turn it on again.
Tried taking out the battery, even tried the one from my brother (he has the I9000), tried different cables, tried different button combinations and nothing, really, nothing happens.
Dunno if it's important but my cappy suffered from the shut down problem... On Froyo it would shut down like 4 times a week, when changed to GB it was once a week...
Anyway, im not in the US (that's why i didn't replaced mine, i've bought it when i went to the US in last October.
It still has the guarantee, so could anyone point me out a direction ? I have a friend that it's going on the end of August to NY (he is going to be there for 2 months), so it maybe be my only chance...
Unless you can find me a solution to fix the phone !

You might want to try to contact Samsung USA directly and tell them your situation. They should be able to help.
1-888-987-HELP(4357)

Nexus 6 (rooted, stock rom) won't turn on anymore. Please help

Hello everyone,
I'm experiencing a pretty tough issue mith my beloved (and, so far, flawless) Nexus 6. It had root and a stock rom on it, 6.0.1 (MMB29V). I had unlocked the bootloader and rooted the phone right after buying it more than a year ago and I've been flashing new factory images a couple times (specifically when 6.0.0 and 6.0.1 were released). I usually do everything via Wugfresh's NRT, not because I can't use adb and fastboot, just because it works fine and I'm lazy.
Yesterday, while I was working, I used "Tiny Scanner Pro" to scan a document (legit copy bought on the store, as any other premium app in my phone) and it got stuck for a while, then a popup about Google Play Services came up. I dismissed it and another appeared, and it kept going like that. I was at a client's and I was in a hurry, so I took the pic with my tablet and forced the phone off. Later I turned it on, it seemed to boot regularly, but when the SIM unlock screen appeared and I entered the (right!) PIN, it said that no SIM was found, then the home screen appeared but after a while the screen went black and it started rebooting. Recovery (TWRP) and fastboot were working, so I decided to take it home and re-flash the stock rom: it had been a while since the last time anyway, a new version was out and the OTA update notification was getting annoying. I connected to my PC in recovery mode and transfered my pics and data via adb while I downloaded the latest stock rom (6.0.1 MOB30D). Then I user NRT to flash it (selecting "Soft-bricked/Bootloop" as current status). It appeared to work fine as it went through the usual copying and unpacking. Then, when the phone was supposed to reboot, it just blacked out. I waited a long time, in fact I went out and came back a few hours later, and it was still that way. Now it doesn't power up, no matter how long or hard I press any combination of the three buttons, adb and fastboot do not detect it in any way, of course, and it doesn't seem to charge either (i.e. I left it plugged to its original charger overnight and it still feels dead cold). By the way, the phone warranty shouldn't have expired, but I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
I've taken a look at similar threads but none of them describes the very same situation. Is there something, anything I can try to do before giving up? I hope somebody can help me. I thank you all very much in advance.
lupus

lupusyon said:
.... I'm afraid it wouldn't cover this since it should still have the custom recovery and unlocked bootloader in its comatose body.
Click to expand...
Click to collapse
Bricked!. When the phone is still under warranty send it for repair. Do not use arguments.
Just: phone will not switch on and does not charge.

Because this is a Nexus device, the custom recovery shouldn't affect your warranty. It is however, a moot point. The device is totally dead, and a call to Motorola is in order.

lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...

dahawthorne said:
lupusyon, I had a discussion with Google about an 18-month-old Nexus 5 on which the radio had died - the "no SIM found" error that seems very popular. They asked me what I'd done to try to fix it. I told them that I'd tried several different radios, half a dozen different ROMs (not just Google stock), in short I'd messed around with it over a long period (it had been rooted with custom recovery pretty much since I bought it).
Response? No quibbles. "Here's a refurbished N5. Just send the broken one back in the enclosed pre-addressed pre-paid bag."
Go for it...
Click to expand...
Click to collapse
I bought it on Amazon Italy Marketplace, I'm not sure if they're supposed to handle the thing or if I should contact Motorola. I'll just check with them first. Thank you everybody for the kind advice, I'll let you know how this turns out. :good:

I confirm what dahawthorne wrote above: it took them about a month but Motorola repaired my Nexus under warranty, no questions asked. It seems they replaced the Mainboard PCB.
Thanks everybody!