yashsingh1/xdaforums huggingface dataset:
[Captivate Android Development] kdwolf85:
You like to ask really obvious questions don't you? Or do you just reword your questions when you get an answer you don't like?:cool:

Yes I know what it flashes. The point of doing it the way I did was to give members an option on rooting or not. I know most members want there phones to be rooted. There are also those few that want to keep their phones as close to stock as possible. That's why I made the one click as a completely stock rom and then gave the option for those who want to root it. The one thing I know the members here at XDA like is options so that they can get their phones to work just right for them. I don't want to push anything onto someone, but rather just give them multiple options.
[Captivate Android Development] freakjc:
i currently have cyanogenmod 7 on my captivate, can I use this flash??
[Captivate Android Development] dajeoo:
Go back to stock jf6 first
[Captivate Android Development] freakjc:
can i reflash it with the odin one click i897ucjf6??
[Captivate Android Development] dajeoo:
Yes
[Captivate Android Development] mwiz123:
Root method:

1. Extract and open Odin3 v1.81.zip and place the zImage-root.tar file in the pda slot.

2. Connect your phone to your PC.

3. Put your phone into download mode (Same as eclair/froyo 3-button combo or adb reboot download)

4. Phone will boot and show the fugu fish.

5. Power off and put your phone into download mode.

6. Place the kernelKF1.tar file in the pda slot and hit start. Phone will reboot.

7. You are now rooted with Stock 2.3.3 Gingerbread.

Im not getting busybox
[Captivate Android Development] Tintillo:
Is not working for me. Success on first step but then cannot turn off and go to download mode, it loops. Without cable, will loop between the ATT screen and the fish. When plug it will loop the battery charging with a black screen. ODIN does not see the phone. Suggestions?
[Captivate Android Development] dajeoo:
Unplug USB from phone, remove battery, plug USB back in, hold both volume keys and put battery back, should then get download mode
[Captivate Android Development] Tintillo:
Thank you. It work to put the phone on download mode. Was able to tow both steps, as indicated in the first post. The phone rebooted and stays frozen on the ATT splash screen. Non of the keys work. I pull the battery and restart the phone and same story. Suggestion Welcome
[Captivate Android Development] Donmotobike:
Sounds you're on Gingerbread, try pressing both vol +/- and power same time? By pressing both(screen will flash) and when the screen goes off plug in to odin(timing it took me several trys so be patient) it will automatically go into download mode then proceed with odin.if this doesn't work try holding both vol+/- and power and release power button while holding vol+/- while you plug in to odin(again all timing)...if you 're coming from cog 4.5.3, i suggest just(avoid fugu) and use odin again to load cog 5.2 kernel(load tar file pda slot)run odin one click and use cwm to load cog 5.2 beta...good luck.
[Captivate Android Development] nfs_phone:
Good choice, if you want the Audience Chip to work

I found that when I updated to the Cog rom and kernal (I didn't check till I'd done both), it disabled any control over switching the noise reduction on and off. The problem is with Cog 5b3; someone else reported that it wasn't a problem with 5b2.
[Captivate Android Development] Donmotobike:
this should be posted on Cog 5 beta 3 thread - sounds like you found a bug....:eek: I don't know why you quoted my comments about odin UCKFI and fugu that is history - im on cog 5 beta 2 - not upgrading to beta 3 because I have no use for video chat LOL(captivate has no front camera???) dont even know why he even put this feature...,more importantly waiting to see if we can do a full backup on CWM:cool:
[Captivate Android Development] nfs_phone:
I did

I've posted in both threads, by mistake, because I was under the impression that the Audience chip was not properly activated with UCKF1 stock. In fact, it works fine there. I was trying to test it by hitting Menu during a call, and I found that I couldn't switch Noise Suppression on and off during a call when I did that. Turns out the reason was that I had it in Speaker mode, and noise reduction cannot work in that mode, because it needs to use a second mic to tell noise from the signal coming in at the mouthpiece.

There is indeed a problem with Cog 5b3, but apparently not with Cog5b2, so enjoy beta 2.
[Captivate Android Development] prbassplayer:
Odin with out bootloaders?

I know this has bootloaders included i was just wondering if there was a way to get a clean GB ODIN without the bootloaders. Way I figure is Flashing bootloaders has its risk and if i want to just clean flash to GB with ODIN (if a rom flashed incorrectly)
[Captivate Android Development] DeMarzo:
Does anyone know a GOOD source to DL the 1 Click in the OP? I've been trying to DL it for a week. Keeps failing around 80%

Anyone else have this problem?
[Captivate Android Development] mrhaley30705:
You mean a version of KF1 without loaders and pit? Check my sig for that very thing. If you want to add the pit, dl the full odin version in my thread and add the pit to it.
[Captivate Android Development] prbassplayer:
Thank you so very much, now for my noob moment what does the pit file do? and why would i need it?
[Captivate Android Development] smanzor88:
heads up the one click gb with out the bootloaders has a prerequisite of having the gb bootloaders first. that package is if you want to get back to stock gb rom currently on a custom gb rom..
[Captivate Android Development] mrhaley30705:
I could try and answer that, but i don't have the right vocabulary for it. If you are jsut going to flash it as a way to go back to stock, you shouldn't need the pit. I have heard of some people flashing and running without pit with no adverse consequenses.
[Captivate Android Development] prbassplayer:
Alright thanks again for the info =)

I know I need GB bootloaders for GB roms, I'm already running Cog 5 beta 2 (great rom btw) but my concern was if i flashed a GB rom and i got a bad flash and needed to ODIN back to stock GB i didn't want to use the one click since it has Bootloaders and if for w/e reason ODIN failed I could hard brick my phone. With just the GB "rom" I can flash with ODIN and minimize the risk. Thanks for the info though =)
[Captivate Android Development] DeMarzo:
Still looking for a good source to DL the 1 Click for KF1. Been trying to DL it from the OP and I get to about 80% and it fails.

Tried every mirror link on from milti-upload. Anyone maybe load this to a torrent or anything?

PLEASE?
[Captivate Android Development] dspielman:
I have flashed my Captivate to stock 2.2 and when I try to install the 2.3.3 I am getting an error. I've downloaded it twice and tried countless times.

<ID:0/005> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> MD5 hash value is invalid

<OSM> End...
[Captivate Android Development] ayqwasi:
Every time I try this rooting procedure, after flashing kernelKF1.tar, my phone goes into a loop, flashing between AT&T and Galaxy S GT-9000 initial screens. What am I doing wrong?
[Captivate Android Development] kdwolf85:
It shouldn't be saying GT I9000 at all. That implies that you flashed an I9k kernel.
[Captivate Android Development] xZeDgEx:
Same, no idea what else to do.

Figured it out, used the second download link. That download is corrupt or something.
[Captivate Android Development] Jay_eS_Iye:
I'm currently downloading but didn't see anything in the thread about the 3-button fix. My phone is one that whenever I did the JF6 1-Click I had to do the 3-button fix afterwards. Do the bootloaders in this 1-Click take care of that or do I need to do the 3 button fix still?
[Captivate Android Development] mrhaley30705:
The new bootloaders will fix the 3 button problem.

EDIT Once you flash the new bootloaders, Do Not flash the old 3 button fix.
[Captivate Android Development] singingmomof6:
Trouble with rooting

I have started from scratch, with the original Odin 1-Click Eclair stock, then done the Odin 1-Click for Gingerbread and that went fine. When I tried to do the Fugu root, I get stuck at step 4, with the phone cycling between the fish screen and the AT&T World screen. I have gone over and over, redoing Odin 1-Click and the Fugu root, with the same result (being stuck at the fish screen). The Odin 1.81 has the following in the log:

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> zImage

<ID:0/006> RQT_CLOSE !!

<ID:0/006> RES OK !!

<ID:0/006> Removed!!

<ID:0/006> Completed..

<OSM> All threads completed. (succeed 1 / failed 0)

What did I do wrong? I've just finished reflashing the Odin 1-Click Gingerbread again. Any idea what I can do now? Do I understand correctly that I need to be rooted before I can flash a custom ROM?

Is there another way I can root my phone besides the Fugu method? Thanks!
[Captivate Android Development] mrhaley30705:
The phone isn't supposed to boot past the fugu screen. Pull the battery, boot into download mode and flash the kf1 kernel. You should then have a rooted phone running KF1.
[EVO 4G Android Development] TommyNgo215:
First, I apologize if I post this in the wrong forum. Mods please move it for me =D thank you.

Second, I just went through hell to have my RSA key restore and I thought I have to post this instruction right the way in hope of it will save the next person.

For some reason my RSA key were missing and I have no idea why or how. But I did backup my RSA key using RA_Recovery a while ago so this instruction is only good if you did so.

Requirements:

-Root explorer Pro (paid)

-Terminal Emulator (free)

Instructions:

1. Assume you backed up your RSA key and have wimax.img file somewhere

2. Use Root Explorer Pro to copy and paste it to your root SD folder "sdcard"

3. Download "flash_image.zip" file from here: http://wiki.cyanogenmod.com/index.php?title=Flash_image

4. Use Root Explorer Pro to extract it to your root SD folder "sdcard"

5. Then copy flash_image file itself and paste to /system/bin (you change it from R/O (Read Only) to R/W (Read Write), paste the files, then change it back it R/O.

6. Open Terminal Emulator

7. Type su

8. type flash_image wimax /sdcard/wimax.img it will reflash the rsa image key to your phone

9. Download Wimax key check from Market to verify. It should now says your key is present!

Good luck!!!

Credits:NewZJ & jesuspgt for helping me getting this done.
[EVO 4G Android Development] sirmx:
Step 5 is backwards, you change it from R/O (Read Only) to R/W (Read Write), paste the files, then change it back it R/O (optional, but safer).

otherwise pretty easy to follow.
[EVO 4G Android Development] TommyNgo215:
there ya go...i edited it to reflect of what you typed =D
[EVO 4G Android Development] NewZJ:
step 8, needs .img after the /sdcard/wimax
[EVO 4G Android Development] TommyNgo215:
yes lol it's been a long day..
[EVO 4G Android Development] ceabbott2:
wimaxkey location

Well f a duck my keys are missing! I have no ideas but explains why it wouldn't connect when I was near a 4g area. Where can I find my wimax keys?

thank you very much

charles
[EVO 4G Android Development] #Winning#:
You will have to pull them from a backup, hopefully you made one!
[EVO 4G Android Development] ceabbott2:
wimax key back up

I know. I made a bunch of back ups but I don't know how long my wimax keys have been gone. Crap, I just deleted a couple of Really Old backups a bout a month ago.
[EVO 4G Android Development] TommyNgo215:
Go to those backup folders and see you have wimax.img

But if you make a nandroid backup of a whole rom.I think.you can just restore that backup. It should be in there.
[EVO 4G Android Development] momegao:
Thanks!

I could flawlessly restore my Wimax keys back. Thanks for everything!
[EVO 4G Android Development] TommyNgo215:
You're welcome. Im glad you got it fixed.
[EVO 4G Android Development] AFschizoid:
sorry to revive an old thread, but i was wondering, if i just made a wimax only backup with amon ra, it made a folder that had the md5 and wimax.img. if i zip that and email it to myself, so if something happens, i have it saved on my email server space, would i just need to unzip it to nandroid/whatever the device id is folder and restore from there? would that hurt my regular rom or is this (terminal emulator) the only way to restore the keys?
[Vibrant General] Longcat14:
I am, and I'll tell you why.

Samsung hasn't even started building a GB ROM for our phone, and that's kind of weird to me, because I would think that they would have something.

I don't remember where I read this, and this could be wrong, but doesn't the carrier has to request the update, and then the manufacturer builds it? (I can be COMPLETELY wrong, so don't hold me to this) If that's true, then we may not see a GB build, because T-Mobile USA wouldn't request it.

Tell me what you think, because this interests me a lot.
[Vibrant General] iynfynity:
Where did you get this info? that they haven't started the gingerbread for us.
[Vibrant General] Longcat14:
http://twitter.com/#!/SamFirmware/status/81421451059671040

http://twitter.com/#!/SamFirmware/status/81257522966700032

There.

They posted the GS4G leak, the Cappy leak, and they have a leak for the Epic 4G.
[Vibrant General] sroach23:
since there have been no vibrant leaks, it automatically means they have not started building it?
[Vibrant General] Longcat14:
It's not that, SamFirmware stated (and I honestly believe them, if they found all these leaks for other phones so quickly), that there's no Vibrant (SGH-T959) build, which could mean A LOT of things, possibly something as simple as Samsung is really lazy and doesn't want to upload it, but it would mean more.

I'm just saying, I don't know what's up, but I'd like to know more.
[Vibrant General] djquick:
And they probably won't, at least not in the near future since there are a ****load of new 4G phones coming out in the near future. The Vibrant is old news already like yesterdays dirty laundry. Technology advances faster than you can fart.
[Vibrant General] Longcat14:
Unfortunately, this is most likely the truth. :/

I hope they don't forget us. All we want is a leak. :(
[Vibrant General] VICosPhi:
Relax, It'll be released in a couple months for sure. Enjoy the new ROM's with working GPS this weekend :)
[Vibrant General] Longcat14:
THAT's the only thing good thing for us about all these leaks, we have working GPS now. :)
[Vibrant General] treyvaporizer:
I fart very fast...

Sent from SGH-T959 (CM7)
[Vibrant General] anthonys2r:
I noticed that as well. But you have to remember that T-Mobile plays real dirty. Remember when we had 2.2 leaks back late November (JK2)? It didn't become official until #NeverAgain made such a huge PR mess for them that Samsung & T-Mobile had to release it. But it was up until then, that T-Mobile didn't want to update out phones because of the pending MT4G & SGS4G release, dirty mfers...
[Vibrant General] savkhetan:
By the way this issue gets more complicated now with the AT&T merger. AT&T strongly believes that updates are not good for business. From their point of view if they don't do updates it gives users more reasons to upgrade to new phones.

So if TMo was borderline crap about this already, the adoption by AT&T is only going to delay things further.

What does that mean for us, enjoy the awesome roms on xda and forget about TMo.
[Vibrant General] Kennii:
Just read da tweets someone should just port from 4g to us

Ya boy
[Vibrant General] shadowofzeus:
Ya, but Google kind of helped us all out with that. Its not up to the carriers if a phone is going to get an update anymore. If Manufactures want to use Android they have to abide by the 18 month update cycle this goes for carriers too. They have to provided updates to newer versions of Android during the first 18 month of a phones life. Our Vibrants really only have six months left of that 18 though. So don't expect an official Ice Cream Sandwich update. I wish google had been enforcing this rule back in the days of the original cliq and cliq xt. The poor XT didn't even get an update out of 1.5. I think Google has gotten tired of all the negative press that manufactures are developing because of the unwillingness to update phones. Of course as you we all know a lot of this has to do with carriers not wanting these updates or their need for unreasonable software packages they want add to the update packages.
[Vibrant General] iynfynity:
How shock i am? Look at this pic. :p
[Vibrant General] cashyftw:
Hmm I don't see it as a problem, well at least as long as we have the vibrant 4g, I'm just waiting for the sgs2, then I'll be gone :D
[Vibrant General] movieaddict:
Well we cant be mad at samsung as its not there fault its tmobil. Most of us will be moving to hercules or sgs2 anyway so no worries crying over this in my opinion.
[Vibrant General] horseycraze:
Yeah, I think it's time to accept the likelihood that Samsung/T-mo won't be providing much further development or support for the Vibrant given the new product lines. It doesn't mean it'll be obsolete though. Thanks developers!
[Vibrant General] j1635:
what does it matter? theres literaly pages upon pages of custom rom's out there that are 100000x BETTER Then what any company puts out in the first place.

im pretty sure for a big majority of people here the first thing they do when they get a new phone is wipe it out and start over fresh.

what is it you want exactly, a bloated gingerbread rom from samsung full of **** you dont need or use?

what a useless thread
[Vibrant General] iynfynity:
Believe me it does matter. ;)
[Vibrant General] j1635:
then please explain to me why. Ive always assumed if there is this many rom's and custom firmwares out, #1 why samsung would even waste time porting new software onto outdated hardware when there is something better out there.

Ok i can see if you want to peek inside there software, but what else could they possibly release at this point that dev's havnt seen yet? not only that but really, once you read about everything thats out there, i sure as hell wouldnt want anything stock from samsung.

Just look at the voodoo stuff, the sound blew me away and the whole time im just sitting there thinking Samsung actually had the balls to release software as ****ty as it was with there phones.
[Vibrant General] xriderx66:
The dev's can't MAKE drivers.

Without Samsung, we're ****ed.
[Vibrant General] PJcastaldo:
This is anything but true.. Every SGS will be updated.. the 4G is very close to the Vibrant so im sure it will be next..

It is very funny to me how every one gets these conspiracy theorys going.. I hate to break it to every one but we would have been given an update regardless of #Neveragain.. T-Mo is a bit slow and of course they are.. they want the SGS4G updated first.. if you where them wouldn't you??? The bottom line is neither Sammy or t-mo has failed with this phone.. you guys are just very impatient, I dont mean that as a cut down or anything, but it is true.. Just chill it will come..
[Vibrant General] PJcastaldo:
Thats not true.. we just dont have the caliber Dev it takes to do this.. But its been done..
[Vibrant General] reuthermonkey:
this thread is full of the blind leading the blind.

None of whom apparently can read a god damn calendar.
[Vibrant General] SamsungVibrant:
MOST OF THE DEVS HERE ARE WORTHLESS WITHOUT DRIVERS FROM SAMSUNG. THEY ARE NOTHING BUT SKINNERS AT THAT POINT.

I'll praise a dev who can write important drivers, but I haven't seen it in the Vibrant forum.

So to answer your question. WHAT ELSE COULD SAMSUNG POSSIBLY RELEASE? THE DRIVERS THAT MOST DEVS DEPEND ON.
[Vibrant General] s15274n:
Wow.. so in this one thread we have bashed Samsung, T-Mobile, AT&T and OUR VERY OWN DEVELOPERS.

What have YOU done to help the problem? Nothing?

I can't believe people pick on XDA /sarcasm
[Vibrant General] shrapnelx:
OK, I'll bite....

Before you start talking crap about anyone, how would you go about writing a device driver without source or even documentation of hardware I/O registers and such? These guys do what they do for free, and on their spare time. I don't know many people that could put the time, effort and invest in the resources it would take to reverse engineer a low level device driver without so much as even really knowing what chipsets are being used in the phone let alone a hardware spec sheet.

Also, many devs have added significant features to our phones that improve performance and functionality, and go far beyond skinning. Have you not seen Voodoo (sound and EXT4), BLN, CIFS support just to name a few? DRIVERS ADDED TO THE KERNEL that improve functionality of the phone. Some were added even before source became available. That's not exactly easy.

I think your comments are ignorant and out of line which is why I felt compelled to make this post. There have been enough devs driven off by ungrateful users like you. I hate to see that this keeps happening in what is supposed to be a collaborative community. Next time you feel the need to make a derogatory comment about anyone in these forums, take a look at what you have contributed and ask yourself if it's so much better than what other have done that you can look down on them an criticize their efforts like you did in this post. At least then you could sound like you know what you are talking about...
[Vibrant General] Longcat14:
I can't believe people would bash the dev's, because of them, we WOULD be stuck on the bloated piece of **** that's called stock.

I was only asking of people were shocked for a lack of a build for the Vibrant, I don't see how people at bashing the dev's, AT&T (Huh?), or anything else.
[Vibrant General] Vibrant03:
Samsfirmware is a little pissed off at some site?
[Vibrant General] Dougefresh91:
With all the other Sammy leaks lately, I too was wondering why nothing for the Vibrant. Probably because it doesn't exist. I personally gave up ever seeing another update when we got Froyo. If we get it, awesome, but don't hold your breath.
[Thunderbolt General] shaggy5991:
I've had my thunderbolt for awhile now and ive been noticing how hot it gets when streaming movies I downloaded a battery temp widget and at ruined it gets above 107 wstreaming movies or downloading, I do live in Atlanta and it is on the high 90,s but I didn't seem to b noticing this on my incredible. I'm rooted and have been running diffrent time running gingeritis v1.0 now
[Thunderbolt General] yareally:
If you're that worried, quit overclocking. Also, not all the heat is from the cpu; some is given off by the internals related to the antenna, but shouldn't be a problem unless it's used excessively over a long period of time. I've had it overheat and reset from doing a large download over LTE for a few hours.
[Thunderbolt General] shaggy5991:
Not really concerned more curious to wether everyone else is seeing fast heat up to
[Thunderbolt General] g00s3y:
It's almost 100 degrees out, you are streaming movies and OC'd, and you are wondering if the phone getting hot in conditions like this is abnormal :confused:
[Thunderbolt General] Dnakaman:
You have to remember that most of that heat is generated because of the reactions within the battery to supply power to the phone. So the more draw you put on the battery the hotter it's going to get. Lithium batteries are notorious for running high temps when being charged/discharged. It's part of the price you pay to have more capacity is a smaller space.

I flown RC heli's for years, so I'm very familiar with how lithium batteries react. They pack alot of power in minimum space, but they can be dangerous is certain situations (that's why cars like the Prius still do not use them in production because of the fire risk).

Just a bit of info to think about.