Please help me
I bought my S I19000 branded Vodafone in Italy, I live in the US.
I was all excited to see the upgrade to Froyo (JP7) on Kies tonight, so I went ahead and did the upgrade. I specifically waited for the official release because I'm not too good with messing with Odin and stuff and didn't want to brick the phone. But apparently I did
Everything went well on Kies, and it showed the upgrade was completed successfully, but my phone rebooted and never came back alive. It got stuck in the flashing S, then the screen turned black and the only thing it does is vibrating every few seconds.
What did I do? How can I fix it? Please help me.. :'(
From reading some posts, it seems I can fix it since I get get into recovery mode.. the question is how do I fix it?
I'm sorry guys, I know this is a newbie question and I should figure it out myself, but I tried and couldn't
Well you can get it to work. But you will loose all your data on it.
You need to do a factory reset.
Then it should start.
Do a backup on your photo and stuff on your internal sdcard and move it to an external sdcard.
Then go to recovery mode again.
This time Format the internal sdcard. Wipe the catch and do a factory reset again.
Now you have a clean phone and you should not have any problem with bad settings from your old firmware.
**Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
I got it to start back up with a factory reset! Thank you!!
Yes, I lost everything, but at least I got my phone back working
Does anybody know what the problem seems to be with these updates? I saw a bunch of posts mentioning updates via Kies gone wrong.. I sure won't mess with it again, but I wonder why this happens.
Well its just settings from old firmware that can mess things up.
That's why it most of the time works with a factory reset.
But do the extra steep to be sure there is not any bad settings left.
It seems also be better if you format the internal sdcard atleast once.
**Using my own JPU kernel, z4mod, 339MB Ram and ext2 filesystem**
Well, after the factory reset I actually found out I have Froyo now.. everything seems to be working smoothly now, fingers crossed it stays that way.
Thank you so much for your help. I panicked quite a bit last night on this upgrade!!
Related
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.
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.
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?
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
patman18 said:
So just like everyone else i've got a bricked i9000m. So before i send it off to repair (thats if they take it that is), Im sorta curious what fixes have all you out there tried on your phones?
So far i have flashed with odin1.3 to jh2 and now stuck a the "S" boot screen.
Is there a way to get cwm recovery on a phone that dont boot?
Click to expand...
Click to collapse
i bricked my phone many times.i flash back to xxjm8 from samfirmwares.com, thats the password aswell you will have to register its free. if it does not work first time try flashinging again.use ordin 1.7 its good.you can get all your updates from ther without getting confussed on the fourm, i have been stuck on that screen many times trying to root my fone on the new 2.2.1 firmware.go to google type xxjpu galaxy root. the is a web site give you xxjpx rooted with voodoo + some cool tools follow all the steps to the letter,if you can print it off its only three pages .
what about adb ? Did tried it ?
a hammer
i flashed back to jh2 after it was in a boot loop from jk4 and then it wouldnt even turn on.. sent back for repair
bobekk said:
what about adb ? Did tried it ?
Click to expand...
Click to collapse
tried it
i can't get the phone to connect. keep getting the stupid "unmounted sd......." crap.
but the funny thing is i can get in to dnl mode reflash with odin, and everything works fine no error codes. But the phone won't boot. keep getting stuck at the s screen
workaround
I've tried everything i can find, i used adb and mounted the card in windows then formatted the card (there is a how to on here for that) but that didn't work. I've tried multiple roms and kernels but i still have the same problem. It seems that my only option is to send it in for warranty. But, if you want to use your phone over the holidays or wait for samsung to come out with an answer before sending your phone in for repair there is a little work around that you can try to get your phone to boot. The phone will be fully functional except that you cannot use the internal SD nor an external SD. Thus, you won't be able to install or save anything to your phone.
to do this workaround just flash the bell froyo rom (there was another froyo rom that i had working but i can't remember which one) then install the voodoo lagfix kernel. When it boots you will hear the "cool voice" state that it is converting it to the ext4 partition and then it will boot into the OS. there will be a program or two that require a "force close" but at least you're phone will work until you can get it repaired. In settings under SD card you'll notice that it says there is no internal or external disk space that's just because you still have the SD corruption and that this is only a work around to get your phone to boot.
I'm curious, for those having this problem and can get into recovery mode, can you report if you're seeing an error msg under the menu and if so, what does it state? Thanks.
Where can you find the official firmware for the i9000m? I had a custom rom installed but my phone decided to brick - jpu worked fine but the minute i upgraded to jpx... Anyway I want to flash the official firmware and take my phone back to bell.
Thanks
I've ran my phone with the original Eclair rom for a couple weeks. I then figured that I couldn't wait for the froyo rom. I've been running the Spike Speedy OC rom, with the JK4 modem and voodoo lagfix. The phone was running just great, very fast. I then changed the lagfix to overkill ext4. Some hours later, the phone hung up. When I rebooted it, it said that the configuration had changed. I saw that one of the options was back to RFS.
What?? It's formatted as ext4. Oh sh*t. Well it didn't boot back up.
I've tried flashing every different firmware I could find. I then tried to re-format the SD manually and found that the partition table was bad.
I've tried to reformat both SD card partitions. The system one (p2) formatted fine, but the "internal SD" (p1) storage one wouldn't format. When I ran fdisk on it, it told me that the partitions didn't end on cylinder boundaries.
Then, I (mistake) flashed a T959 firmware on it. At that point, I wasn't able to get into the download mode using the 3-button combo. Oh shi*... Now I really messed this up. I've managed to get it into download mode using ADB and flash the bell firmware back on it. Oh yeah!! Here we go again.
After the fact that I had installed the T959 and flashed back I9000 firmware, I couldn't find the /dev/block/mmc*** anymore. As if the SD didn't load up.
At that point I inserted a microSD in, and it was recognized as the internal SD. I managed to partition and use that external microSD card just like the internal one and got the phone to boot and work. However, no storage.
All of which I was trying to do while my USB connection was on-and-off, because the usb connector was damaged. It initially had corrosion because my car plug that was kept on the floor of the car, with all the dirt, water and snow. I used alcohol and a tooth brush to clean it, between flashes. As well, flashing it through a VirtualBox VM since I'm on Ubuntu. Sh*t..
This morning I figured I would stop trying, flashed the JH2 firmware on it and brought it to Bell. I tried to get a refund with the argument that this phone is badly designed - with the samsung movinand flash chip - and that it would fail again even if they fix it. It didn't work out for me since I bought the phone about 40 days ago. I was thinking of getting a refund and buy a Nexus S, when a compatible one comes out. It has a different flash chip - a iNand from Sandisk I believe. Oh well. If it fails again, I can still call VISA and give it a try through the purchase protection plan. I have to mention too that I tried calling bell with my concerns - nothing they would do too.
I don't recommend you take my approach. IMO, maybe try, as root, to check the partitions using fdisk /dev/block/mmc(something) and if they appear ok, try to format the SD card using fat.format /dev/block/mmc(something)p1 - but that's it. I'm an experienced linux user, but I'm not a developper. I don't even clearly understand this ODIN flashing stuff. It's like not all firmware you find on the net have the same amount of components inside. I'm thinking stuff from the other flashing is still remaining, not replaced by the later flashes.
I have to say that the next time I'll approach this using fdisk and fat.format only (If I've got a recovery mode working, with root and adb support). Perhaps I will write down the numbers for where the partitions start and end on this SD card when I get my refurbished phone.
Some might say that I had time to spare... I wrote this for you that might be thinking of fixing your 600$ brick yourself.
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...