My SGS rebooted overnight and got stuck at the Cyanogen boot screen. I got into recovery and reflashed the cyanogen ZIP but it didn't fix it. When I went to wipe the phone, it said there was a bad block on the cache partition.
When I tried to reflash an image using ODIN, it failed every time. Previously this has always worked fine.
I think it's a hardware problem with the internal memory - does this sound right?
If you tried Odin with repartition turned on, then it looks like a service return might be required
jc
3d_jc said:
If you tried Odin with repartition turned on, then it looks like a service return might be required
jc
Click to expand...
Click to collapse
Thanks, it was!
Got the phone back today. It says they calibrated it and reflashed it. Seems to be working fine.
I'm confused - what do they do differently to Odin?
Edit: Also, I'm worried the memory problem could still be there.
How to expand phone memory ?
How can I expand internal phone memory.
I have avielable only 1,85 GB but I need at lesat 3 GB to upgrade Eclair to Gingerbread.
Pleace help ?
Related
I'd like to start of saying I've read almost every thread regarding this and I understand that there's a good chance that my internal SD is permanently blown up I'd just like to establish some things here that may put me in a different boat.
hatdrawn said:
I just want to be clear ...
So I last night I flashed JPK, PDA/MODEM/CSC with 512pit installed latest oneclick lag fix 2.1.1, SGS tools and other basic apps. Was running perfect all night except that RAM seemed to be eaten up easily.
Then this morning Advanced Task Killer Froyo Beta started acting up. So I tried a reboot and then I got this black screen issue.
Tried reflashing JPK again. Just successfully flashed JH2 but still the black screen.
Recovery/Download mode work. With 2.2 recovery mode I was getting SDCARD connect errors on screen, but since JH2 I don't see them. Tried wiping cache partition, and factory reset. Still black screen. I've tried without external SD and SIM and just recently with external SD.
In this JH2 recovery mode "update media, finished" and Apllying MultiCSC works properly too. When in recovery mode, Kies tries to recognize it, but boot/blackscreen I get nothing.
Is there anything else I can try? I have read through this whole thread, but it's a lot to read and understand. Anything with ADB? When in recovery mode ADB shell returns a device not found
Click to expand...
Click to collapse
Currently it's back on JPK for the time being and using ADB I can finally get it to recognize there is a device, but it says it's offline. What does this mean? Does this mean that it wasn't in debug mode when it crashed? Or something else? At this point does this help me at all. At one point I did get internal and external drives to show up in my computer, but I couldn't acess them. As if they weren't mounted. Actually, that's how it's behaving now.
Can anyone think of anything else for me to TRY at least? I don't want to give up just yet. I realize all signs point to bricked but I just want to try a few more things.
Any tips are appreciated.
Thank you very much
So this is my second GT-i9000 that has suffered from a damaged internal sdcard. This one has some strange behavior though as it wont boot with any stock kernel installed.
I tried flashing back to 2.1 JH2, as well as JM9.. it goes through the animation then dies. I also tried flashing voodoo over 2.1 to see if something was still using ext4 - no dice.
This is where it gets interesting. If I flash oc120_froyo_v2.0_UV_alpha.tar over JM9 the phone boots, with the warning Damaged Internal SDCARD. I can use it - but get constant FC's and no access to the /sdcard mount.
I tried running parted and print the partition it but it said invalid disk label. I tried creating one but no dice.
I want to flash it back to stock so I can bring it in.. any idea what this kernel would potentially do to the phone that can't be undone with a flash???
Edit: Just exchanged this for my third phone.. Apparently this is a huge problem with the SGS. The dealer said they returned lots of these
Well it finally died. I got the infamous SD card failure message. For the past few days It was getting slower and slower and I was getting odd Force Closes everywhere. Then the red exclamation mark and a message about the SD card.
The very weird thing is that the failure was about the EXTERNAL SD card. Cannot find mount point... cannot read... Not the ususal INTERNAL SD card message.
Sure enough, if I try to read the Transcend 16Gb MicroSD on my pc or laptop, it appears completely fried. (Cr*p, that's were my backup was!).
But the phone wont boot on wihout the external card! Why? All I can get to is the Download mode. No boot and no recovery.
I'm in Montreal so it appears easy to get it fixed... but should I try flashing it first?
davidke said:
Well it finally died. I got the infamous SD card failure message. For the past few days It was getting slower and slower and I was getting odd Force Closes everywhere. Then the red exclamation mark and a message about the SD card.
The very weird thing is that the failure was about the EXTERNAL SD card. Cannot find mount point... cannot read... Not the ususal INTERNAL SD card message.
Sure enough, if I try to read the Transcend 16Gb MicroSD on my pc or laptop, it appears completely fried. (Cr*p, that's were my backup was!).
But the phone wont boot on wihout the external card! Why? All I can get to is the Download mode. No boot and no recovery.
I'm in Montreal so it appears easy to get it fixed... but should I try flashing it first?
Click to expand...
Click to collapse
Sound you have some data corruption (or suffering the Bell BUG http://forum.xda-developers.com/showthread.php?t=883820)
First try to retreive the data from your external Sdcard with your PC, using the tool "testdisk 6.11". Maybe you'll be lucky enough to retreive all your data with it (repairing your FAT).
If the repair is a succes, then backup the data on your PC and do a low format of the ext sdcard to start clean.
When it's done, try to clean everything on your phone (if you can boot it in recovery), clean the Dalvik, clean the cache, do a factory reset, disable all extra tweaks (if you use a custome kernel already: lagfix etc).
If all process is ok, now you ready to flash a stock and clean rom with the usual tools (no external or sim card in it during the flash and first boot).
Report back when it's done.
GL.
TestDisk is now hard at work. Thanks for that. There's hope for the data!
Phone wont go into recovery. I had 3BR but it's not working now.
Download mode is all I have. I could theoretically try reflashing with ODIN. Repartitioning might not be a bad option considering the state the phone is in. Should I try?
davidke said:
TestDisk is now hard at work. Thanks for that. There's hope for the data!
Phone wont go into recovery. I had 3BR but it's not working now.
Download mode is all I have. I could theoretically try reflashing with ODIN. Repartitioning might not be a bad option considering the state the phone is in. Should I try?
Click to expand...
Click to collapse
Yes you can try that, but be sure to flash a stock rom first (go for a 2.1).
GL .
All data recovered thanks to TestDisk!!!
As for the phone...
It flashes with Odin no problem. (used JH2, which is what I had on there anyway)
But still wont boot. The problem appears to be in the boot partition.
Should I try "Phone Bootloader Update"? (I'm a bit afraid of that because I might lose my 3BR fix)
What does "Phone EFS Clear" do?
Additional symtom: Cant recharge it either (no problem I have external charger so I can always have a full batt for this process). It starts to display the battery charge graphic and then just boot cycles.
davidke said:
All data recovered thanks to TestDisk!!!
As for the phone...
It flashes with Odin no problem. (used JH2, which is what I had on there anyway)
But still wont boot. The problem appears to be in the boot partition.
Should I try "Phone Bootloader Update"? (I'm a bit afraid of that because I might lose my 3BR fix)
What does "Phone EFS Clear" do?
Additional symtom: Cant recharge it either (no problem I have external charger so I can always have a full batt for this process). It starts to display the battery charge graphic and then just boot cycles.
Click to expand...
Click to collapse
Good news for your data!
No doubt if you do a bootloader update with a stock one, you'll lose the 3BCombo (or maybe flash a stock bootloader with the 3BC enabled, not sure if it exist btw??). Try to reflash the 3BC fix only first and see how it work.
Anything that involve EFS is a: DO NOT TOUCH IT =), hope you did a backup of it btw (your EMEI is stored in that folder: No EMEI = No network).
Waiting your feedback.
ttf said:
No doubt if you do a bootloader update with a stock one, you'll lose the 3BCombo (or maybe flash a stock bootloader with the 3BC enabled, not sure if it exist btw??). Try to reflash the 3BC fix only first and see how it work.
Waiting your feedback.
Click to expand...
Click to collapse
Tried a couple of things...
A) Updated bootloader with 3BR fix only: No change, Galaxy-S logo then Off.
B) Flashed JL2 (bootloader not checked): Slight change, now it boot cycles.
C) Flashed JL2 + bootloader: Slight change, now it just hangs and the Galaxy-S logo (waited 60 minutes, phone was getting pretty hot so I stopped it).
At all steps I can get back to Download mode but not recovery.
At this point I assume it's hopeless?
davidke said:
Tried a couple of things...
A) Updated bootloader with 3BR fix only: No change, Galaxy-S logo then Off.
B) Flashed JL2 (bootloader not checked): Slight change, now it boot cycles.
C) Flashed JL2 + bootloader: Slight change, now it just hangs and the Galaxy-S logo (waited 60 minutes, phone was getting pretty hot so I stopped it).
At all steps I can get back to Download mode but not recovery.
At this point I assume it's hopeless?
Click to expand...
Click to collapse
Not sure but really sound like a defect internal SD/or more.
Last hope?: repartition + pit 512 + bootloader and Stock 2.1
That killed it for good. Now it's a paperweight!
No nothing. It's like the on#off button was unplugged!
Oh well. It's really nice to have gotten back the data.
davidke said:
That killed it for good. Now it's a paperweight!
No nothing. It's like the on#off button was unplugged!
Oh well. It's really nice to have gotten back the data.
Click to expand...
Click to collapse
Well that's a bad news, maybe pulling out the battery during one or two hours will help to revive it.
Otherwise if it's really the internal sd issue you might check that thread about internal SD bug (if not done yet) http://forum.xda-developers.com/showthread.php?t=902724 and RMA it.
Don't worry they'll change it with a brand new one. Ring samsung directly if you can.
No worries. I am five minutes away from the service center. Mobo replaced for tomorrow morning they said.
Had I come in before 3PM they left we with the impression they would have changed it while I wait!
Having followed all these threads, I was well aware of the issue long before it actually happened to me. The only thing that surprised me was that it broke the fat table on my external SD.
I was holding back because of the instabilities; with a better unit in hand I'll pop in a fancy rom.
External SD card causes reboot loop
I think I have a similar problem as yours. Just yesterday when I did a restart on my SGS, it suddenly went haywire. The boot loop was continuing for almost 30 mins until it suddenly became stable and reboot as normal.
However, something didn't work out right. I can't view all my pics and videos from gallery, and even my mp3s are not detected inside the music player.
But the very same files are still readable from My Files when I manually dig into these folders.
Same thing happened again just now when I was on my way to work in the subway. I finally had the sense to remove my external sd card and voila, my phone reboots smoothly without a hiccup.
So the question here is, is it that my external sd card is failing or is it that the phone's external sd card reader is failing.
Could anyone with the similar problem share with me their findings?
Hi i have a bell galaxy s i just flash ugkc1 firmware but when the phone boots i get force close message for almost every app.
i think the internal sd might be corrupted tried to format it but all files are still there
any idea ??
thank you
your SD card usually nothing to do with application force close, those files which you see after formatting on SD card should be there so do not worry about them.
if you want to find the reason explain about your previous rom and kernel. did you do a factory reset or wipe before and after rom installation?
Here is two simalar topics. I also have that problem and cannot solve it yet.
http://forum.xda-developers.com/showthread.php?t=1076101
http://forum.xda-developers.com/showthread.php?t=1069867
When i looked in internet i found sth similar for HTC, but devs corrected it. They parted some files from working devices and pushed it to system with adb.
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
Maybe sth like that will also solve our problem but we need help.
If you find any sollution please infrom us. Maybe it will be useful for us too.
Regards
thanks for your replies
all this strated when i updated to 2.3 with kies using spooffw upgrade went fine but phone didn't boot it was stuck on the first boot screen,
so i flashed back to 2.2 and here i am ..
Did you try booting twice or did you jump the gun flashing back? My phone appeared to be stuck during the first boot screen on the first time starting 2.3.3.
garbz said:
Did you try booting twice or did you jump the gun flashing back? My phone appeared to be stuck during the first boot screen on the first time starting 2.3.3.
Click to expand...
Click to collapse
i tried booting twice it ddn't work recovry mode didn't work either
now im back on froyo i still can use the phone but only as a phone all apps fail to start and i get force close message
flashed my phote to 2.3 (jvk) ans i installed speed mod... still the same
im pretty sure its an internal sd failure. is there any way to fix this ? i bought my phone some guy on kijiji so i don't think i have any warranty..
thank you
biscuit26 said:
flashed my phote to 2.3 (jvk) ans i installed speed mod... still the same
im pretty sure its an internal sd failure. is there any way to fix this ? i bought my phone some guy on kijiji so i don't think i have any warranty..
thank you
Click to expand...
Click to collapse
I doubt it is an SD problem. Go to recovery, clear cache and dalvik and fix permissions. If the problem persists to a factory reset and reinstall your apps from the market.
Sent from my GT-I9000 using XDA Premium App
thanks again for tryin to help i already tried this but didnt work
Edit :
flashed back to stock 2.2.. now i get ''blank internal sd'' on the notification bar. phone doesn't seem to detect internal sd card is this a hardware or software problem ?
thanks
now i flashed sppedmode kernel phone seems to be running a little better ( less force closes messages) but i still can't delete files or format my sd card
any idea ?
I tried to flash darky 9.2 (odin version). Then i reach with ADB to the internal when it is in CWM. I pushed there some custom roms and flashed with CWM. But it did not help either.
isn't there any way to fix a corrupted sd card ?
Hi,
I installed Galaxian Soup 1.5.1 beta a week ago and all has been running fine. This morning the tab was blank like it had run out battery so I put it on charge and found it wasn't dead. Tried to reboot and it's just stuck at the "Samsung Galaxy Tab 8.9" screen. I was using it fine last night and haven't changed anything!
I've tried ODIN to restore Stock Recovery which said it passed and worked, but still the same problem. It has removed CWM though. When I try to do anything in Stock Recovery it complains about not being able to mount the /data directory.
Is there anything else I can try, do I need to use ODIN to flash a ROM again? If so, can you tell me which file to use as there are hundreds in the Galaxian Soup zip.
Thanks!
Flash stock rom with Odin. Unfortunately you also need to wipe data in stock recovery for this to work, so you will loose everything.
Thanks for the reply. Unfortunately this hasn't worked, it passes in Odin but then on the tablet it says E:failed to mount /data, and "your storage not prepared yet, please use UI for format and reboot actions.
Trying to factory reset fails.
Any other ideas?
OK, a bit more detail. I use ODIN to flash the stock rom found here - http://forum.xda-developers.com/showthread.php?t=1483168
It passes and goes into recovery but complains in red letters about not being able to mount /data, can't access /system/csc/XEU/system in yellow and can't mount /cache or a few other subdirectories.
I select wipe data which appears to work although it complains about make_extf4fs failing on /dev/block/mmcblk0p8. It then complains about not being able to mount /cache and other subdirectories again.
I then select reboot, it complains again about not being able to mount /data and /cache and switches off, not reboot. If I turn it on again I'm straight back to recovery.
Got to be something I'm missing here!
Any input appreciated.
It seems your partition tables are messed up, but i have no idea how this could happen if you didn't flash anything that could cause this, maybe a hardware problem?
There is a way to repartition the tables, you need a PIT file for this. I have not done this myself, so unfortunately i don't know much about it. Try to search for a PIT file, but make sure it's for your tab model, otherwise you can mess it up completely.
Many thanks - that fixed it! For future reference and for anyone searching this thread I found the pit file here - http://forum.xda-developers.com/showthread.php?t=1406137&page=9 and flashed it with ODIN together with the standard firmware I mentioned in the earlier post.
It's not all good news though. The tablet now keeps freezing. Even in recovery while I was trying a factory reset for the freezing. This leads me to believe it may be a hardware problem that caused the original brick and ongoing freezing issues. What do you think? Does it save a dump anywhere when it crashes?
Glad to see it worked. Maybe try to flash the stock rom again, now without the pit file. Also try factory reset in stock recovery. If you are still having problems, then im afraid its a hardware problem.
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Mbuxton said:
Yeah, I came to the same conclusion. It was hanging even whilst in stock recovery which means it had to be a hardware problem. Took it back to the shop and got a refund, new one is on it's way.
Bit nervous about ROMing the new one! The only thing I can think of is maybe overclocking damaged the cpu, although I only set it to 1.4Ghz. Or I was attaching a card reader and it was complaining about a service crashing when I removed it. Maybe it would have happened whether I messed with it or not!
Click to expand...
Click to collapse
I have been flashing different roms, kernels and recoveries on my tab for more then 200 times probably. And i have been using Galaxian-Soup AOSP ICS rom with molteys kernel for almost two months. Never had any problems (that i didnt create myself). Never used overclock, but havent heard of anyone who has had problems with it either.