Related
After trying to partition the EXT feature within CLMR once my phone reset it came back up with the boot screen everything normal than nothin but a blank screen. I go back Reflash with Odin and Current Vibrant-Tmo image on here. Result was delayed audio for TMobile start up GIF and sound and no Screen response. Wen tback attempt #2 with Odin/T959UVJD flash phone resets and goes absolutely dead. Remove battery same thing. Anyone else have trouble with Clockwork Mod's partitioning?
I also noticed if you get the phone-!-pc error just running the 512pit file seems to fix it atleast it did for me.
If you had read up on here, you would know that Clockwork tries to partition the internal flash and breaks your phone. You need to Odin flash with the "re-partition" box checked. That should fix it. I have posted a ZIP you can flash that will parition the external card properly, you can edit the script and change the partition sizes if you like, it's set to create a 1GB partition for EXT4 with the remainder as FAT32.
It has been said several times in several places...
DO NOT PARTITION WITH CLOCKWORKMOD RECOVERY
I reflashed with Odin and checked Repartition and thats when it just died after reset, no power no nothin.
I also made the noob mistake of partitioning with clockworkmod . However, my device wasn't bricked. instead, it left absolutely zero memory left for third-party apps and the like. I'm not sure if I should reflash with ODIN since my issue isn't as serious as a brick. Any experienced members on this thread please help.
honoluluacx said:
I also made the noob mistake of partitioning with clockworkmod . However, my device wasn't bricked. instead, it left absolutely zero memory left for third-party apps and the like. I'm not sure if I should reflash with ODIN since my issue isn't as serious as a brick. Any experienced members on this thread please help.
Click to expand...
Click to collapse
Follow this
http://forum.xda-developers.com/showthread.php?t=745547
^ Since the links in that thread no longer work (Eugene left XDA), all you need to do is flash eugenes froyo that doesnt brick (sounds like you have it), pull the battery when done, then flash the stock ODIN pit/tar for JFD, Fixed.
True, that works even better
http://www.4shared.com/file/dJiyRz3v/EUGENE373_SamsungS_Froyo_PDA.html
s15274n said:
^ Since the links in that thread no longer work (Eugene left XDA), all you need to do is flash eugenes froyo that doesnt brick (sounds like you have it), pull the battery when done, then flash the stock ODIN pit/tar for JFD, Fixed.
Click to expand...
Click to collapse
So do I need to reflash eugene's froyo rom or, since I already have it, skip the reflash and go straight to odin? Also, thanx in advance for all the helpful senior members.
HELP!!! I followed the instructions to the letter, but after about three attempts with ODIN, by vibrant still won't boot up. I can still get to download mode, but can't reboot.
power off phone
pull out battery
GRAB THIS STUFF : http://forum.xda-developers.com/showthread.php?t=1047087
turn on odin
attach phone to pc with usb cable
now while holding down both volume buttons put battery back in.
now you should be in download mode and go back to stock with odin from here!
make sure u put the proper .pit and .pda file in there proper places on odin and ur set to go.
Enjoy and also make sure u have the proper samsung drivers
honoluluacx said:
HELP!!! I followed the instructions to the letter, but after about three attempts with ODIN, by vibrant still won't boot up. I can still get to download mode, but can't reboot.
Click to expand...
Click to collapse
Are you online?
I followed the guide. Unfortunately, the device hanged during the reboot. I didn't do anything during that time, so I threw in the towel and told T-Mobile I tried to update to 2.2 and sent it in. Thanks for the links though.
So a buddy at my wrok got a new vibrant. I have a mts and a g1 and am familiar with rooting and all that. So of course seeing what I can do with my phone he wanted to root his and learn about android. So we rooted his phone and he was runing bionix 1.4 oc uv. He told me his phone died because his batery ran low. He then preceded to try and turn his phone on to make a quick call. Well it would only boot into recovery so he asked me to help. Him fix it. I took a look at his phone and I tried to turn it on and it goes strait from the vibrant screen to the standar blue recovery. He thot the phone mite not be reading the sd in recovery mode and only read the internal memory ,because he would push install update.zip like he would before to get into clockwork and it would just give an error. Well I eliminated the sd not readin question because in the error message ot says reading sdcard/update.zip. and since he has no update.zip its not loading anything. So can I just rename a rom zip from here name it update.zip and will it fix the problem,or do I need to put the clockwork update.zip on there. Or is there a nother way to fix it. Stock image?
lol yeah that would be me. i saw that one method to fix something like this was to use odin but everytime i try to download odin, ubuntu tells me that the archive type is not supported. i was using the link from the vibrant "bible". i dont really care if i have to go back to stock as long as i have a working phone.
**new knowledge... no odin for linux so far as i can find so if anyone has ideas using ubuntu then that would be great.
Lol this is who I'm helping^ hey we never tried just putting a rom on ur sd and renaming it to update.zip. take the latest bionix and rename it update.zip put it on ur sd and flash it
No voodoo lagfix? Cuz that complicates things
Sent from my SGH-T959 using XDA App
Ya I believe I installe jacs kernel with his lag fix. Can I just use odin to put his phone to stock and re root
careful
if you ran into the problem with the lagfix enabled flashing a rom over the ext4 partition might soft brick it. I ran into a similar problem the other day and was able to get my phone going again with the instructions from the bionix thread its titled Fix 1 in the last part of the OP
http://forum.xda-developers.com/showthread.php?t=782027
this will get his phone back to stock for sure. but yeah you need ODIN
k amac10 used odin and now it will boot to the galaxy s screen then go black and stay that way but the buttons at the bottom of the screen will light up. but it still stays black. any body know a solution using linux since my windows vista part of my laptop crashed after an update and i'm fighting with windows on how to fix it. i've been trying to see if there was any software for ubuntu to do the same thing as odin. but no luck so far.
Using a windows machine w/ ODIN:
Flash "eugene's froyo that doesn't brick"
Then "JACs stock rom"
From there you should be back to out of the box status. All links & resources can be found in the "ROM bible" thread
All~G1 said:
Using a windows machine w/ ODIN:
Flash "eugene's froyo that doesn't brick"
Then "JACs stock rom"
From there you should be back to out of the box status. All links & resources can be found in the "ROM bible" thread
Click to expand...
Click to collapse
+1 for this advice. This is my standard method now for backing myself out of a dumb corner I've stuck myself in with this phone. Can do it in my sleep now!
masterotaku said:
+1 for this advice. This is my standard method now for backing myself out of a dumb corner I've stuck myself in with this phone. Can do it in my sleep now!
Click to expand...
Click to collapse
Haha... Well put! My usual flash process:
-DL new ROMs @ night over wifi
-Wake up, read the early adaptors reviews
-flash ROM, brush teeth
-flash other goodies....
From here I'm usually good to go by the time I hop out the shower if all is well. If not:
-get eugenes froyo loaded, shower
-flash JACs stock nand, fix breakfast
-push /sdcard back in, eat
-go back to previous ROM, leave for work... Lol
I think that most ppl "freak" at first cause the initial setup is *****! GL to the OP, that should work though
Okay. So I pushed Axura final onto my phones internal sd card and booted into recovery mode. The damned Axura copy ( it downloaded properly via google chrome, no errors) had some issue with it and DID NOT install properly. I tried again and again to make it work, did not load flash from voodoo eclair 2.1 to axura which is 2.2.
Now I want to use ODIN and come back.
I get into download mode BEAUTIFULLY using youtubes """Samsung Vibrant download mode; Corntez" .
and then load Odin, load pit file, and the tar/jar file. detected as COM 6 Odin says "added" . then run it. RUNS perfectly. firmware update start; cache.rfs;modem.bin;factoryfs.rfs; and all, and the blue bar finished completely.
Then restarts, "VIBRANT" says "data wiping failed " , everything else succeeds...lots of small writing....restart' VIBRANT" ; then Samsung Galaxy S shiny logo.
Now.....the plot thickens and my vibrant does not move forward. Black, black screen.
If I touch the bottom touch keys---viz, home etc...they light up fine. But the screen. the beautiful screen, remains as dark as Lord Voldemorts heart.
What to do??
I forgot to mention that I moved from a forward port on my thinkpad to an aft port )); and the COM4 in ODIN changed to COM 6 , promptly.
Odin is causing some issues. seems like. Any suggestions and links for newer, better versions of the T mobile stock firmware.????
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
houston123 said:
Need I mention that I had voodoo before I tried to put Axura on? I did.
Thanks for all the help, in anticipation,
cheers
Click to expand...
Click to collapse
Houston we have a problem. Voodoo MUST be disabled BEFORE you flash. There are plenty of info on the board on how to do this. Then ODIN to stock then FLASH. Not all ROM's need a lag fix, some just run smooth!
my phone is doing the same thing but all i did was hit the voodoo button that was available in the oclf app and it went dumb the women counted down and said complete after a while and then it stuck on the vibrant samsung screen. i flash with stock rom and now its doing what this guys phone is doing please help us
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
houston123 said:
Hey, yes, I read somewhere, that voodoo needs to be disabled. I did not do that, I had issues doing that.
Click to expand...
Click to collapse
For the dear love of [deity]/self-sufficiency, go read how to solve your problem
(You need to flash Eugene's "froyo that does not brick." Then flash whichever firmware you want.)
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
houston123 said:
Can someone post a link to Eugenes Froyo that does not brick please. Eugene himself has removed all support. Also, I found a zip file for Eugene somewher and NOT a tar or whateva file type ODIN uses to restore firmware.
Click to expand...
Click to collapse
http://eb-productions.proboards.com/index.cgi?board=samsungsgs
I have tried but doesn't work for me. Unfortunatly I too did not disable voodoo before flashing and now I am stuck and can not get into download screen. I guess I will have to take my stuff to a cell phone repair since I have ran out of options.
got eugenes software. Now I am going to try out this:
""""
ok so here is what you have to do:
1. download odin, froyo that doesn't brick, and 2.1 true stock
2. go to download mode, flash the pit and tar file from the froyo that doesn't brick (DON'T RE-PARTITION!)
3. it will boot into recovery and error out, DONT PANIC, that is what is supposed to happen
4. remove battery (from phone) and usb from phone and computer
5. put battery back in, access odin and download mode
6. flash the pit and tar file from the true 2.1 stock (RE-PARTITION THIS TIME!)
7. if done successfully, your phone software will like when you just took it out of the box!"""
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
houston123 said:
If all this does not work out, I have the 6 $ a month insurance from T Mobile---how do I use that? They might just say **** off, you screwed with the ROM and bricked the phone! Should I told them that someone flicked at Swing dance class.....instead of " I bricked it" sorry!!!!
Your opinions on this???
Click to expand...
Click to collapse
My opinion on this is not to worry unless it doesn't work. But since you know how to use Odin and your phone can get into download mode okay, it should work.
With the insurance there is a hefty copay. But you should be fine.
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
dude that's not even close to a brick as the phone is still responsive somehow..
do this:
1. pull out battery wait 5-10secs
2. connect USB to computer and phone
3. hold down the vol +/- buttons
4. plug in battery
5. you should be in download mode now
6. do what you gotta do with ODIN
good luck
Dont use that method to get to DL mode . Do it this way . First turn off your phone , then plug the usb cable into your computer ONLY . Next hold both volume buttons and plug the micro usb into your phone . Also use odin v1.3 and flash the rom of your preference .
Edit : xtone beat me to the punch
trill12 said:
I partitioned my SD card using ROM Manager, turned the phone off and got a black screen with lit keys. So, I read around and was told to use ODIN to reflash the stock TMO build, so I did. Now, Im getting the TMO logo and Galaxy S screen, but I get a black screen still.
I cannot get into download mode. I vol - and power and I get the Vibrant logo, then it goes back off. Even when plugged it, I get the batt charging animation, then back to the Vibrant screen.
I tried to push the update.zip to the SD card through ADB, but I get a permission denied message, meaning the root was killed.
So, is this phone pretty much screwed? I cant think of any other way to get it going outside of moving the update.zip to the sd card by a 3rd party measure i.e card reader/another phone
Click to expand...
Click to collapse
Yes using ROM Manager to repartition your phone will create the "soft-brick" you are experiencing. But as one person has already noted, this can pretty much be recovered using ODIN.
Definitely follow the advice given in Posts 2 and 3 of this thread to get into Download mode. If you're not getting the desired results using ODIN, what settings are you using? For example, what are the names of the .pit and .tar files you are using? Did you check or leave unchecked the "re-partition" option?
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
trill12 said:
Sorry for the noobery. Im usually good at this.
Well, I was able to get into download mode and get ODIN to run, but im getting a MBD checksum error when I boot into recovery.
And I cannot install CWM through the market because my Application Storage is at 0.00B for some reason.
Click to expand...
Click to collapse
What ROM did you flash. You might want to perform a factory reset and then flash the stock JFD ROM and see if that fixes your problem.
Good luck.
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
blizzard1017 said:
Oh this is a nightmare.... exactly what happened to me.
I'll be honest, I tried and tried and tried all sorts of stuff and somehow I got it back reading again.
I would ODIN to Eugenes Froyo that doesn't brick and see where that gets you. Thread is in developers section and I am pretty sure that's what got me back working but follow ALL the instructions. With no application room I couldn't push, unistall, install ect...
Click to expand...
Click to collapse
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Just get to DL mode as xtone and I stated in post 2 & 3 . Then flashed to JFD with odin v1.3 and click the repartition box in odin and you'll be fine .
Sent from my SGH-T959 using XDA App
I had this problem for the last two days, but I found a way to fix it thanks to a user (whom I don't know the name of)
I did this to go back to stock firmware (JFD), make sure you have that downloaded.
Look for Eugene's Galaxy S Froyo PDA, for the i9000, not the Vibrant. Flash it through Odin with the 512 pit file. It's not going to boot up but take you to recovery mode instead, and it's going to remap your Volume buttons, but you can still get into DL mode (up is now down, and vice versa but whatever)
Now Odin back to stock, using the same 512 pit and there you go! Should boot up with no problem. Now you can redo everything, but remember to never partition through ROM Manager ever again!
Sent from my SGH-T959 using XDA App
Is there a link you could provide him?
AgentFour20 said:
That's only needed if he flashed a rom with the wrong kernel or if he flashed a rom without disabling voodoo .
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
His exact symptoms happened to me when the noob in me decided to repartition in Rom Manager awhile back. I am just suggesting he uses this tool as an option. It's definitely a good tool to use regardless of how he got where he got.
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Mr.Duck said:
something like this happened to a buddy of mine, i'm trying to fix it, but the guy was completely stock so it makes no sense... I've tried everything, and i cant seem to find eugenes files...
Click to expand...
Click to collapse
Eugenes rom are on his new site www.eb-production.proboards.com
Sent from my SGH-T959 using XDA App
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
trill12 said:
OK, I got it fixed. Heres how.
I was finally able to get into ODIN and flash Eugenes Froyo.
So, from there, I was getting an MD5 checksum error when Id try to get into recovery, and I couldnt install the ROM Manager from the Market
Well, upon inspection of a the Nero V3 build I had downloaded, there was a ROMManager.apk there. So I pushed it onto my phone, reflashed to CWR (had to do it about 3 times) and reinstalled Nero V3.
After installing the build, I was able to re-enable voodoo and its theres no more MD5 craziness when I access the Recovery
Click to expand...
Click to collapse
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
AgentFour20 said:
So voodoo was the culprit . lmao
I dont remember you ever mentioning that . Any way glad you figured it out and have your phone back .
Click to expand...
Click to collapse
Apparently. Completely forgot I attempted to enable it. I was freaked all the way out trying to repair the damn thing.
Okay, so after installing the kang build 25 ICS for the vibrant, everything went fine. Randomly I get a random reboot and my phone says there was an "encryption error" and that I have to do a factory reset. Since I already had everything backed up, I didn't mind the data wipe. When it went rebooted the CWM screen came up and started wiping everything but when it got to the "formatting data" part, it failed. I tried this many times and it kept failing... SO, I decided to ODIN back to JFD. After doing so, all I get is the Vibrant screen, then an instant shut down. I even tried Eugene's old No Brick Froyo PDA, then tried to reinstall the JFD image, but got no luck.
Question is: What should I do now?
Any help will be GREATLY appreciated. Thanks!
Its a little involved but It's all I could find to help buddy
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Perhaps it could be a bootloader problem? If you're sure you are doing Odin right, including repartition with the pit file, you could look at your SBL.
.
Sorry but what is SBL?
lolrus101 said:
Sorry but what is SBL?
Click to expand...
Click to collapse
I dont know how to explain it very well lol but to check if the rom you are trying to odin has the sbl in it. Rename it and put a .zip at the end. Then extract to see if its in there it should be named "sbl". To change it back simply delete the .zip off the original file.
JFD
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Try odining a rom that has the sbl file in it thats probably why its not working.
---------- Post added at 04:14 AM ---------- Previous post was at 04:09 AM ----------
Here http://forum.xda-developers.com/showthread.php?t=1278683 you need to have java installed to open it
Just tried the Heimdall thing. No luck. As soon as it says rebooting, it goes to the vibrant screen, then the battery charging screen, then continues to bootloop. Same thing happened with Odin
why don't you try what I did
http://forum.xda-developers.com/showpost.php?p=23056603&postcount=10
lolrus101 said:
I'm trying to ODIN the original JFD firmware, and I just checked that it does not have SBL in it.
Click to expand...
Click to collapse
The SBL is the Secondary Boot Loader, which is loaded by the Primary Boot Loader.
I haven't personally encountered any roms which also flash bootloaders.
I did manage to get my phone bootlooped in some weird way which apparently could only be fixed by reflashing the SBL. Note: flashing bootloaders is more dangerous than regular roms.
I am presently running a GB SBL from this thread:
http://forum.xda-developers.com/showthread.php?t=1117990
ian577416 said:
http://www.youtube.com/watch?v=Rdn5GoRjhn0
It's not the easiest thing in the world to accomplish but It is a guarantied way to get your vibrant into successful download mode to reflash to stock.
At the least something to get you started
Good Luck!
Click to expand...
Click to collapse
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Flashed the GB bootloader and no luck either . Flashed back to the froyo one, and got the data wipe error again, the phone rebooted, and now its at "KERNEL PANIC - UPLOAD MODE"
AdamOutler said:
a 301kohm jig is ONLY good if you have a valid Initial Bootloader, Primitive Bootloader, Partition Table AND Secondary Bootloader. If you damage any of those, a 301kohm jig won't work.
Use UnBrickable Mod. http://forum.xda-developers.com/showthread.php?t=1277056
Click to expand...
Click to collapse
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
lolrus101 said:
I have already tried the Heimdall method... and I can access download mode. I think the thing that is causing the bootloop is that the Data wipe fails after a restore. Thats when the bootloop kicks in
Click to expand...
Click to collapse
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
cashmundy said:
If you did Odin/Heimdall to stock after flashing the SBL, and it is still messed up, its beyond me and I'd really like to know the fix. Wiping should be irrelevant after Odining to stock.
If you are getting errors in recovery when you try to wipe/format/restore, that indicates a mismatch between the kernel and the partitioning or filesystem.
Click to expand...
Click to collapse
SO the thing is I used the GLITCH kernel with vibrant build 25... I dont think I was supposed to... could that have caused the problem? maybe a voodoo problem?
There are two glitch kernel series that I know of, one for CM7 and one for CM9 and ICS (I think, not sure, that all ICS builds and CM9 use the same basic filesystem scheme).
All stock builds use a Samsung FS scheme which is different from the two above. So there are at least three mutually-incompatible families of FS+kernel pairs.
I used the CM9 kernel I think...
After the installation went fine, I got the encryption error which told me to reboot. as soon as I did, I got the Data wipe fail. Any ideas?
Encryption Error
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
tabthelab said:
I'm going through the same thing. I had my phone at ICS passion for months, last night I noticed my phone was in a boot load screen, but it was dimmed. I simply went and took out my battery. . maybe not the best idea, cause I'm now unable to flash back to stock.
I used odin to go back to stock, but I keep getting a boot load/reset. Nothing is happening.
If anyone has found out more on this, please let me know. Thank you so much.
Click to expand...
Click to collapse
If you are still able to access Clockworkmod Recovery CWM (NOT STOCK RECOVERY) then try this:
http://forum.xda-developers.com/showthread.php?t=1447303
Otherwise just give up. There is currently no fix for this bug as of now.
This is really getting out of hand ICS rom devs should put a big caution sign on their thread(s) stating the following:
WARNING THIS ROM WILL BRICK YOUR DEVICE!!!
Goodluck... in the meantime find yourself a spare phone like i did cuz you certainly ain't fixing this one.
Sent from my Galaxy Nexus using XDA
mother of god
I hope this helps you. I finally, after hours of nothing, tried to use Odin to flash to 2.2 froyo. cha ching. got in.
tar file I used here: http://forum.xda-developers.com/showthread.php?t=833024&page=49
worked for me. I hope it helps you