yashsingh1/xdaforums huggingface dataset:
[Vibrant Android Development] GoodVibrant-ions:
It would make a lot more sense if you decided to be helpful and give information about what specific roms/kernels you were using previously, than to tell someone incorrectly that he was "likely" to brick his phone. Likely implies more than a fifty percent chance and from what I've read out of 1550 downloads 3 or 4 have had severe problems. That's less than 4 tenths of 1 percent chance of bricking. It was a very specific set of circumstances that caused it...and if you read this thread, you would know that. And if you read his post for that matter, you would know his phone doesn't fit the circumstances to be at risk. Which makes me think you dont read instructions anyway......which is probably more likely the reason why you sir are now the proud owner of a brick.
[Vibrant Android Development] :
Im using it now anx have flashed back and forth yo backed up stock kernel and back to this one. No problems. +1
[Vibrant Android Development] PJcastaldo:
Since it doesnt happen to every one, and we all seem to try out the same kernels and roms.... maybe think you and the others are suffering because your stupid and did something wrong? :eek:

I on the other hand have not only flashed between dead horse and dragon and now DOW with absolutely no problems.... i didnt ever change from voodoo in ULF though. I am seeing great battery life, high 19's in linpack and over 2100 on quadrant. Great work.
[Vibrant Android Development] Sdobron:
So far, so good going on day 3.

Any actual bricks on the T959 source reported thus far?
[Vibrant Android Development] Poser:
Experience: Flashed from DOW t959 HD to v1.4 resulted in non-boot (note, not bootloop). Stuck on vibrant screen, no response from capacitive buttons. Unable to access recovery. However, download mode functional. Odin'd stock KB1+voodoo and booted normal. Will download v1.4 to PC, confirm has and try flash again. Please note (despite morfics instructions) I choose to do all kernel flashing through recovery.
[Vibrant Android Development] traicer:
That's what I was wondering, how many of these bricks happen with the 959 kernel
[Vibrant Android Development] jaysins:
Same has happened to me. I relfashed it twice, once on bionix 1.2 and when I restored my phone I figured might as well update it 1.2.1 and reinstalled the 1.4 kernel and again I had the issues mentioned above occur on my device where I could not even get into the recovery.
[Vibrant Android Development] roffee:
I flased from stock voodoo. everything is ok including HD recorder and playback. why others has so many weirdly things:(
[Vibrant Android Development] Sym_Link:
I was the one who bricked my phone today in the IRC. I was not forced by any means. The state I got my phone into was by flashing a ULF kernel and I did it to see if I could find any errors that would lead to a solution. In doing so, I lost my internal sdcard, as well as my data partition. A mount showed I had no /dev/mmcblk0. The fix I used was exactly as morfic says in the OP, to flash JE8. I used all 3 files in the JE8.zip : CSC, Phone, and PDA along with the 512 pit. I also checked repartition. My first attempt failed in Odin as it was stuck on the repartition step. I rebooted my phone, which gave me the pc! screen. No worries though, as Odin picked it up and I tried again with success. This time it booted and I had the mmcblk0 area back with data and internal sdcard.

I have never had any issues with any of morfic's kernels until I either, bravely or stupidly, however you want to look at it, flashed a ULF kernel. I am now once again running DoW v1.4 and loving it. My suggestion would to try again. It worked for me, and the way I found it was this in which another user, in this thread, fixed their phone with JE8. I suggest you give a try once again.

Oh yeah, and I did need a smoke after that, lol. But hey if helps someone, it was well worth it.
[Vibrant Android Development] Poser:
Note: I was not coming from stock voodoo, but from prior version of DOW

UPDATE: Confirmed download hash, adb pushed to phone and re-flashed. Boot is normal and will put phone through paces and report back.

UPDATE 2: Extremely responsive UI, and stability through standard benches (linpack, nenamark, neocore, quadrant).

@morfic, will v1.4 support fs conversion to JFS as well?
[Vibrant Android Development] jaetm83:
morfic,

First of all I really appreciate your hard work to bring out all the awesome kernels and other goodies!! I am posting definitely not to blame you on the problems I have had, but just to report what I ended up with and to hear your opinion on it, if you don't mind.

Here's what I've been through: Got stock in early January > rooted > flashed Nero 4 > Nero 5 > Bionix-V 1 > Bionix-V 1.2.1 > Eugene's Dead Horse vibrant-1 > Bionix-V 1.2.1: phone refused to boot, stuck at Vibrant boot image > JFD > Bionix-V 1.2.1 > DoW14fow-i9000: **noticed when phone is plugged to PC it mounts CD-ROM + 2 removable devices > JFD > JI6 > Bionix-V 1.2.1: CD-ROM still mounts > Eugene's JK2 2e+SD Fix > JFD > JI6 > Bionix-V 1.2.1: still no changes > JFD > Official KA6 using Mini Kies: mounting issue not fixed yet > ODIN'ed KA6 Stock+Voodoo: to gain root/CWM, I didn't know the modified 3e > Bionix-V 1: seen someone saying with Official KA6 going back to JFD would cause trouble because of new SBL, I thought the sbl.bin included in Bionix-V 1 package would remedy this > JFD > Bionix-V 1.2.1: not fixed yet > sombionix's vold fixes (both i9000 and vibrant versions): only changes the order they mount > Eugene's Froyo That Doesn't Brick > JFD > JI6 > Bionix-V 1.2.1 > DoW14-T959-HD: I love Voodoo Sound!

I checked sys/devices/platform/s3c-usbgadget/gadget/ folder at this point and confirmed the kernel still creates lun2 folder although it's not referenced in vold files, and CD-ROM still mounts to PC.

OMG, now all at a sudden, one of my hardware touch-sensitive button, the search button, failed to lit up. 3 other buttons lit up as usual but not the search button. I didn't have BLN control app at the time, so I downloaded it to see if there are any setting I can tweak to make things work properly. I had no luck, the light's gone. Fortunately T-Mo rep agreed to replace my phone, and it should be arriving by mail this week. I reverted back to JI6 to send the phone back.

Do you know by any chance if there's a way to completely clear out system partition so that no remains from the previous kernels are left out. The thing I haven't tried so far is the fix linked in OP. I won't flash it as I will be sending this back to T-Mo soon, but just wanted to find out if there really is a way to achieve a real "clean" flash for future reference.

Also do you think the system incompatibility between Dark Horse and DoW could somehow make some internals fried and make the light go out? I never dropped the phone, it's in my TPU case at all times, so it's quite odd to see a hardware failure after having the phone only for about a month and a half all the while all other things still work just fine. Even both of my SD cards never failed to mount to PC or to Phone all the way through my long journey. Only other problem I have had is the mounting issue which didn't really affect functionality of the phone at all.

Thanks so much for reading and replying in advance. I love your work and all the awesomeness TeamWhiskey brings us!
[Vibrant Android Development] tuffCookie:
morfic, thanks for all your hard work.

i flashed the v1.4 kernel without any issues. phone is super responsive and just sprints through all benchmarks. haven't experienced any sort of lag, reboots or wifi and/or data issues.

in regards to HD (1280 x 720) video recording, i'm only able to record 1-2 seconds and then i get a recording failed error followed with a camera failed error.
[Vibrant Android Development] a4 moda:
First of all, Thank you.

I flashed the JE8 Rom/Kernel/Modem/PDA/Phone - I flashed it 4 times already since you posted.

I checked Re-partition, I didn't check it,

Result is the same.

Vibrant screen, then phone shuts off. Nothing happens. I can't get into recovery, but I can get into download mode.

So, there's no change from what was happening before.

On another note. I've never used a ULF on this phone. It's always been TW roms + Voodoo. That's it.

A smoke? I smoked a whole pack in one night when I found out about my expensive paperweight 6 days ago!!!

Any other ideas?

Thanks again.

** okay, backtrack.

here's what I've tried so far.

I'm trying to adb push a sdparted.txt file, onto Sbin so that it can give the phone the command to convert the entire partition to ext 4.

Eugene's OLD Froyo Rom- ADB Connects, but NO ROOT access

Eugene's NEW Froyo Rom- ADB does not connect, no Root access

Darky's I9000 Resurrection ROM- ADB connects, but no Root access

Eugene's New Froyo ROM + Supercurio's Voodoo kernels - adb does not connect, No root access

JI5, Ji6, JFD- all shut down on me. I boot and get the "vibrant" screen. Then the phone shuts off. No ADB, No root, no NOTHING.

Thanks
[Vibrant Android Development] vnamee:
Just flashed 1.4. Still getting same stability, benchmarks at 1.4 ghz. HD recording tested for 30 sec. Recording and playback working. Will check out battery life tomorrow (unless there's another update).
[Vibrant Android Development] atlaswingpasaway:
Just flashed this over bionix 1.2.1 with stock+voodoo WHICH was flashed from stock JFD.

mine crashes on 1.4GHz with neocore benchmark. gallery is fine. psx4droid and fpse are ****ty, wont even start. kind of faster. but i cant reboot.

this kernel has performed better so far coz i was able to do my everyday stuff @ 1.4Ghz. but when i do intensive apps, or do a reboot, i cant take it.

will test something else for now.

EDIT:

reboots on 1Ghz is fine. just the 1.4Ghz that has a bit more problems. works great otherwise

(conservative)
[Vibrant Android Development] Smartassassin:
Morfic, just flashed new 1.4. So far all is running well. Will report any issues. Back with the old HD version I had a strange reoccurance. Always in red recovery I would freeze at some point. As soon as I held the vol up down would refresh the red recovery. I would be golden after that....my battery drain seems a bit much...im thinking it might be theme related...scarlet leftovers...will be flashing trigger again and seeing if that is what is causing potential prob/drain.....
[Vibrant Android Development] PowSniffer0110:
Can someone please post a market apk the one in bionix 1.2.1 like I said for some reason my market is just gone and have got no help. Appreciate ANYONES help. THANKS!
[Vibrant Android Development] SnowHydra:
​

http://db.tt/q6HlZFc

http://db.tt/0PnPULh

Here you go, push the two to system/app, might work. From Bionix 1.2.1
[Vibrant Android Development] FRIEDjellyWALNUT:
The 344 mb test kernel kills the sleep tracking feature in Sleep As An Droid. It seems to work when you first activate it, but it randomly dies during the night. I've missed class two days in a row now lol.

And also account syncing (Gmail, Twitter, Facebook, etc.) seems to work very oddly, sometimes it works and sometimes it doesn't.
[Vibrant Android Development] Poser:
definitely some anomalous behavior:

- shortcuts disappear (but still respond when blank area is touched)

- force closes on SNS apps and MMS sometimes

- data corruption (lost sms... but had backed with Ti)

Perhaps another bad flash...

system is blazing though. Did not have these problems on DOW14 t959 HD
[Vibrant Android Development] scrizz:
Why do you need me?

You need me to call people idiots?

Want me to call people out for their lack of reading comprehension?

I am everywhere.

I just don't get how so many people can have these problems.

@Morfique/Morfic:

Thanks for your work!

:D
[Vibrant Android Development] z3NN9:
Wow guys, stop derailing this thread.

Everyone here knows well enough if you brick your phone its only your problem.

Most of us have flashed DoW, dragon, and other voodoo kernels before on our devices without issue. Myself included and I havent had any problems whatsoever.

Theres a possible solution for you who care to try in the OP but its certainly not anyones obligation to fix something you broke.

Sorry for the rant but I'm sick of the same people complaining over and over.
[Vibrant Android Development] compuguy1088:
Actually, I'm having the same exact issue. It still occurs with the new 1.4 kernel as well. I didn't initally bring this up, because I thought it was related to me previously using the dead horse kernel...
[Vibrant Android Development] PowSniffer0110:
Not bad flash. I had market and all 16,000 of my sms' erased.. unluckily I hadnt backed them up for over a month so.. whatever. Got my market working again by pushing into system but none of my themeing is working on the market. and the market crashes sometimes
[Vibrant Android Development] jkhrist:
Anyone else losing data connection when sending or receiving sms messages I have to toggle airplane mode every time
[Vibrant Android Development] muchelaguito:
I have a small issue, more like an annoyance:

When I enable WiFi, sometimes it disables by itself before even connecting to the AP. A second attempt connects without issues, and very rarely a third attempt. Nothing serious, I can live with it.

Other than that, it's working wonderful.

Forgot to mention: I'm using V 1.4, released the 21th.
[Vibrant Android Development] morfic:
still included in v1.1, link in OP
[Vibrant Android Development] morfic:
any such widget, terminal, sl4a scripts, anything that can write to /sys
[Vibrant Android Development] cashyftw:
Just trying to understand,

we have a jfs, and a voodoo version?
[Vibrant Android Development] ceoesquad:
Ok just flashed and everything seems to be snappy I no u said it has bln but it does not support bln pro with the blinking it says it need 2.3 or something idk what that is bit I love this its better than the dragon kernal but I just want the bln pro to work any ideas on what that could be
[Vibrant Android Development] hanbaoquan15:
Hi Morfic

I just tested with the Car's AUX, the audio works fine but there's still a problem with the mic, the other end cannot hear me.

Also, is the phone runs at 1Ghz default? Because I had to use an overclock widget to make it runs at 1.4Ghz.

Thanks Morfic
[Vibrant Android Development] Corvette Dave:
Been 30 minutes and still stuck. I tried to go into recovery and get the splash screen again. stuck....
[Vibrant Android Development] Settai:
OP says it runs at 1Ghz on boot
[Vibrant Android Development] eunkipark92:
Keep clicking power button and volume up and down fast I stead of holding it till u get into recovery. Just keep doing it.

For aomereason the vibrant doesn't blink anymore and its harder to go into recovery now..

axura 2.3.0 with adw launcher ex
[Vibrant Android Development] hanbaoquan15:
Thanks, I must have missed that.
[Vibrant Android Development] Corvette Dave:
I give up!

Going to Odin
[Vibrant Android Development] junxracr:
Flashed jfs zip booted and kept getting force close of setup wizard. Could not mount cache or open rec/log in recovery file exist. Went back to dead horse jfs advanced, and now my phone boots with DoW audio lol.

For now Thx for the great audio morfic. I might convert to rfs and try this later ;-)
[Vibrant Android Development] cashyftw:
Same here, got force closes.
[Vibrant Android Development] Zeltex:
Hmm...my wifi stopped working after I flashed this :(
[Vibrant Android Development] PJcastaldo:
Any one have any ideas why this kernel has never booted for me? 1.3 dow worked great, i originally figured it was because this one was set to 1.4 default, but now with booting at 1g it still freezes right away.. hmm
[Vibrant Android Development] Pancake345:
This worked great for me after a couple of reboots.

Sent using high-tech smoke signals
[Vibrant Android Development] es7241:
How's this battery life, I see it says normal battery life I find that hard to believe but if its true then im going to flash this right away
[Vibrant Android Development] Settai:
Downloaded on Trigger v2.1 and everything is working great, been running for about 3 hours. Using setCPU to OC to 1.4Ghz on conservative and no lock ups yet.
[Vibrant Android Development] }{Alienz}{:
Morfic, do you have colorfix in there?
[Vibrant Android Development] d33dvb:
In case the OP thinks the sound issue is fixed, it isnt, it still will not route to headphones without a mic inline. The op to test needs a REGULAR pair of headphones or speakers or cassette adapter to test. A regular headset that came with it will seem fine.
[Vibrant Android Development] :
So if I use the head phones the phone comes with can hear?
[Vibrant Android Development] december.underground:
I would have to agree some people just don't take the time to read the op and take time to understand it, especially considering the fact that this could brick a phone if not done properly. The old saying goes measure twice cut once LOL so read the op over and over again till you understand it and it should save you some heart ache.

+1 morfic great work.

0bey <-_->
[Vibrant Android Development] takato23:
i have sleep issue. I don't know why.. the first day i've installed this i got it working in 1.4ghz without problem. Yesterday i have the sleep issue so i take it back to 1 ghz. The problem wasn't fixed so I reinstalled froyo>bionix> this kernel.. but it keeps happening
[Vibrant Android Development] ajjus:
I have these exact same issues. Not complaining in anyways. Just here to troubleshoot if you guys need any help. I have these additional issues...

-Sleep of death even without using profiles in setcpu. (I unstalled setcpu now)

-No cellular Signal. Need to power off, remove battery and Power on to make it work again.

-Interminably wifi disconnects.

-Sudden battery drain.

ROM : TM Bionix V1.2.1
[Vibrant Android Development] I7oobie:
16,000 SMS? Holy Sh*t! :eek::eek::eek:

You know that takes up memory, correct?
[Vibrant Android Development] jrafael:
So far the lastest kernel its running great in my phone, downloaded right from xda app, and flashed from voodo recovery on top of of old dow 1.1.1

tested phone, sms, hd camera, working great, no fc, no sleep of dead.

Fyi: I'm using setcpu to oc up to 1.4

No profiles, just 200~1400, with scaling set to: on demand.

Sent from my SGH-T959 running bionix 1.2.1+ka6 modem+dow 1.4 oc
[Vibrant Android Development] jkhrist:
I had the same thing happen, but luckily I had a titanium backup from the day b4. My main issue is sms anytime I send an sms I get data connection disconnects and have to toggle airplane mode on and off. Changed from axura2.3.1 to trigger 2.6 and same thing happens. Any suggestions. This is the 3rd post I have made addressing this issue can I get some feedback please?
[Vibrant Android Development] smashpunks:
How do I get to the red voodoo recovery.... Never done it before lol. Is it in sgs kernal flasher?. Thanks

Edit: I used the app to flash, all is well... Great so far...

Still, what's the red recovery?

Holy crap v1.4 set at 1.4ghz is cruising.....
[Vibrant Android Development] xtone:
that's the voodoo recovery.

seeing as you installed this kernel, you can access through:

1. using 'adb reboot recovery'

2. 3 button combo

3. use the powermenu - well i dunno what rom you're running most have it
[Vibrant Android Development] jrafael:
From Rom manager reboot to cwm recovery (green letters) select advance then reboot recovery

:-)

Sent from my SGH-T959 running bionix 1.2.1+ka6 modem+dow 1.4 oc
[Vibrant Android Development] vnamee:
Still having the same wifi issues. I have to toggle it a 2-3 times for it to connect. Also, I do believe my alarm did not ring this morning either, but I wasn't exactly clear-headed. Also, nandroid doesn't work either as others have posted. It hangs on /data. Other than that, battery life seems decent. Battery is 50% after 8 hours of constant emailing and wifi. It works great otherwise.
[Vibrant Android Development] TR88:
Hey I'm coming from HD v1.1 right now, can I just flash over v1.4 or should I flash the stock voodoo kernel first?
[Vibrant Android Development] cezzarmicu:
possible bug?

Guys,

I have tried the new 344mb kernel yesterday and speeds were great. I got 1600+ on quadrant easily (no overclocking)

But after a reboot, I noticed that all the texts on the screen were like shivering/wiggly. I then rebooted two more times to check if it was just a fluke but the wiggling was still there. It was clearly visible from the status bar to the home screen. So I decided to revert back to kb1+voodoo and everything went fine again.

Anyone else had this experience before?

Btw, i am running trigger 2.1.1 if that helps
[Vibrant Android Development] BuLLeT_PrOOf_wAlleTz:
No its cuz when morfic made a comment about eugenes kernel.

Ur eugene's lackey so they were expecting u to defend eugene again
[Vibrant Android Development] kaizasoshi:
how is battery life for those of you who are clocked at 1.4?
[Vibrant Android Development] The_Chrome_Coyote:
Battery could be better but I still get through a day of moderate usage. So far I've only had the phone freeze twice, but both times led to data corruption. First with tapatalk app, then with kik and sms data.

Otherwise the OC works great and is the first froyo OC I've been able to run. I could OC like a fiend on the eclair kernels, but never on froyo until this one
[Vibrant Android Development] skyhigh2004:
Yeah last night I was trying to flash a rom and when I went to do a factory reset and then later the rom flash and it kept hanging at data. After awhile of looking I noticed in advanced in clockwork my data partition was un mounted. Re mounted and all problems seem to go away. Dont know if anybody else has experienced this but worked for me. Dow 1.1 and edt 2.2.1 beta 2.
[Vibrant Android Development] bartek25:
flashed and after i cant even get in to recovery ...nawh thanks , soft brick .
[Vibrant Android Development] The_Chrome_Coyote:
Err. Nm, v 1.1.1 doesn't work for me, get constant sleep of deaths. But 1.1 works fine besides the data corruption when it freezes
[Vibrant Android Development] smashpunks:
Been running 1.4 @ 1.4ghz all day on bionix v 1.2.1. only wierd deal is the wifi just like others posted, but that's not too big of a deal for me..

Battery is good too...
[Vibrant Android Development] nelson0140:
When I reboot sometimes the bln app gets turned off and voodoo control volume resets anyone know why?
[Vibrant Android Development] morfic:
I read this at lunch, and was glad others can do the math too :)

Thanks.

The 1550 is exact, the HDs don't go as high, not sure how much is due to FUD scaring people off and how much is due to the various versions this early in the process.

I Do wish i had done a thread for t959 source based onw :) but DoW is DoW, so it stayed on here :)
[Vibrant Android Development] morfic:
That is i think why people brick. (I mean the unawareness that it is there)

You don't always need it, but when you need it and don't know it's there, people get in trouble.

The recovery specifically built by supercurio for voodoo with a voodoo submenu and included in most kernels supporting voodoo. (basically supporting ext4 aside from the disable/enable options)
[Vibrant Android Development] cezzarmicu:
hi morfic,

sorry to bump my post, but could you please look into it? it might just be me experiencing this though. thanks
[Vibrant Android Development] xtone:
turn screen off and on. dont reboot just lock and unlock. that should fix it
[Vibrant Android Development] cezzarmicu:
Thanks for the response but I did that too and it did not fix the issue. Maybe my phone can't handle OC'd kernels (even if i don't OC them?)
[Vibrant Android Development] smashpunks:
I'm not having the issue on bionix 1.2.1 running at 1.4 ghz version 1.5.
[Vibrant Android Development] cezzarmicu:
i guess it's really my phone then. i also had this issue when i used the dragon kernel (again, not overclocked and not undervolted). i'm currently using sonique's kernel (also with voodoo and based on official ka6 release) and all seems to be fine (even after a reboot - crosses fingers :D)

+++

and yes, i flashed it in red recovery :)
[Vibrant Android Development] PowSniffer0110:
not too much.. actually