Related
Hey, I got a Samsung Galaxy S Vibrant GT-I9000M a few months ago and have since tried a few ROMs. I was upgrading from Darky's 8.1 rom to v9.1 by downloading the app for adjusting the settings for the new rom. The phone restarted itself some time after the instillation of the application and was then unable to mount the internal or external sd cards. A few minutes later I restarted it and the phone would only boot to the Galaxy S screen and song before going blank. I've used several versional of Odin3 with several different firmwares, pit files, enabled/disabled re-partitioning, including trying to flash the original I9000UGJH2 firmware. Nothing has gotten my phone functional again past the Galaxy S boot screen.
Is there anyone who can give me some help?
I just tried the the JPC firmware and still no luck ... Does anyone have any info they can share?
try this:
JH2 with or without repartition. Phone won't boot just flashes initial start screen
flash JL2 without partition and you're back to stock JL2.
if what pr0cs suggested, does not get you back to running OS again, then your internal SD is toasted
It didn't work ...
I get this message:
E:Can't mount /dev/block/mmcblk0p2
(Invailid Argument)
E:copy_data_default_apk: Can't mount DBDATA:
I was getting the same message with a few other firmwares. If it is just a corrupted internal memory unit, why would it have failed to mount the external sd card aswell while the phone was half working? Something doesn't seem right. I hear there is a way to modify the phone to boot from a formatted micro sd card, but I'd rather not have to get that in depth. My friend has the exact same phone if it can help in anyway.
call samsung send it in for repair
or find your invoice and go to a Bell store
that error is a definite confirmation your internal SD is hosed
even if you get it to boot with another ROM, you will not be able to access your SD cards
My condolences.
But..
Welcome to the club. It's not exclusive .
Will they be able to tell the firmware has been swapped if I flash it back to I9000UGJH2? I think it voids the warranty ...
it will not void the warranty if ur flashing it to OFW
Techloid said:
Will they be able to tell the firmware has been swapped if I flash it back to I9000UGJH2? I think it voids the warranty ...
Click to expand...
Click to collapse
I had this problem and fixed it with I9000XXJPU.rar search samsunggalaxysforums.com
http://www.google.com/m/url?client=...gQFjAB&usg=AFQjCNGbNJgSCIx6HmVWl9Bm_P5niowAgA
Sent from my GT-I9000M using Tapatalk
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
Sent from my GT-I9000M using Tapatalk
Techloid said:
Will they be able to tell the firmware has been swapped if I flash it back to I9000UGJH2? I think it voids the warranty ...
Click to expand...
Click to collapse
flash it to JH2, then flash it to JL2,
factory wipe it
then back again to JH2, make sure it hangs in a black screen during boot, or infinite boot loop
then send it in for warranty
Techloid said:
Hey, I got a Samsung Galaxy S Vibrant GT-I9000M a few months ago and have since tried a few ROMs. I was upgrading from Darky's 8.1 rom to v9.1 by downloading the app for adjusting the settings for the new rom. The phone restarted itself some time after the instillation of the application and was then unable to mount the internal or external sd cards. A few minutes later I restarted it and the phone would only boot to the Galaxy S screen and song before going blank. I've used several versional of Odin3 with several different firmwares, pit files, enabled/disabled re-partitioning, including trying to flash the original I9000UGJH2 firmware. Nothing has gotten my phone functional again past the Galaxy S boot screen.
Is there anyone who can give me some help?
Click to expand...
Click to collapse
I was having a similar problem with my Captivate, except it happened after re-applying a lagfix to stock 2.2. Flashing Rogers stock 2.1 and 2.2 didn't fix the problem, but I was able to get a full boot after flashing to AT&T stock. After that, I was able to flash back to Rogers stock and it was as good as new.
James Palm said:
I had this problem and fixed it with I9000XXJPU.rar search samsunggalaxysforums.com
http://www.google.com/m/url?client=...gQFjAB&usg=AFQjCNGbNJgSCIx6HmVWl9Bm_P5niowAgA
Sent from my GT-I9000M using Tapatalk
http://samsunggalaxysforums.com/sho...CIAL-STOCK-FROYO-2.2.1-IS-OUT!!!!-(i9000XXJPU)
Sent from my GT-I9000M using Tapatalk
Click to expand...
Click to collapse
Thanks James! It seems that the xxjpu firmware has a fix for internal-sd failure. I had the phone sent in the first time, but this worked for me when I tried it the second time my phone decided to die. It seems the problem is in not checking the bootloader update in odin when upgrading to the 2.2+ firmware. I'll try not to make that mistake again!
nzahorchak said:
I was having a similar problem with my Captivate, except it happened after re-applying a lagfix to stock 2.2. Flashing Rogers stock 2.1 and 2.2 didn't fix the problem, but I was able to get a full boot after flashing to AT&T stock. After that, I was able to flash back to Rogers stock and it was as good as new.
Click to expand...
Click to collapse
captivates are built slightly different... so this problem will not be the same, this fix won't work on the i9000
I am in desperate need of help you guys! I screwed up so hard that I don't even know where to begin...
THE SITUATION:
-Right now when I go to turn on my phone, it will only stay on the current SAMSUNG GALAXY S I9000 screen (the very first screen when booting your phone) and it keeps flashing in and out.
Before trying to use Odin to put back the original Kernal on my phone, it was just stuck as the SAMSUNG GALAXY S I9000 screen, still wouldn't start. <I followed this website step by step>
http://www.samsunggalaxysforum.com/...-to-a-stock-rom-after-installing-darky's-rom/
BEFORE ALL OF THIS EVER HAPPENED:
I finally rooted my phone and manage to download Clockworkmod recovery on my phone and then used it to flash Darky's 10.2 custom ROM. Everything turned out great except at the beginning of the boot, the screen turned all rainbow coloured, completely distorted, and it continued to do that. I then tried to go back to Recovery mode to do the Voodoo lagfix but I couldn't even get into the recovery mode anymore, it either wouldn't let me, or it did but the screen didn't go to it properly (more likely the first one). I read somewhere that if you reflash your phone again, it should make all the tweeks go away. So I tried that from the Darky's tools menu and ever since then, I've been stuck with the Boot Screen this whole time...
I already bricked my phone once, and that was before the Flashing Boot Screen.
I really need help you guys, I would at least like to have my phone back to the original basis, at least! Your help would be greatly appreciated!
THANK YOU
P.S. (i'm not that great at all this phone tweeking, but I've succeeded in doing it up until yesterday)
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
gfacer said:
Can you get into download mode (vol down+home+power while putting the battery in)?
If you can, just reflash a stock or custom rom in odin (like a darky odin rom) as guided by whatever rom you choose.
If you cannot get into download mode then we should know that too.
Edit: oh it looks like you could (and hopefully still can). Try a different rom or reflash. Sometime things do go wrong but as long as you can get to the download screen you should be fine in the end.
G
Click to expand...
Click to collapse
Yes, I can get into download mode! (thank you for reading my post).
If it's not too much to ask, could you maybe find the ROM that would be good for me to flash, considering my situation?
I want to be sure that it's what the top tech guys would recommend
A link would be appreciated
thank you again!
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
gfacer said:
I'd start with a Darky rom - lots of users - active forum and odin editions for your situation. I have to go but you'll find the link on the first page of the development section.
G
Click to expand...
Click to collapse
So in essence all I have to do is flash the Darky ROM V10.2 with Odin using the Download mode on my phone and it should be okay?
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Wait one caveat. Was it a gingerbread rom or froyo? Use a Darky rom of the same type...
Then yes it should be ok if you follow their guide. Cross fingers.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well...I did everything you said. The ROM is on there alright, it flashed and everything (And I know this because now when the boot screen STILL FLASHES, the darkcore & darky's rom logo are on it too).
THIS TIME AROUND:
The stock recovery seems to work...
any ideas??
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Alright I'll try and reflash the same one using a different version of odin the. I'll let you know what happened
gfacer said:
Well we are sort of in long shot territory now... OK first try using a different odin version or ez odin and reflash.
If still not working??
Might be warranty time then but others are welcome to chime in.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
tried ezodin, flashed it, and i still get the exact same thing I've exhausted every single possibility there is!!!
I really need help on this, my warranty is not gonna do anything because i have the phone rooted..
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
gfacer said:
If you flash a stock rom with pit the root is gone. It won't boot but they can't prove it was you either and I don't think it was you.
But see my other post on your other thread for one last thought.
G
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
okay that could be useful data potentially (let's hope it won't have to be).
If you didn't see my reply from the other thread, here it is:
Once I rooted my phone, I automatically went from Stock Froyo to Darky's 10.2 extreme edition. It worked and everything except for that color disfiguration and the clockworkmod recovery not working.
It's weird because after I flashed my first darky's rom, i checked the phone and it said that the firmware version was 2.3.X (I believe X may have been 4). So from what you're saying, I don't exactly think it has anything to do with the fact that I went straight from froyo stock to GB darky ROM.
So are you saying that I should flash darky's 9.3 for Froyo and THEN flash the latest version?
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Ok, so just to be 100% on this
-I should flash Darky's 9.2 froyo onto my phone,
-then I should flash regular GB onto my phone (Not sure about the bootloader part though, if you could clarify that)(Also where would I get JUST a stock GB ROM?)
-then I can flash a custom GB ROM?
gfacer said:
No I think that you need froyo re edition then stock gb with bootloader (as the instructions say I thought) then a custom gb like 10.2.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
roma17 said:
well i can safely say that flashing the 9.2 froyo rom was a fail. It's still doing the same old routine.
I just know that this problem can be fixed somehow without sending it in to bell or samsung or something.
Click to expand...
Click to collapse
I think you are right but other than trying again and again, which I've done before -though now I know why I had too - I am out of suggestions. Good Luck and if I have a brainwave I'll let you know.
Sent from my GT-I9000M using XDA Premium App
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
gfacer said:
OK a few last brainwaves:
1) Try a fully complete stock rom with cache.rfs, dbdata.rfs, factoryfs.rfs, modem.bin, param.lfs, zImage, and sbl.bin (this was from JL2 rom for Bell - not sure if they all have the sbl.bin) and pit.
The key is to make sure it is complete. Try downloading the same rom from 2 different sources just to be sure its not a corrupt download (going overboard I know).
2) Can you get into recovery? Try to format partitions (not system) under advanced features (I think - I only have 3e right now as I am trying to diagnose other issues).
3) If you have a froyo rom on at one point, try to put a steam recovery kernel on. Its not really being developed anymore but I think that if you put a CWM packaged rom on to the external SD you could flash from there or at least move it to the internal and then flash it. Worth a shot. Or you might be able to transfer one in regular CWM recovery - can't recall as I have not had to try for about 8 months.
4) If you really want to try something completely different, and I am not sure I've got the balls if it was me but if you can get a file to flash from CWM or steam that you can get on from the external SD, you might try CM7. It uses a completely different file system so you'd have to go back to froyo via odin only (as a samsung based rom will not play well when flashed on top of the cm7 file system).
And calling it a day at this one...
Click to expand...
Click to collapse
Okay, basically at this point, I just want my phone to work I've tried what you said. I remember that before rooting my phone initially I was running Froyo 2.2.1. So I found the ROM for that ( http://www.samfirmware.com/WEBPROTECT-i9000.htm ) Just like you said. I downloaded from the *Provider Samsung Galaxy S i9000 heading and picked the I9000BOJS5 ## from February 2011 because I think somewhere around there I updated my phone to Froyo. Flashed it, did everything, still no luck.
I've had a recent hunch though. When the bootscreen boots up, it keeps saying i9000 only, when before it used to say i9000M at least for a little bit (yes my phone is i9000m). Is there a stock froyo rom that's specifically designed to go with the i9000m model? Or are they just all the same?
Never give up
-Thank you so much
So if I reinstall the stock ROM from another Galaxy Ace (same one this thing shipped with), the phone doesn't boot, at all.
I put Cyanogen back on, and it boots fine, but my data connection never works and my voice/messaging connection constantly craps out and I need to reimage again. (Weird...if I go back to a working image, then reinstall my current one, it works fine.)
I'm at a loss...but I'm only one step away from returning it anyway.
IrishRed said:
So if I reinstall the stock ROM from another Galaxy Ace (same one this thing shipped with), the phone doesn't boot, at all.
I put Cyanogen back on, and it boots fine, but my data connection never works and my voice/messaging connection constantly craps out and I need to reimage again. (Weird...if I go back to a working image, then reinstall my current one, it works fine.)
I'm at a loss...but I'm only one step away from returning it anyway.
Click to expand...
Click to collapse
U mean currently u r on cm7 & want to flash a stock rom, but u get bootloops rite?
Sent from Galaxy Ace GT-S5830 using Jusada's awsum ICSunday2 + Slaidmod script.
Dont jus say thanks, use d 'THANKS' button. [XDA RULE]
domnic79 said:
U mean currently u r on cm7 & want to flash a stock rom, but u get bootloops rite? [XDA RULE]
Click to expand...
Click to collapse
Something like that, only it doesn't loop. When I load up a stock rom, it simply hangs at he startup "Samsung Galaxy Ace" screen.
after installing your stock rom wipe your cache and dalvik it will work , if not , use odin and flash a different stock firmware first may be KPN or KPH
Irishred is that the stock koodo 2
3.4 rom? I've been looking everywhere for that, could you post a link maybe as I'm sure there are others looking for this also.
Thanks
Sent from my SAMSUNG-SGH-I997 using XDA App
Well, if you can't flash the stock rom, there's only one thing to do then.
Use ODIN. T_T
It'll push your recovery back to the stock crap too, but then again, there's no reason why it shouldn't work, anyway.
there might be case that it works but you are too lazy to find solution for it to work
what problem you have when you flash stock roms with odin??
You have to flash via Odin, because your internal memory was formated to ext and the stock rom uses a different (I don´t really know which is used by stock rom, but you can google it.)
GerasVille said:
You have to flash via Odin, because your internal memory was formated to ext and the stock rom uses a different (I don´t really know which is used by stock rom, but you can google it.)
Click to expand...
Click to collapse
This is what I was suspicious/worried about. Okay...now to learn to use Odin.
I just found this on sampro.pl I'm at work now so I can't download. Have a look
hotfile.com/dl/137128537/a629597/GT-S5830D_TLS_S5830DTLKI4_S5830DTLSKI4_S5830DTLKI4.rar.html
Sent from my SAMSUNG-SGH-I997 using XDA App
EXT format issue ?
Just a thought...
I once installed a Cyanogen rom on a Galaxy S that changed something in the memory - and stock rom was not working afterwards. I had to go back to Cyanogen. Too bad if you're planning on selling it in stock rom condition.
The only way back was to find a stock rom that contained the whole package - including correct pit file, pda, modem and a repartition of memory.
Flashed via Odin.
Is it a one file/multiple files package? Kernel update?
I hope any of this is can help you solve the problem.
It is a one file package. Password is sampro.pl. It is multi-csc for koodo & telus. Mine loaded up telus so i had to change it. It works great. I will go back to myth ics rom. Its just nice to know that if I need to return to stock I can.
Sent from my SAMSUNG-SGH-I997 using XDA App
Spider9909 said:
It is a one file package. Password is sampro.pl. It is multi-csc for koodo & telus. Mine loaded up telus so i had to change it. It works great. I will go back to myth ics rom. Its just nice to know that if I need to return to stock I can.
Sent from my SAMSUNG-SGH-I997 using XDA App
Click to expand...
Click to collapse
Wow, been looking for this
Will give it a try, Thanks!
Edit: Works great, all back to stock Koodo (temporarily). Thanks again for posting Spider, XD
just to add...
I experimented with a few custom ROMs but they rendered some functionalities un-usable. I tried to recover from a full system and data backup which failed.
From that: 1)Followed instructions from androidadvices.com (androidadvices.com/update-samsung-galaxy-ace-s5830-xwks9-gingerbread-235-firmware/-- page 2) But used stock ROM for Koodo (GT-S5830D S5830DTLKI4) from spidre9909's post;
-- a download link to ODIN is included...
2)Rooted the phone and re-installed Clockwork;
3)Restored my full backup created just before my trials with custom ROMs
Now I am back! At this point, follow unroot procedures — if you want to…
Hope this helps...
DXKPB is the firmware I know that includes data.rfs (which means your /data would get formatted with rfs, and that means stock ROM will love your phone again)
Sent from my GT-S5830 using Tapatalk
how long does this process normally take flashing by odin
meckino2002 said:
how long does this process normally take flashing by odin
Click to expand...
Click to collapse
5-7 minutes
domnic79 said:
U mean currently u r on cm7 & want to flash a stock rom, but u get bootloops rite?
Sent from Galaxy Ace GT-S5830 using Jusada's awsum ICSunday2 + Slaidmod script.
Dont jus say thanks, use d 'THANKS' button. [XDA RULE]
Click to expand...
Click to collapse
thanks
IrishRed said:
So if I reinstall the stock ROM from another Galaxy Ace (same one this thing shipped with), the phone doesn't boot, at all.
I put Cyanogen back on, and it boots fine, but my data connection never works and my voice/messaging connection constantly craps out and I need to reimage again. (Weird...if I go back to a working image, then reinstall my current one, it works fine.)
I'm at a loss...but I'm only one step away from returning it anyway.
Click to expand...
Click to collapse
it's interesting you mention that your wireless connection doesn't work properly. I flashed the newest firmware (something from vietnam I think) and the same thing ... my connection keeps waffling back and forth from H to 3G to nothing at all.
Okay, so I did a factory reset, no custom roms, only had official Froyo and Speedmod kernel. I also unrooted. Why do I keep getting "Unregistered device" from Kies Mini? Maybe it's because my Baseband version on "About Phone" shows "I9000UGJK4"? Or is it maybe that their servers are being bombarded by Cappy users updating their phones? Any help is greatly appreciated.
If you have flashed a custom ROM before, it won't work. Just wait on a Odin/Heimdall one click!
Sent from my SGH-I897 using xda premium
aicirt17 said:
Okay, so I did a factory reset, no custom roms, only had official Froyo and Speedmod kernel. I also unrooted. Why do I keep getting "Unregistered device" from Kies Mini? Maybe it's because my Baseband version on "About Phone" shows "I9000UGJK4"? Or is it maybe that their servers are being bombarded by Cappy users updating their phones? Any help is greatly appreciated.
Click to expand...
Click to collapse
This worked for me, I tried this morning, I had the same issue while on CM9 ICS.
As mentioned flashing any rom your device's I'd might change. I've never had my imei change but read enough ppl to know it happens.
Sent from my SGH-I897 using Tapatalk
I don't know if this matters, but I've never installed a custom ROM, only a custom modem and kernel. Would that change the IMEI?
Have you messed with unlocking it?
Sent from my ICS powered i897
I'm pretty sure kies mini will detect kernel changes. I had stock froyo with a flashed kernel and it wouldn't let me update. I flashed everything back to stock, but was still rooted, and it still wouldn't let me update. I ended up doing a full flash back to stock kb2 and it finally let me upgrade.
I wonder if I flashed the stock kernel and unrooted if it would have worked. At the time I was too lazy to browse for everything and already had the heimdall package downloaded.
Sent from my SAMSUNG-SGH-I897 using XDA App
If your "About Phone" shows anything other than SGH_I897 kies mini will not recognize your device. I was running andromeda , wouldn't see it so I went back to stock, oneclicked jf6. After that kies immediatley recognized it. I probably didn't have to go back to jf6 but, I had nothing better to do for that next hour. If you do go back to jf6 you will have to kies mini twice to get GB, first time it will install froyo, when it's done close kies, unplug re-open kies, re-plug your phone kies will show update again, click and sit back and wait for it to finish. ...you now have GB.
Thank you all for your help. I finally got it. I ended up RE-flashing back to stock using this method: http://forum.xda-developers.com/showthread.php?t=1300843
Turns out that I did in fact have a custom modem and custom kernel, and when I flashed back to stock the first time (I used Clockwork Recovery), it didn't put back the original modem and kernel, thus making Kies Mini not recognizing my phone. So, after RE-flashing the ORIGINAL OFFICIAL Froy update using the above link, everything went smooth fronm there. Hope this helps somebody.
Hi XDA developers,
I'm a newbie. I've been searching posts on xda and still couldn't remedied the problem. I currently have the i9000m from Bell Canada. I upgraded my i9000m to 2.3.3 Gingerbread earlier in Kies. Recently, I've been trying to unlock my phone and without rooting, the best solution seems to be going back to Eclair, so I followed the youtube tutorial by djeddieone and tried to go back to Eclair using Odie. It basically flashes a rom (I suspect that's a T-mobile rom that shouldn't be flashed onto my phone) in Odin. My phone no longer boots and cannot get into recovery mode. (When I try to start the phone, there are random colour dots showing on the screen.) The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Thanks in advance.
I highly doubt that Bell will release a new update for the i9000m. You are better finding a newer rom (JVT or newer) and flashing that via Odin. Im using CM9 nightlies (but I feel it has too many bugs for daily use). If you can find a newer rom that is tweaked, you should notice better battery, faster, etc.
Just my $0.02
Hey I had similar issue - tried flashing new firmware w/odin & stuck with download only... I finally went to a Bell store to send it in, but they were able to use new firmware recovery software to re-flash stock gb2.3.3! I just said Kies messed-up the phone... Anyway, it will get you back to stock functionality. Good luck!
Sent from my GT-I9000M
vassosman said:
I highly doubt that Bell will release a new update for the i9000m. You are better finding a newer rom (JVT or newer) and flashing that via Odin. Im using CM9 nightlies (but I feel it has too many bugs for daily use). If you can find a newer rom that is tweaked, you should notice better battery, faster, etc.
Just my $0.02
Click to expand...
Click to collapse
I have not found any bugs since I update to the latest update-cm-9-20120425-NIGHTLY-galaxysmtd-signed.zip
bioniceric said:
The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Click to expand...
Click to collapse
Since you can still get into download mode, you're OK.
You can download the UGKG3 ROM files from this thread:
http://forum.xda-developers.com/showthread.php?t=1102881
Search for UGKG3.
The file is in 7Zip format. If you don't have something to unpack it, get IZArc.
Flash the 3 files and you should be up and running.
bioniceric said:
Hi XDA developers,
I'm a newbie. I've been searching posts on xda and still couldn't remedied the problem. I currently have the i9000m from Bell Canada. I upgraded my i9000m to 2.3.3 Gingerbread earlier in Kies. Recently, I've been trying to unlock my phone and without rooting, the best solution seems to be going back to Eclair, so I followed the youtube tutorial by djeddieone and tried to go back to Eclair using Odie. It basically flashes a rom (I suspect that's a T-mobile rom that shouldn't be flashed onto my phone) in Odin. My phone no longer boots and cannot get into recovery mode. (When I try to start the phone, there are random colour dots showing on the screen.) The only mode that works seems to be downloading mode. I think I need to flash a stock rom from bell, but the link on sammobile (i9000ugjk3) seems to be expired and cannot be downloaded. So i'm trying to find alternative ways to see how to remedy this problem.
Thanks in advance.
Click to expand...
Click to collapse
After you restore your phone to KG3 via Odin/Download mode per Black Rose's link earlier in this thread, you should be back where you started on KG3.
Then from KG3 ( 2.3.3),
I suggest:
1) Use SuperOneClick to root your phone (SuperOneClick can also UNroot your phone later if you want).
2) Use Galaxy_S Unlock by Helroz available on the G-store.
This worked well for me with no problems.
And just for reassurance, NEVER flash a ROM that is not explicitly for the i9000/i9000M to this device.