Any one know of anything else I can do with my fascinate. Running 1.1 Zinc with no kernel. My phone does not approve. Anything I'm missing out on?
zachsx said:
Any one know of anything else I can do with my fascinate. Running 1.1 Zinc with no kernel. My phone does not approve. Anything I'm missing out on?
Click to expand...
Click to collapse
I wouldn't approve of that, either!
Seriously, if you were able to flash a ROM, and you did it through Clockwork Recovery/ROM Manager, then you are running a modded kernel.
Voodoo seems to be causing some people more trouble than they feel it's worth, so I'd suggest one of jt1134's or Dirrk's non-Voodoo kernels, or Birdman's once it's past the testing stage.
Non-voodoo? I must have missed those. Search is not being my friend. Care to link a guy up? The only kernel threads I can find are their voodoo kernels.
Sent from my SCH-I500 using Tapatalk
PhoenixPath said:
Non-voodoo? I must have missed those. Search is not being my friend. Care to link a guy up? The only kernel threads I can find are their voodoo kernels.
Sent from my SCH-I500 using Tapatalk
Click to expand...
Click to collapse
swing by irc #samsung-fascinate on freenode.net. check topic for kernel links
My phone started lagging badly 3 days after the vodoo lagfix...how ironic. When I disabled it, it nearly bricked my phone. Desperate to get my phone up and running, I did a wipe. It killed the phone's internal memory. Had to reflash back to stock and since then my phone has been running really well w/o the lagfix even. Maybe my phone had a bad image like a computer. Not doing anything else to my phone til froyo comes out. I am rooted though.
Sent from my SCH-I500 using XDA App
You could try more cow bell. I heard it's the only cure for some fevers.
I've been semi-bricked three times when I've disabled Voodoo, and I did it right. So I use a non-voodoo kernel now. I'll wait until these bugs are ironed out. Join the irc chat and jt and the other devs commonly post kernel links.
Yup.. Using jt's 1031 test kernel now (novoodoo). Running beautifully.
Sent from my SCH-I500 using Tapatalk
Technically voodoo hasn't bricked a single phone. User error and then likely a small error in the proccess itself have caused some ugly problems but it can be overcame with a little work
Sent from my SCH-I500-Fascinate using XDA App
ksizzle9 said:
Technically voodoo hasn't bricked a single phone. User error and then likely a small error in the proccess itself have caused some ugly problems but it can be overcame with a little work
Sent from my SCH-I500-Fascinate using XDA App
Click to expand...
Click to collapse
I said semi-bricked. It wouldn't get past the boot screen. It couldn't have been user error two of those times, because I used reboot button to do it.
Kamar234 said:
You could try more cow bell. I heard it's the only cure for some fevers.
Click to expand...
Click to collapse
Thank you for this. Seriously though, I've been running jt's voodoo kernels since their release with only minor problems. I've disabled voodoo and flashed other kernels no less than three times without issue. Granted it does take a while to boot after enabling/disabling voodoo. The first few times I thought I screwed up, but it always boots for me.
Sent from my SCH-I500 using XDA App
Mean Bro Greene said:
Thank you for this. Seriously though, I've been running jt's voodoo kernels since their release with only minor problems. I've disabled voodoo and flashed other kernels no less than three times without issue. Granted it does take a while to boot after enabling/disabling voodoo. The first few times I thought I screwed up, but it always boots for me.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I think it's a phone to phone thing. Some people have no problems just turning off voodoo when they flash ROMs and kernels. I have to use adrynalyn's voodoo uninstaller and wipe completely if I want to change ROMs or kernels.
Weird.
Yea when I tried to turn voodoo off it took 4 reboots before it took. No issues after that though.
*EDIT* Posted in wrong thread...my apologies
Used the "reboot button" app to disable Voodoo. It hung on "Samsung" for over an hour after robot women said "operation completed" or whatever. i finally admitted defeat and did a battery pull. Restart resulted in a boot loop. I was able to recover following the "remove Voodoo" thread and flashing the stock Nandroid. From there I flashed jt's v.4 Super Clean ROM with Frost's theme. Having had the stones to try Voodoo again but honestly my phone is running good with just the Super Clean ROM. Having a recent Titanium backup really helped get my phone back in order quickly.
While it was an unpleasant experience it ended well and resulted in a nice clean and fast Fascinate. Best part though is that I'm no longer afraid to flash my phone since I now know I can recover fairly quickly.
Martian21
martian21 said:
Best part though is that I'm no longer afraid to flash my phone since I now know I can recover fairly quickly.
Martian21
Click to expand...
Click to collapse
...that way lie the dragons...
Yeah, that's pretty much what destroyed any hope I had of *not* being a total ROM-a-holic. I have owned this thing for no more than 2 weeks and have pushed over a dozen different roms/kernels on it.
I cannot even imagine what this poor phone will be going through once we start getting things like Cyanogen's up and running.
(currently using jt's 1031 USCC non-voodoo kernel...at least until I get home.)
Related
I rooted the MT3G with ease. And the flashing of Roms and stuff is easy for Mt3g. But it seems hard for the Vibrant. I don't use abd or anything cause frankly. I don't know how. Can you guys maybe give me suggestions?
Sent from my SGH-T959 using XDA App
Read, understand, experiment. Ppl only get their troubles or "panic" because they dont have anything setup & dont know how to get them selves out it. If you dont want to learn our try to use the tools that are available then just wait till the one-click ROMS or CM comes out.
If you want to take the time to learn then I would suggest to head over to the vibrant "bible".
Easiest way is just to down load one click lag fix from market there is a root option there. Or it really was easy this oas my first android phone. Download the update filter put it in the internal sd and rebooted using hold vol + vol- and power. And installed from there no problem.
Just check out the stickied thread about vibrant tips and tricks
Sent from my Samsung Galaxy S using XDA App
There is also a "One Click Lag Fix" that you can download here, it takes like 20 seconds to root this phone, you shouldn't be scared
chris279m said:
I rooted the MT3G with ease. And the flashing of Roms and stuff is easy for Mt3g. But it seems hard for the Vibrant. I don't use abd or anything cause frankly. I don't know how. Can you guys maybe give me suggestions?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I wondered about rooting too at first, but as it turns out it's very easy. I've read several comments on how easy it is to root the Vibrant compared to Android phones back in the olden days.
And if you want to flash a neat ROM, go check out Bionix.
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=782027
w_bovine said:
I wondered about rooting too at first, but as it turns out it's very easy. I've read several comments on how easy it is to root the Vibrant compared to Android phones back in the olden days.
And if you want to flash a neat ROM, go check out Bionix.
http://ip208-100-42-21.static.xda-developers.com/showthread.php?t=782027
Click to expand...
Click to collapse
+1 on the Bionix!!
Master™ said:
+1 on the Bionix!!
Click to expand...
Click to collapse
I thought I saw you over there!
Im rooted with one click lag fix. Now i need to flash Rom without bricking. And i used the one click root & lag fix that was on the market.
Sent from my SGH-T959 using XDA App
chris279m said:
Im rooted with one click lag fix. Now i need to flash Rom without bricking. And i used the one click root & lag fix that was on the market.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I just got this phone 2 days ago (my first smartphone ever!) and I've flashed it probably 6 or 7 times now...
Important advice: Right now, once you've installed Clockwork ROM Manager, make a backup of your ROM! I really wish I'd done this, just a near-stock, untouched backup (yes every thread post starts with "make a backup!" but I was stupid)
Now for some encouragement: If I, with zero knowledge of Android/rooting/ROMs/build.prop files/Clockwork/adb/Odin before Sunday at 4 pm, managed to F with this phone as much as I have and not even come close to bricking it, you'll be *golden* just flashing it with a well-known ROM.
Flashing ROMs is super easy with Clockwork. It's like... 3 or 4 clicks easy.
Right now I'm running Bionix and really enjoying it. You might check it out while we all wait for Cyanogenmod to come out for Vibrant.
TL;DR: I've been pushing files, flashing broken ROMs, all sorts of fun stuff and my phone is still pluggin' away. I wouldn't worry too much about bricking. Just read the threads, search the Googles, and ask for help if you get really stuck. And backup.
Make sure you check out Eugene323's stuff as well. He puts out some incredible work.
chris279m said:
I rooted the MT3G with ease. And the flashing of Roms and stuff is easy for Mt3g. But it seems hard for the Vibrant. I don't use abd or anything cause frankly. I don't know how. Can you guys maybe give me suggestions?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I had more problems with my MT3G than I did with this phone. It took a day to root and rom the MT3G since I have the one with the head phone jack (stupid gold card crap).
Do what everyone has suggested. DL the One Click Lag Fix and touch the option to root. I'm running the Bionix 1.3 and it's good.
Just odined back to jfd, rooted and used oclf lagfix. Question is can I flash from this point or do I need to remove lagfix?
Sent from my SGH-T959 using XDA App
Remove lagfix.
Sent from my SGH-T959 using XDA App
Thanks a million. I thought so but needed to be sure. P.s. I'm about to flash my FIRST custom rom any pointers.
Sent from my SGH-T959 using XDA App
The two top dogs around here imo are bionex or axura. Each have their own pros and cons (barely cons). I'm personal to Axura myself, although im still on nero v5. Been getting tired of redoing my homescreens over and over again. I suggest going into the release threads, found in developmet forum, for the respective roms and taking a look at screen shots and youtube search video reviews.
You really cant go wrong either way. Check out the rom bible thread for more awesome roms.
I would defantly stick with the Auxura rom or Som's Bionex rom, Ive bounced between the two, Each rom has it's own feel, while Axura's roms are ultra fast, The Bionex rom has more Gingerbread feel and smoothness, Make your own decesion, but as the previous poster said you can't go wrong with either of them.
Just a word of advice, get in the habbit of disabling Voodoo each time you flash, I made the mistake once and ended up softbricking the phone and it was a nightmare for me getting it back to stock via ODIN.
Good Luck
Actually, if you already have voodoo installed and the rom you're flashing to also has it, you don't need to disable it. I speak from experience
Sent from my SGH-T959 using XDA App
notverycreative said:
Actually, if you already have voodoo installed and the rom you're flashing to also has it, you don't need to disable it. I speak from experience
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This is true, but new. It has only been that way for a little while. Also it ONLY is true if you are going from Voodoo 5 to Voodoo 5 (meaning the one that has the RED recovery).
notverycreative said:
Actually, if you already have voodoo installed and the rom you're flashing to also has it, you don't need to disable it. I speak from experience
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thought, OCLF was ext2 and Voodoo was Ext4 wouldnt that cause problems...
ZachLL88 said:
Thought, OCLF was ext2 and Voodoo was Ext4 wouldnt that cause problems...
Click to expand...
Click to collapse
Yes. Yes it would. Read the post right above yours where I said (emphasis added):
T313C0mun1s7 said:
This is true, but new. It has only been that way for a little while. Also it ONLY is true if you are going from Voodoo 5 to Voodoo 5 (meaning the one that has the RED recovery).
Click to expand...
Click to collapse
Hey guys. I haven't been on froyo in a LONGGG time.
Basically I flashed ics on my brothers phone because he here wanted it to look cool like mine lol.
Now after a few weeks he's getting like 2 hours on his battery. He's a heavy user.
I'm going to get him back onto froyo...
My question is which thread do I follow on instructions for froyo rom flashing I mean I remember the voodoo lag fix etc but I totally forgot how to enable etc.
Sent from my SGH-T959 using xda premium
Voodoo is enabled via recover if i remember.. just odin, root and flash rom and kernel.. then go into recov and turn on voodoo lol
Sent from a cell tower to the XDA server to you.
Yeah alot of roms will enable after flash, I believe you have to repartition in Odin too or you'll throw it into a softbrick. Like the previous post said if it does not enable then for into your voodoo setting in the recovery and change it there.
Sent from my GT-I9000 using XDA App
IIRC once you enable the lagfix and Linda does her thing, you should end up with 4 massive files on your internal called system/...Lzo, data/...Lzo or something like that (you'll know exactly what I am talking about when you see them), these can be deleted as Supercurio said they aren't needed. It is just what happens when the lagfix is engaged.
Thanks guys, but the lagfix wasn't like.. you know my only question.
I was trying to ask how i would go about Flashing the ROM.
Does this seem like a good method?
ODIN to stock
Flash any Froyo ROM without doing anything else
Enable voodoo if it already isnt enabled
isn't that like the basic thing i have to do? did i miss anything?
again thanks guys.
My bad. Yep just like you said. Maybe take care to make sure froyo bootloader but I guess if you Odin then that part is out of the equation.
Woodrube said:
My bad. Yep just like you said. Maybe take care to make sure froyo bootloader but I guess if you Odin then that part is out of the equation.
Click to expand...
Click to collapse
Yeah my brothers on Passion V5 or something haha he doesn't like updating so often, so i've given up and im just going to put him on Froyo.
Thanks wood.
-limited to 8 thanks per day-
I cant pinpoint at all whats going on. I get at least 5 screens of death each day. I full wipe and everything before I flash a rom on my phone. I'm currently on Turkbey v7. Someone please help me out
Return to stock, if it happens still probably best to return it if you can.
LiLChris06 said:
Return to stock, if it happens still probably best to return it if you can.
Click to expand...
Click to collapse
oh no... i just got a replacement a few weeks ago..
Did you mess with clocks/voltage at one point? There may be an init.d script or some other kernel settings leftover from those that you gotta get rid of. Flashing back to stock should fix that if I'm not mistaken.
Can you still return your replacement?
afrojoc said:
oh no... i just got a replacement a few weeks ago..
Click to expand...
Click to collapse
that jus tmeans you'll need another
Did you clean out the kernal settings between ROMs/Kernals?
No I didn't mess with any overclock or voltage settings.
I can still get another replacement phone until a year has passed since this phone has been released since thats when I got the first phone.
And tomorrow I'll try flashing back to stock and then flashing a rom afterwards. I have to study for my summer class tonight.
Thanks alot everybody!
afrojoc said:
oh no... i just got a replacement a few weeks ago..
Click to expand...
Click to collapse
well replacements are usually refurbished, if im not mistaken. Theres probably a higher chance that something is wrong with a refurbished phone over a brand new phone. So maybe not that unexpected that something will go wrong, especially with custom software
I would try running the kernel cleaning script and flashing a new kernel. I known NEAK didn't like me and locked up several times a day. But its so darn fast....just giving an example. What kernel r u running now?
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
I would try running the kernel cleaning script and flashing a new kernel. I known NEAK didn't like me and locked up several times a day. But its so darn fast....just giving an example. What kernel r u running now?
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
NEAK...
NEAK is working great here with UCLD4. I used to have tons of SoDs with LD3 on the stock kernel, just about every time I turned the phone off it would SoD within a couple minutes.
So because I felt too lazy to go to stock, I found the kernel cleaning script and wiped everything off my phone and flashed the script. Then I reflashed the Turkbey rom since I just like it and so far I haven't gotten any SODs as of yet.
afrojoc said:
So because I felt too lazy to go to stock, I found the kernel cleaning script and wiped everything off my phone and flashed the script. Then I reflashed the Turkbey rom since I just like it and so far I haven't gotten any SODs as of yet.
Click to expand...
Click to collapse
Yayz! If I wasn't such a fanboy of AOKP I'd try it. I just totally fell in love with this ROM. maybe one day....glad things are working for ya.
Sent from my SGH-I777 using xda premium
Phalanx7621 said:
Yayz! If I wasn't such a fanboy of AOKP I'd try it. I just totally fell in love with this ROM. maybe one day....glad things are working for ya.
Sent from my SGH-I777 using xda premium
Click to expand...
Click to collapse
Its not bad. Im mostly on it cause i thought i got the least amount of SODs on here hehe. Its my safe zone to be at.
But anyway thanks for your help and everyone else who spent time and effort to help me solve this stupid problem! I love this forum..
Voltage
Min volts may be set too low. Bring first step up to 200. Allot of times its too much deep sleep.
Rooted, Unlocked, running Beans 18 w/Faux Kernel. Recently my Note 2 has been turning off randomly and won't turn back on unless you pull the battery first. I haven't made any voltage changes and don't have any Verizon software installed. I have seen in other forums that people say it is a hardware issue. However, I never had any issues in the months of ownership until I started installing custom Roms. The Screen of Death (SOD) is becoming an issue across different phones so I am wondering what the common denominator could be. Something in Android? Can't be a hardware issue due to the variety of people using different phones, different roms. Suggestions? Done the factory reset, fix permissions, re-install Beans, different kernels...
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Which version of Faux were you running? V4 I believe had problems with lockups.
Lodingi said:
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
I've tried MeanBean but I am sort of a crack flasher so I didn't stay on it long enough to know. I always clean install everything to avoid problems. I'd really hate to think it could be the Beans. It's been very reliable. Then again...I never had this problem before either...
RemnantKing2 said:
Which version of Faux were you running? V4 I believe had problems with lockups.
Click to expand...
Click to collapse
I am running V3. I believe that is the one that Bean's has an an option. But it happened using Pegasus too. There is no rhyme or reason either. It could just be sitting there and I go to use it and find it off. Which sucks for obvious reasons...
S0UTHPAWK1LLA said:
I am running V3. I believe that is the one that Bean's has an an option. But it happened using Pegasus too. There is no rhyme or reason either. It could just be sitting there and I go to use it and find it off. Which sucks for obvious reasons...
Click to expand...
Click to collapse
Have you tried reverting back to stock and seeing if it persists? And if does can you send it back through warranty?
RemnantKing2 said:
Have you tried reverting back to stock and seeing if it persists? And if does can you send it back through warranty?
Click to expand...
Click to collapse
Man..what a drag..but no, I haven't gone stock yet. I guess it makes sense to go ahead and go stock and maybe even un-root to see if it helps. I definitely can take it back with the BB extended warranty. What gets me is that as you start researching this random turn off issue, you start to see a pattern with more and more sites registering more and more complaints. I get the sneaking suspicion that Samsung knows something.. Possibly hardware issues with the Exynos chipsets. Pure conspiracy theory fodder naturally...Thank you for your suggestions...
Lodingi said:
I did have issues with Beans. My screen would lock up and require a battery pull. I have not had these problems with Clean ROM & MeanBean.
Have you tried another rom?
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
It's not an issue with Beans. I've had beans on my phone since it was an S3. I've run every build from 3 on this up until now. As daily drivers. So don't imply Beans' ROM gives BSODs.
It's your kernel. The first thing you need to do before you do ANYTHING else is wipe dalvik/cache and flash a new kernel. Dirty flash the ROM again to get aroma. Pick anything other than what you did (faux) and see if you can reproduce. If you can't? There you go.
First step to troubleshooting.
P.S. faux released v5 and I haven't had one lockup. I got them hourly with v4.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
It's not an issue with Beans. I've had beans on my phone since it was an S3. I've run every build from 3 on this up until now. As daily drivers. So don't imply Beans' ROM gives BSODs.
It's your kernel. The first thing you need to do before you do ANYTHING else is wipe dalvik/cache and flash a new kernel. Dirty flash the ROM again to get aroma. Pick anything other than what you did (faux) and see if you can reproduce. If you can't? There you go.
First step to troubleshooting.
P.S. faux released v5 and I haven't had one lockup. I got them hourly with v4.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yeah..yesterday I flashed Faux v5. It was wonderfully smooth, but I did have one BSOD requiring a battery pull. As of this morning, I am going stock, rooted, unlocked to see what happens. I loved Beans and I don't mean to imply anything about the rom.
S0UTHPAWK1LLA said:
Yeah..yesterday I flashed Faux v5. It was wonderfully smooth, but I did have one BSOD requiring a battery pull. As of this morning, I am going stock, rooted, unlocked to see what happens. I loved Beans and I don't mean to imply anything about the rom.
Click to expand...
Click to collapse
Try stock or PB&J kernel with Beans. Bet you'll be good.
Sent from my SCH-I605 using Tapatalk 4 Beta
1ManWolfePack said:
Try stock or PB&J kernel with Beans. Bet you'll be good.
Sent from my SCH-I605 using Tapatalk 4 Beta
Click to expand...
Click to collapse
I went stock rom and stock kernel. I am really crossing my fingers hoping not to pick up my phone and find a black screen looking at me. I love being rooted and unlocked so worse case is I set the phone back and have it replaced. Thank God for the BB extended warranty at this point cause I don't have to deal with Verizon on the replacement. Samsung should come clean though...I feel like they are holding out on us about this.
S0UTHPAWK1LLA said:
I went stock rom and stock kernel. I am really crossing my fingers hoping not to pick up my phone and find a black screen looking at me. I love being rooted and unlocked so worse case is I set the phone back and have it replaced. Thank God for the BB extended warranty at this point cause I don't have to deal with Verizon on the replacement. Samsung should come clean though...I feel like they are holding out on us about this.
Click to expand...
Click to collapse
I don't, I have seen a few incidents with this but not enough to call foul on Sammy's part. 9 times out of 10 it is the users fault for doing something they shouldn't, and most of these complaints you have found are from the same people with the same screenames on different websites.
There will always be a few phones with issues because nothing is perfect, just because you may have gotten a faulty phone doesn't mean Samsung is sending out defective products. If we were in the Nexus forums with all the **** that went down there I would agree but we aren't. Nothing is perfect.
Sent from my SCH-I605 using XDA Premium HD app
Well...I went a whole day on stock without an issue. Not that that means anything, but that my note 2 may be finicky about custom roms. I have always done clean installs and don't mess with voltage on kernels. I am gonna try Beans again to see if I can figure out what I enabled that could've caused my black screen of death. The only thing that I can say for sure that I know was on was Bluetooth each time. Thank you all for your help. It is what makes XDA the go to site.