Hey folks, heres a synopsis of what I did:
1) Stock Bell Vibrant, rooted.
2) Installed Clockwork, installed, backed up.
3) Tried to install voodoo for vibrant.
Then during reboot, it sat at the "Vibrant" screen for well over two hours before I gave up on it.
Pulling battery and rebooting always ends up on "Vibrant" screen.
I booted into clockwork recovery, and recovered my backup using nandboot. It runs the process for a while then outputs:
ClockworkMod Recovery v2.5.0.4
Checking MD5 sums...
Restoring system...
Restoring data...
E:Can't mount /dev/block/mmcblk0p2
(File Exists)
Can't mount /data/!
If I reboot, I'm stuck at the same "Vibrant" screen.
I've been searching the forums, and the only solution I can find is to re-flash, but I can't find a stock bell rom for the galaxy s... I was under the impression clockwork backed up my original rom.
Anyway, any help you can provide would be great!
Thanks
Shado
You need to learn how to use Odin if you are going to mod your phone with beta software.
You can use Odin to reflash your device to stock. From there you can start over or skip it. Since you had problems with Voodoo make sure you follow the instructions with the addition of checking the "repartition" box.
Check this thread for instructions on Odin: http://forum.xda-developers.com/showthread.php?t=748074&highlight=ODIN
Youtube tutorial: http://www.youtube.com/watch?v=AnY7P14JSWQ
I agree odin is a lifesaver for most ppl here, and it doesn't hurt to learn something new
I've not installed Voodoo yet, but I read through the thread yesterday and If i remember correctly when Voodoo BETA creates it's EXT4 partition it was actually formating the internal SD card. Deleting most of the data, which would include backups. It seems as though people were using Eugine's 2.2 Froyo Rom then going back to there original nanbackup by moving over a backup that they were smart enough to store on their pc. This is all verbatim, and straight from memory. Start at page three and read on if you havn't yet. I hope this helps.
http://forum.xda-developers.com/showthread.php?t=781456&page=3
I love xda and everyone on it!
When I was waiting for a reply I found samsungfirmwareworld and grabbed I9000UGJH2 which was the latest Bell firmware, and I also found the 512.pit.
Following the instructions on that Odin instructions link got me back to stock, and avoided any major medical problems (like heart attack, stress induced coma, etc.).
Thanks so much!!
Now that I'm back to stock firmware, is it ok to re-root, install clockwork, and restore my backup I made pre-voodoo? I did copy the entire clockwork folder from the phone to my PC.
shadoslayer said:
I love xda and everyone on it!
When I was waiting for a reply I found samsungfirmwareworld and grabbed I9000UGJH2 which was the latest Bell firmware, and I also found the 512.pit.
Following the instructions on that Odin instructions link got me back to stock, and avoided any major medical problems (like heart attack, stress induced coma, etc.).
Thanks so much!!
Now that I'm back to stock firmware, is it ok to re-root, install clockwork, and restore my backup I made pre-voodoo? I did copy the entire clockwork folder from the phone to my PC.
Click to expand...
Click to collapse
You do know that the Bell Vibrant is an sgs i9000 and NOT the same as the t959 vibrant for t-mobile that this forum is solely for/about, right?
And yes, you should be perfectly safe to restore your clockwork folder and do a nandroid restore.
Cheers,
=)
~ Jocelyn
s0niqu3 said:
You do know that the Bell Vibrant is an sgs i9000 and NOT the same as the t959 vibrant for t-mobile that this forum is solely for/about, right?
Click to expand...
Click to collapse
Yeah, I figured that out over the course of this whole process. I guess just because they share the "Vibrant" name, doesn't mean they're the same. Given the large number of Bell users here, I'm surprised we don't have our own forum for the i9000m. Would it be more appropriate to post in the i9000 forums, even though the Bell phones (from what I understand and firmware wise) are far from their European counterparts?
Either way, for having these problems and potentially posting in the wrong forum, you folks have been great
I have the same problem but i cannot get the samsung usb drivers to work. please help
@shadoslayer... i'm not really sure but i think the only diff between the bell vibrant ang the international i9000 is the hspa bands since bell vibrant has north america hspa.
except maybe for the few that do not have the 3 button combo.
btw, i'm using a bell phone too, on JM7 firnware.
Sent from my GT-I9000 using XDA App
Clearly I'm an idiot and get over excited. I now need to find the stock Bell firmware to use with Odin so I can go back to normal. Any Canucks with a link to it?
EDIT: I got it back to Bell's stock firmware.
So we can't use what other odin post is using for the i9000m bell vibrant?
How did you get it back to bell firmware?
beowolf said:
I have the same problem but i cannot get the samsung usb drivers to work. please help
Click to expand...
Click to collapse
Download kies
Related
post no longer relevant
If you want to update this, My modified cwm thread has the RED clockwork odin package.
adrynalyne said:
If you want to update this, My modified cwm thread has the RED clockwork odin package.
Click to expand...
Click to collapse
i think omj is going to change his op on af...ill copy that over when he does
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Did you get this solved? Check out the thread at AF I had the same problem
worked like a charm..thanks!
SoCalSpecialist said:
worked like a charm..thanks!
Click to expand...
Click to collapse
ok so i havent been able to find a full answer..but does this leave the device in DI01 or 05 or 09?
just by looking at the files it seems as if it goes from 05 to 09 but once in about phone>build number it reads : DI01
so im just looking for a little clarification here..just rooted my Facinate minutes ago so im still stuck in the whole mindset of the Incredible.
I tried this. Have EA28. Not sure how. Didn't install. Saw install screen on phone last night and hit cancel.
Anyway, Ran Odin, CWMRecovery_DJ05_DL09.tar.md5, reboot, blue text, apply sdcard:update.zip, switched to red text, install zip from sd card, choose zip from sd card, su-2.3.6.1+busybox1.19.zip, choose zip from sd card, DJ05_DL09_kernel.zip (plain kernel due to dl09), ran titanium backup, could not acquire root priv.
Startup screen has sound, but not animation anymore. Installed superuser and it shows titanium backup under "allow". When I run TB, I get the error screen and below in another small screen says, "Titanium Backup has been granted superuser permissions". But can't get anywhere to backup apps. Says Root Access: Failed.
ideas?
Another thing that confused me was the red cwm says voodoo lagfix recovery v2.5.1.x. I thought you weren't supposed to use any voodoo for DL30? Not that I've made it that far due to titanium backup issue, but....
Can anyone confirm whether or not this to sure does or doesn't work with ea28? My wife updated he phone and now she wants it rooted.
Edit this does work for EA28. Everything went smoothly. Thanks nitsuj.
Sent from my SCH-I500 using XDA App
mdisaac said:
When I get in Odin and select CWMRecovery_DJ05_DL09.tar.md5, it fails.
I did not touch any settings in Odin, just clicked PDA and selected that file.
Edit: Redownloaded that file and got it to work. I am now having an issue when applying update.zip... it starts but then comes up with an exclamation point inside of a triangle and the little Android guy... phone reboots fine.
Click to expand...
Click to collapse
I also got stuck at the same screen. what did you do to resolve it????
Here is the link to my guide for rooting with a MAC. I do not have a PC and used these steps to successfully root my phone. After completing last step in guide and getting blue cwm on your phone, DL new red cwm and install
http://forum.xda-developers.com/showthread.php?t=967641
Sent from my SCH-I500 using XDA Premium App
EA28 going to DL09?
Hello..
I am just getting around to rooting my fascinate now. I have EA28. From the instructions, it appears you are going back to DL09. Is that correct? What is the significance of that? Should I care?
Thanks in advance!
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
s44 said:
This thread is old and should be deprecated. The directions still work, but you need to use the Odin package of ClockworkMod in this thread (it's the very first item linked) instead of the md5 file (DL05_DJ09) above.
However, if you're going custom the thing you should *really* do is Odin in one of the full-Froyo packages. This will include both root and recovery.
Click to expand...
Click to collapse
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
I have been reading all the threads but many of them are very long. The DL30 thread is over 50 pages long.
So should I:
1) follow the instructions in this thread but use the new ClockworkMod then
2) update to froyo.
What is the most current thread for updating to froyo on the fascinate while after I am rooted?
Appreciate it.
TheTinRam said:
Thanks S44. My goal is to go froyo, but I need to be rooted first in order to do that.
Click to expand...
Click to collapse
Actually, no you don't. Download mode is magic. You *do* need to be rooted to back up apps with Titanium, if you want to do that. In that case, follow the directions above (with the new recovery). Then back up your user apps + app data.
Whether or not you do this, you should move to Froyo with a full-Odin package. Download the ROM you want (either Nameless, Super Clean, or whatever) in zip form to your SD card. Follow the directions here (under "Most Thorough Method of Fixing Every Problem You Might Have") using the first two files here and the recovery I mentioned in my previous post. Yes, this is sort of overkill, but better to avoid stuff like corrupted dbdata from the beginning and not have to fix it later.
You might want to wait a day or so because it looks like jt is finally fixing up Clockwork.
EDIT: I read almost all of the 52 pages of the DL30 thread to realize that DL30 is out of date . I guess Its going to be EB01 or Superclean. Do you know if Superclean has the audio out via USB working for the docks?
I have some questions in regards to picking ROMs:
I am a little confused in where to find the latest versions. For example in the "most thorough me..." thread, there is a link to super clean version form 3/30/2011 yet wiki has super clean from last year. Where can I look at all the ROMs and descriptions?
Which froyo ROM would you recommend? I love Google's stock froyo, but I also want to use the fascinate's USB audio out on the car and desktop dock. I also would like to wifi tether.
Thanks again!
This post had a link to download ODIN but it was removed. Could you please provide that link again. It also had a link to "Samsung Drivers", don't I need that too?
I am going to take a shot at following the ""Most Thorough Method..." steps tomorrow morning and install superclean on my Facinate. Quick Q: In step one, it simply says to ODIN EB01. I can just do this without being rooted?
Also, you said jt is fixing up clockwork. What do you mean by this, what exactly does not work?
I know these are noob questions, but I am just starting out with this.
Thanks
Driver links are here. Odin is here.
Yes, download mode lets you Odin in complete firmware packages without root.
Most people are using Super Clean, so that has the most support (and themes), but there are some odd issues floating around with it. My guess is that a lot of those issues have to do with not cleaning up in the super-thorough way I'm suggesting, and with the permissions bug after flashing a theme (below). There's also navendrob's EC10-based "Nameless" ROM, and ahmgsk's DL30-based "TrulyFascinating" ROM. Nameless is good but he's about to drop a version 4 with a lot of fixes, so you might wait a day or so for that. TrulyFascinating seemed to be pretty good (heavily stability-tested), but he hasn't updated it in a while (busy with more recent Epic leaks, I guess). You might try running it with one of the state-of-the-art EC10 Voodoo kernels.
There are a couple of Clockwork bugs, but the one causing the most current problems is that the old one couldn't fix permissions properly. This causes issues after making a change to the /system after the initial ROM flash, generally when you flash a theme on top of it. The new one I linked above *can* fix permissions, but still requires you to manually mount /dbdata beforehand (actually, go to the "mounts and storage" submenu and make sure /system /dbdata and /data are all mounted -- that is, the option referring to them says "unmount", which will happen when they're mounted -- before you go to the "advanced" submenu and run the fix permissions script). The new new one coming soon will just fix it without a problem, and do other stuff too.
Once again thanks. I have everything I need....or so I thought.
I restored my phone to factory, loaded the drivers, fired up ODIN and added the PDA and PIT. I hit start.... nothing happens. "All threads complete, succeed 0 / failed 0"
Looks like I am missing something. Do I need to somehow tell ODIN where the phone is? I don't see a way to do that.
PS in step 4 its states "ODIN the CWM Recovery package ROM from this post". Does CWM bin file go into PDA or phone in ODIN?
I one again apologize for my noobiness.
The Clockwork step comes after you do the full package and boot with that.
Make sure you have Odin open *before* you connect the phone in download mode.
Hello, all!
I've purchased a vibrant for my wife over the weekend (i'm on sensation), and have several questions.
The guy i bought it from did a hard-reset supposedly, and said that it reverted it back to the stock android build. Seemed weird, but the first thing i did was update it via kies mini to the froyo build. It's been working fine, except for the camera started messing up last night. Going into black screens, showing "camera failed" errors. It also takes some time (2-3 secs of black screen) to process a picture after it has been taken. I don't remember it doing that on the stock build. I did update it to the latest firmware.
Should i root the phone and flash a different rom? (which rom would you recommend?) A short google search revealed a lot of people having slow-downs after the froyo update.
Appreciate your help!
just to follow-up. wife's been having problems with the music player app hanging, then the phone shut down while she was installing something.... i'm going to wipe everything first to see if it helps any, but will end up rooting it and flashing something else, most likely.
Before rooting make sure you odin back to stock 2.1. That should het rid of the problems
Sent from my SGH-T959 using xda premium
Definitely do what the above poster suggested. Go to the development section and get the AIO toolbox. It has everything you need to get back to stock and get you rooted. If your looking for a good stable rom I'd recommend bi-winning v3. Good luck.
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
RussianBear said:
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
Click to expand...
Click to collapse
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
dseldown said:
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
Click to expand...
Click to collapse
Wow, didn't know this. Will delete kies asap. btw, this rom that i've flashed has a custom kernel (bionix? + voodoo). i did a backup of the stock rom via recovery. do i need to flash the stock kernel first before rolling back to stock?
hereeny said:
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
Click to expand...
Click to collapse
thank you, will check it out!
Project-V is a Great 2.2 ROM, I made a few themes for it too: Blar and WP7 Style
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
lucash312 said:
This is the first time I rooted my phone and I used step 6 on this link in your forum http://forum.xda-developers.com/showthread.php?t=1238070 . Everything went fine but I then downloaded rom manager and when I select flash clockworkmod it only gives me the choice of choosing the samsung epic4g or the samsung galaxyS i9000. It does not give me the option of choosing the fascinate. I selected the i9000 but stopped there because I figured that I should try to fix this situation and be able to select the fascinate, before I move foward. Please help me move foward so I will be able to put a rom on my phone. Any help would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
rom manager is useless for the fascinate...
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
MultipleMonomials said:
I also ran into this issue. If your CWM is not "sticky" (it goes to System Recovery <3e> when you reboot recovery), you must flash the appropriate version of CWM with ODIN before a ROM flash. (CWM ALL.tar for bml roms [anything that is not cm7, MIUI, or ICS] or cwm4_fixed_for_cm7.tar for MTD ROM's [cm7, MIUI, or ICS])
Click to expand...
Click to collapse
if the op would of followed the guides instructions correctly, he would not of ran into that issue in the first place...
droidstyle said:
rom manager is useless for the fascinate...
Click to expand...
Click to collapse
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
You can flash any .zip ROM with CWM. There's no need for ROM Manager. BTW, you can post a link if you uncheck "parse links in text automatically."
Nymblz said:
But if that's the case, why does Koushik make a ROM for the fascinate and have it available on his site?
(Does the Epic4G simply represent all CDMA phones, and the i9000 GSM? Don't see why that would matter anyway tho)
(I can't post a direct &#% link yet, but it's on his website.
This makes absolutely no sense!? He's got ROMs up there for just about every Android phone on the market, all to be used with ROM Manager.
I wanted to install it via Odin but naturally that would be too simple: it's a zip file and Odin won't recognize anything but tar and 2 others formats.
Click to expand...
Click to collapse
all you need to do is boot into cwm recovery via the power menu and flash away. the problem with rom manager on the fascinate is getting into the right recovery...causes more problems than its worth on this device. make sense yet? probably not since you have not been down this road yet, but many of us have. so take the advice given or dont and learn the hard way.
Honestly, I am trying to take the advice given but not all of it fit my situation.
I'm definitely something of a noob to Android (Not to linux or IT though). I've had my phone for all of a month and rooted it only days ago.
It's all starting to come together, finally. It's tricky for a noob because there are so many different versions of the phone hardware, versions of Android, this or that kernel that only works with these ROMs, old/newer versions of those, old posts and advice, newer posts with adjusted advice.. etc.. It's been a week long crash course!
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
So you see, I was in a catch-22; I needed CWM to flash CWM? Odin was my only option at that point.
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Nymblz said:
It's tricky for a noob because there are so many different versions of the phone hardware
Click to expand...
Click to collapse
You are on the Samsung Fascinate. If it is Verizon then it is model number i500. If it doesnt say Fascinate or i500 it isn't for your device and you don't need to worry about it. If you flash something that isn't stated as being for the i500 or VERIZON Fascinate then you will have a lovely new temporary paper weight.
Nymblz said:
Anyhoo, I couldn't flash/upgrade CWM because it didn't stick from the original Odin install. When I rebooted, I'd always return to the stock <3e> recovery. Even after two more installs of CWM via Odin.
I used the cwm-recovery-all.tar in your guide, Droidstyle. (great job BTW)
I followed the directions in Section 6 to the letter. I even printed it out and highlighted key sections.
Click to expand...
Click to collapse
You couldn't have followed it to the letter because it is a well known fact that if you boot up with a stock kernel still flashed it will replace your recovery. Droidstyle certainly knows this and certainly accounted for it in his guide. So, you need to either boot directly into CWM or flash a non-stock kernel prior to rebooting the phone.
Nymblz said:
Then I read on another thread here about renaming the /system/recovery-from-boot.p script, and installing CWM once more.
That worked, so now I can finally boot into CWM recovery like a happy man. (I also tried a more specific version of CWM for good measure: cwm4-bml-i500.tar, not really sure if that made a difference)
So I made my first real nandroid backup last night.
Click to expand...
Click to collapse
Yeah it sounds like that will work...not the most elegant way to take care of it...but it sounds like it would be okay.
Nymblz said:
Next on my list is a new kernel. Still deciding between KGB, lean, and whatever else is out there.
Click to expand...
Click to collapse
We already talked about the kernel situation. Consider Geewiz if you want something thats all-in-one and pretty much impossible to mess up. KGB is good. Leankernel always gave me the best battery life but YMMV.
Nymblz said:
I still don't get the whole mess with ROM Manager though. I agree with you, DS, I just don't get why he'd have zips for every phone under the sun but his own app doesn't seem to allow them to be used. It's bizarre. The latest reviews on the market are not flattering either.
Click to expand...
Click to collapse
He showed no interest in helping the devs here get ROM manager working (again) on the phone. If you gave him money, blame him for not providing the support and resources to get it working on this phone. Some people are umm...."lacking in people skills."
Oh, and as great as the Gingerbread ROMs are...the mtd ICS roms blow them out of the water
Hi everybody,
I've got a friend's I9000M (Vibrant) and needed to upgrade its Froyo OS.
As I'm used to CM9, I started the Full Update Guide as described in the wiki. First I followed [1], by mistake, and flashed a I9000 kernel (hardcore's) into the I9000M using Heimdall (having the phone in Download Mode). It didn't boot up, of course. I was stuck there for a while until I realized that I should have been following [2].
That kernel, cmenard's booted up ok. But then I realized that I needed the CM9 zip in the INTERNAL card (I had it on an external card, as I'm used to other devices). So I had to go back to a stock Froyo ROM.
I looked around for a while and the best I could find was XWJSD (I don't know which firmware revision I had installed before). That kernel booted up OK, seemed to work, so I copied the file to the internal card. Just in case, I tested if it worked as a fallback, so if I screw up I can go back again. WiFi was not working. Everything else seemed ok.
After I flashed cmenard's firmware + CWM, I found that Recovery mode can't mount any partition (only system, no data, no sdcard) [3]. So I'm stuck and can't install CM9 from SDCARD.
So it seems that I can only flash Heimdall-packaged firmwares. I looked around for other alternative ICS / JB ROMs, and the only ones I found weren't Heimdall-packaged. They needed to be installed via Recovery.
So,
1. do these mounting errors mean I fried the internal card? can they be solved?
2. is anyone aware of an ICS / JB ROM packaged in a way Heimdall can upload?
3. do I have a way to know what stock Froyo firmware will work best with this phone?
4. regarding the WiFi issues, does that mean that I need a different firmware or can it be fixed?
Thanks in advanced, any help is much appreciated!
P.S. I looked around the forum but couldn't find answers to these question. If these are asked elsewhere, then I apologize/
-- nachokb
[1] (I can't post outside URLs) the "Samsung Galaxy S: Full Update Fuide" article in CyanogenMod's wiki
[2] (I can't post outside URLs) the "Samsung Vibrant: Full Update Fuide" article in CyanogenMod's wiki
[3] video of CWM Recovery errors: (I can't post outside URLs) Youtube Video ID t2VBt7TsohM
I would ask around the I9000 thread. If you flash any of these ROMs, I think you'll be asking how to fix your friends phone...
Yeah I think toast is right. Even though its called galaxy s vibrant, the i9000m is different than the t959.
sent from the depths of helly bean
Toast6977 said:
I would ask around the I9000 thread. If you flash any of these ROMs, I think you'll be asking how to fix your friends phone...
Click to expand...
Click to collapse
I wondery why, given that this phone is a I9000M. I flashed a different ROM for a while, but after that I flashed a stock ROM and it worked OK.
Thanks!
Yeah I think toast is right. Even though its called galaxy s vibrant, the i9000m is different than the t959
Click to expand...
Click to collapse
Is the T959 somewhat more resilient to internal card damage?
I doubt it, the phones are nearly identical.
sent from the depths of helly bean
Yeah I think toast is right. Even though its called galaxy s vibrant, the i9000m is different than the t959.
Click to expand...
Click to collapse
Just to be sure: this is a Bell I9000M, not a T-Mobile SGH-T959.
I just flashed stock XWJSD. It almost worked. System looks fine. Internal SD Card is fine - NOT toasted :good: (I even could access its previous contents).
Sadly, no WiFi (can't obtain IP address, keeps trying) and SIM locked (!) so no calls and no 3G . So, I'm holding a nice brick in my hands.
I've been trying to flash UGK3G, but I don't know how to flash its 3 files (CSC, PDA, PHONE) with Heimdall, and every forum post or tutorial says something different. Almost giving up here .
Thanks for your answers anyway!
-- nachokb