Black screen of death. It's what I call it because that's all I get.
Here is a summary of what happened.
1) My Samsung Galaxy S started to get slower and slower. I decided to turn it off and back on (using
the power down button) to see if it would get any faster.
2) I would then only get the first start screen, then the graphic S screen after which it would go
blank (black screen of death). After about 2 min, if I pressed any keys, the two buttons on the bottom
would light up and stay on. If I pressed any one of them, it would go off and back on.
3) I could hold the power button and it would reboot.
So, that's were it was, here is what I have tried so far.
a) Check to see if I could get into download mode. Yep, that works.
b) Check to see if I could get into recovery mode. Yep, that works.
c) Hmmm, oh well, lets do a system wipe. Yep, can do that but it still would not boot up. I just get
to the graphic S screen and then the black screen of death.
d) Lets take the battery out. (over night) Nope, still black screen of death.
Based on the above, a flash should work right. Sorry, but I had a lag fix installed. Well no matter
what, I could not get the phone to boot so I guess I better try flashing anyway.
I've tried several images. Most of them get the error "your storage not prepared yet, please use UI me nu for format and reboot actions" OK, this is because of the lag fix. I then installed stzupy's image and that fixed the "your storage not prepared yet bla, bla bla. But still black screen of death.
I've tried flashing over and over, with pid 512, 513, 803. Nothing. I still come up the black screen of death.
So, can someone guide me in the right direction. I've done searches on this but everyone else seems to have had a different problem. Mostly doing a Factory Reset worked for them. I've done that over and over. After removing the battery, after flashing, before flashing. Nothing seems to get me past the black screen of death.
Thanks in advance for all and any help,
Jeff
p.s. Please don't reply with a message saying something like flash X's kernel. I need descriptive instructions such as flash with "this kernel" into CSC (or pda or modem) using XXX pid while checking repartion (or not). In other words, don't assume I know what I am doing. I don't.
there is now way you can save your apps installed but your sd card files will be there.
Only thing you can do is reflash my friend
webstar1 said:
there is now way you can save your apps installed but your sd card files will be there.
Only thing you can do is reflash my friend
Click to expand...
Click to collapse
Really don't care about my apps. (I have everything backed up onto my computer via Titanium Backup) But if you check my message above, I have reflashed until the cows come home. I still get the black screen of death.
- Jeff
Sorry Jeff Your Samsung Galaxy S is 'Proper F*cked Mate'
Yes sir I believe you are toast indeed! Your internal SD card is probably toast. I believe you're a fine Canadian of course assuming you've got the Bell i9000m? A lot of us have had this and there's a poll on it actually. Mine just toasted out about 2 weeks ago, thankfully i've an awesome friend in Canada on the forum that has helped me out!
No matter what you flash or try to do, it will not mount the sdcard in there or let you format it manually. You'll have to send it back to BELL or Samsung.
BA_Flash_GOD said:
Yes sir I believe you are toast indeed! Your internal SD card is probably toast. I believe you're a fine Canadian of course assuming you've got the Bell i9000m? A lot of us have had this and there's a poll on it actually. Mine just toasted out about 2 weeks ago, thankfully i've an awesome friend in Canada on the forum that has helped me out!
No matter what you flash or try to do, it will not mount the sdcard in there or let you format it manually. You'll have to send it back to BELL or Samsung.
Click to expand...
Click to collapse
Sigh! That's what I've been worried about. Yep, bell i9000m. Oh well, if I gotta, I gotta. Only 1 month old.
- Jeff
Flash stock, then give it back to samsung to repair, they should then
Sent from my GT-I9000 using XDA App
Had the same problem today. Wanted to change from JPA to JPO so thought it best to do a factory reset, but when phone booted up again, it started, then the screen went black with the occasional vibration. Tried all the usual things, removing battery & waiting, wiping cache etc., but no luck. Then put it in download mode & installed JPA again, but same problem on bootup. Thought I had finally managed to brick my phone (horrible feeling). So I solved it this way :-
Installed JM8 using .512 pit with repartition ticked, hooray my phone booted up again. The long delay after the S logo & finally completing boot was nail biting to say the lease. Now everything is working great & I am in the process of installing JPO.
Related
Hi guys,
UK G1 (Dream) phone recently updated to the 1.6 build, all working fine.
Yesterday I tried installing the free app Shop Savvy. the phone resetted itself after install and sat on the G1 boot screen permanently.
Now phone will pass this boot screen (Tmobile G1)
Tried:
Recovery mode - will not work at all
Quick boot - brings up the multicolour screen but does nothing after.
**PHONE IS NOT ROOTED**
looks like I have had the phone JUST over a year, not looking good...
Any ideas?
You can boot in to the SPL/bootloader so thankfully you haven't bricked
If you're on a contract with tmo you could take it back to the store and they should give you a replacement, but where's the fun in that?
If you want to fix the problem yourself, all you need to do is downgrade to firmware 1.1, then accept the OTA update to 1.6.
Here's the procedure:
1)Put the phones SD card in to a card reader and format as fat32
2) Extract this file and copy it to your SD card as 'DREAIMG.nbh'
3) Put the card back in the phone and hold down power and camera to boot in to the bootloader.
4) Flash it. (Action button is the trackball).
It's a good idea to leave the charger plugged in and have a decent amount of charge in the battery (eg 40%+).
Afterwards the phone will restart and you will need to re-enter your google account info. All your apps and data will be gone, but there's not much we can do about. You can set things up and install apps while you wait for the prompt to update.
Thanks alot AdrianK,
Really appreciate the steps and info, nice one
I have done some flashing on other phones etc so I have no problem with this. However, I am wondering how a normal app such as Shop Savvy could corrupt my ROM and am wondering if it might not be better to get a new phone as this one could have hardware fault?
What do you think?
Silver.
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
SilverfoxUK said:
OK,
did exactly as you said Adrian. Phone went through all the flashing routine then, right at the end said press action button to continue (trackball) every time I press the trackball phone returns to the bootloader screen
What now?
Click to expand...
Click to collapse
I think you can take the battery out restart the phone
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Once you get to RC7 use these to build back upto 1.6
http://code.google.com/p/official-android-firmware/downloads/list
SilverfoxUK said:
Thanks but unfortunately I have already tried that.
Phone just sits on the G1 boot screen as before...
Any other Ideas?
is that ROM you linked for me a UK ROM Adrian?
Click to expand...
Click to collapse
Yeah that's the RC7 ROM, the UK ROM for 1.1. RC29 is 1.1 for US phones.
This is all very odd, especially that it was an app that caused it, or as you suggested possible hardward failure. Oh well, I guess all you can do now is take it back to tmo.
Hi,
I have lost the ability to use my internal and external storage memory. Is there anyone that can tell me how to fix this. I am at a loss.
Thanks
Zack Cadieux
I have the same problem after flashing JPH firmware. (I know how to flash FW, I've been flashing every FW as it was released)
It says that there is an I/O error in mmcblk0p1.
I think i'm screwed as well.
Not one person knows what is going on
Hi,
Im supprised that even the dev's know nothing about this issue. I have read almost every thread and nothing to show how to respolve this issue. Is there anyone???
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
http://forum.xda-developers.com/showthread.php?t=734475
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Dawgplg said:
I had the same problem. I have a Bell Vibrant which I flashed to JPH using the Kies method, rooted, then One Click Lag Fix. Things worked for about a day then I lost my storage. Luckily I did the samsung 3 button fix first.
I downloaded the Tmobile Stock Rom, and used the following instructions to flash.
It booted up to the Tmobile Rom, and everything worked. I then used Odin to flash back to JPH.. rooted.. and now am contemplating the Lag Fix.
Not sure if it was related to the problem but I had my phone connected to my computer transferring files before all hell broke loose. I may have yanked the USB without unmounting... Just a thought.
Good Luck..
Click to expand...
Click to collapse
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
LordSoth said:
My situation is about the same. I did the update and applied the root and lag fix. Phone worked fine for a day or so and then it just locked up and couldn't detect the sd cards anymore. I rebooted and it was stuck on the S for over 30 minutes...I flashed HJ2 and when it rebooted all that happens is I get a gray blinking battery if it's attached via USB and if on battery it boots up to the I9000 initial screen and shuts down. Lucky for me the shop will do a swap when they restock in about a week. Back to the HTC for now.
Click to expand...
Click to collapse
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Dawgplg said:
Dont recall if I did any of the Recovery options, but I remember the big Grey Battery... You could even try flashing back to JPH through Odin... It may wake it up. But good to hear they will replace it, at least you have something to fall back on.
Click to expand...
Click to collapse
There was another thread I read about this exact same issue happening and the guys had to return the phones in the end. Yea I was lucky I was under the 30 days limit. By the time I get a new one hopefully a proper Froyo build will be out.
Phone was flashed to 2.2, however after shutting down the phone and booting it up again, I get Black SCREEN + glowing buttons.
Device : Samsung i9000 from Bell running flashed 2.2 Rom.
I've tried following this guide :
STAGE 1 (applies only if you are coming from an earlier Froyo build)
* We are now going to flash the XWJM8 firmware again (Éclair), so make sure that you load the files for this firmware in Odin.
* In PIT, load the 502.PIT file
* For PDA, select the ‘CODE_I9000XWJM8.tar.md5’ file and for PHONE, select the ‘MODEM_I9000XXJM4.tar.md5’ file. Leave all others blank.
* Make sure that the Re-partition box is checked. All other settings should be as shown in the screenshot below.
*Sorry can't post link, forum restriction*
After stage 1, Odin says Passed, my i9000 reboots with still a black screen+ glowing buttons.
I want to start Stage 2, however I can't find the file ‘JPO_JPO_U_JPP.tar’ file.
I've looked up for solution for the last 2 days and can't seem to find a solution anywhere.
Things I've tried on my own without sucess :
Flashed again this time with a CSC from bell, I've read that sometimes without CSC flashing can't be done, but even with the CSC files, my phone is still ''bricked''
Anyone have any idea how to fix this? Ultimately, I want to go back on 2.2 but for now, I just want my phone to boot again =(.
Hate to say it but it sounds like yout internal sd card is dead like MANY OTHERS who have flashed... No way to fix except to send for repairs to bell/samsung...
Sent from my GT-I9000M using XDA App
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Isn't there a way to try and access internal sd card?
Have you try doing a factory reset?
Yeah, I've tried doing so, after reading and researching online, I think this could fix my problem.
forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
see reply #7
However adb doesn't even reconize the phone =/
terranq said:
I wish you'd stop stating that flashing fubar's your phone. Many people running stock, unrooted devices are reporting the same problem.
Click to expand...
Click to collapse
I diddnt specifically mean that it was the flashing that did it but it is OBVIOUS that it happened after he flashed right???
It is known that flashing will sometimes "speed up" the death of an already faulty sd card and that is what I meant by my original post...
And PS... The number of people reporting their sd cards failing on stock firmware w/ no lagfix or no previous flashes to "unofficial firmware" is WAY lower than those reporting sd card death after flashing or adding lagfixes, etc...
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
terranq said:
Which obviously points to an existing hardware fault that is exacerbated by flashing, not caused by flashing
Click to expand...
Click to collapse
And again... I did not specifically state that it was the "flashing" that killed the OP's phone. I simply stated that this seems to happen to MANY people after they flash. NOT the same thing...
Did you come to this thread to argue or to help the OP? I simply posted a reply last night stating that it seems his internal SD card is dead so that he could prepare himself for having to send it away for repairs. I did not respond to the OP to get into an arguement with anyone over "what causes the internal SD cards to fail".
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
cuem said:
Don't argue guys! I appreciate all your help
What is the best way to ''fix the internal sd card''
Isn't there a way to like factory reset the internal sd card.
Click to expand...
Click to collapse
@cuem,
Unfortunately... If it is an actual dead internal sd card (which it seems to be since the steps you followed already did not seem to fix the issue) the only way to fix it is to send it back to Bell who in turn will send it off for warranty repair.
IF you have just purchased the phone within the last 30 days (possibly 60 if Bell is still extending the DOA return policy) and you have a receipt you can take it back to Bell and get an exchange.
Again, unfortunately these are your only options to get this fixed...
Sorry to be the bearrer of bad news...
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
cuem said:
Just when I think this couldn't get worst,I was wrong.
I tried using Odin3 One-click downloader, I wanted to flash it with At&t stock firmware( hopefully it would work) then flash it again with 2.1 clair
After using Odin3 One-click downloader, it said sucessed, but now my phone is STUCK on At&t blinking logo and I can't go into download mode anymore.
I've tried the 3 keys combo, adb doesn't reconize the phone.
I'm pretty much screwed,warranty won't work if Bell sees At&T logo blinking upon power up.......
Click to expand...
Click to collapse
Ooooooo... That is not good. The American Vibrant is NOT the same as out i9000 models.
What you need to do now is search the forums for the homemade jig thread that will force your device into download mode. Search the forums and you will find it.
Be prepared to be "handy" as you will have to build the jig from scratch...
Sent from my GT-I9000M using XDA App
Yeah, I've read about the Jig thing, I've also read about heating your phone with a hairdryer,
I'm currently trying out the hairdryer, but it doesn't work =/
Might have to try the Jig thing, which seems a little complicated with ordering since I'm running out of time =/
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
This has happened to me, I just flashed with an older version, for me JM5 worked fine.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
I had the same thing after flash and spent many hours and tried many different methods to get it back up with no success.
I'm leaving the country for Europe on January 2nd for vacation. This was the last thing I needed... Hopefully I get it back before then, but I'm not holding my breath.
cuem said:
Jig worked, im back to my intial problem.
BLACK SCREEN + GLOWING BUTTON.
Click to expand...
Click to collapse
Well... At the very least at least the firmware is now correct so you can send it away for repair if you need to...
Sent from my GT-I9000M using XDA App
I followed this guide
http://www.tunandroid.com/content/i...du-firmware-i9000xwjpa-pour-samsung-galaxy-s/
I believe now oneclicklagfix is installed on my device, can I flash again or that'll brick my phone, how do I uninstall oneclicklagfix if I can't boot up the phone but only acesss clockwork mod menu?
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Funkadelick said:
So apparently the official 2.2 Froyo is rolling out. I haven't checked yet but I will when I get home. I have some newb questions.
I got my phone and haven't touched a thing to it. Just added lots of apps. No root. No lag fix. Nothing.
My question is, if I upgrade this officially via Kies:
1) Do I lose my contacts / stuff ?
2) Do I lose my apps ?
I heard people saying that once you upgrade to do a hard reset of the phone -- why ? What happens if you don't ?
With this in mind, how and what is the best way to back up all my apps ? I haven't rooted but i DO have Titanium Back up. Would Z4root work for i9000m ? can anyone confirm ?
Click to expand...
Click to collapse
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
BlackDino said:
1) no
2) no
3) hard resets are only if you experience a ton of lag while operating the phone
4) z4 does not work on jk4
Click to expand...
Click to collapse
how do you root jk4 then ? 2.1 eclair on bell i9000m
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
A lot of people have been complaining that their SD cards have been screwed. Luckily mine went through without any problems and hasn't given me any trouble so far.
Froyo is insane tho, before the phone used to lag a bit, now the moment i touch it it opens. No need for lag fix in my opinion, everything works blazing fast as is.
One thing to watch out for is the WIFI. It was working normally at the beginning but after 3 hours it just disconnected for no apparent reason and has trouble connecting back.
Good luck
rajesh26e4u said:
Why is this stupid update corrupting internal SD's left and right? Bell better get me a new phone! Cause this one is bricked(I think) it goes up til "S" logo and then nothing but blank screen. If I touch the button, they light up but still nothin on the screen.
I should have gotten a different phone to begin with, but too bad Canada doesn't have all the good phones US has like D2 DX HTC Evo etc. Going up to Bell tomorrow for an exchange.
Click to expand...
Click to collapse
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
urfase said:
1. Phone is currently rooted. Do I have to unroot it before applying the firmware upgrade from Kies?
2. Do I have to perform a factory reset before applying the firmware upgrade?
Click to expand...
Click to collapse
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Videonut said:
1. NO
2. Good idea to factory reset before and after. Can't hurt and any noncompatible
programs and data will be gone.
Click to expand...
Click to collapse
1) but will it erase root upon upgrading?
bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Yep, but for optimised result, this is a must do!
You can probably have it work without doing a factory reset, but you can encounter weird behavior, bugs and stuff!
Anyway, you might end up doing it anyway to solve the firts boot issue
I'm one of the users who upgraded to Bell Froyo (from stock FW with root and lagfix - undid the lagfix before upgrading) and then encountered the broken internal SD card issue. I ran Volume UP/Power/Home(middle button) to reformat everything and it is up again. Inside the OS, I ran the internal factory reset again. So far so good. *crossing fingers*
I updated mine last night. However I've had major problems since. Initially it would just freeze up randomly and require removing the battery to get it back up and running.
Today I decide to reset it to defaults which seemed to go fine, although shortly after getting it all setup again, some Samsung app of sorts came up with an error and had to be forcefully closed. Then I was left with a black screen and only the notification bar.
Powered off the phone and went to turn it back on, and now it just loops through the Samsung GT i9000 screen (white writing). Not even the colourful S logo comes up.
I'm able to get it into Download Mode but not Recovery Mode. I'll have to do some reading about this Odin stuff tonight. Hopefully I can revive it, otherwise I guess I'll had to send it in for repairs. No idea if Virgin Mobile repairs will go through Bell or if I take it to them directly.
This is my first Android phone and I've only had it for just over a week. I thought I was making a good decision, but now I see it has quite a defect with the internal SD card failing.
Slow after upgrade
I upgrade my phone last night ( as per bell and Samsung) It is now slower than before. Quadrant Standard has it under 900.
Any ideas how to fix it?
bimmerboii said:
1) but will it erase root upon upgrading?
Click to expand...
Click to collapse
Just use SuperOneClick after you upgrade to Froyo, I've tested and have root on JK4
http://forum.xda-developers.com/showthread.php?t=803682
I have an unlocked phone from Bell that I already upgraded to the international (or European?) JPP/JPO 2.2, what is the best way to downgrade or restore back to default firmware before using Kies to get the official update? Does factory reset restore stock firmware?
I upgraded to official Bell froyo last night ..thn rooted.But how can i Unlock now? i tried using SGS unlock app it says no unlock codes found?? Please help
God damn samsung and bell!
it seems like they're giving defected phones to their costumers!
I have the corrupted sd card too, took it to guarantee now it takes more than 1 month to fix this!
this is f-ing xmas for god's sake. i want my phone
Same problem here!
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
ciudadbonita said:
I do have 2 good samsung galaxy s vibrants from Bell, however when i got the second one i upgraded to Froyo and now i cant unlock it because i cant read the stupid file inside the phone so,
How can i go back to my previous JH2 baseband?
Or
How can i unlock JK4?
I did my unlock on the other Galaxy using the script you donwload from somewhere in this website and then connecting the phone via usb cable with debugging on and mounting sd but with froyo i dont even know where my USB settings went!!!
Thanks for your help, greatly appreciated.
Click to expand...
Click to collapse
Have you found any solution yet?? I am thinkin to flash back orignal samsung firmware using Odin n then unlock..atleast i will be able to use the phone then
Videonut said:
Don't panic yet...
Try this
Volume UP/Power/Home(middle button)
Factory reset/Wipe
Click to expand...
Click to collapse
what if after this, it's still stuck after the s logo boot up?
does this mean i have a broken internal sd?
Hi guys,
Gone through about 100 threads these last couple of days, but nothing helps, so have to start a new one.
What happened was that the other day my phone started ringing.
The screen however was black, so I could neither see who was calling nor answer the call.
I let it ring out, then I held the power button so it would shutdown.
Tried to restart it, and that's when the fun started.
The phone got stuck in a boot-loop, only showing the Galaxy S logo (not getting to the animated one).
Left it in this loop for several hours, since I've had problems recently with the phone needing to do this cycle 5-10 times before booting up.
This time it wouldn't boot, however.
I've tried putting the phone in a bag of rice for 18 hours, in case of any moisture inside, not helping.
Then I tried recovery-mode, formatting the whole thing, but I got the following error:
"E:format_volume: rfs format failed on /dev/block/mmcblk0p2"
Found this thread to try to fix the format error.
Got into download mode, but Odin does not recognize the phone, and I started believing all hope for fixing it without sending it in was gone.
I've also tried applying a couple of update.zip's from the SD-card, just to have tried it, but every package got Signature verifcation-error.
Anyway, when I headed to bed last night I left the phone in the boot-loop, and to my surprice, 8 hours later it had booted into first-time configuration.
YES!!!
Configured the phone with language etc., then all of a sudden the animated Galaxy S logo appeared...
And it appeared again, and again, and again for about 15 min., until I unplugged the battery.
And now I'm back at square one, stuck in the boot-loop (not getting to the animated logo)...
I have the latest versjon of KIES, not that it probably matters.
Does anyone have an idea of what the problem might be?
What rom were you using? stock or custom? Maybe it has something to do with lagfix if it was activated... im guesing, im not dev just normal user... Maybe try to reinstal usb drivers.
Just use odin 1.3 reflash official rom , everything would be OK.
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
mortenlm said:
Not sure about the ROM, bought the phone used... But pretty sure it's stock..
Since Odin didn't recognize the phone, reflashing it with official ROM would be hard...
However, as for the Odin problem, that was caused by a faulty USB-cable...
Used another one, and Odin worked like a charm.
The phone won't start after running through the steps in the thread I mentioned before, but I will try to reflash it with offical ROM now and see how that works.
Click to expand...
Click to collapse
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
porkapple said:
Not sure about used phone, But if I bought the phone used, I would reflash rom first. Because I do not even know what they done before , reflash offical rom would be fix some problem.
Click to expand...
Click to collapse
Well, I would have if I knew... But stupid me thought that a phone was a phone.
How wrong was I?
Anyway, a little update here (the problem is kind of solved now):
Flashed the phone with 2.3.3 Gingerbread I found on dkszone, after running the steps in the previous mentioned thread.
And the phone started like a charm.
But after a few hours of configuring etc, I managed to insert the SD-card again, and all hell broke loose again...
Come to think about it, thats what I did yesterday too, so I've come to the conclusion that the SD-card is the main problem...
However, now the phone is slow... REAL slow... Kind of like my 1.5 year old HTC Touch Diamond 2 with WP6.5...
It takes up to 2 seconds to open menu items, keyboard etc.
Is there any way to fix that?
Or should I flash it with another ROM?
You mean the external sdcard? Maybe try to format it...
OK, so this is what I've now figured out:
The phone is damaged...
It seems that the internal SD has gone AWAL, and internal storage has somehow created itself on the external SD-card, thus the phone crashed when I switched cards...
When trying to format the USB-storage, I receive error: SD-card has been removed
So I guess I have to ship the phone off to Samsung ASAP...