yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] joe.kerwin:
Here is how to properly flash into another ROM without using odin. OP feel free to share this as I'm sure many, if not all users might encounter this issue. First off, let me say that I haven't used ROM manager for awhile really simply because I don't see it as necessary, but since we can't actually see recovery on this ROM, it's quite necessary. Now the problem I recalled after I ran into some trouble is usually after a fresh flash, the first boot into recovery usually gets stuck on 2e recovery and you have to hit reinstall packages which will result in another reboot into cwm. My trouble was when I went to flash a ROM on top of this, I waited 20 minutes and nothing ever happened, finally just hit the power button and it rebooted instantly. This told me that it must have just been sitting in some form of recovery and when I hit power, it selected the top option "reboot system". My phone booted up just as it had been with all my apps and data in tact, still on 2.3.2. This was AFTER I had selected wipe cache/data in ROM manager in addition to selecting a ROM to flash. So I tried again, and it worked, quite quickly actually. My point is, you'll probably have to do the flash rom command from ROM manager twice, but don't assume so. Do your first time flash with the update.zip most of us already have on our internals, wait at least 10 minutes just in case it did work the first time for you, if it remains at the rainbow screen tap the power button once, if it reboots instantly, that means you didn't fully boot into cwm and your phone should boot up fine still on 2.3.2. Then enter ROM manager once again and do the same steps: flash ROM > select ROM > check wipe cache/data > select reboot and it should go just fine then. Just to save some time if some of you think you have to odin, you might not.
[Vibrant Android Development] ronnieb00:
Yeah, no worries. Bionix V 1.2.1, standard, no esoteric kernels.

I'm not super savvy, so I'm only an occasional flasher and haven't used any non-ROM associated kernels. I've ODINed back to JFD and downloaded the ROM again, will flash from there and let you know if it hiccups again.

Thanks.
[Vibrant Android Development] Demiurgic:
Couple things

- No need to worry about the E: partition cache error when you first flash happens to me too. When you go back into recovery with androidscreencast you can see that it will wipe recovery with no errors.

- DO NOT FLASH CWM for NEXUS S this will break stuff. Nexus S uses cwm 3.0, supercurio's kernel is cwm 2.5. A lot changed; such as cwm 3 uses the edify/updater script so most of your cwm zips wouldn't flash anyways

- If you have had your filll of gingerbread goodness and want some froyo there are a couple ways to get back:

*flash thru rom manager( only if you really have to since you can't see whats going on but should work..maybe) or recovery with android screen cast

*ODIN back to stock. Note: the usb drivers seem hit or miss with this. If odin doesn't recognize your phone; go into control panel/devices and uninstall the samsung usb drivers. Pop usb cable out/in so pc will re-install drivers for you.

*Or flash a froyo kernel with working recovery thru odin or rom manager(should work but I haven't tested this yet). Pull batt/reboot then go back into recovery and flash rom

- Those having trouble flashing just make sure you got a good download. The only time I had issues flashing was because of a partial download and I didn't realize it. Maybe Whitehawkx can put the MD5 up. If you hear the chipmonk you should be good but if it hangs wait a few mins then reboot.
[Vibrant Android Development] ronnieb00:
Coming from JFD stock worked fine as far as I can tell. Phone has just powered on and waiting the 15 mins, but looks good. Not sure what the problem was bionix -> ginger beta.
[Vibrant Android Development] Whitehawkx:
Great post Demiurgic. I'm going to add it to the OP. Thank you.
[Vibrant Android Development] ronnieb00:
Boot Loop

One more thing to possibly help troubleshooting...

Most of my sdcard was wiped, but I still had a voodoo log on it. I thought it was strange that there were A LOT of "voodoo conversion" attempts in the log (ie. numerous boots w/ chipmunk linda), considering I was already using voodoo under bionix-v.

Thanks again for your work.
[Vibrant Android Development] Br1cK'd:
I believe those logs generate every time you reboot. I run voodoo disabled, and still have tons of logs that generate even though I clear them out regularly.

Sent from my Loki powered Vibrant via the XDA App
[Vibrant Android Development] yb2fast:
Mine did the same thing and works fine.if you read.if you read,

white said that would happen.you are downloading voodoo as well.thats the chipmunk, just let it do its thing for a while
[Vibrant Android Development] jangst123:
Great job Whitehawkx! U D Man

And thank you deeznutz, you tip made me feel much better about taking this awesome ROM for a spin!

--

Daily Driver:

ROM http://xdaforums.com/showthread.php?t=967861

[KERNEL]OverStock v1.4 341MB, Voodoo Sound, Color, Lagfix, BLN 3/7/2011

[Audio Theme] Project Linda 2.0 - 2/28/11

[Theme Mashup] Blackout with a splash of color - Bionix V 1.3.1 - 3/5/11
[Vibrant Android Development] Demiurgic:
For the people coming straight from another 2.2/2.2.1 rom and having boot loops/issues did you disable voodoo before you flashed? I wonder if the voodoo config might differ from a vibrant kernel to the I9000 kernel. Guess I will have to install some roms to test out.
[Vibrant Android Development] deez1234:
I love this. I think I will be putting down my nexus s for a couple of days. Gingerbread on the Vibrant makes the phone feel like it should. Thanks for the hard work! This has changed the way I look at this device.
[Vibrant Android Development] :
My video player starts showing rainbows after a few minutes of use but i havent changed anything reinstalled twice and it still does it even after i reboot the issue remains and it seems to.affect the camera and just about anything that uses video... Even my gameloft games like dungeo hunter show the rainbow
[Vibrant Android Development] Whitehawkx:
Rainbow on camera/video seems to be hit or miss. I have not had it happen, but there have been reports like yours. Demiurgic posted how to fix this by editing the build.prop a few pages back. I'll make a note in the OP that 3D games don't work. Gingerbread in general has issues with 3D.
[Vibrant Android Development] shovelhead83:
This rom is awesome with great potential. However after a days use it began to run too slow to use. Reboots temporarily fixed the problem. I am looking forward to the progress of this rom. Thanks for all your work.
[Vibrant Android Development] :
Thanks my guy
[Vibrant Android Development] Whitehawkx:
The best way I've found to fix the RAM issue (sluggishnish after persistent use) is to use the included Gingerbread launcher and set Activity/Process Management in Spare Parts to aggressive. There are reports that on LauncherPro (probably ADW as well) that doing this will kill the launcher when you open another app. On the GB launcher it seems t work pretty well and keeps the RAM around 240-260ish (give or take).

Glad you are enjoying it. Rest assured progress has not stopped here. :)
[Vibrant Android Development] LoveistheGroove:
I have been using the [ROM][BETA-2] 2.3.2 - XWJV1 [Gingerbread on Vibrant!][EDT][3.6.2011][BETA-2] since it was uploaded. Actually I've played with each XWJV1 ROM you've released, but never was ready for it to be a daily until Voodoo was included. I *love* the stock Twiz graphics/theme from Samsung. The newer colors are perfect...but I digress...anyway I just wanted to let you know that my phone went into *kernel panic mode* (while running this rom) and so far I don't think I lost anything. But I needed to let you guys know because it happened when I plugged my phone into the wall outlet that I always use (USB). I have had this kernel panic mode happen before on my phone, (when using USB tethering) and that time I lost all of my files on my external sd card. It also randomly reboots and camera is very laggy. I learned the hard way that you don't use old 2.2 apk's. How do I get a low battery camera hack on this rom (SGS Tools causes constant #9900# error messages)? Also, how can I get my favorite version of Swype (2.15XXXXX) with the large keys & nicer colors to work on this ROM? It will install fine AND WORKS! - after deleting the (libswycore.so?)...but after rebooting, it force-closes Swype over & over...so I have to revert to the ugly Swype with small keys. Sorry for the ramble but I appreciate your work and help/advice a lot.
[Vibrant Android Development] DonutYankee:
I'm using the TouchWiz launcher and have it on Aggressive and it's helped a bit. I'm guessing no Vibrant 2.3.2 source is what's making it hard to stop memory leak? Samsung needs to hurry up with this.
[Vibrant Android Development] cashyftw:
No one else has had pretty bad battery? just trying to figure out what I did, or what app I installed, I have an idea, but idk if it's just me.
[Vibrant Android Development] shovelhead83:
Ahhhhhh Mannnnnnnn! I was using stock gb launcher but had activity/process set to normal like the op says. I already odined and flashed another rom but I definately got my selfish greedy eye on this for the next update. Thanks for responding. And thanks again for ALL YOU DO!
[Vibrant Android Development] C-4Nati:
I know this is beta but I hope this gets faster cuz TW's 2.2 roms are faster.
[Vibrant Android Development] Demiurgic:
Ha it sure is easy to forget where you came from. This is the first gingerbread build for the I9000...not the vibrant. It might be hard to remember but the first froyo builds were way worse off than this. This has more memory and is leaps and bounds faster than the early froyo builds. It's only going to get better :D

"Patience: A minor form of despair disguised as a virtue. ~Ambrose Bierce"
[Vibrant Android Development] C-4Nati:
Im very patient but gingerbread talks came about months ago so at this point patience isn't something high anymore lol.
[Vibrant Android Development] lightninbug:
:::Edit:: Deleted Post

Wrong forum meant to be in G-Tablet forum..While I'm at it.... Dont have one?!!GET ONE!! BEST ANDROID TABLET OUT THERE AS FAR AS PC POWER IS CONCERNED..AND THE BOARD NEEDS SOME MORE DEVS.
[Vibrant Android Development] projectxmatt:
Tried changing the heapsize from 64m to 48m still having the rainbow issue with the camera and gallery. Oh well I can live without for now. Great rom. Been all day off the charger and battery is running better than mine did on bionix. Keep up the great work.
[Vibrant Android Development] projectxmatt:
Could have edited post above but felt this was worthy of a double post. I was able to fix my rainbow issues. Here is what I did and the results of each step.

1. Changed spare parts to aggressive (no change)

2. Changed heap size from 64m to 48m (no change)

3. Cleared launcher defaults, pressed home selected twlauncher, pressed home again selected launcher (set as default) loaded up camera, and gallery and both are 100% OK now.

I'm assuming it may have something to do with the launcher. As once I cleared the default and loaded the tw then switched back to the gb launcher everything started working. So for those having rainbow issues in the camera and other apps. Trying clearing out your default launcher.
[Vibrant Android Development] stevencpoynter:
Having some issues with odin trying to get back to the stock jfd firmware. I could be considered as one of the people having issues flashing this rom over the bioniix 1.3.1 rom.

Anyway, flashed this GB rom and got the crazy rainbow bootloop (waited 20 minutes as it looped over and over). I can get access to download mode but whenever I plug in the USB cable with odin open there's no communication going on betweeen the phone and computer...like..nothing. I get a nono sound and no com3 or anything from odin. Tried uninstalling the samsung drivers and plugging the phone back in to reinstall them with no avail. I even reinstalled the samsung drivers I downloaded originally with the phone and get nothing. Switching USB cables didnt work either, any advice?
[Vibrant Android Development] Whitehawkx:
With the phone on, plug it up to your computer and open adb.

Type "adb reboot download"

See if that works.
[Vibrant Android Development] stevencpoynter:
The thing is, the phone loops until I plug it up to USB, then it goes to the battery charging screen.

The only screen it wont loop at is the download screen.

Anyways, it's not even coming up as a listed device under adb.
[Vibrant Android Development] Whitehawkx:
Make sure you have the correct drivers for your OS installed or it won't work. This rom doesn't install anything that affects the ability to enter or use download mode.
[Vibrant Android Development] stevencpoynter:
Working on it. Thanks.

I'm downloading the new drivers manually because all have installed save for the SAMSUNG_Android which fails to install due to the phone boot looping and cutting off whenever I plug in the USB.
[Vibrant Android Development] andROIDS:
I didn't see this posted, and was wondering if anybody else has experienced this. I flashed per the instructions and when it reboots after flash, I hear Linda's voice and see the rainbow screen then a couple seconds later the phone just turns off. I rebooted the phone, and see the rainbow screen and hear Linda and the phone turns off again. That's all it will do. What did I do wrong? Bad flash? Bad download? Any help is appreciated. Thanks.
[Vibrant Android Development] stevencpoynter:
You're probably going to have to Odin just like I did.

I fixed my problem btw, couldnt get the drivers to install for the life of me on two separate laptops, drug my old pc out of the closet and the **** installed right away like butter. Booted the old version of Odin up, com3 lit up, flashed and now ive got a working vibrant again.

Curiosity almost killed the vibrant, I think i'll hang back for a while, this ****'s giving me grey hair lol. Thanks for the help!
[Vibrant Android Development] theyownus:
if you are still having issues with odin give heimdal a try. i couldnt get odin to work at all but after realizing that heimdal needs the files loaded seperately (not the large .tar or .md5 file but the ones inside) it worked like a charm, even when odin wouldnt recognize my vibrant.
[Vibrant Android Development] turbosix:
such a goofy problem. a buddy of mine had to bring his vibrant to my work so i could odin it back to stock, he's got half a dozen pc's and laptops at home and couldnt get any to work. odin works fine on my work PC and on an older dell laptop i've got.

maybe its because they're both running XP.

glad you got everything to work!
[Vibrant Android Development] stevencpoynter:
Thanks dude!

Is that a GNX you got there?

Sex.

Love watching them skat down the strip
[Vibrant Android Development] iwapu:
I have the same issues when I flashed I9000 XWJS7 on my Vibrant, BUT they are automatically fixed after I flashed Categorically Worthless kernel. This may be worth a try. Maybe it works on this ROM also.

At least devs can try to look for fixes in kernel?
[Vibrant Android Development] scrizz:
i thought JS7 was 2.2.1?
[Vibrant Android Development] yb2fast:
White,again thanks for the hard work been using this for 3 days no problems.live it.question though, does this support ffc, cause I want to install one so was wondering.

One other thing how hard would it be to add 4g to this.other than that this would be a perfect rom for me.thanks again
[Vibrant Android Development] Whitehawkx:
Glad you are enjoying it. :)

I don't have a FFC to test, but this includes the i9000 camera which has the option to switch to FFC. I assume it works, but there have been no reports to confirm or deny this.

As for 4G, we unfortunately will never have that on our Vibrants. :(
[Vibrant Android Development] yb2fast:
Ok thanks white,guess I'll order one and find out, let you know.thanks again
[Vibrant Android Development] cashyftw:
The FFC DOES work with this, of course you will have the normal issues with the ffc, read the FFC mod thread to find out.
[Vibrant Android Development] DonutYankee:
I don't have a FFC installed, but the camera app doesn't crash when you tap to switch to front facing camera. Just a blank black "preview" and you can switch back to rear cam. Latest version has been running great for me. Twitter app is a little glitchy, but I'm guessing that's their app's issue. Spare Parts crashes though if I attempt to go into battery info in that app. Battery life itself has been good for me. Easily lasts a day now, though my battery metering is confused once it gets past 94% so I let it charge for a while after it tells me that it's fully charged. RAM issue is a lot better now with Spare Parts aggressive setting and going into Task Manager and clearing memory out. With Beta 1 that didn't help at all.
[Vibrant Android Development] turbosix:
anyone hit the 5gb cap with this rom?

either it takes awhile for them to cut me off of HSDPA or they're unable to activate whatever throttle is in place (or perhaps its just not there in this rom?)

will update later, i just got the text message and saw i was at 5.2gb. oops.
[Vibrant Android Development] Br1cK'd:
Don't be coy Scrizz, you know that you know.

All, unless White states its compatible, I wouldn't flash the previously advertised 2.2/2.2.1 kernel (cwk) with this build, stick with what your dev is providing you as he toils away at this port.

Sent from my Loki powered Vibrant via the XDA App
[Vibrant Android Development] turbosix:
its an 84 t-type, close enough (except in resale, ouch!)
[Vibrant Android Development] STiGLOGiC:
I don't know why some of you have been complaining about speed. This ROM is SUPER fast. Much faster than ANY TW ROM I have run. No offense to TW at all. Their ROMs are top notch, but this is just blazing. I'm not a big believer in quadrant scores, but TW ROMs have always landed me in the mid 1500's. This ROM always lands me in the mid 1700's.
[Vibrant Android Development] hitman818:
Is that with voodoo?
[Vibrant Android Development] STiGLOGiC:
yes it is. I can't see recovery so I couldn't disable without some serious memory pressing.
[Vibrant Android Development] DonutYankee:
I have to say, the browser on 2.3.2 is worlds faster at rendering pages than 2.2 or 2.2.1.
[Vibrant Android Development] scrizz:
you need to enable JIT ;)
[Vibrant Android Development] pegasus912:
I was told jit was already enabled. If it is not can you give some instructions? Thanks
[Vibrant Android Development] yvliew:
this rom has serious memory issues. It lags when the memory goes as low as 30mb left...
[Vibrant Android Development] DonutYankee:
Task Manager, clear memory. Repeat. Do that once in a while and this is the fastest ROM out there.
[Vibrant Android Development] DonutYankee:
Noticing that when I go to battery info in settings and see what uses the most battery it shows Google Maps, which I haven't used in over a day. I restarded my phone last night with a full charge to see this morning what used the battery. Battery life has otherwise been decent for me. Almost made it 24 hours last night.
[Vibrant Android Development] avio07:
any work being done on this to fix the bugs? are there any 100% stock gingerbread roms out?
[Vibrant Android Development] Whitehawkx:
Work is being done on this still. This rom is 100% stock with only changes made to help it function better (with the exception of voodoo kernel).

I am also working on mods for this as well. Currently lockscreen mod is 4/6 complete. Having issues with epic and fascinate but is most likely a gingerbread specific issue.
[Vibrant Android Development] xsteven77x:
What would the main difference in everyday use and bugs is there between this and cyanogen?
[Vibrant Android Development] theyownus:
one big one that has me on this rom over cm7 is the battery life...
[Vibrant Android Development] cfye1971:
Installed right over 2.2.1 with voodoo on and she fired right up in about 1 min..been running for a few days without reboot and have no lag.great rom..battery life is good .unpluged at 6:00 this mourning and still got 75% left...
[Vibrant Android Development] sl0play:
It looks and runs like a dream. VERY fast most of the time, but I did get a few solid seconds worth of lag at times. Wi-Fi drops randomly sometimes it doesnt wake from sleep mode, all things that have been said.

Definitely fun to run for a few days, and a great taste of whats to come!

Thanks to all the devs for so much awesomeness!
[Vibrant Android Development] DonutYankee:
Battery life is getting better for me as I go along. I cleared my battery stats while on JFD before flashing this and battery was a bit off at first but is now pretty damn good. Only bug remaining is memory leak and Google Maps for some reason sucking up juice in the background without being on.
[Vibrant Android Development] scrizz:
don't forget this is Samsung stock, while CM7 is AOSP based. ;)
[Vibrant Android Development] one4house:
I am also interested in enabling JIT if it is not enabled by default?
[Vibrant Android Development] Whitehawkx:
JIT is enabled. However quadrant scores do not calculate everything. You can change some stuff in the build.prop so they get calculated but it breaks video playback and camera. All you'll get in exchange is a higher quad score, the performance is already there.
[Vibrant Android Development] Emama:
Wow, cant believe the only thing that is not working is only GPS!!

cant wait until it works!! I need GPS all the time so hold on to bionix first!!

Great JOB!!
[Vibrant Android Development] lightninbug:
Update coming tonight?:confused::D:D:D:D:D:D:D
[Vibrant Android Development] Whitehawkx:
I MIGHT get an update out this weekend. MIGHT. I want to work on a few more things yet. So far i have 4/6 lockscreens (all but Epic and Fascinate) and power menu. I'm gonna work on fixing the reboot issue when waking the phone while listening to music. I also want to play with the audio routing some more. Would be great if we could eliminate the need for the ToggleHeadset Widget. Don't worry though, future updates WILL come. :)
[Vibrant Android Development] chriswallen79:
Has anyone gotten there ffc to work on this
[Vibrant Android Development] Whitehawkx:
FFC has been confirmed working.
[Vibrant Android Development] wizern23:
Why is recovery broke? Do we need cwm 3.0 recovery to get rid if the double rainbow?
[Vibrant Android Development] :
^ he might b on to sonething
[Vibrant Android Development] Whitehawkx:
The double rainbow is caused because Gingerbread doesn't play nice with the froyo bootloaders. Flashing the bootloader for this build would fix the double rainbow, but you would most certainly hard brick when you tried to come back from it. Don't do it. The version of clockwork won't change the rainbow.

Also, recovery still works you just can't see it. If you download android screencast you can see recovery on your PC screen and operate it like normal. That's what I use. :)
[Vibrant Android Development] :
U should put that in the op white btw your the man
[Vibrant Android Development] wizern23:
Oh okay. Thanks for the explanation. I just really wanted to know why it was like that. Its nice to know that its to keep noobs from bricking their phones.
[Vibrant Android Development] misquia:
It doesn't seem I'm able to delete the bloatware even with chuck norris mode, is this normal?
[Vibrant Android Development] The Tech Game:
hey not to be "that guy" (this build is awesome, great job) but games lag ALOT on this build, im not complaining im just saying its NOT just 3D games that are all messed up with this build, any game like angry birds or glow hockey, maybe you should add that to the known bugs??
[Vibrant Android Development] one4house:
I am getting the crazy rainbow when watching any kind of video. What setting do I change to get rid of this?
[Vibrant Android Development] Whitehawkx:
You can try editing the build.prop. There are instructions for that in the OP.

You can also download the FuguTweaks from this thread here - http://xdaforums.com/showthread.php?t=981125. Unzip the files and move the two files in /system/bin to the same folder on your phone and reboot.