Database Develop

Galaxy S stuck on boot - can't access internal SDCARD, help!

I'm having a major problem with my galaxy s I9000. I havn't installed any lag fixes or unofficial firmware, just apps from the app store. I was just using my phone, on the web downloading a movie file, phone locked up, i powered it down and now i have this "Cant access SDCARD" errors, even when trying to factory reset from the Android system recovery menu. I'm pretty upset, just got the phone a month ago. My phone now hangs on a blank screen after the galaxy s logo, lights on, I can access the download screen and have tried flashing the latest official firmware tonight with odin....this did not fix any problems still hangs on a black screen after the galaxy s logo when booting, and gives me the same error, "Can't mount SDCARD" in red text below the regular recovery options after the firmware installed succesfully (at least according to odin). Anyone have anymore ideas about the internal sdcard getting messed up? how can we format it or wipe it clean when we can't access it?!? please help!

take it easy. thats why products have warranties...because sometimes components fail. i am sorry it happened to you but you might just have to send it in for a repair. it can and does happen to all products at some point or another

if your 3 button download mode works
you can try using the repartidion option in the Odin3 meanwhile flashing a JH2 ROM

Thanks for the ideas fellahs, I did try to reflash with odin and repartition checked, I've looked alot into this problem and can only conclude that my internal sdcard is borken. no matter what i do , even after what looks like a successful flash, the phone boots into recovery mode with the same red text under all the options every time, "can't access SDCARD". I'm currently waiting for my local retailer to get them back in stock so i can make an exchange , I got suckered into the protection plan at Futureshop but perhapes this is one time it may actually come in handy, I just hope it all goes smoothly and i can get a new phone, although it dosent give me much confidence that the phone is sturdy enough to last the 3 years id like it too.

oh yeah, this is one of those times when the futureshop/bestbuy no hassle protection plan does wonder
they will exchange it for you no question asked

This happened to me too -- any way to fix it ?

I had the same problem, but I really need some files from the internal SD, and my phone wont boot at all, anyone ?

[Q] Samsung galaxy S vibrant stuck on "S" screen at boot

To start, I was using I9000XXJP2 firmware on an unlocked samsung I9000 from Bell. I installed a lagfix a few days ago and everything was working fine. The phone was really slow and freezing a lot today so I decided to restart. Ever since then, the phone is stuck on the Samsung S screen (not the one with the triangle). I can get into download mode just fine and i tried reflashing XXJP2 using odin back onto the phone. Odin does everything fine up until i see a blue 'reset' on odin and the phone is in recover mode with the options asking for me to restart the system etc. I restored to factory settings from there and even cleared the cache and restarted but it is still stuck on that "S" screen at startup. Odin only says "pass" once the phone is disconnected. So as of yet I haven't been able to flash a working ROM back on the phone. If you have any ideas as to which ROM i should try, if you could place a link with that, I would be very grateful.

I've had this problem myself a couple of times (just happened today in fact).
Boot into recovery mode (vol-up, home & power). Do you see any error messages in yellow under the menu?
I was unsuccessful at reflashing any of the Froyo firmwares so I reverted back to the last official 2.1 firmware from Bell JH2. Since I was coming from a 512 pit firmware, I didn't repartition or specify a pit file. This ended up working for me. I've since flashed to JK3 and am about to go back to JPU.

Reply:
I actually do see an error message E:can't mount /dev/block/mmcblk0p1, Can't mount SD card.
I should mention that Im using the unlocked bell phone on fido. Will i lose the unlock if i downgrade? Also, if you could point me to the site where i can download bell firmware, that would be awesome. I went to samfirmware.com and they dont have canadian versions there.

Unless one of the pros comes by and says otherwise, I understand that's the error indicating internal sdcard issues.
However... if the thing is dead, you can't hurt it more by trying some fixes
You can get the official and unofficial Bell firmwares from samfirmware.com, you just have to look in the US section. You want the firmwares starting with "i9000UG". Here's direct download links for you:
JH2 (official 2.1)
http://www.multiupload.com/ZNBT2RY5Y0
JK3 (unofficial 2.2)
http://www.multiupload.com/WTZGSKJGPF
JK4 (official 2.2)
I've heard people flashing this via CWM but I haven't see the files.
Also, I've seen references to people saying their phones begin working again after this error msg after they've left the battery hour for hours.
Let us know how things go.

Reply:
No go. When i flash to 2.1, it just shows the "S" screen and turns off. When i flash to 2.2, does the same thing as my first post. I still can get to the download screen through all of this so I hope its not messed up too bad.

I tried several times this afternoon before it worked including clearing data/cache.
Although, I had a different error message so you might be SOL in the end.

called samsung
So I called samsung this morning and they basically said they won't repair it because Bell handles repairs. Since I dont have a bell account, I can't get it repaired. I keep reading on forums that if you can get into the download mode, if you see the battery icon when you plug the phone in, its not totally bricked so i still have hope yet everything I've tried doesn't work. I tried to adb into the phone in recovery mode and it detects it but says I dont have permissions to push files onto the phone. If anyone can tell me what possibly went wrong and if it is fixable, how, that'd be awesome because right now this is a very expensive paperweight.

Captivate gets stuck with black screen after booting. No response to anything

Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?

Titerepayaso said:
Phone: Samsung Captivate I-896, with AT&T stock Android 2.2 flashed to it. Rooted and unlocked.
Action: Deleted some *.odex files from Root/Data/App, following a guide to get around the "out of space" message while trying to install software. Cleared Delviks cache directory.
Problem: First restart after above actions(which didn't resolve the out of space message issue), phone shows start-up animations, gets stuck with black screen. Left like this overnight, nothing happens. Vibrates every 50 seconds or so. Respons to hardware Vol+ press with the home/back/menu backlight. Otherwise, no response to anything, black screen(backlight on). Does not receive phone calls. I do not know for sure if the action listed above is the one that caused this situation, but I assume so since it was the last action taken before the issue appeared.
Solutions attempted: Tried every possible permutation/combination of buttons/usb cable/etc/ restarts etc. listed here: http://forum.xda-developers.com/showthread.php?t=858765&page=1, except Jig. The phone would not go into recovery or DL mode.
Question.
Am I correct in assuming that forcing the phone into recovery mode and reflashing a new system(or reflashing the old one) is the only way to get the phone to work again?
There is no way to "soft-reset" the phone, with all settings reverted back to stock, if it does not boot up completely?
Click to expand...
Click to collapse
Sounds pretty accurate. You'll have to get a jig to get in download mode, flash stock Odin KK4 to fix w/e happened during your testing.

Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?

Titerepayaso said:
Thanks Bwolf. I just tried ADB console on a different computer and it connects to the device just fine in spite of black screen. I guess I had one thing right, USB DEBUGGING enabled before this whole deal.
Question: is there any way I can restore the phone using the console without wiping everything?
Click to expand...
Click to collapse
Make a backup with ADB.
Once that's done, push download mode with it and get Odin KK4 (without bootloaders). You'll have to start from there to fix w/e went wrong.
You don't have to wipe your sd doing so but you will lose your apps and such. If you backed up your phone with your Play Store account, it will re-download your apps as you're done booting up.
To get back up where you were, grab Corn Kernel, flash it with Odin 1.87 and then follow the full instructions of the ROM you wanna use.

[Q] Rooted Captivate running 2.3 freezes after Android load

Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.

ktvanhorne said:
Running a Captivate that I rooted and upgraded to 2.3 over a year ago. All was working well. This week it began freezing after it fully loaded after a reboot or power-on. It will go through the ATT, the Corn logo, and the S animation. It will scan the USB storage devides (internal and external) and then quietly freeze. It will sit there with the wallpaper moving around, but the first key stroke done after all has been loaded up will cause everything to freeze.
While it is starting up, I can enter my passcode, use all of the menu buttons and get to applications or settings. However, once the scanning is done, wherever I am will freeze. I can get all the way through the perform a factory reset procedure before the scanning is done, but it I will run out of time before the phone can start the reset.
Seems like something in 2.3 got corrupted and I need to reload the software without going through the boot-up (I went through Kies, but once the phone booted up, it disappeared from Kies and it told me the phone was disconnected).
Any step by step to either repair 2.3 or to install another droid system prior to the phone booting up? I'd appreciate the help.
Click to expand...
Click to collapse
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.

BWolf56 said:
You could grab Odin KK4 without bootloaders and flash it in download mode.
From there, use Odin 1.87 to flash Corn kernel if you wanna be rooted and have a custom recovery again.
Then it's your choice whether you wanna stay on 2.3 or look into 4.2 ROMs.
Click to expand...
Click to collapse
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT

ktvanhorne said:
So, do you agree with me that it seems to be a software issue? Or is this something to try and see if all goes well with the new install? I have no problem if this is something to try since nothing else is working, but I am just curious if my diagnosis is correct.
Thanks for the quick respond.
KT
Click to expand...
Click to collapse
My guess is that something got corrupted, so yes, software issue. Find the required Odin and 2.3 kernel for the I9000 and flash them in download mode. It should run fine after that.

Got things resolved
Thanks for the help. I tried to follow your steps, but I could never get the phone connected to the PC. It would charge, but not connect to let Odin in. (It will connect to another PC without issues. I uninstalled and reinstalled the drivers, but no dice). However, in the process of putting the phone into download mode and rebooting it back somehow got me into the recovery screen. I did a factory reset through there and it worked.
Thanks for the help of all the contributers to the site.
K

July OTA Update Bricked my Phone -- AT&T refusing to replace. Help!

Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!

LiquidArrogance said:
Completely untouched phone from AT&T. Have never rooted or modded this phone in any way.
The update that came out this month was sending my phone into random boot loops. Would have to take the battery out and after a few tries it would stay on for a while then at some point in the day randomly go back to the boot loop.
I backed everything up through Kies then went into the recovery menu and attempted a factory reset. This sent the phone into a permanent boot loop -- would never turn on or off. Sammy logo flashes and it would reboot. Only way to get it to stop is to take the battery out.
Attempted to go back to 4.4 through Odin since those where the only firmware files I was able to find. Updated failed. Now, when I turn it on and I just get "Firmware upgrade encountered an issue. Please select recovery mode in kies and try again."
Kies will not recognize phone. Cannot update firmare from internal storage because I can't even get into recovery menu -- it just goes right back to the same screen.
Called AT&T and the rep told me he would replace the phone through warranty even though I was past my warranty date. He told me this update has messed up a lot of phones and this is not the first he's of it. Then his manager gets on to approve the warranty replacement and she refuses to honor his promise -- tells me they won't do it, I'm SOL, and I can use my upgrade. Maddening!
Please help -- I need a working phone!
Click to expand...
Click to collapse
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.

muniz_ri said:
Most attempts to downgrade only flash the kernel so here is the OF2 kernel which should get your phone to boot again. Flash with Odin:
G900A_OF2_Stock_Kernel
Once your phone boots place the G900A_OC4_tF2_OTA.zip onto your extsd card and flash as update from stock recovery. That should get you back to 100% factory stock. Do a factory reset after flashing and if it still does not work I suspect a hardware problem.
Click to expand...
Click to collapse
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop

Is there physical damage on the phone, thus why att didn't do the warranty?
Sent from my HTC One_M8 using Tapatalk

LiquidArrogance said:
Thank you for the reply!!
Kernal flash worked and I was super excited to get back to recovery menu -- way more progress than I've had up until now!
Unfortunately when it went to reset after installing the update from external storage, it went straight back into the Sammy logo boot loop
Click to expand...
Click to collapse
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck

muniz_ri said:
Take it to Best Buy or an ATT Store and have them reflash it before you toss it away. Good luck
Click to expand...
Click to collapse
No idea what just happened. I've been messing around throwing the kernel you recommended at it as well as the stock partitions. Kept getting back to boot loop but at one point it stuck out, said it was upgrading, optimizing apps, and now it's running. So weird.
I'm way too scared to do the factory reset at this point, though.
Thank you again for your help, I really appreciate it!
Edit: Unplugged the USB cable and it immediately shut off and went back into boot loop. Wow.

this sounds like a hardware problem.. i sent my phone to Samsung and they actually repaired it, it was the pba board, i had the same problem.. i flashed everything it needed to recover from a bootloop. and sometimes it would become non responsive. go to best buy and see what they tell you.
Sent from my UNROOTED SAMSUNG-SM-G900A on OF2

Update:
Thanks to everyone for their replies. I was able to get the phone to boot thanks to everyone's help. Did this by flashing kernel then partitions which would allow the phone to boot.
I finally figured out that the phone would only boot if plugged directly into a power source. As soon as I disconnected the power cable, it would send it right back into the boot loop. I ran some battery "repair" and "calibration" tools but these did not fix the issue. Whenever I would run a battery drain tool, the stress on the battery would cause the phone to shut down.
All of this led me to believe it was an issue with the battery. I held my wife's S4 battery to the contacts on the S5, and it works just fine, even disconnected, and even with the stress test on the battery.
SO -- I'm going to buy a new battery and see if this fixes my problems. I think I just had the perfect storm of battery issues coupled with firmware problems.
I'm pretty sure I know what caused the battery to go haywire. I work in a max security prison and have to leave my phone in the car all day. Outside temperatures regularly hit 105F+ during the summer, so who knows how hot it's getting in the car. Obviously I always leave the phone turned off, but I suspect the high temperatures caused the damage.
Going to try to find a new battery today. Will keep everyone posted! Thank you again for all of the replies.

I had the same issue and would just like to thank you for the files! They helped me unbrick my phone! Much appreciated.