Related
This issue only applies on Canada Bell Galaxy S Vibrant I9000m (not international i9000)
My experience:
installed Voodoo.. one day, my phone wouln't boot up..
Upgrade a lite version of firmware through odin and update.zip
cell phone stuck at S logo forever
I went to the bell store and got a replace one
I didn't learn my leason...
upgrade 2.2 version to my new device
works fine for 3 days and then fail to reboot
bell store sent my device for repair(i waited 10 days)
they said one of the components on the motherboard got replaced.....
SO please aware!!!!!!
First, DO NOT use odin to retore or upgrade your galaxy. This will cuze flashing(when rebooting), rebooting fail, and stuck at S log.
Reason: Since your model is i9000m not i9000, 99%of the firmwares will not support this model(basically you are using a wrong firmware)
Second: do not install OCLF or Voodoo!! if you feel your homesceen lagg!! you can install laungh pro or ADW(i prefer ADW, fast and easy)
Reason:For people who are using the international i9000, it is fine becasue they can restore the device via odin. Since bell i9000m has no compatible firmware!! DO NOT take the risk!!!!! wait untill 2.2 version which is coming at the end of Nov
I agree with you. Bottom line is dont mess around with the Bell Galaxy Vibrant. Just wait until Bell releases 2.2 for it. It's not the same as the regular i9000 where you can flash roms all you want.
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
If you read around, you're actually one of the lucky ones. I'm on my 5th Bell SGS and of the failed ones:
A) Zero changed ROMs
B) Two I tried to lagfix
C) Three I tried root
My most recent one has survived a little over a month now... rooted, but I've never touched another rom/lagfix.
If you read the Bell SD issue thread, the worldwide 2.2 is a huge contributor to Bell SGS failures.
I agree i was researching about lag fix. When i look for bricking incidence by voodoo or ryanza, it's usually i9000m for some reason.....
But i say we are lucky ones because we dont face too much lag problem. Phone lags at times which i understand. It's been performing way better than my netbook.
Sent from my GT-I9000M using XDA App
ca7846 said:
I agree i was researching about lag fix. When i look for bricking incidence by voodoo or ryanza, it's usually i9000m for some reason.....
But i say we are lucky ones because we dont face too much lag problem. Phone lags at times which i understand. It's been performing way better than my netbook.
Sent from my GT-I9000M using XDA App
Click to expand...
Click to collapse
The lag problem was not an issue for me running JH2 for about a month. Then the slow attacked, and it was lagging lagging lagging..
So it looks like about once a month I'll have to revert to a Nandroid backup to undo the lag mania.
TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
i know that there are some people, such as yourself, that aren't experiencing any issues, but other people, such as myself, have flashed froyo correctly, and have their phone die within a couple of days as a result. there has to be something else that is different, if the hardware is the same.
if you look at the two threads about sdcard failure, it's 12% for the i9000's and 30.97% for the i9000m's. clearly more than double the failure rate. i think there is definately something that is different between the two. i just wish someone could figure it out so i could safely flash international roms.
wang1chung said:
i know that there are some people, such as yourself, that aren't experiencing any issues, but other people, such as myself, have flashed froyo correctly, and have their phone die within a couple of days as a result. there has to be something else that is different, if the hardware is the same.
if you look at the two threads about sdcard failure, it's 12% for the i9000's and 30.97% for the i9000m's. clearly more than double the failure rate. i think there is definately something that is different between the two. i just wish someone could figure it out so i could safely flash international roms.
Click to expand...
Click to collapse
Spot on. Most threads here with the Bell i9000M are mostly seeking help to fix their bricked phones. And if you read them, the problem usually comes after applying lag fix or flashing a rom, etc. It wont come immediately, but the phone will start to "die" out. It may or may not happen to you, but the probability is quite likely.
I think the difference is.most of the euro 9 000 r 8gb.versions... the 9000m r 16gb versions... diff memory chip.
Sent from my GT-I9000M using Tapatalk
TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
I agree with you. We all know there were some 9000m with internal memory issues that caused some failures and flashing has its risks, no matter what phone you use.
I've flashed my i9000m now about umpteen times, I've run voodoo, oclf, among other things and haven't had any problems. So now I'm using JPK without any lagfix, and its running perfectly now.
wlz1028 said:
This issue only applies on Canada Bell Galaxy S Vibrant I9000m (not international i9000)
My experience:
installed Voodoo.. one day, my phone wouln't boot up..
Upgrade a lite version of firmware through odin and update.zip
cell phone stuck at S logo forever
I went to the bell store and got a replace one
I didn't learn my leason...
upgrade 2.2 version to my new device
works fine for 3 days and then fail to reboot
bell store sent my device for repair(i waited 10 days)
they said one of the components on the motherboard got replaced.....
SO please aware!!!!!!
First, DO NOT use odin to retore or upgrade your galaxy. This will cuze flashing(when rebooting), rebooting fail, and stuck at S log.
Reason: Since your model is i9000m not i9000, 99%of the firmwares will not support this model(basically you are using a wrong firmware)
Second: do not install OCLF or Voodoo!! if you feel your homesceen lagg!! you can install laungh pro or ADW(i prefer ADW, fast and easy)
Reason:For people who are using the international i9000, it is fine becasue they can restore the device via odin. Since bell i9000m has no compatible firmware!! DO NOT take the risk!!!!! wait untill 2.2 version which is coming at the end of Nov
Click to expand...
Click to collapse
Very good morning,
First I want to congratulate you for the support given from this site, second I would like to explain my problem
I have a Galaxy S GT19000 8 gb I have it with my operator Movistar, the problem is that for some reason I upgraded the firmware by mistake and now I get the logo type AT & T and I finally fails PANIC KERNEL, I tried to restore it but Unfortunately in any PC that connects Sea XP, VISTA, WIN7 recognizes me, I wonder if there is any solution to this problem and now I have to admit that only serve to throw.
Greetings and again good work that they are doing.
I don't have any issues with my i9000M.
I've rooted it, flashed 3 times with official firmware from Kies (no registry change) and also applied OCLF. My phone is still up and running! (*knock on wood*)
MaelstromXC said:
I don't have any issues with my i9000M.
I've rooted it, flashed 3 times with official firmware from Kies (no registry change) and also applied OCLF. My phone is still up and running! (*knock on wood*)
Click to expand...
Click to collapse
go flash jpm, and report back after 3 days and a few reboots.
the issue isn't with official bell roms, it's with international ones. if you flash jpm, you have a high chance of your phone bricking (unless you're one of the few lucky ones).
shadoslayer said:
I agree with you. We all know there were some 9000m with internal memory issues that caused some failures and flashing has its risks, no matter what phone you use.
I've flashed my i9000m now about umpteen times, I've run voodoo, oclf, among other things and haven't had any problems. So now I'm using JPK without any lagfix, and its running perfectly now.
Click to expand...
Click to collapse
well, if we are so sure the hardware is the same, the only thing left is the bml's, correct? if that is where the wear leveling is, why don't we extract and compare? i sent mine in, but i do have a backup of bml3 and bml6.
I had Darky's 2.2 ROM on my i9000m for two days before flashing back go JH2+Voodoo. I didnt specifically have any problems with the phone, but the ROM took away my 850MHz band so I reverted.
Hi,
I'm new here and I bought a Bell Galaxy last week. Yesterday, I installed OCLF on it and have no problem yet. Should I uninstall it to make sure?This thread put a doubt about my OCLF installation.
Any advice? If my phone bug, there will be a "factory reset" option for me?
Regards,
Snooze
I have the Bell Vibrant i9000m and have flashed about 5 times. Unlocked and running on Rogers. I've only had one problem and that was the phone restarting during a flash, went into download mode and restored to stock 2.1 via Odin3 1.3.
I have the GT-I9000M and never encountered a problem of flashing different firmwares, until I tried flashing voodoo. I believe the problem lies in the original F/W Kernal's not recognizing the partition of the internal SD since the Partition are in a different format. Creating a SD Card Failure when putting an original F/W without disabling voodoo first. Since it cannot mount the partition it cannot copy over files over to install a different F/W. I just wish there was a small Flash Kernal that would simple wipe the SDCard, partition and format to the original format for convenience sake of all these troubled i9000 users. I've just encountered this and is the only time I've ever encountered a problem with SDcard failures. I've flash numerous F/W without any problems. I've gone 2.1 to 2.2 back to 2.1 (UG8/JH2/JM8&Voodoo/JPA/JPK/JPM). From losing my 850 band just to get it back with the right procedure. All I can say RFS may not be the best file system but its the one I'll probably stick with when I get my phone back. Besides 2.2 was never that bad without a lag fix anyways just wanted to try something new. Also just in reference it has also shown in polls that it didn't matter whether you were on 2.1 with or without lagfix or 2.2 with/without lagfix either that the Sd Card could also fail. For now I'm just sharing my experience
Woolios said:
I have the GT-I9000M and never encountered a problem of flashing different firmwares, until I tried flashing voodoo. I believe the problem lies in the original F/W Kernal's not recognizing the partition of the internal SD since the Partition are in a different format. Creating a SD Card Failure when putting an original F/W without disabling voodoo first. Since it cannot mount the partition it cannot copy over files over to install a different F/W. I just wish there was a small Flash Kernal that would simple wipe the SDCard, partition and format to the original format for convenience sake of all these troubled i9000 users. I've just encountered this and is the only time I've ever encountered a problem with SDcard failures. I've flash numerous F/W without any problems. I've gone 2.1 to 2.2 back to 2.1 (UG8/JH2/JM8&Voodoo/JPA/JPK/JPM). From losing my 850 band just to get it back with the right procedure. All I can say RFS may not be the best file system but its the one I'll probably stick with when I get my phone back. Besides 2.2 was never that bad without a lag fix anyways just wanted to try something new. Also just in reference it has also shown in polls that it didn't matter whether you were on 2.1 with or without lagfix or 2.2 with/without lagfix either that the Sd Card could also fail. For now I'm just sharing my experience
Click to expand...
Click to collapse
totally agree...http://forum.xda-developers.com/showthread.php?t=793404...look at the number it doesnt matter if it is 2.1 2.2 or no lagfix....the amount of sd card failures are the same...it isnt the rom its just ur phone...numbers dont lie
TriC_101 said:
This Thread is pointless.. just because you have issues does not mean that all i9000m phones will have the same issue.. I for one have been running 2.2 for a long time now.. and so have many others.. I have flashed my phone over 20 times now.... and the i9000m has the same hardware as the i9000 the only thing that is different is the stock firmware and the radio.. they are made on the same line.
Click to expand...
Click to collapse
Exactly what I was thinking.
I've looked around and I can only find ODIN roms for J16. Anything that can be flashed with Clockwork? It's probably right in front of me knowing me. Am I missing something?
No, ODIN is not an option.
I just installed bionix fusion, which is based on JI6 but with the JI2 modem. However there is a clockwork-flashable JI6 modem that I used.
This took about 10 seconds to locate:
http://forum.xda-developers.com/showthread.php?t=808830
I saw that, but I also saw that it had some wifi bugs while reading the topic. I'll try it but I need a clean and bugless flashable image of J16.
I hate bumping topics, but I have to. Are there any stock J16 clockwork flashable images available that do not have Wifi issues?
If not, do you think when Froyo stock is released they will have one? I really want Touchwiz froyo when it comes out (Soon! The i9000 is getting updates as we speak). Whether it's having stock J16 and upgrading through the carrier or flashing a stock froyo rom through clockwork, I just want to make sure I have TW froyo.
If you just need the ji6 modem then can't you just go to team whiskey website they have the ji2 n ji6 modems.. If thats not what your looking for then sorry.
Sent from my SGH-T959 using XDA App
It doesn't appear that there are solid flashable JFD/JI6 ROMs. Some will argue about TouchWiz, Bionix has integrated a portion of TW in Fusion but you want stock. So....
Option 1) Buckle down, sell the Apple, get a PC, use Odin, install JI6.
Option 2) If you've got a newer Apple, buckle down, install parallels/bootcamp, install XP/Win7, use Odin, install JI6.
Option 3) Use a friends PC, use Odin, install JI6.
~SB
ODIN isn't an option because you are using a Mac? I don't think I read that. Please inform us otherwise why you can't use ODIN.
wait, if all this is just because of froyo, just freaking flash eugene r6 when it comes out or just wait for one of the developers to get the OTA froyo and make a flashable version.
Flash bionix and enjoy it in the meatime...
kangxi said:
ODIN isn't an option because you are using a Mac? I don't think I read that. Please inform us otherwise why you can't use ODIN.
Click to expand...
Click to collapse
99.7% of the time that's the predominant answer as to why someone can't use Odin. So I'm assuming that's why s/he can't...
I'd like an answer too, I hate following the SWAG principle.
~SB
I should have mentioned why I can't use ODIN. Haha. Well, there ARE only Mac's around me but my issue is that my computer that I have with me where I'm at currently is my netbook. ODIN is too big for the resolution on my little 10.1 inch screen. Haha. I guess I can try dual booting an old copy of XP on my brothers Macbook.
EDIT: I might have been the only one in the world to not like Bionix. The standby battery life was meh on my device. I'm using AOSPish by Anderdroid and I love it. My quest for stock TW was in case I ever needed to send the device back to T-Mo.
It's really a shame to start off in a place with a post that has someone mad at themselves for performing a soft brick on their relatively new Verizon Samsung Fascinate. I have to admit I love the phone, but after seeing some videos about DarkyMod I was so impressed I felt compelled to try it.
All I've done, far as I know, is Rooted the phone, but I also used Odin and apparently flashed the incorrect kernel. So what happens now is when I power on my Fascinate, I get a Galaxy S (GT-i9000) screen. At this point, the phone reboots. I know I'm an idiot for having used the wrong Odin kernel, but after attempting to decipher the post in the Darky's installation for "first timers" I apparently choose the incorrect kernel.
At any rate, I suppose I could ask for an experienced modder for the right kernel, the one that would allow me to perform the flash after I had installed the ROM Manager, etc.. But I doubt that would help. What I'm looking for is a file which has been removed from the forums here, and was originally in someone's Dropbox account.
I believe that the file that I'm looking for is the "Stock-i500-VZW-Kernel.tar.md5"... I might be incorrect, as I had mentioned I believed I had successfully "rooted" the phone, but when I used Odin to flash the kernel, I think that's where I went wrong. Can anyone help me find this file? Or should I get the modified kernel, which will allow me to perform the backups and then the flashing to this mod? Thanks ahead of time, I do apologize for the length of the post.
-
T.C.
Samsung Fascinate (Verizon) DL09
http://forum.xda-developers.com/showthread.php?t=867648
thats full d101 thread
http://forum.xda-developers.com/showthread.php?t=885262
thats full dj05 thread
both should be able to get you back to stock through odin then you can restart what you did. personally i keep both handy since i already had to use them due to an error that cause the phone to freeze up completely at the samsung logo. hope that helps
Thank you kdaz!
I'll give that download a shot real fast and see what happens. I'm assuming you've modded/rooted your Samsung Fascinate? Which of those Odin kernels did you use to successfully start changing things? I never did get past the "update.zip" part, it always came back with an error.
Thanks for taking the time to write a response, I really feel bad to post and have my first ever be a soft bricked phone, haha!
Quick thank you...
After looking all over the forums here, and elsewhere... I did find what I was looking for, though I didn't manage to restore the kernel and save my settings, I did unbrick the phone by reapplying the DL01 firmware with the Odin software. The forums here were a huge help, and I just wanted to say thanks!
haha glad you got it working. yes i have rooted and modded mine. got it last thursday brand new and was modding it on friday when i got back from vacation. friday night i feared that i had totally bricked it but luckily found both of those files on the forums. i believe i used the dl05 one then imediately updated to the dl09 radio and now running blaze voodoo kernel clocked at 1.2ghz and i honestly forget what rom lol waiting to use aosp
Thank god these phones are so easy to unbrick with Odin. Almost impossible to truly brick, though sometimes you might lose some data here and there or it won't save your data etc. That's why you might need to odin the full stock rom more than once
Thanks for the responses guys, kudos!
I had really hoped to start using Darky's ROM but it turned out that I didn't have the right modem file, or at least, that's what Darky said. At any rate I was kind of curious which custom ROMs you guys are using and why? The names alone should be sufficient, there's so much information here on these forums.
I admit I'm worried to reflash but at the same time, I know how to do it and if something goes wrong I just use Odin and apply DL01, or whatever the original ROM is called. Any thoughts about good and fast custom ROMs on the VZW Fascinate, guys?
Look for the full DL09 Odin, DI01 is really old and DJ05 was killed inside VZ before it was ever released to the general public.
As you have discovered, the Fascinate is its own animal and you cannot flash stuff made for other Galaxy S phones to it unless you feel like breaking your phone on purpose. Most of us are running one derivative or another of DL09 that has been hacked up in various ways to remove the stock bloatware, add root/themes, add new functionality into the kernel, etc. Some of us are using AOSP or CyanogenMod froyo-based roms which (still) have many/most things broken. We are finally about to have official updates to 2.2 and that is the missing piece that was needed to get full custom development working. Big changes will be coming before we know it.
[email protected]
I had just read earlier that there was a Froyo leak, I'll be really curious to see whether or not it speeds things up or not. It sounds like the custom ROMs are here for our VZW Fascinate but what I'm really looking (and waiting for like everyone else) is just Froyo. I'm grateful to everyone here who reached out and helped.
I'm not sure if my rooting days are done, but I got pretty scared when I thought I'd bricked this thing. Can't thank you guys, and the community, enough.
im currently running OTB ul1300 kernel which has the voltage turned down and processor speed of 1.3ghz and im currently running the dl09 supah clean rom. was running kaoscinate yesterday but missed being able to use my camera. the flashablility of this phone is great..i love just switching roms and kernels almost completely at will. cant wait until they get the leaked froyo out to use but im enjoying trying everything else until then.
tclore77 said:
I had just read earlier that there was a Froyo leak, I'll be really curious to see whether or not it speeds things up or not.
Click to expand...
Click to collapse
If you really want a boost in your phone speed, you should look into getting custom ROMs and kernels, not Froyo. There are a bunch of kernels out there that are overclocked (and even undervolted, to save battery life too) that will significantly improve your performance.
The best thing you can do with your phone is to get yourself a custom ROM - something like Blackhole 3.0 by sonofskywalker or SuperClean 0.4. Those will get rid of the bloatware crap that Verizon puts on your phone, and (more importantly) change the default search from that P.O.S. Bing back to Google.
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)
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
tamaleddon said:
Weird colors on boot usually are a sign of an incorrect bootloader version. Since you seem to be familiar with darky stuff (ugh) you could try the darky resurrection edition; there should be easy to follow instructions on their site.
Click to expand...
Click to collapse
I just flashed the RE version and it's making some progress. Definitely no weird colors.
PROBLEM:
-the boot screen is still flashing when trying to boot my phone, only this time it's with the "Darkcore & Darky's ROM" logo on it. The flashing is at a slower pace this time around.
ALSO:
I can get into the stock recovery screen, I hope this can somehow help
what should I doo!!?!
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
gfacer said:
Ok see your here too and more q's for you based on what I see here:
1) What did you start with as a rom before 10.2 (stock GB, Froyo rom or ???)
2) The RE version - was that GB or Froyo?
I am thinking as the other poster alluded to is that maybe you went from a Froyo rom to 10.2 without getting the GB bootloader from a stock rom (odin with bootloader update checked) and now you are still working with the wrong bootloader?
If that sounds like what happened try flashing the RE edition for Froyo (9.3 I think) if you haven't already.
G
Click to expand...
Click to collapse
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?
As far as i read on the Darky Site you have to activate Lagfix to install 10.2
Do you?
In other case.
Install Resurrection 9.2 FW:
(sorry. new member no links outside allowed: Go darky forum, stable roms, darky resurrection 9.2)
If that works your bootloader if for Froyo and afterwards you can go on to flash Darkys 10.2 like written in the Darky Forum.
But i would suggest to stay on Darky´s 9.5 with 2.2.1
It is the stable version with no bugs at all. This gingerbread sucks a lot with Akku Drain, Light sensor and other thing. Also no call records.
I will stay on 9.5 so far. Best solution at the moment...
The thing with installing 10.2 you installed without installing 2.3.3 rom before could be, that is maybe possible to install Darkys 10.2 Theme on a 2.2.1?
But no guarantee...
roma17 said:
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?
Click to expand...
Click to collapse
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
sxi200 said:
The colour distortion problem is 100% caused by incorrect bootloaders. Download jvq from samfirmware (or another 3 file gingerbread of you have one already), use the Odin version contained in the download, tick repartition and update bootloader then flash.
Download cf root for jvq and flash that as PDA without repartition. After the phone boots downlaod darkyrom from the market and from it flash darky 10.2.
Personally the kernal that comes with darkys takes too long to load the phone so I use galaxian instead. Phone flies and it's the first custom jvq rom I've used which doesn't reboot itself.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Thanks for your response! Greatly appreciated. But at the time, I'm just looking to get my phone to work. It still doesn't work, it's still only stuck flashing the bootscreen, nothing else.
From my other post:
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
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Could be that you have a lagfix enabled and the stock ROM can't read the EXT4 file system. If so, try flashing another custom ROM via Odin (e.g. GingerReal), disable the lagfix to go back to RFS, then from there you can go back to the stock ROM.
gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Well CM7 forum is down but here is the most of the link, you can google this and look at the cached pages. cyanogenmod topic/15707-how-to-restore-to-stock-on-your-gt-i9000m/
You should be able to click to the multi upload link too.
Now - you are aware of course that our i9000m models can suck and die fairly readily, especially when flashing certain roms. Has yours even been returned yet? Mine has and they replaced the motherboard. You may actually have a warrenty job and in any regard they won't likely fight too hard (just flash it to one of the jl2 or kc1 rom first).
If you want to find out for sure. look for the i9000m threads where they install eclair and use the external sd to boot and then look at the memory (internal then shows as external I think - its in the thread). Basically if it shows 0 available you're hooped.
gfacer said:
Yes jl2 or kc1 roms are I9000M specific. But both need dbdata.rfs added to the roms from samfirmware.com if you repartition.
There was a post on the cm7 forums with a complete jl2 rom someone compiled with dbdata.rfs added. Look for that post as it might have some other info too.
The i9000 you see means the kernel is for i9000. But that shouldn't matter.
It's worth a try but I think that a trip to samsung is on your phones future.
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
I'm downloading the ROM from this link, could you verify it?
http://forum.xda-developers.com/showthread.php?t=883568
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
there is a I9000UGJL2_homebinary_add_param.tar
and a SS_DL.dll
so All i would have to do is just put that .tar file in PDA field and get a regular .pit file and check off the re-partitions
gfacer said:
It may not have dbdata.rfs in it which you need if you repartition. I think they leave it out so regular users do not have to reinstall all their Apps.... Just look at what's in the file...
Sent from my GT-I9000M using XDA Premium App
Click to expand...
Click to collapse
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Great!
My advice would be to pretend it never happened, but read all the instructions for the rom you are interested in and start from scratch.
Generally I would go custom froyo kernel from odin which will root you and give cwm generally, update bootloader to gb via a stock rom or ezbase, then flash 10.2 via cwm.
Darky has excellent guides also look at ezbase thread.
Sent from my GT-I9000M using XDA Premium App
roma17 said:
Okay, I have great news!!!!!!!!
I flashed that previous stock froyo ROM and finally can use my phone once more!!!
THANK YOU VERY MUCH!! Special thanks goes to gfacer! I could never have done it without you!
needless to say, I still require a custom ROM such as Darky's 10.2 RE on this phone of mine.
As a final request, would you be so kind to list all the things necessary for me to do in order to get all the way to darky's 10.2 with the lagfix and all?
Or if not, at least a thread or website that says exactly how to do it on my phone (i9000m) ?
Thanks ever so much!!!
Click to expand...
Click to collapse
To load Darky 10.2 successfully on your phone, you have to flash JVP or JVQ bootloader over your phone. The best solution is flash Stock Rom with bootloader over your phone. Then, flash Darky rom over your phone.
The vibrant i was rooting needed to be reverted back to stock in order to root. I launched odin and download mode on the phone and put in the tar and pit files to revert it to stock. After doing this, the phone was soft bricked, when i turn it on it only shows the Vibrant screen and then turns off and on again. Recovery mode won't boot up, it gives a fuzzy screen, however Download mode still works. I tried multiple times to use odin and flash a stock rom again, but it resulted with the same vibrant screen turning on and off again.
I reinstalled and updated drivers, tried using the command prompt to launch recovery(this led to "error:device not found"), tried one click unbrick programs, all to no avail.
Is there any other solutions? Thanks
First thing I must ask, what is the device model number? Does it have front camera?
I must ask these questions as there have been a lot of people posting in this section with a T-Mobile Samsung galaxy s 4g (sgh-t959v) or with the Telus galaxy s vibrant (gt-i9000m.)
If you indeed are in the right place, T-Mobile galaxy s vibrant (sgh-t959) you can try the vibrant AIO toolbox. You can DL it in this thread
http://forum.xda-developers.com/showthread.php?p=31279153
You can find more info about it here but I think the DL links aren't working, that's why I gave the other link.
http://forum.xda-developers.com/showthread.php?p=11358713
Paranoid, sitting in a deep sweat...
samsgun357 said:
First thing I must ask, what is the device model number? Does it have front camera?
I must ask these questions as there have been a lot of people posting in this section with a T-Mobile Samsung galaxy s 4g t959v or with the Telus galaxy s vibrant i9000m.
If you indeed are in the right place you can try the vibrant AIO toolbox. You can DL it in this thread
http://forum.xda-developers.com/showthread.php?p=31279153
You can find more info about it here but I think the DL links aren't working, that's why I gave the other link.
http://forum.xda-developers.com/showthread.php?p=11358713
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
Toolbox is no good :/ still have the same issue. usb debugging may not have been turned on...i'm pretty sure it was on because the phone was upgraded to gingerbread via kies before
edit: yea it has a front camera and it's a t959
No its a t959v, the t959 never got upgraded to gingerbread and doesn't have a front camera unless you added it.
Try this http://forum.xda-developers.com/showthread.php?p=19601787
Here's some more files etc for your device http://forum.xda-developers.com/showthread.php?p=11819954
Paranoid, sitting in a deep sweat...
nice catch..
all better! thanks!
jaydoubleyou said:
all better! thanks!
Click to expand...
Click to collapse
Don't forget to hit the thanks button!
Paranoid, sitting in a deep sweat...
Now I see why Toast made that thread.
Like Tibbs said, Nice Catch!!!
samsgun357 said:
First thing I must ask, what is the device model number? Does it have front camera?
I must ask these questions as there have been a lot of people posting in this section with a T-Mobile Samsung galaxy s 4g (sgh-t959v) or with the Telus galaxy s vibrant (gt-i9000m.)
If you indeed are in the right place, T-Mobile galaxy s vibrant (sgh-t959) you can try the vibrant AIO toolbox. You can DL it in this thread
http://forum.xda-developers.com/showthread.php?p=31279153
You can find more info about it here but I think the DL links aren't working, that's why I gave the other link.
http://forum.xda-developers.com/showthread.php?p=11358713
Paranoid, sitting in a deep sweat...
Click to expand...
Click to collapse
I am not the original asker but I as well have a problem and I don't want to start waves of simillar questions. Soft Bricked my phone yesterday by overlooking a most likely common mistake. I flashed CLM Recovery but accidently selected the wrong model UGHHH! Now I get the T Mobile Screen and I can get into download mode, thats it. I am aware of this Vibrant AIO ToolBox but Im not sure how it works and I am aware of ODIN which I have also never used. I downloaded ODIN and it does recognize my device. It looks pretty simple to use although I may be wrong. One of my major problems is I can not download any Stock OS Roms because the range at about 200mb and I am currently staying with a relative that has dial up. I dont know if I could get something faster through email. What I would like is step by step instructions on how to get my phone back to stock or somewhat functional. Any help would be greatly appreciated as we all know how hard it can be without your phone. Thanks, J
Samsung Galaxy S 4G ((ROOTED))
SGH-T959V
GingerBread 2.3.6 (Installed Stock)
T-Mobile USA
Capablities: Download Mode
Your also in the wrong thread. Don't flash any files from this section. This is for T959 not T959v.
You can find files to flash your phone back to a working state over in the Samsung Galaxy S 4G section of the forums.
You were just sliced bread before you were burnt by the toaster.
jlwarner687 said:
I am not the original asker but I as well have a problem and I don't want to start waves of simillar questions. Soft Bricked my phone yesterday by overlooking a most likely common mistake. I flashed CLM Recovery but accidently selected the wrong model UGHHH! Now I get the T Mobile Screen and I can get into download mode, thats it. I am aware of this Vibrant AIO ToolBox but Im not sure how it works and I am aware of ODIN which I have also never used. I downloaded ODIN and it does recognize my device. It looks pretty simple to use although I may be wrong. One of my major problems is I can not download any Stock OS Roms because the range at about 200mb and I am currently staying with a relative that has dial up. I dont know if I could get something faster through email. What I would like is step by step instructions on how to get my phone back to stock or somewhat functional. Any help would be greatly appreciated as we all know how hard it can be without your phone. Thanks, J
Samsung Galaxy S 4G ((ROOTED))
SGH-T959V
GingerBread 2.3.6 (Installed Stock)
T-Mobile USA
Capablities: Download Mode
Click to expand...
Click to collapse
Head over to the SGS 4g section and look through the stickied threads. They should have the files you need as well as instructions. The steps for your device are probably identical to the vibe but I don't want to steer you wrong. Your biggest problem will probably be getting Odin to recognize your device. Try different USB cables and different com ports. You might have to manually load drivers on the computer. Good luck.
No tickee, no laundry!
Be careful with odin
what stock are you trying to flash? 2.2.1 or 2.2? Because some stock can fry your motherboard, like my vibrant, and then the phone is unusable....
help help help
hi i try to upgrade mu vibrant t959 in android 2.2 to android 2.3.5 and after odin fail my phone never turn on again i press all bottom and the screen is till in black if somebody know why i need to do for turn on again let me know or tell me if my phone is damage.thanks
frankie3335 said:
hi i try to upgrade mu vibrant t959 in android 2.2 to android 2.3.5 and after odin fail my phone never turn on again i press all bottom and the screen is till in black if somebody know why i need to do for turn on again let me know or tell me if my phone is damage.thanks
Click to expand...
Click to collapse
what files did you put into odin to upgrade to 2.3.5? the newest stock rom the t959 officially got for odin was 2.2.
if your phone can still get into download mode, you can use the vibrant AIO to return it to stock.
You can download AIO here - http://d-h.st/kWH
Here is the AIO thread - http://forum.xda-developers.com/showthread.php?t=954509
frankie3335 said:
hi i try to upgrade mu vibrant t959 in android 2.2 to android 2.3.5 and after odin fail my phone never turn on again i press all bottom and the screen is till in black if somebody know why i need to do for turn on again let me know or tell me if my phone is damage.thanks
Click to expand...
Click to collapse
Sounds like a brick, sorry.
Try plugging into charged and see what you get.
You also might try a jig to see if you can get it back in DL mode. Also try heimdall one click.
If all else fails go to
www.mobiletechvideos.com
They do JTAG repair and also sell the jig.
I approve this message.