yashsingh1/xdaforums huggingface dataset:
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
Completely forgot to include the phone specs, my mistake:

Recovery Version: 3e

HW Version: I500.05

Model #: SCH-I500

Firmware Version: 2.2.1

Baseband Version: S:i500.05 V.ED04

Kernel Version: 2.6.32.9

Build Number: SCH-I500.ED04

Just a note on that build number, one of the clockwork mod posts had a whole list of CWM's which were like JYX, JYZ, stuff like that, and they were like "pick whichever cwm matches your phone's build #, blah blah" My phone's build # has no J's in it, and I didn't want to brick it.
[Fascinate Q&A, Help & Troubleshooting] abrixxxx:
Did you boot directly into recovery after putting your battery back in ? You can't boot into the OS before going straight to recovery from odin or else it overwrites the custom recovery with the samsung one.
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
My mistake, I read that when I initially joined, but forgot about it when I posted :(.

So ROM Manager is completely useless now?

I'll take a look at that now.

Confirmed 3x, holding down power + vol-up + vol-down starts the OEM Android recovery mode (ie. Android system recovery <3e>). From what I understand about the CWM, once it's installed and working, I should never see this screen again, it should always be the CWM boot screen, no?
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
I don't recall, actually, I'll try that now before I check out JT's recovery.
[Fascinate Q&A, Help & Troubleshooting] bangdrum:
Same as above. But also hold all three buttons and wait for samsung logo to turn on off and back on then let go.
[Fascinate Q&A, Help & Troubleshooting] abrixxxx:
Most likely you booted into the OS then powered down then did the 3 button method which would make the samsung recovery overwrite the one you odin'd.

Do this odin the recovery.tar I linked then when you put the battery back in hold volume up+volume down then press power as well make sure you're holding all three at the same time no just two of them. If you go to the custom recovery good job if it boots into the OS try again there is no way it should boot into the 3e recovery if the recovery is being flashed via odin and says pass.

Yes ROM Manager is 100% useless for us fascinate users.
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
Okay, I did that after flashing it with Odin (without letting it boot the OS) and "CwM Lagfix 2.5.X" came up. I then tried rebooting the phone and didn't hold it down and then it went into the OS. I then shut it down, pulled the battery, and held all three buttons again, but it brought up the standard Android recovery system :(.

From what I understood the clockwork mod was permanent, but everything I've seen on my phone makes it only temporary. Am I doing something wrong?
[Fascinate Q&A, Help & Troubleshooting] Falcyn:
2.5? That's an even older version. What link did you use? The one I gave you: http://xdaforums.com/showthread.php?t=1046905 is a 3.x.

And yes, ROM Manager is essentially useless for our phone.

EDIT: You could always just ODIN the whole UKB 2.0 package, too, which will get you jump-started with CWM, a new kernel, and obviously the ROM itself:

http://www.mediafire.com/?a63v435opsaq3g3
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
Yeah, I first tried it with the package I was working with from the thread I linked to in the OP from here.

Doesn't matter, though, same thing happened. I used the package in the link you gave me, flashed it to the phone, rebooted into recovery, worked fine with 3.X, then rebooted it and let the OS load, then powered it off, then tried to reboot into recovery and I got the standard Android system recovery.

Unless I'm missing something this "Android recovery system <3e>" should never be seen again, but it seems like the CWM flashes I'm doing are volatile on OS loads.

I'll check out that link now.
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
FINALLY!

I installed UKB 2.0 and CWB worked at first...so then I hit "Reboot" and loaded the OS. The OS loaded (UKB) and then I held the power button, and hit "recovery mode." This restarted it, but it loaded into "Android recovery system" - I was about to kill somebody, but then I noticed it was 2e, not 3e. So I took the CWM 3.0 and flashed it back, and now, whether I hold all three buttons or hit "recovery mode" from the hold power menu in the OS, it boots into CWM 3.0.

I'd like to say I think I've seen the last of the Android recovery system - but I know I haven't :(.

The only thing I can't figure out is why it has ARS 2e AND CWM on it. Seems like they're direct replacements for one another...I would say the UKB 2.0 ROM shipped with just ARS 2e and that was that - but it showed the CWM 3.0 before I loaded the UKB OS.

Is the ARS sitting "under" the clock work mod? Or are they direct replacements for one another?

EDIT:

Also, which 2.0 ROM was that? I've been using this page as reference. That seems like the official page for that ROM. None of the 2.0 ROMs there are the link you gave me, though. I'm just curious if I should update the kernel or not, as the ROM either A) Didn't update it, or B) Included the same version. While I'm asking a question a second here, what is the PBJ setting and the OTB? I'm assuming OTB means out of the box, but I could be wrong, and I believe PBJ has something to do with power or under/overclocking, but I'm not quite sure..and even with the word android, google turns up lots of results for sandwiches under the query.. :(
[Fascinate Q&A, Help & Troubleshooting] Falcyn:
I do know that for a time we had to boot into the stock recovery, hit "update.zip," and then we'd reboot into CWM so at least at one time they did run side-by-side... but I honestly don't know if stock recovery is completely replaced now or if it just gets ignored.

Anyways, that was the official UKB/CR 2.0 ROM, but the ODIN file wasn't put together by TSM as it contains all the other components too. landshark68 packaged that up and his packages are all reliable.

As far as the kernel goes, the one included in what you flashed is a non-Voodoo PeanutButta Jelly Time kernel with a -50mv voltage reduction to help with battery life. That's a regular speed (1ghz) kernel.

Only The Brave (at first I thought it stood for Out of The Box too, go figure) is a more customizable kernel that can be both overclocked and voltage-reduced but starts out with neither.

I would recommend sticking with the PBJ kernels, personally, as they're actually good out of the box without having to play around with voltage controls manually.

The only reason you'd really want to switch kernels now is if you want to go to Voodoo... the PBJ kernel that ODIN file set you up with isn't.
[Fascinate Q&A, Help & Troubleshooting] garywojdan81:
The key to making cwm permanent is replacing the stock kernel. You can odin anything you want but if you leave the stock kernel it will overwrite your recovery every time it boots. Any of these custom kernels that are packaged in ukb roms should have the proper cwm included, but it may not hurt to update the recovery as new ones become available.
[Fascinate Q&A, Help & Troubleshooting] wilshyre:
^^That's hysterical! Haha, I LOL'D when I saw that. I promise I'm not being an ass. PBJ stands for imnut's peanut butter jelly time kernel, and OTB stands for nemesis2all's Only The Brave kernel. If the package you flashed did not come with either one of those 2 custom kernels, you need to flash one. Either OTB 1.6 for Touchwiz based roms, or one of imnuts' PBJ kernels. Since I usually always use OTB, I'm more familiar with it and I know that it will permanently install CWM 3 for you upon installation and then you should no longer have any problems with stock recovery replacing your custom recovery. I'm pretty sure that PBJ does the same thing, but I dont know for sure as I havent used it. If you want full overclocking/undervolting abilities, you should probably flash OTB.. PBJ is not overclockable, I dont think, but again I could be wrong.. OTB gives you full control of voltage used for each frequency step available using the app "voltage control."

Oh, and voodoo, too. OTB kernels are all voodoo-enabled. Now you can run OTB kernels with voodoo disabled manually in recovery under the voodoo options, but with hiw good and reliable voodoo has become, and considering how much it speeds up your phone, im not really sure why anyone would use a galaxy s phone without voodoo or ext4 formatted partitions at least. But thats just me, as I realize some people prefer standard non-voodoo kernels.

To sum it up, I know for fact that using OTB kernels will replace stock recovery with CWM3 voodoo-enabled recovery, and you wont have it reflashing stock recovery like stock kernels do (which is the reason for the problems you were having).. PBJ might do the same thing, but im not sure because they're not voodoo kernels so I don't know if the PBJ kernels actually replace/update your recovery partition like OTB does. Either way, PBJ will not reflash stock recovery once you have a custom CWM kernel flashed, so as long as you do that you should be good to go.

Anyway, I hope you got it working right by now. I just thought that was utterly hysterical when I read that part about whenever you google for PBJ kernel that it comes up with a lot of results about sandwiches. Hahaha, that's classic.
[Fascinate Q&A, Help & Troubleshooting] tonu42:
Tbh this guy if he can't handle this stuff he will eventually brick his phone and cry bloody murder. Their is an all in one which I don't know why you didn't flash that.......
[Fascinate Q&A, Help & Troubleshooting] M00NEY:
I bet this is the source of much of your frustration.

You need to go straight to recovery and flash a kernel - the stocker is putting the samsung recovery in place before you get to cwm...

Swyped...
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
Gotcha, now a Voodoo kernel just has the lagfix and other Voodoo project items bundled into the kernel?

Gotcha, so now it's permanent (yay) :)

:)

Yeah, I think in PBJ it's set in stone, because there's different PBJ UKB ROM's with +/- voltages, so I'm guessing it's a packaged thing that's compiled into the ROM.

I believe I saw Voodoo in CWM on this Kernel. Guess it's just the OEM version with whatever PBJ fixes, and Voodoo packed into it.

Maybe at some point I'll try OTB, it definitely seems like a nice touch to be able to adjust your clock on the fly. Though I wonder if there was a particular reason why UKB only offered PBJ kernels and no OTB ones :-\.

Bite me.

I was "into the rooting game" for like 4 hours before making that post.

It's hard to just "pick up" random tid-bits of information from forum threads - because everybody uses TLA's and if you're new to it, you don't know what all those TLA's mean.

So while it's possible that I brick my phone at some point, that's a risk I'm taking, so in other words I should PM your ass in like a year when my contract is up and I get a new phone and tell it to stick it up your ass sideways.

AND, if you read (which you didn't), you'll see I already flashed the all in one and am running 2.1 perfectly stable now. Why did I not flash the all in one? I didn't know about the all in one. If I had, I probably would have done that a long time ago.

If you're not the one doing the hacking on the ROMs then 80% of the battle of "rooting/hacking android phones" is simply the act of knowing what's out there, different patches, compilations, images made by different people, issues, successes, etc. between different packages. So if you're like me, and busy, and can't always afford to read the latest and greatest, it puts you as a disadvantage.

So in short, shove it.

Yeah, go figure O.o. Didn't think the OS booting re-wrote the recovery partition/sector on boot, from an OS perspective, that's just weird.
[Fascinate Q&A, Help & Troubleshooting] DirgeExtinction:
I think you should have flashed a custom kernel before attempting to ODIN CWM 3.x

It would've made things a bit easier for you since the main reason the blue Samsung recovery comes out is because you have the stock kernel.

But it seems you already got UKB installed which is good. :)
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
It turns out the package I was linked to by Falcyn had the same kerenl version, but it was a PBJ Voodoo kernel with no voltage changes. So it seemed like I hadn't, but I had.

I didn't know the kernel flash was what the recovery partition was part of.

As for flashing CWM 3.X directly, I wasn't aware that the Kernel was going to re-write the ARS on boot-up, and if I didn't catch it before it booted, I'd have to re-flash.

Learned a lot in this little thread - thanks a lot guys :). Sorry about posting in this forum, I forgot amiss my frustration :(.
[Fascinate Q&A, Help & Troubleshooting] wilshyre:
Actually, every new release of UKB ComRom offered versions with OTB kernel. In fact, UKB 1.0 and UKB 1.3 came packaged with OTB kernels only. UKB 2.0/2.1 offered 2 different versions withPBJ kernels, one with the latest OTB kernel, and one without a kernel. look it up in Nitsuj17's thread for COMROM. They even came with the voltage control app packaged in as a system app so you could over/underclock and under/overvolt immediately. Now there are probably ODIN files on other forums and whatnot that were made by other people, or even links copied from nitsuj17's thread, and maybe the forum and posts you were looking at only listed the UKB versions with PBJ kernels, but in the original threads by nitsuj17 and adrynalyne for UKB comrom here at xda, they all offer otb versions. And like i said, the earlier versions came with otb only.

As far as the voodoo recovery options you see in your recovery, they require a voodoo kernel to work.. The voodoo recovery versions you see and that you are using are the only fully functional recoveries we have for the fascinate, so thats why mostly everyone is on some version of the voodoo recovery that have voodoo options in it, even if they are not using a voodoo kernel. The voodoo recovery can be used without voodoo or voodoo-enabled kernels. All other versions of CWM are not fully functional, so even though you see voodoo options when booting into recovery, you still have to have a separate voodoo kernel that supports ext4 file systems installed in order to activate voodoo.. otherwise enabling voodoo in recovery while using a non-voodoo kernel will do absolutely nothing, and flashing the ext4 formatter by navendrob would result in unreadable partitions when using a kernel that doesnt support ext4. But it looks like PBJ actually is a voodoo-enabled kernel, so it would support everything needed to enable voodoo.

Sent by way of unspeakably black magic.
[Fascinate Q&A, Help & Troubleshooting] Syndacate:
lmao, wow, there was way too much "voodoo" in that second paragraph for me to capture it all.

So let me see if I'm understanding this right, the CWM comes with voodoo options regardless, but they may or may not work with the kernel that's installed.

A kernel can be voodoo enabled, which is packing into it some of those options, so there's different "types" I guess you can say of the same kernel but with different voodoo features packed into it?

I saw the OTB kernel in the UKB thread but the PBJ ones had -50 and -100 as the only options. So that means that those PBJ kernels are underclocked/volted by 50ua?

One thing I'm missing, though, is why doesn't everybody just go with the OTB kernel? Then you can OC/UC on the fly, opposed to it being pre-packed in and you having to re-flash it if you want to change the clock? I mean if they're voodoo enabled and the same version, for all intents and purposes the only difference is the clock, no?
[Android Software/Hacking General [Developers Only]] tipstir:
HONEYCOMB GBV500 MOD RELEASED FOR GINGERBREAD OS 2.3.1 6.21.11

HONEYGREEN GBV500 MOD RELEASED FOR GINGERBREAD OS 2.3.3 6.21.11

HONEYCOMB GBV600 MOD RELEASED FOR GINGERBREAD OS 2.3.3 6.21.11

Totally reprogrammed MOD for the best performance plus OC to 720MHz max over 528MHz min.

Before under Android Eclair OS 2.1

After under GingerBread OS 2.3.1 / OS 2.3.3

Source: KTZ
[Android Software/Hacking General [Developers Only]] tipstir:
GUI update for HoneyComb Hybrid MOD OS 2.3.1 see first post!
[Android Software/Hacking General [Developers Only]] oostah:
where do we download it at. thanks for your work i have been using your roms for about 5 months on my kids coby mid7015
[Android Software/Hacking General [Developers Only]] oostah:
i found what i need but when i get to this point

Make sure you have PRESS RESET ON THE BACK AN PRESS POWER + HOME BUTTON AT THE SAME TIME UNTIL YOU SEE FWDN MODE IN BLUE ON SCREEN

i dont get the FWDN on the screen it reboots

im running this rom now

[DEV] ATZ MID7015A 2.1 06/09/11 HONEYCOMB HYBRID V20.0-B25P

thanks for any help or info
[Thunderbolt Q&A, Help & Troubleshooting] itsmejson:
Hi guys,

I'm planning to upgrade to a TB hopefully

this weekend, but also considering the iphone.

I'm about 70/30 in favor of the TB

Just wanted to get your input and see if you

guys that already have your TB, used it, gotten

comfortable etc:

- Can you still say that you are happy w/ your

decision?

- any items that you dislike that you've discovered

from your daily use that you had not noticed before?

- build quality still holding up well?

Thanks for your time
[Thunderbolt Q&A, Help & Troubleshooting] tct08:
I've had my bolt for about 2 months now and I am very pleased with it. I never had the reboot issues so that was a non factor. Battery life honestly isn't that bad. I can make it 12 hours which is enough.

That's probably largely due to rooting and installing custom ROMs, which is actually the biggest advantage. The developer support is massive on this device, at least matching what I was used to on the Incredible, which had some of the best dev support next to the Evo and Nexus devices.

Don't fret the lack of a dual core processor, I honestly thought I would but clocked at 1.4 I don't notice ANY lag. And honestly, having a slow network (IE not Verizon 4G) would cause far more noticeable slow down than not having a second processor.

Hope this helps!

Sent from my HTC Thunderbolt
[Thunderbolt Q&A, Help & Troubleshooting] sublimaze:
I agree with all of the above. I've had mine about 2 months as well, and I wouldn't trade it for anything. I briefly considered exchanging my TB for a Droid Charge, but the Charge dev support is virtually nonexistant, and I can't stand Touchwiz. I've had better battery life with other phones, but I routinely get 16-20 hrs on my TB and I have a couple of extra batteries, so the battery isn't an issue for me. Mine is slightly overclocked (1.4ghz) and the Sense UI is silky smooth, so even though it has a single core cpu, it handles everything I throw at it. As mentioned before, you'll appreciate the difference between 3G vs. 4G much more than single vs. dual core.
[Thunderbolt Q&A, Help & Troubleshooting] SMR-DINO313:
I agree too . I had iphones since first gen . Even when iPhone 4 came out I was talking smack bout Android phones . But I switched to Verizon from ATT and was debating either iPhone 4 again or thunder bolt . Picked the TB to test out . And gladly I say I made a good move that day . Great phone and puts the iPhone in the ditch .
[Thunderbolt Q&A, Help & Troubleshooting] C@rn@ge:
I love it. Das BAMF just came out with 4 new rom versions under 24 hours.

Christmas in July.

But to answer "- Can you still say that you are happy w/ your

decision?" Yes because it has kickstand. :D
[Thunderbolt Q&A, Help & Troubleshooting] crookshanks:
When I bought this phone I thought the kickstand was absolutely the dumbest thing I've ever seen on a phone. Fast forward three months and now if I look at a phone and it doesn't have a kickstand I wonder how the user is able to deal with it.
[Thunderbolt Q&A, Help & Troubleshooting] allchannels99:
Mine did nothing but glitch and power off with factory flash. 1 week later I love it... running MR2.5, BAMF Stripped 2.1, and lots of apps.
[Thunderbolt Q&A, Help & Troubleshooting] Frammer:
Temptation

The Samsung Galaxy S2 is tempting to me. I personally think the device looks amazing.
[Thunderbolt Q&A, Help & Troubleshooting] robotsforeveryone:
I remember when a kickstand and a FFC were the big draws.

I even got a 3rd line on my account just so I could get this phone.

But with 3D phones, dual core processors and fancier UIs I'm a little bummed out about this phone. If it wasn't for BAMF I'd have probably just sulked until the next big thing. As you can see I don't wait long to jump on the newest device (BTW, the mythical Bionic and GS2 don't impress me so it might be a looooong wait :rolleyes:):

Droid 1 - 11/09 - 4/10

Droid Inc - 4/10 - 7/10

Droid X - 7/10 - 3/11

Thunderbolt - 3/11 - present
[Thunderbolt Q&A, Help & Troubleshooting] mattsonhistb:
The thunderbolt is well beyond expectation. The 4G LTE network is literally 20 to 30 times faster than the iPhone's 3G network, there are a couple dozen ROMs to test, and Android is better than iOS.

Also, there's a kickstand on the Thunderbolt, how can you not love it? If you overclock to 1.4 GHz like many of us do, you will most likely notice no lag. If you're smart with your battery, and take steps to save it, you should be able to get 12+ hours with it, even with somewhat heavy internet use and even a few videos or games everyday.
[Thunderbolt Q&A, Help & Troubleshooting] cdurand:
I love my Thunderbolt.

I had read all about battery life issues but decided to go for it anyway.

No battery issues to speak of and after rooter and going to BAMF the battery is even better.

The 4G speed is outstanding where available. I get 5mbps around my area (Mountain View, CA) but when I go to San Francisco it hits 20mbps+. Doesn't seem to matter where in San Francisco I am either, speeds are always amazing.

I never thought I'd use the kickstand. I just thought it would be there.. but I use it all the time. I do wish you could charge the phone while using the kickstand.. this seems like a major screw up on the people who designed the phone.
[Thunderbolt Q&A, Help & Troubleshooting] eraursls1984:
The Thunderbolt is the best 4g option right now, if it were me I'd get it before 7/7 to get locked into the unlimited 4g. If 4g isn't something you care about then I'd say the Droid X or X2. I like my Thunderbolt but not as much as my X, the thunderbolt is lacking in build quality, Motorola have always had the best from my experience.
[Thunderbolt Q&A, Help & Troubleshooting] (•.•):
my friend had one, but he sold it allready and will never buy a htc again.

He told me, it was ok, but nothing special..

most older htc models sucks anyway, mostly because of their bad camera and clumsyness.
[Thunderbolt Q&A, Help & Troubleshooting] ace2525:
Still loving the Thunderbolt. While the charge has a nicer looking screen, I still prefer HTC and the Sense UI over any other UI
[Thunderbolt Q&A, Help & Troubleshooting] loonatik78:
I went from an Incredible to the tbolt and its not a switch I've second guessed for a second. Had mine rooted the same day I got it. I don't see how an iFone holds a candle to the tbolt in any way.
[Thunderbolt Q&A, Help & Troubleshooting] itsmejson:
appreciate everyone's response :)

awesome, thank tct08 for the sharing your experience :)

great that's definitely encouraging. I've been looking at the section w/ all the roms in it and i'm thinking i'm going to try one BAMF's roms ;)

i keep seeing mr1/2 throughout the forums - what exactly is/does that mean? from what i've read it does it have to do w/ gingerbread at all?

thanks matt for your user experience as well. @ this point i'm definitely going to go w/ the TB, my wife's planning to go w/ the iphone route lol.

for overclocking, is there a tutorial on how to get that done? is that involving changing the kernal or something?

- - Another question I had that for you guys: on my current blackberry I have multiple email accts on it

w/ the thunderbolt how many email accts can you setup on it? is it only 1 main one that we need to forward all emails to or ability to setup multiple accts?

thx again