yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] avgjoegeek:
Yup and no new leaks as AT&T is still waiting for Samsung to release something worthwhile to them so they can push it to us.

So... until then everything will probably be i9000 based.

Um - but why can't it be Nexus S based? Just curious :D
[Captivate Android Development] derek4484:
Can't be nexus S based. The hardware is too different. Only the screen and cpu are the same. Everything else is different. You would need a 2.3 kernel & drivers written for SGS, not nexus s.

Thats how we eventually ended up with 2.2 roms for cappy and i9000. 2.2 firmwares were leaked out from samsung that had the necessary kernel and drivers for the hardware.
[Captivate Android Development] dacket84:
If you're seeing exactly what you quoted, then you already have the dump extracted on your SD. Unless you did a master reset/clear then the dump is already there and all you need to do is flash the GB kernel. Hence the "mkdir: can't create directory 'data': File exists"
[Captivate Android Development] erych:
But is it a problem that i cant tar the file? and thanks for not ignoring my post like those other ppl did :]
[Captivate Android Development] erych:
yeah didnt work my friend, started up normally, first thing i saw after flashing was the at&t screen lol

edit: i tried flashing the kernel xcal made ANd surerc, neither did anything for me.
[Captivate Android Development] opcow:
On most ROMs I use these days /sdcard is a symlink to /mnt/sdcard and that causes file exists errors when pushing files via adb. Push to /mnt/sdcard instead.

Scratch that. I don't know what I was replying to and I don't think it's relevant.
[Captivate Android Development] dacket84:
I ran into that problem before too. All I did was one click flash back to stock, then ran master clear. Loaded a froyo rom that did the lag fix on first start up. Then started all over. Worked fine after that. Also the CWM flashable one works great and is much easier to load. Just make sure you're running a froyo rom on all ext4 before you flash the GB rom.

http://xdaforums.com/showthread.php?t=887037
[Captivate Android Development] erych:
oh I didnt know it had to be a Froyo rom... thanks a million!

edit:how should i do a master clear exactly is it an adb command?
[Captivate Android Development] dacket84:
The easiest way to do that is to use Odin3 one click --> http://xdaforums.com/showthread.php?t=731989

I get the best results if you open the program THEN put your phone into download mode, do master reset. When back to stock, turn on USB debugging, open Odin first then plug in USB then do master clear. After that, you should be as close to stock as one can get after hacking. Then you should be set and ready to throw on your froyo rom. The new Perception works well. It will automatically set voodoo on first boot.
[Captivate Android Development] erych:
Oh right I remember about odins master clear now, duh haha. is it supposed to take a while before anything hapens?lol 0_o

edit: oh hey i keep getting the $ sign instead of the # sign now know why that is?
[Captivate Android Development] fatttire:
Master Clear: *2767*3855#

***WARNING**** there is no confirmation prompt :)

Haha someone on another forum passed that code off as a "lag fix" or something... caused a little distress initially.. definately dangerous
[Captivate Android Development] erych:
Ah thanks yea i remember reading that the code is dangerous, um whenever i try to flash the system-dump-as-root.tar.gz to get gingerbread at all, it always, after rebooting gets stuck at the att loading screen, now i know that since there IS the att screen it already hasnt worked, im doing everything perfectly as i am supposed to to the best of my knowledge, this is what i do:

at first i revert to stock with odin so its back at factory eclair

then root my capt. with one-click update.zip

then apply voodoo lagfix(its sweet with the mechanical voice someone should make that a speech engine FTW)

then run superc's commands in cmd with adb and all...

then I flash xcal's captivate version of nsongs or w/e but it just gets 'stuck' at the att load screen... :[

so then i run nsongs and it doesnt work either

HALP PLAAAEEEAZZZ
[Captivate Android Development] flashman2002:
Just find a Froyo rom that has Voodoo. Once you have that installed, do the adb commands. It won't work if you are doing it in stages like this.
[Captivate Android Development] flashman2002:
Nevermind.
[Captivate Android Development] erych:
i heard perception is a good one, but how do i use it? would i need to revert to stock again, cause right now my captivate is rooted and has voodoo3
[Captivate Android Development] erych:
then it should work? or what, why never mind?
[Captivate Android Development] flashman2002:
I didn't think I read your post correctly about what you have done. The easiest way to run 2.3 is to use a Rom that already has Froyo and Voodoo 5. If you use Perception 10 that will work. Try this:

1) Download Perception 10 either to your phone, or to your computer and transfer to your phone via USB. Also make sure you have the GB .tar on your internal sd card root for easy ADB command access.

2) Make sure you have the clockworkmod update.zip on the root of your internal sd card (make a backup of the update.zip and place it on your computer).

3) Use Odin to flash back to JF6.

4) Use 3 button combo to get into recovery.

5) Select reinstall packages (it should reboot a second time and select reinstall packages again).

6) If you select reinstall packages and it comes back with an error, reboot system, once rebooted select usb debugging and transfer over the update.zip you copied to your computer over to your internal sd card. Do step 5 again.

7) Select install zip from sdcard and find where you have the Perception 10 rom.

8) Select install rom, and let it work its magic. After it is complete reboot system. At that time you will begin to hear Voodoo.

9) Give system time to reboot (about 5-10 min).

Once it is up do the ADB commands then flash the kernel from xcalibur using the full Odin.

Hope that works for you.
[Captivate Android Development] opcow:
That's where you went wrong.
[Captivate Android Development] flashman2002:
Thats actually what you should do when you install these 2.2 Roms. :confused: So why would that be wrong. Using Voodoo 3 would be wrong.
[Captivate Android Development] erych:
haha i used voodoo3 hahaha
[Captivate Android Development] erych:
thanks yeah ive got perception, and did it this way before i actually saw it, lol looked at the how to flash roms for noobs here in the captivate adnroid dev forum. but i really like the perception, is gingerbread with all its faults really worth it?

edit:alright this is pissing me off now, i wanted to get gingerbread, but i cant busybox the system-dump-as-root.tar.gz again! [im so frustrated, this should be working!] edit2: it says **no such file or directory** which is a LIEE
[Captivate Android Development] erych:
dude can i use cwm to busybox the tar.gz sysdump file?
[Captivate Android Development] dacket84:
Nope.

What I do every time I flash GB is this: One click back to stock/master clear, dump my Update.zip, froyo-voodoo_enabled-rom-of-choice.zip and gingerbread-rom.zip sdcard of my phone.

1) Then unplug USB

2) pull battery

3) put battery back in

4) hold vol + and vol - then press the power button till ATT logo shows up

5) let go of pwr button while still holding vol + and vol - till the recovery screen comes on.

6) select "reinstall packages"

7) phone restarts back into recovery by itsself...

8) then select "reinstall packages" again, this time it should go into the clockwork mod recovery.

9) select install .zip from sdcard

10) select choose zip from sdcard then select the froyo rom

11) after that is done select +++++Go Back+++++

12) then select "reboot system now"

after Froyo is all done booting up. hold the pwr button till the menu appears, then select "recovery". Phone will reboot into recovery.

repeat steps 9 and 10, except on step 10 choose the GB rom instead of the Froyo.

It's much easier this way, I think rather than messing with the adb commands.
[Captivate Android Development] erych:
ahh well now i need a gb rom... thats muuch better than adb hahah dude you're the beeeest!!

edit:forgot to say, masterclear neevveer works for me though... :[ through odin at least lol i havent tried the #code yet heard its dangerous
[Captivate Android Development] dacket84:
You can find the GB rom for download in this thread --> http://xdaforums.com/showthread.php?t=887037
[Captivate Android Development] opcow:
I installed gingerbread right alongside my the Assonance ROM I was using at the time and dual booted by changing kernels. And, no, you should not flash to stock when installing 2.2 ROMs, despite what you may have been told.
[Captivate Android Development] erych:
YESSSSS thanks to flashman2002, and dacket84 for the big assists guys!!! you all are the best!!! gingerbread now working greeaaaat on my captivate!!!!!
[Captivate Android Development] tnayrbj:
help getting started

I am using Darky's 8 with speed mod K12I EXT4-SYSTEM BLN2.3 STABLE, will that work to load GB on top of??

I just don't want to brick the phone :)

Update: yes it will just have to apply the ext file system first.

Thanks

Jon
[Captivate Android Development] flashman2002:
It has nothing to do with what I have been told. If I am flashing a Rom that has different kernel, modem, rom, I will flash back to stock. If I am going straight across I have no issues flashing over. It is not as you say "you should not" because you can and really should to save heartache and needing to flash again because of boot loop or FC. And yes, when you install the 2.3 it is dual booted, which means when you want to go back you just flash your 2.2 kernel. That has nothing to do with what I said and first installing a 2.2 rom...because it is NECESSARY to have a 2.2 rom with a kernel that supports EXT4 to boot 2.3. Got it? I am sure you do know, or everything I have just said is BS, and the guys saying the same things in the threads are saying BS as well.
[Captivate Android Development] flashman2002:
Let us not forget this is the same thing as what you would do using the ADB commands...just in cwm zip form. This is a great way of doing it in case ADB does not work.
[Captivate Android Development] G-Man.:
Can this GB rom be flashed over Cognition v2.3b8? I cant find any ext4 lagfix options in CWM.... I know its got voodoo 5 enabled... is that good enough? Or do i need to switch 2.2 roms before attempting to flash this GB rom?
[Captivate Android Development] flashman2002:
Voodoo is ext4 conversion. http://project-voodoo.org/lagfix
[Captivate Android Development] flashman2002:
Double post...sorry.
[Captivate Android Development] Jmurph3:
I'm not really in the mood to sift through all 600+ posts to find what might possibly be my answer, so I'm going to ask.

What''s going on with this project?

Has Supercurio took off without word and put an end to the GB port?

I know everyone has lives, so unlike most, I'm not going to get upset about it.
[Captivate Android Development] jozymozy:
Ever seen that particular Sportcenter commercial with Dwayne Wade working on jis highlight package?

John Anderson: *pokes head in door* "Hey, Dwayne, I was wondering when we'd have that highlight package ready."

Dwayne Wade: "When it's ready."

John (meekly): "oh, okay. Because we were really hoping to get it on soon because..."

Wade: (deliberately): When. It's. Ready.

It's like that. also search function, put some effort into finding your answers before you just ask, etc
[Captivate Android Development] EtherealRemnant:
I think its ridiculous how many of these phones have been sold and yet so many other devices have mostly-working GB ports.
[Captivate Android Development] Konner920:
I think it's ridiculous that HTC gets more support than Samsung phones x_x
[Captivate Android Development] TheEscapist:
Supercurio is working on Voodoo sound, the CM team took over and are going to release CM7 when it's ready.
[Captivate Android Development] opcow:
Flashing to stock, despite what you may have been led to believe, isn't necessary.
[Captivate Android Development] techmik67:
Why do you insist on running all over the forums telling people not to flash stock? It DOES prevent a lot of issues from arising when changing roms. If the dev of a rom suggests flashing stock 1st, I suggest listening to THEM......
[Captivate Android Development] rraquib:
I concur with opcow. Going to stock is not necessary if you know what you are doing.
[Captivate Android Development] techmik67:
#1 - Not everyone knows what they are doing, and some people THINK they know what they are doing. That's 2 sets of people who would be ill-advised by your advice (which would sound a lot better as opinions, not stated as facts)

#2 - If you DO know what you are doing, then you

know

when to flash stock and when you can skip it, and therefore don't need to read it here.

So you are saying, "if you know what you are doing, it's not necessary", but you're saying it to PEOPLE WHO DON'T. That advice is FAR more likely to cause problems/bricks than a simple flash to stock, IMHO....

;)
[Captivate Android Development] sschrupp:
Very true.
[Captivate Android Development] opcow:
I suggest using your own brain instead of that of some ROM developer who may or may not actually know the best way to install a ROM. If you presume that the fact that some guy put together a ROM is evidence that he has some special knowledge of the install process then you are mistaken (I'm sure this strikes you as inconceivable).

As to why I stated my opinion on the matter, it's because a person with a perfectly good froyo install shouldn't be told to wipe it in order to install the dual bootable gingerbread. They are perfectly welcome to if they want, but when you tell them they must because some person told you that you must because some other guy told him he must because perhaps 3 or 4 months ago there may have actually been some reason to do it with some particular ROM or another, you are spreading misinformation. I'm sorry if my heresy has offends you.
[Captivate Android Development] techmik67:
Dude, they make decaf now......
[Captivate Android Development] :
I would like to think that the owner of the ROM has tested it thoroughly and booted multiple times and tried multiple ways to break it so they can get thier ROM to run as smoothly as possible. So if the owner says to flash back to stock first, Im going to listen to his advice.
[Captivate Android Development] opcow:
Actually, people who don't know what they are doing are ill-advised to be unnecessarily using odin. When they brick their phones what will you say? You'll say it was their own fault for not following instructions or whatever.
[Captivate Android Development] opcow:
You are correct, sir.
[Captivate Android Development] opcow:
I would like to think so as well. Unfortunately they are busy with other things and probably aren't inclined to doing all that and so they just go with the thing everyone has always done (on the captivate forum). I, on the other hand, have tested many versions of most of the ROMs in this forum without going to stock for months with no issues. Plus I read install scripts:

<snip>
format SYSTEM:
format CACHE:
format DATADATA:
format DATA:
delete_recursive SDCARD:.android_secure
delete_recursive SDCARD:Voodoo
delete_recursive SDCARD:Android
delete_recursive DATA:dalvik-cache
delete_recursive DBDATA:databases
<snip>
[Captivate Android Development] BigEHokie:
I don't have a dog in this fight, but I generally don't get the feeling that everything is tested, re-tested, and tested some more to ensure everything runs as smoothly as possible. If so, bugs wouldn't get re-introduced, things that previously worked stop working, etc. An Android ROM is a HUGE piece of software and to do proper regression testing before a ROM release would take months with the appropriate team in place, not a few days by a couple of people.

Just my 2 cents, I'm a software engineer :)

With that said, I have no problems with clear/no clear, bugs being introduced or re-introduced, etc. I love what the ROM cookers and developers are doing and it makes my device 100x better than stock. If something does happen they usually address it pretty fast.
[Captivate Android Development] cruiserbax:
This is just my experience with this tech demo of GB. I have yet to flash stock before installing it, it doesn't really bother your in-place ROM it does symlinks if I am not mistaken, and it uses a special kernel to boot. I have not had any issues flashing my old kernel to go back to my 2.2 ROM either. looking at the manual install method I don't see anything being done that would matter if I went to stock then flash a ROM with ext4 fs or not. in other ROMs I have had a couple issues where flashing didn't work out and I had to flash stock but as 9 out of 10 times I don't have any issues I always flash first then flash stock if something goes wrong. I love Darkys ROM because it doesn't wipe, no issues yet and I've installed every new version to date. Also most ROMs out there now have a kernel that supports multiple fs so I haven't had any fs issues when flashing a new ROM since way back in the early voodoo and oclf/loopback days, again just my experience.

EDIT: I also forgot to say that if I published a ROM I would also have a single set of instructions that would include flashing stock or something. The reason being, I don't know what each and every person has done to their phone so doing the instructions this way I can have a way to install it where you bring your phone to a known state that I know should work to install my ROM. Still I would know that anyone who knows what's up with their phone and my ROM will probably deviate from my instructions, it's just a surefire standard (guide line) to prevent some possible issues or questions from some (never all though)
[Captivate Android Development] tnayrbj:
My 2 cents

+1

but if everyone would ignore opcow he would just go away. I have been on this site along time and found that people who don't do much, say alot. This guy is trying to say to flash or not to original and he probably believes what he is saying, but when DesignGears, Darky and the rest of the Big Dogs say do it. I DO IT.

My 2 cents

Jon
[Captivate Android Development] opcow:
That's a reasonable philosophy, assuming you tested doing that. There was a Cognition release (2.2b9, I believe) which, if you followed the given instructions about flashing to stock first your phone would be unbootable, but if you flashed directly over the old version (or used the odin version of that ROM) it was fine. Obviously this is a case where the cwm install wasn't tested from stock. I'm not aware of any other releases with that kind of bug, but it does illustrate the fact that starting with a 2.1 base for your 2.2 install does have potential pitfalls.

My proscribed method would be like this: For those who have to ask how, do the CWM install, if you have problems reinstall, if that doesn't solve them and you know which odin package to use and how to use it then do that (and let me know what you were running before, because I'd like to see if I can duplicate and eliminate the issue). Everyone else, do what you want.
[Captivate Android Development] opcow:
You're right, although I planned to do some Android software development, I haven't gotten around to it.

I'm just a user.

But I've been on the other end. I've done lots of freeware software over the years. I wrote an xbox firmware patching tool called xbtool and I developed or improved many of the patches it provided, I also wrote other xbox firmware utilities and the only HD partitioner for the platform and was part of a team of people who developed a custom version of the xbox firmware. So yeah, big whoop, I'm not saying fall down and praise me I'm just saying don't assume I'm just a taker who does nothing. I try to give back what I can when I can, but I'm not going to be a "big dog" in every arena (which is just fine with me--I don't do this for attention).

So I don't do a lot, but I'm willing to help or give advice if I can. You disagree with my advice on this particular issue because "the big dogs" say otherwise. Personally, I feel I can save people some trouble and maybe even a phone or two, so I give my opinion.
[Captivate Android Development] Dani897:
^ you are very opinionated and argumentative which makes you seem trollish. And that causes a reaction.

I understand the idea of a flash to stock. And the devs are just trying to prevent the situation of holding one hand to get out of a boot loop. Some non wiping roms would have problems if the previous rom was not the same build. A factory reset is often enough to prevent problems. 90% of the roms for this phone wipe data so it is not usually a problem. Also it is a bit to do with lagfixes.

The oneclick odin application re-formats all the partitions to rfs. Flashing a kernel without ext4/2/jfs support on a lagfixed rom would be problematic. Even some kernels without a way to detect lagfix settings are problematic.

Telling people good practice to keep the install clean is a way to prevent those "help im hopless and im in a bootloop" threads. Keeping the advice consistent for the roms that wipe prevent those " I did this before and this time it didnt work so now I blame you" posts.

But I agree. This particular rom has zero need for a flash to stock as this rom can coexist with any other rom.
[Captivate Android Development] geokhentix:
Either way, it's not big enough of an issue for us to clutter the thread with a bunch of semantics. It works either way. I think it's pretty commonly known that a flash to stock is "recommended", rather than required. It's a something that people will still do, people who like to take extra steps and keep things organized. Personally, I also master clear before I install a new ROM. I know I don't need to, but I like things clean. Obviously this ROM is a bit different, but generally, if it takes under 5 minutes and it can thin out users bombing the thread with the same monotonous FC/boot loop problems, it's worth it. For those of us at XDA who may know that said operation does not require a wipe for correct operation, we can nix ourselves the grueling 5 minutes and start at step 3. Everybody is still happy in the end, making an issue out of this, or even drama in this release thread about something so retarded, is moot.
[Captivate Android Development] silverslotcar:
+1 LOL!! Auburn wins the BCS National Championship!
[Captivate Android Development] EtherealRemnant:
Great. We'll see GB in 6 months then. :mad:
[Captivate Android Development] opcow:
Ok, fair criticism, I suppose, but I think there's more to it than that. Sometimes I think it's almost as if it's become a religious issue and I've blasphemed. Yeah, I'm being a bit hyperbolic here, but it seems like people are offended that someone has the gall to say that the advice they are giving, or some ROM dev they are all sycophantic about has given, is wrong.

Check this out: http://briefmobile.com/how-to-android-2-3-samsung-galaxy-s. The instructions written by supercurio there do not in any way mention odin flashing stock firmware. So I get reactionary people who act offended that I've proscribed the same method from the original instructions for using this dump.

Ok, I understand where you are coming from and I'm not trying to be difficult, or argumentative, I'm just addressing your points.

I agree with your theory as to why it might be recommended, I just happen to think the reasoning behind it (of devs, not you) is false. Secondly, I fail to see where reformatting to rfs then installing a bunch of files on it, then reformatting it as ext4 and installing files is useful. Maybe I'm wrong.

I agree with the philosophy, I just don't think it actually works in practice and I think it ignores the issues regarding inexperienced people using odin.

Thank you for the honest criticism. I'm sure I'm at least partly to blame for the reactions I get, but in this case I even gave advice that agrees the originator's proscribed procedure, so those who can only base their opinion on that of someone else really had no reason to be all butthurt about it.