Hey guys, I just need to know how far up **** creek without a paddle I am and how I got here. I had a stock JF6, a friend told me to root with unleash the beast so I did. Been running great and aside from using metamorph to install a few swype themes and nav bar themes, it was stock. I had managed to learn a bit and heard clockwork mod was a great thing, and was making backups regularly.
Well since everything was going so well, I decided to dig deeper and install cognition 2.1. Things went fine, until I got to first boot, then I realized all my stuff was gone, should have known and me being changed my mind. So I went and booted into recovery, and tried to restore my most recent backup, well of course it failed when it came to data because cognition had formatted it.
Well after a lot of formatting data/cache, I tried to install the cognition 2.1.zip, got an error message.. Failed to install. After rebooting I was stuck in the att white screen boot loop. So once again formatted data, and this time I ran update.zip(unleash the beast).
HERES my question, now I seem to have some kind of hybrid, on first boot of cognition I got the custom boot sounds and wallpaper. Nothing now, however my baseband is now JH7, and it says something about voodoo lag fix. But still says 'beast .... Teaser' for system info.
I'm so confused, what's the best way for me to get a stable version of cognition running? Ill just install all my data, I just wabt to know exactly what my phone is running.
Sent from my SAMSUNG-SGH-I897 using XDA App
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Sent from my SAMSUNG-SGH-I897 using XDA App
sdotbrucato said:
Best bet is to flash back to JF6, root, install ROM Manager, and load Cognition from that.
Also, that question its better suited for q&a, not the dev forum
Don't forget to disable lagfix before you Odin.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
Sorry, I just mainly check here and the themes and apps section.. Completely forgot about the other ones.
So if I wanted to flash back to jf6.. Would I just get one of these stock dumps floating around and flash it? Or is there a better way?
Sent from my SAMSUNG-SGH-I897 using XDA App
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Sportsguy15 said:
Use the Odin One Click that's posted at the top of this forum. It will flash you back to stock in a matter of seconds.
Click to expand...
Click to collapse
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
bamathrasher said:
THANK YOU.
this is what I needed to know. So basically, odin one click, use any method to root (probably just use a one-click this time), and then download rom manager and install cognition from clockworkmod? and thats all it would take?
Much easier then what I had in mind.
Click to expand...
Click to collapse
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
bobbylx said:
Yep, that's all you need to do. I've started doing that any time I flash a new rom, ie, One-click to stock, root, rom manager, flash new rom.
I have had similar issues when I try to flash over an existing rom, plus it is nice to start with a fresh rom, no bugs.
Click to expand...
Click to collapse
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
rajendra82 said:
Data on ext4 survives an Odin flash, so if you are on voodoo, it's a bit more involved than just flashing.
Click to expand...
Click to collapse
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
bamathrasher said:
I saw something like this in the Cognition thread, about creating a file called "disable-lagfix" or something and placing it on the root of the sd. Is that the extra step you are referring too, and if so, I definitely need to do this?
Click to expand...
Click to collapse
Yes. That's the correct method to put /data back on RFS. Once you have created the file and rebooted, a robotic lady will inform you that the /data is being converted. Once this boot finishes, you are at a point where Odin or Clockwork will be able to help you. When /data is in ext4 format, the other programs don't recognize it, and don't work properly.
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
bamathrasher said:
just for future reference, what type of data are you talking about here? I have no data I'd like to keep at this point, after I bricked my phone last night, I basically tried everything in clockworkmod until I got it back to a workable state so I'd have a phone to use today at work. How am I supposed to make it through a work day without being able to text? its impossible. haha.
So if I have no data I desire to keep, is this necessary or is this a different type of data, important data for the system?
Click to expand...
Click to collapse
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
rajendra82 said:
If you noticed in my post I did not say data but /data. There is a difference.
On your Captivate there is a total of 16 GB of internal memory. The memory is partitioned into several block devices. One of these partitions is mmblk0p4, which once booted, is mounted to /data. This directory stores your apps installed from market, your user information, your call log, your text messages, and so on. It has to be working for your phone to boot up properly. Although /data looks like a directory, since it is a link to an actual device, it can be on its own file system which is different than other devices mounted to other directories. On a default Captivate (i.e., before you install Cognition, which includes a choice of two voodoo lagfix kernels) the block device mmblk0p4, mounted as /data is formatted in a proprietary Samsung RFS file system, which is too slow. When you install the voodoo kernel, on first boot, it formats the device in a much faster ext4 file system if there is no file or folder called disable-lagfix in /sdcard/voodoo, thus severely reducing the lag. The problem is that the default kernel, the recovery mode kernel, and the Odin flasher program understand how to deal with this device formatted in RFS. If your block device is in ext4 and you restore the system through Odin, you will end up with Odin not wiping off the contents of /data, which is what you actually wanted. I am not sure if you end up with a working /data device in RFS and a chunk of unused ext4 information, or a kernel not understanding /data in ext4 and hanging. If you are in this state, your best bet is to flash on a voodoo kernel through Odin, which will then understand the ext4 /data. Once the voodoo kernel boots, you then create the disable-lagfix file and reboot, to get /data back in RFS. Then you go into download mode, and wipe the /data on RFS with Odin.
Click to expand...
Click to collapse
thank you for taking your time to write this up for me. Very helpful.
"You do not have enough free space in /data to use this fix. Please free up space before using this fix"
?????????????????
I checked my /data folder -- it's empty except for a few small .txt files
I have a 32 GB external SD card
My internal SD card is 50% free
WHAT GIVES ??????????
Is there any other lag-fix's ?
I have OneClickLagFix V1+ (1.0 with extra's)
Please help
Use voodoo lag fix
same thing happens to me after flashing JPK..
Sent from my GT-I9000 using Tapatalk
Its your internal built in 2gb phone memory which doesnt have enough space.
OCLF requires 1.2gb of space on it to work.
You can do what I did which was to titanium backup everything, reset to factory (frees up your phone memory), do OCLF/voodoo and then restore your backup.
Voodoo works better than OCLF but there's no permanent way of uninstalling it other than reflashing it. Got sick of waiting for Froyo and did it anyway.
KaliKot said:
Its your internal built in 2gb phone memory which doesnt have enough space.
OCLF requires 1.2gb of space on it to work.
You can do what I did which was to titanium backup everything, reset to factory (frees up your phone memory), do OCLF/voodoo and then restore your backup.
Voodoo works better than OCLF but there's no permanent way of uninstalling it other than reflashing it. Got sick of waiting for Froyo and did it anyway.
Click to expand...
Click to collapse
So in order to do Voodoo i HAVE to reset factory ?
I don't have ODIN do I have to reflash ?
jaju123 said:
Use voodoo lag fix
Click to expand...
Click to collapse
I don't have or know how to use ODIN yet -- im still kinda new
Also, I don't have the 3 button recover/download mode -- (i can't get KIES to upgrade my firmware for the life of me) -- so flashing/reflashing isn't the best option for me
I was hoping for like an App like Ryan's was out there
I guess not. So there's only Ryan's and Voodoo ?
Funkadelick said:
So in order to do Voodoo i HAVE to reset factory ?
I don't have ODIN do I have to reflash ?
Click to expand...
Click to collapse
You dont have to reflash. You need to have 3 button recovery mode though and it will apply the lagfix on boot.
You'll only have to reflash if you want to completely remove voodoo from your phone instead of just disabling it.
A word of warning though. I had the same encounter earlier when OCLF couldnt lagfix my phone because of the disk space. I did voodoo and it worked but then my phone only had like 20mb left.
Its best to reset to factory, apply either lagfix and then restore your apps with Titanium Backup
I had the same issue on JPK initially because OCLF 2.1.0 wasnt able to write to the system folder. It had prepared the files to move but failed at that point.
I assume yours is the same.
I did this to fix it:
open terminal emulator on phone and type:
su
busybox mount -o remount,rw /system
I manually deleted the file "linux.ex2" in folder /data/ext2 to free up the space...
After that rerun the lag fix, works fine
And you couldnt post this problem in one click lag fix topic why? Just wondering what compels everyone to make a dump out of this forum.
This is ridiculous...
You guys really need to calm down with this "new topic" button"
Funkadelick,
This thread has nothing to do with development and does not belong in that section. This topic has also been covered in other threads as mentioned above, and therefore really should not have been posted in the first place.
Before posting any more threads, go read the "please read before posting" thread at the top of the forum section as all of these subjects are addressed there along with other important ones as well.
Thread closed.
Once you activate the lagfix, files are created in the sdcard that are just over 1gb in size. Can i delete these files or are they important?
Sent from my Green Robot Device
I don't think the lagfix will work if you delete them.
So it disables the lagfix? If that was the case, it should be as simple deleting those files and disabling lagfix instead of going through CWM and waiting 15mins for it to disable.. Right?
Sent from my Green Robot Device
don't know if it's the same thing deleting/cwm but should be better to remove it
through cwm to make sure it's all gone. yeah it's quite a big file but i don't really mind.
got enough space for apps/games on the phone, and 4gb card for music, it's only $10
Hey guys,
I bought my Galaxy S a week ago from amazon.
I installed a rom (called pilotX - comes with SGS tools, Voodoo and other stuff), and downloaded a few apps, some of them were given root access (Titanium backup, etc..).
Then they have began crashing all the time.
Tried to remove them, but after a reboot they return! Even after I do a factory reset, and cache reset.
I think the internal sd card is "write locked" or something, if I fire up "My Files" and delete everything, than unmount the sd card and re-mount it, everything comes back.
Other things I've tried:
* Installing other firmwares via Odin.
* Installing other kernels / ROMS.
* Formatting the SD card from settings.
* Formatting via the "phone number".
My phone is a rack now, when I power it up there are so many "End task" windows that I can't get to the desktop (can do it after a few tried though)..
Any idea what's happening?
Thanks in advance..
Edit: More info - I also installed speedmod-kernel-k13d-500hz - another kernel (with odin).
The apps are installed on the phone internal memory I think, I can still see them even if I unmount the internal sd card..
Something is clear to me here.
I think you did not disable lagfix before you flash another kernel
that the rom included voodoo lagfix and you flashed speedmod kernel.
so you messed up your memory part of your phone.
You don't have to worry.
download stock firmware, with pit file, repartition.
this just disable everything and will bring your phone back to original state.
Start again from there.
Thanks dirn,
By stock firmware I guess you mean one of the formal firmwares?
I've tried a few already, with their pit files.
Currently I have I9000XWJM8 installed (tried JQ3, JM9 and some more as well, originally had JQ1).
Even with repartition, the memory still seems jogged..
The kernel was burned before I installed the ROM, so even if it included a lagfix, the memory problems started right after I downloaded apps from the market, before I even changed kernels and firmwares to try and fix this..
are these firmwares in 3 files ?
they must be a 3 file firmware if you are using PIT and re-partition, Also did you make sure the re-partition box was checked before you started the flash.
old eclair 2.2 works well for me when i have issues, perhaps it will work for you too
Positive,
I ticked the check box,
chose 3 files, chose the right PIT, been with Eclair all along - tried to switch to Froyo once to see if there's any change but no good..
It's killing me, I gotta understand how it happened..!
you dont have the SGS I9000 M << do ya ?? definately I9000 international.
could you post a screen shot of what odin looks like before the flash
Hi everyone,
Today, to prepare for the install of Darky's 10.1 (currently running 9.5) I decided to turn off the lagfix. On the advice of someone at work, I also decided to format the internal SD (using the section in the options menu of the phone). I booted into recovery, and disabled the lagfix as normal, all seemed well. I then turned the phone off (to remove the SIM and SD), and rebooted just to double check that the lagfix was successfully disabled, and the lagfix was reapplied for some reason.
How do I stop this happening again? and how do I tell if the lagfix is definitely turned off?
Thanks
Rob
To update:
Just rebooted again after unchecking all the boxes in the voodoo sound app. Now the voodoo sound app still has both boxes unchecked, and the lagfix status is "Lagfix RFS Only, compatibility mode, no EXT4 conversion", is the correct?
Thanks again,
Rob
Yes, problem solved, and very interesting to know, thanks for sharing
Insanity cm017/glitch v10c