Update: I figured out the issue
So, I had my device rooted and attempted to install the Voodoo lagfix. I had the SRE 1.3, but I didn't apply the one click lag fix. From what I found, there shouldn't be any problem applying the voodoo lagfix over the SRE kernel. Anyways, to be sure, I reflashed my kernel back to the stock JH7, and used the update.zip method. I got the robot voice telling me it was done, but it stayed on the ATT startup screen for, well, EVER. It never booted up past that point. Worried I had done something wrong, I reflashed, and ran the remove lagfix thing as there was a voodoo folder created. I tried it again and I got the same thing.
Again, I removed the lagfix, reflashed, and tried again, but this time, I fell asleep (for 8 hours or so...) and it was still at the ATT boot screen.
Am I doing something wrong?
Note: I do have my device overclocked (as included with the SRE build I used). Would that matter?
Thanks!
Looks like the overclocking wasn't compatible. This thread can be closed/deleted. Thanks
Hey folks, so here's a basic summary of what I've done up to now...
Rooted... have Rom Manager, etc...
Flashed JH7 OTA with Clockwork. Worked nicely. Set some things up, happy at this stage so I made a backup.
Decided to try Cognition, was 2.1.4. Had some trouble with a few things.
Disabled lagfix, simple enough.
Flashed to a backup made when I was on regular JH7.
So to the question... when I go to About in Settings, my Kernel still says
[email protected] #Voodoo_lagfix_3.0_v1.9.
Shouldn't the Kernel have converted back when I restored/flashed my backup?
Clockwork won't reflash your kernel (unless it's a package with included kernel) however the voodoo kernel you currently have on your phone operates the same as a stock kernel until you remove the disable-lagfix folder. Cognition 2.1.4 does utilize that version of the kernel to enable init.d scripts for things like MobileAP to function
You just have all the answers don't ya?
Thanks again, really appreciate it.
maximus-dev said:
You just have all the answers don't ya?
Thanks again, really appreciate it.
Click to expand...
Click to collapse
Haha I do my best to stay informed around here
Hi peeps, sorry if this is a repeat or nooob thread.
Here's how it went:
I flashed JM8, then to JP6 Froyo, then I rooted using CFroot, then I apply Voodoo 5.
All is well until I apply Voodoo. The market was lost and my quadrant is about 1540 but still kinda laggy.
So, I reflashed everything once again.
I "disable_lagfix" on Voodoo and went through JM8, JP6, CFroot again.
After completion, I deleted the disable_lagfix file.
I played with the phone the whole day and thought I had Voodoo enabled. But my quadrant is only 977 now.
So, do I have to Odin flash Voodoo again? I want Voodoo but I don't want it if it clears up my settings and apps. Yeah I can restore them but it takes super long time and I don't want that.
Suggestions please.
Thanks to mods for moving it here.
SO, earlier today Supercurio put together something special for those of us in Canada on the i896- a stock Rogers Froyo kernel with voodoo injected into it. Following logic, those of us on the stock Rogers Froyo should be able to have our cake and eat it too: a kernel modified especially from Froyo, intended for the Captivate, with voodoo lagfix but without the need to reflash an i9000modem or kernel. Here are the files:
Kernel: stock Rogers Froyo i896 w/ voodoo injection
Modem: Stock Rogers I896 UXJL1 Modem
Before trying a flash, I unlagfixed and backed up via Titanium Backup.
First I tried the kernel flash. I knew it wouldn't work with the modem, but I flashed it first to make sure there were no issues.
Rebooted into recovery- RED SCREEN
I did not enable the lagfix at this point. Just a straight reboot.
Regular boot screen; Rogers logo; Samsung Splash screen- then everything goes black. The home key buttons will light up and never go out if pressed. The phone stays like this until I pull the battery(I waited 25 min before I gave up).
I have tried various configurations regarding flash order(kernel/modem), I have repartitioned the card, factory reset before starting, everything I can think of, but this kernel won't boot past the splash screen.
However, when I revert to SpeedMod kernel(k13c) everything goes back to normal.
I would have thought I could flash this stock kernel over the i-9000 based kernel with the lagfix on both without issue, clearly I am wrong.
Can anyone see anything in my process that is inherently wrong, or even better would some other brave soul with stock Rogers Froyo be willing to try a flash? I wouldn't bother if this is your first crack at it though.
Thanks in advance to all who can help out.
So after wiping all caches and factory resetting, I get the following message at my Red Recovery screen:
E:Can't mount /dev/block/mmcblk1p2
(File Exists)
Is this important?
clemmie said:
So after wiping all caches and factory resetting, I get the following message at my Red Recovery screen:
E:Can't mount /dev/block/mmcblk1p2
(File Exists)
Is this important?
Click to expand...
Click to collapse
I get that all the time. No idea what the hell it is and have had to manually select my GSM bands when I flash a new rom or wipe dalvik cache since it started. Other then that no problems seem to be caused by it, for me.
Call off the dogs- after I installed the driver package that was included with Odin 1-Click I managed to get a master clear and a flash to the AT&T stock.
I must have spent 3 hours installing different driver packages today.
A shame it didnt work out smoothly. I'd be interested but am far too new to risk the troubleshooting..
Sent from my SAMSUNG-SGH-I896 using XDA App
Well, I have some very good news. This little kernel seems to be pretty special. After getting myself back to Rogers Froyo, I have done a few tests. I am getting very solid Linpack scores of 15-16 mflops and Quadrant Standard scores of 1400-1500. Using CPU benchmark, we have scores of about 725 ms @ 1000 hz and 700 ms @ 550 hz.
These scores are very solid and are about 20-25% improvement over stock Rogers Froyo Kernel.
This is promising as the kernel is a native Captivate kernel and could do a better job of servicing the many Froyo ROMs out there in terms of simplicity and stability.
The stock modem still needs more testing in terms of gps fixes and accuracy and data speeds.
I'll get back to you about those shortly.
If you have thought about staying on Rogers Froyo, this would be a good start for improvement.
clemmie said:
Well, I have some very good news. This little kernel seems to be pretty special. After getting myself back to Rogers Froyo, I have done a few tests. I am getting very solid Linpack scores of 15-16 mflops and Quadrant Standard scores of 1400-1500. Using CPU benchmark, we have scores of about 725 ms @ 1000 hz and 700 ms @ 550 hz.
These scores are very solid and are about 20-25% improvement over stock Rogers Froyo Kernel.
This is promising as the kernel is a native Captivate kernel and could do a better job of servicing the many Froyo ROMs out there in terms of simplicity and stability.
The stock modem still needs more testing in terms of gps fixes and accuracy and data speeds.
I'll get back to you about those shortly.
If you have thought about staying on Rogers Froyo, this would be a good start for improvement.
Click to expand...
Click to collapse
I would highly recommend this Kernel!! All the above benefits, plus fantastic battery life. The stock modem seems fine, although I've had better data transfer speeds and GPS locks from JL1 kernel, but this stock modem is perfectly fine.
Would love to see anyone else's results as well!
I like what I see so far. I am getting 1575 scores on quadrant (I know it doesn't mean much) but overall lag is gone.
I was a little freaked out this morning as the Rogers network was dead here this morning and I thought maybe I had done something with all this to kill cell / data. But everything cleared up after a few hours and I was back to normal.
Outcast, were you able to flash this custom Kernel without the issues that Clemmie came across? Much like phrenicthenub, I'd love to see the performance increase without the current bugs of custom ROMs, but I don't think I'm competent enough to troubleshoot if it all goes to hell.
As long as you disable any lagfixes and return any O/C or U/V kernels to normal you won't have these issues. Everything should work fine.
Sent from my SAMSUNG-SGH-I896 using XDA App
Did you guys do the 3e recovery fix first before being able to install CWM?
Hi guys... So i was trying to get SpeedMod to work with a i9000 modem like JK4, but my bluetooth is always noisy...
Right now, i have:
Latest SpeedMod kernel with LagFix enabled
JK4 Modem flashed.
What do i have to do to get this Rogers Supercirio's Voodoo kernel and modem ?
Thanks.
Elisha, I just took the plunge and got these flashed. Definately do the e3 recovery fix before setting up clockwork or anything else. That was the one part that gave me any trouble, but as soon as I got that sorted, everything went very well.
I'll try to pay attention to how things seem to perform and post my findings. Thanks for the encouragement again, Clemmie.
TheGrub said:
Hi guys... So i was trying to get SpeedMod to work with a i9000 modem like JK4, but my bluetooth is always noisy...
Right now, i have:
Latest SpeedMod kernel with LagFix enabled
JK4 Modem flashed.
What do i have to do to get this Rogers Supercirio's Voodoo kernel and modem ?
Thanks.
Click to expand...
Click to collapse
First you will need to boot into recovery and disable your lagfix. Back everything up with Titanium Backup. Download the files above to your root folder and reboot into recovery again. Using cwm, use the install zips option and flash both the kernel and the modem. Reboot yet again into recovery, clear your caches, then enable the new lagfix in your cwm options. It will take a while to convert your partitions from rfs to ext4, so be patient.
Sent from my SAMSUNG-SGH-I896 using XDA App
Thanks Clemmie,
I disabled LagFix from cwm and the speedmod kernel, rebooted, flashed modem with original JL1 modem, and then reflashed kernel with stock rogers froyo. backed everything up with Titanium backup. So i am currently back to stock, with a backup.
cwm is not in my recovery menu now, so if i use ODIN to flash the .tar version of supercurio's stock+voodoo kernel, does it contain cwm ?
ODIN with this kernel should work and then enable lagfix on first reboot by converting to ext4 right ?
Thanks alot, i am just starting with all this and want to make sure i understand everything before i take the plunge.
Thanks.
TheGrub said:
cwm is not in my recovery menu now, so if i use ODIN to flash the .tar version of supercurio's stock+voodoo kernel, does it contain cwm ?
Click to expand...
Click to collapse
Correct, it does.
TheGrub said:
ODIN with this kernel should work and then enable lagfix on first reboot by converting to ext4 right ?
Click to expand...
Click to collapse
Also correct.
Sent from my SAMSUNG-SGH-I896 using XDA App
Thanks ! i'll try that a little later... i'll let you know how it goes...
Well, so far, this Kernel seems to be the best thing to ever happen. I consistently get a score of 1501 in Quadrant standard (not from a fresh boot or anything, and running beautiful widgets and things, so I don't know if that makes a difference. I know with most benchmarks you're meant to close as much as possible, etc) and things just seem to be nice and smooth overall. On top of that, the battery life is, all of a sudden, seemingly PHENOMENAL! All whilst using the stock ROM. Either one of those benefits alone would have made the flash worth it. This is the way this thing should have run from the beginning.
I'll test out how well the GPS works, and try to pay attention to my signal strength with WIFI and calls and report back.
Thanks I figured as much as I had to do the 3e fix after I accidentally upgraded to the official Rogers Froyo the first day I got the phone.
Shroff said:
Elisha, I just took the plunge and got these flashed. Definately do the e3 recovery fix before setting up clockwork or anything else. That was the one part that gave me any trouble, but as soon as I got that sorted, everything went very well.
I'll try to pay attention to how things seem to perform and post my findings. Thanks for the encouragement again, Clemmie.
Click to expand...
Click to collapse
Ok, so i have used the tar version with ODIN3 v1.52 to flash stock+Voodoo-Froyo-I896-UXJL1. As i said, i was on stock kernel with stock JL1 modem.
Flash went great, took about 5 seconds, then rebooted. First reboot took about 7 or 8 minutes with a robot voice telling me the different steps it was in...
Everything workd without hickups... This kernel works realy well and speed is definitely there !
Thanks for the help guys...
I seem to have a recurring problem with my root on the FireFly 2.8 rom, though it may have been present on Serendipity and I never noticed.
My problem is this: Before I flashed FireFly, I used Odin to revert to stock 2.1, master cleared, and then rooted using the One Click Galaxy S root, which worked fine. I was able to flash the rom using CWM and Titanium Backup as well as other apps that require root said they had proper permissions.
At some point, I do not know where, I lost my root. Now, when I try to use Titanium Backup or Firefly fixes, the app tells me Root access FAILED.
I have superuser as well as the current busybox. Can anyone help me with possibly telling me how to enable my root or how to reroot if necessary?
I have tried z4root but it never does anything anymore.
And when I try to use the One Click Root again I can not click "reinstall packages" because I am taken to CWM instead of regular recovery.
Any help would be appreciated, thank you.
You probably converted system to ext4. Go back into Recovery and go to the features of whatever kernel u are using and reapply root.
Sent from my Captivate running Continuum 4.0 with Onix 2.0.5.
I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.
#1 in CWM "reinstall packages" is the 2nd option down! called "apply update.zip" (kinda makes sense doesnt it?)
#2 if you have CWM you can root without one click root.
boot to CWM recovery> Clockwork Features > root + install superuser
adv
Edit: Nevermind, looks like someone already solved your problem while I was typing my BS out.
skrallbro said:
I was neveraware you had to reroot after converting the system to EXT4. Worked like a charm though! Thanks for your help.
Click to expand...
Click to collapse
You don't normally have to....
I has this same problem with FireFly 2.8. I never had that issue with older versions of FF. But, as mentioned, if you reapply root in CWM, it works again.
I love the FF themes, and stability, but I may go back to FF 2.6. FF 2.7 had charging death for me, and FF 2.8 I have issues with keep the lights on. That's how I found my root issue. Now, with the root fixed, keep the lights on seems to disable itself after a while. Definately after every reboot it turns back off. I never had this issue before with cog, perception, or any of the earlier FFs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.
Elisha said:
Your rom probably came with a kernel that implemented lagfix upon first boot. It happens if you manually apply lagfix as well and re-rooting in CWM works like a charm all the time.
Click to expand...
Click to collapse
All the FireFly versions I have used have the lagfix optional, and applied through CWM, but 2.8 is the first one that applying the lagfix affected the root of the ROM. I also didn't have this issue with Cognition or Perception, both of which apply the lagfix on first boot.
So the kernel is the issue, not the ROM? A different kernel may fix this?
Sent from my SAMSUNG-SGH-I897 using XDA App
quarlow said:
So the kernel is the issue, not the ROM? A different kernel may fix this?
Click to expand...
Click to collapse
Yes and no. losing root from converting system to ext4 or back to rfs, can happen with any kernel, and for the charge death that was the onix kernel in those versions. The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.
i have never lost root converting my system
but i havent converted it in over a month. Just leave it EXT4 when i upgrade/change roms.
havent had any problems not converting it so i dont bother. (except going to stock)
but when i used to convert back and fourth every flash out of fear... NEVER LOST ROOT
I've only lost root converting on Continuum but never on FireFly or Apex so not sure if it is kernel or rom.
Sent from my GT-I9000
studacris said:
The keep the lights on, does that kernel have bln options in cwm? I use sp voodoo do idk.
Click to expand...
Click to collapse
Yes FF 2.8 has bln options in CWM. I have issues with bln active or disabled (in FF 2.8). I have not tried managing the bln with the app from the market, would that make a difference (vs managing bln in CWM)?
Sent from my SAMSUNG-SGH-I897 using XDA App