Edit: So further research has led me to the conclusion that my internal sdcard is dead.
I've got what seems to be an odd issue, did some searching, can't find anything similar.
I've been playing with JPK for the last week or so. Tonight, answered a call, put my phone down for... ~5 min, came back it was stuck with the screen off and the capacitive buttons lit up. Poked at it, messed around with all the buttons for about 5 min, gave up, pulled the battery.
Tried booting, It would go past the initial Galaxy S screen and then black. Tried that a couple more times, then tried clearing cache and factory reset from Recovery mode. Still no dice.
Ok, go on computer, grab JM8 (first firmware thread at the time), flash, wait, boots, gives me an error about unaccessible SD card. Change a few settings, sign into Gmail, pull/insert the SD card a couple times. Give up, try rebooting.
Since then I haven't gotten past the initial loading screen again.
I've now tried flashing JM6 (used for almost a month before JPK), JM8, JM9, JPK. All with the same results. The only thing I haven't tried is getting a new 512 pit on the off chance mine is corrupt.
The odd part is that I ONLY have download mode. I can't get into recovery, or all the way into Android (or even the animated S screen).
Also odd, if i plug it in while off, the battery icon never fully boots. It shows up (empty, just the shape, no green even though the phone should have at least 50% battery), gives me the little fan symbol, then vanishes, repeat.
So I'm pretty much out of ideas. I might try flashing from an 803 pit tomorrow, on the off chance that will fix it.
Either way, I'm confused. Suggestions?
Try returning the phone to samsung
Sent from my GT-I9000
I had the same problem with my i9000m... Looks like the only option right now is to send it back through Bell. Took a couple of weeks for mine to get repaired.
Related
Hi,
I have a rooted GT-i9000m (bell Galaxy S Vibrant). I used the one click lag fix to root my phone and it works fine.
A few days ago out of no where all the apps started auto closing as soon as i opened them and then both the menu and back touch buttons lit up and the screen went black. I held the power down till it rebooted only to get and error with com.android.calendar even tho I never use the app. When it finish's booting none of my installed apps are showing.
The first time it happened with com.android.app and I did a full wipe and factory reset and just reinstalled everything.
Ideally I don't want to system reset to factory settings again and lose all my files and notes that i copied back on to the phone 2days ago...
Please note I have tried clearing the data for the calendar app in settings -> apps and i cleared the calendar back up. My problem is that none of my installed apps are showing...
(Update) I also cant reinstall or update apps due to a Installation error - Insufficient storage. But there's room on both SD cards. I also set 850mb for apps when i did the one click lag fix and i don't have 850mb of apps installed.
(Update 2) I did a factory reset again this time i didn't format the internal and external SD cards. (It works like new again) Thus I got to keep all my personal files and ring tones ect. The only thing that was deleted that I didn't back up is my Notes. This leads me to my new question whats best for backing up apps on a rooted SGS (bell Vibrant)?
If anyone has answers they would be much appreciated.
i had the same problem
install rom manager from the market place
there is a option in there "Fix Permissions" just run that and it will fix it up for you
only takes 1-2min to run
Tried what you said but i cant install anything... I get Installation Error - Insufficient storage available.
I now understand the cause of the problem. I change my battery once and some times twice a day. At first I would wait for the long shut down (untill the screen goes totaly black) and then take off the back and swap out the battery. At least 3 times the phone would boot up and ask me for the network unlock code (I bought the unlock code directly from bell for 75$). I found this rather annoying so i tried just taking the battery out wile it was on (idle) and it appeared to work flawlessly at least 20-30 times before the phone would start to do an endless force close loop cycle. This kept forcing me to do a factory reset on the phone. I can only assume the one click lag fix and my disregard for the need of the shutdown before removing the battery must be all the cause of my problems.
I will try and see if my phone is more stable with out the one click lag fix.
nope that is not the cause of the problem
but it sounds like you are another victim of the lag fixes that is killing your internal SD card.
not the fault of the lag fix, it just make the problem apear sooner than later
I have been having a similar issue and I'm using Voodoo lagfix. I think it's because I took the battery out before it had completely shut down.
read this
http://forum.xda-developers.com/showthread.php?t=793404
Well the phone bit the dust today. I opened up google maps to look up an address and it crashed with the usual error. So i rebooted the phone and now it stays stuck at the boot logo. (the glowing S with both touch keys staying lit) So i did the recovery thing again but this time I had to do the Vol-up + home + power in order to get the phone working some what. IDK but it wont let me log into my google account to sync my contacts. My APN settings are correct and working and I even tried off my Wifi at home. I'll just hope its a google problem and not my phone acting up. Thanks for the pointer to the bad internal SD. That may be the problem kinda hard to prove it to Samy thoe...
I get force close errors after about 4-7 days of use. Now its gotten worse. A few days ago I was looking up an address and my phone crashed and rebooted it self. It then hug at the S boot logo for 20mins. I got to my friends apartment building to find my phone still stuck at this boot logo. I couldn't remember his apartment number or buzzer code... Normally i just check my contacts list and buzz the code. I was standing out side in the Canadian fall cold wind trying to get this phone to work... OMG i almost just smashed it on the spot. Anyways I remembered about something i had read on this forum about the recovery mode ( i had used it to root ) so i tried that out got the little menu and tried every option before having to do the dreaded factory reset. Well nothing work with the exception of the factory reset it got my phone working in about 5mins... LOL
Anyways I thought I might try upgrading the firmware when I got home. What a mistake... I cant control my phones MP3 player via my bluetooth car stereo any longer. Tried everything even a factory reset and formatting the internal and external SD's. I tried running it with out rooting it again and with out the lag fix in hopes that I wouldn't get a force close error. Wouldn't you know it about 5 hours after the factory reset un-rooted just after i finish coping over all my music. I get a force close error! So I tried again and this time the phone ran for about 30hours before it started giving me force close errors about the email now...
Sigh I've tried just about everything in my power to make this phone work. So I assumed it must be the phone... I called Samsung up to get a RMA going... Wouldn't you know it they tell me that I have to call my carrier to get it RMA/repaired. I try to explain that I bought the phone with out a contract and bought the unlock code from Bell so I could use it on Fido. They tell me to call Fido... ROFL Fido wouldn't even give me their APN settings when i got this phone so knew they would be of no help. They don't even have one android phone in their line up i tell the sammy rep. So they tell me I should go back to the Bell store I bought it from to get it repaired/RMA'ed.
I doubt Bell will be of much help but here's hoping.
Do you think my phone is broken, bad flash, buggy memory, ect and needs to be RMA'ed?
Update...
I got my phone back from repairs 2 weeks ago. They flat out replaced the phone for a new one. This was a huge headache for me because the new one wasn't unlocked. Took Bell 2 hours to get the new one unlocked wile my wife waited out side double parked downtown! (I thought it would be a quick pick up and I would be out) The blue-tooth works flawlessly again!!
Much to my dismay the replacement phone has started acting up much like my first one did. It gets several force close errors a day and has gotten to the point where it no longer can send or receive text messages (using Handcent). The stock Music Player app also force closes at random with more frequently. It looks like I got another Lemon. This time around I did NOT root, lag-fix, or flash firmware. I will be sending it for repairs as soon as I can afford to buy another phone to use wile this one is off at repairs. My back up phone is a 3~ year old Iphone3g that my son has made his... (cracked screen, vol rockers dont work, power button is jammed in, the LCD screen it self is bleeding on the top edge)
The Vibrant never let me down other than as a phone. As a divx player or using all-share it rocks! I use these features A LOT to play my 720p divx movies on any TV or the projector in the bedroom .
with that being said I might keep the phone just as a portable movie player to bring from place to place and put my sim in something more stable.
I may have bricked my phone while flashing with odin to stock froyo 2.2 rom. The download mode works but i cannot get into recovery mode it just flashes at the logo screen gt-i9000m over and over and over again.
Is there a way past this or do i have to send this phone in for repair?
I have stock everything.
My phone battery died and I have spare batteries and changed it to a fully charged one. It booted up and said that a bunch of apps have to be FORCE closed... so I rebooted it.
Now it's doing the same thing yours is... the logo screen flashes over and over.
I pulled the battery to hard boot it. Then without turning it on I plugged it in to charge... so it tries to go to the charging battery icon and then flashes the logo screen over and over again.
This is my second phone... first one kept eating battery life and got real real hot.
omg stoopid samsung. I can get into download mode just fine, when i reflash it just stuck at the boot logo. Are you able to send yours away for repairs? i have mine unlocked but i also got warranty from where i bought it at wireless wave. i rather not send it in though...
I couldn't get into any menu's... sent the piece of **** away for repairs. I almost threw it at the wall behind the clerk at the bell store.
same boat here, i woke up this morning to find a bunch of forced closed messages. so i hit okay, my phone was all screwy so i turned it off, pulled out the battery, put it back in and started the phone and ta-da the galaxy S TEXT (not logo) kept...well it looks like it would boot over and over again just to the title screen, shut off and boot again. If i do the 3 button press to get to download mode i see that screen and i cant do anything else, actually i dont know what to do there.
I bought this thing in august so i am good for warranty, oh i haven't once rooted or lagfixed or anything, i just unlocked it, and with rogers instead of bell, but yeah i called bell and they refuse to help. The guy was not cool with me unlocking the phone, says i might not be covered under warranty anymore.
Next week i am going to take it to the bell repair center in person, see what they say.
Not sure what to do now. EFF!
Last samsung phone ever. the LG optimus 2X looks pretty awesome.
I'm having the same issue, my phones all stock.
When I got my phone this morning is was turned off, I plugged it in, powered it up, saw the Samsung logo and intro play and I walked away. When I came back I tired using my phone but only the lights, on the buttons, turn on but the screen and the rest of the phone doesn't respond. The lights will stay on forever.
If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Sent from my GT-I9000 using XDA App
Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
gtg2 - Try booting into recovery mode (vol-up, home and power). Do you get an error message under the menu? If so, report it here or do a search on that specific error. It appears that some errors are easily recoverable from via flashing while others are not.
The flash will go through completely and pass, as soon as it reboots to the Gt-i9000m logo it will just loop continuously. even when you hold down vol-up, home and power, it just doesn't recongize those buttons but will recongize vol down, home, power what gives?
Valinorian - If you can get into download mode, have you tried flashing it with some other Rom? Like DocX custom rom?
Yeah tried darkys 5.6 rom, does the same thing shows gt-i9000m logo then loops it self
dtran00 - that sucks man, but bell offers unlock codes so i dont' see how that can void your warrenty when you have to pay $70 for the unlock codes no?
Spudsicles - hopefully i won't have any troubles but i might end up throwing it at them lol
Seriously this is a good phone but the problems omgosh.
regarding everyone with the boot loop errors, Sounds like you have got the corrupted internal memory. This is a common problem everyone has been having including me. You will have to send the phone off at bell. I'm still waiting for mine to come back to me, sent it off Dec 1, although some people are reporting repair times within 5 business days.
To the best of my knowledge, that does NOT necessarily indicate flawed internal memory. I've experienced a few errors myself - one was a real SDCard issue which required repair while the others I was able to recover from.
Have you tried reflashing firmwares via Odin with the repartition option checked?
Have you tried booting into recovery using ADB? I'm not an ADB pro myself but do know it's possible. You'll have to google for instructions.
I woke up this morning and my phone would not boot. it would get past the Orange boot screen, as i am locked to Orange, and then i t would get to the sgs boot screen and stay there for about 5 minutes, then finally turning itself off along with a few random vibrations. I kept trying to turn it on, i tried numerous ways such as taking the external sd and sim card out, taking the battery out for 2 hours but the same thing kept happening. My phone was not rooted and has never been hacked in anyway, i have had this phone not long. It was working fine the night before. I fixed this by going into recovery mode, as i could get into both recovery and download mode fine, and i restored to factory settings from that. Now it works fine. Anyone know what was up with it and how i can fix it without restoring if it happens again. I didn't look it up when it was happening as i didnt have access to the computer,
Thanks
What you describe sound like a bootloop, which could be caused by many things, if it recurs my suggestion is to take it back to orange and insist on replacement/fix. I was with orange but hacked my way out of their crap software ages ago!
Insanity cm 015/glitch
Back-story: A few days ago (okay, maybe two weeks, I've been lazy), I put my Tab into my backpack after using it all day at work. Everything was fine. The following morning, I pulled it out, and noticed something weird. The YouTube icon had removed itself from the homescreen, and almost everything I tried was simply unresponsive, or crashed instantly.
I rebooted the Tab, and then realized that it wasn't online either, claiming that it was in airplane mode. Couldn't seem to change that. Searching for "stuck in airplane mode" revealed a few threads saying to remove the SD card and reboot, which did nothing for me, and a few threads saying to reflash the modem.
So, I followed the instructions in http://forum.xda-developers.com/showthread.php?t=1275031 and it hung up on the modem step. For like an hour. I finally gave up, rebooted the phone, and tried again. This time, it hung up at Modem again, I walked away after half an hour, and when I came back, it was sitting at the phone-exclamation-point-computer display on the phone, and the computer indicating failure.
Ever since then, no matter what buttons I mash, I can't make it enumerate as a USB device of any sort. Half the time I can't even make it turn on; it'll show the exclamation-point display only when plugged into the charger.
EXCEPT ONCE. Odin saw it, I smacked "Start", and Odin immediately failed. If I can get it to do that again, I'll jot down the exact error message.
So, right now: It's got enough sense to show the phone-exclamation-point-computer (does this string of hieroglyphs have a name?), but it won't show up on USB. What next?
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
GreenMunky said:
I have a Verizon, stock, unrooted Moto X. Today while updating several apps in the Play Store my phone all of a sudden flashes a black screen, followed by a split second of the boot animation (one of the animated globe scenes) then went black. Pressing and holding the power button force resets my phone, which goes through the entire boot animation, then the Verizon logo, then an unresponsive black screen. I've done the 3-button reboot and then told it to reboot normally, but with the same result. Eventually after about 6 or more failed bootup attempts, it'll finally boot up all the way. I don't remember which app was in the process of updating when this happened, but it did happen twice today. I've got 8+ gigs of free space available on internal storage. Has anyone had this happen before? Any idea what could cause it or what I should do about it? I'm afraid it might keep happening more frequently or my phone might just up and die . Had it since November.
Click to expand...
Click to collapse
If a factory reset does not fix the issue, all I can suggest is find the thread "Return to Stock" and follow the instructions to flash the entire stock SBF for your carrier. This should fix any corrupted files, if present. Either option WILL erase everything, so backup anything you need first.
Good Luck
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
KJ said:
Maybe your battery stats are off? Were you low at the time? Sure sounds like the power just died?
Click to expand...
Click to collapse
Nope, phone had been off the charger only a few hours, still had 85% or so. I actually tried plugging the phone in while it was booting up to see if an extra jolt of juice would somehow help it to fully boot up... made no difference. After 6-8 failed boot attempts, it finally booted up and has been running fine since... although I have yet to try to manually reboot it.
Well, if it acts up anymore...I'd consider a full wipe and return to stock. Same android version you're on now of course.
Otherwise...probably a fluke. ?