Related
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
you need to disable the voodoo fix before you do anything, because its like you said, it still assumes its ext4. In odin its trying to flash its looking for rfs partition. If its too late to disable voodoo, you may want to try flashing one of the 2.2 ROMs through Odin, those seem to fix all bricks (non JTAG bricks that is), and brings phones back to life. If you use a 2.2 i recommend Eugenes very first one where you don't have to mess with kernels and such
boimarc89 said:
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
Click to expand...
Click to collapse
I had the same issues. Here's what I understand. Voodoo changes the filesystem to ext4, as you know. But RFS can't read that. For some reason, the kernel doesn't flash properly because it still sees the ext4 partition.
So here's what I did to fix. Pain in the arse, but it works.
In ODIN, Flash Eugene's Froyo that does not brick ROM in the bible
When that is complete the recovery will come up and there will be some errors. That's ok. We don't want this one.
THEN flash RFS (you should already have it) from the bible.
SHOULD be good to go. Like I said, it's dumb that you have to go through that, but it is what it is. I did it 4 times in 5 hours using trial and error. I know this method works.
Good luck!
in adb, i ran "adb shell", "mount" and i checked the "/dev/block/" and it said "/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vflat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0". so i think its rfs..i think lol is there a command in adb that can disable the lagfix?
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
I agree, flash to froyo that does not brick, then flash back to the original firmware, not leaked updates. I have had great luck with checking repartition when flashing froyo, keep it checked when flashing back to stock. Then uncheck it and flash the stock rom a second time.
Sent from my SGH-T959 using XDA App
boimarc89 said:
in adb, i ran "adb shell", "mount" and i checked the "/dev/block/" and it said "/dev/block/mmcblk0p3 /data_tmo rfs rw,nosuid,nodev,vflat,llw,check=no,gid/uid/rwx,iocharset=utf8 0 0". so i think its rfs..i think lol is there a command in adb that can disable the lagfix?
Click to expand...
Click to collapse
No, the problem is probably mmcblk0p4 a.k.a /data being and ext4 filesystem, but if you flashed the stock kernel the phone won't be able to mount /data since it won't understand the ext4 filesystem... and THAT's the problem.
boimarc89 said:
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
Click to expand...
Click to collapse
Is that sarcasm? I hope it is
boimarc89 said:
is the RFS file ur talkin about, "s1_odin_20100512.pit" ?? or is it somethin else?
Click to expand...
Click to collapse
that pit file just tells Odin how to setup the partition tables... its the actual .tar file that contains the .rfs install files... if you can get into Clockwork and install a custom ROM, then you can disable the voodoo lag fix, and reflash the stock kernel so you can go back to stock
or
like everyone else has mentioned go to froyo, then go to stock
If you can get into clockwork, just flash the flashable zip version of the froyo Rom. Accidentally forgot to disable voodoo when I flashed it earlier. What do ya know, the ROM booted all the way up. That will work without odin. Given that it wasn't a fluke and u have access to clockwork still. If not odin is your only option. Point blank.
http://dl.dropbox.com/u/9742964/Vibrant_Frankin_Twiz_Update3.zip
thats eugene373's Frankin-Twiz3 custom ROM preloaded with JACs Voodoo kernel, just flash through Clockwork and it'll install the voodoo fix again so you can disable it
If it doesn't help you, it may help others in a similar situation.
i got it now..im running the ji2 firmware trying to get to build.prop so i can fix the missing market apps..idk how to get to it...can i extract it by adb?
boimarc89 said:
i got it now..im running the ji2 firmware trying to get to build.prop so i can fix the missing market apps..idk how to get to it...can i extract it by adb?
Click to expand...
Click to collapse
Use a root explorer app and edit it directly from your phone.
boimarc89 said:
i need help...my vibrant is sitting at a blk screen after odining the stock jfd.tar . i had had voodoo lagfix and a market lagfix on there earlier and i dnt think i took it off correctly bcuz i was late to class but shouldnt odin take care of thatif i selected repartition and the stock jfd.tar file?...could it be that its still setup as EXT4 and not rfs like it should be when its stock? now i JUST noticed that it will only boot completely if i load a custom rom despite using odin to revert to stock. what happens is that it boots to the tmobile pink square but no sound, when the galaxy S screen comes on, then the tmo sound comes on (late), then the screen goes blk w/ the touch buttons lit. in order for it to boot i have to flash the root update in clockwork, reboot, then flash a ROM, reboot....have i done somethin wrong? why wont it boot when i odin it?
Click to expand...
Click to collapse
I'm probably asking for it, but ...
How is this thread "in the rom bible"? You messed up in some manner, didn't quite understand exactly what you were doing, you don't fully understand what a fstab is or how partitions really matter, sure, I understand that. But why does this warrant a thread: yeah, that's a bit beyond me ...
After reading several other threads promoting self-policing, why oughtn't it be sought here.?! If the only reason that this thread is offered a place in dev is because there is a mention of ext4, then we are all in trouble.
I've been flamed and chastised before for my views, but if no one polices, then who will? Is your question really geared toward the development of something Android related? Then perhaps you have a valid thread. But if it's not genuinely development related, why are you posting here?!
disable-lagfix in an update.zip
This article has a link to install the disable-lagfix with an update.zip file. If you have access to recovery I suggest you use that.
http://androidspin.com/2010/09/23/overclock-add-some-voodoo-to-your-samsung-vibrant/
So I downloaded the voodoo lagfix.
And made a back up using the threads on this forum. I made my back up before I installed lagfix.
Now if I wanted to revert back before I had lagfix, couldn't I just flash back to my first back up to basically get rid of lagfix, or would that not work? I'm really just preparing for froyo. And the OTA and would like to do that without using any adb commands... Is there maybe a simpler way to do this?
Swyped via Fascinate.
That will not work as you need to change the /data from ext4 back to rfs. Just remove the lagfix like you are supposed to and things should be fine.
There is a lagfix removal tool posted in the developer forum. It will probably cause you to wipe your device though.
How does it work ?
Swyped via Fascinate.
Hi everyone, this is my first post. I am one of those who waited patiently for 2.2 that I decided to finally root today. I followed all the instructions to root from the sticky here. The process went without a hitch and I flashed the jk6 stock from Team Whiskey from the development section.
I really enjoyed the 2.2 experience while it lasted until I flashed the JL5+voodoo kernel from supercurio's thread. I was under the impression that you could flash different kernels over the old ones. It went through the process of partitioning to ext4. Once it was done, I went to settings and about phone to see if there was JL5 anywhere and it wasn't. It still showed JK6. So I panicked. I disabled voodoo through clockwork recovery and went to the process of reverting back to rfs which I believed. I used odin to flash back to jfd. I know, I didn't restore the backup from clockwork because I wanted to start over( I still have those backups on my external sd card). To my knowledge, the flashing to jfd would completely wipe the data, replace the baseband, kernel, recovery and os.
I then used samsung kies mini to update to JI6. Everything went ok so I decided to root again. Instead of loading the update.zip to internal sdcard. I decided to use tga_gunnman once click root. That process went great until went it rebooted, the clockwork recovery screen popped up to my amazement. It seemed that there were still original files since the first time I rooted. I checked my files on my vibrant to find that I still had original files such as the clockwork back up, titamium back up, and even voodoo. I thought the flashing would completely remove all the data and files. So I panicked again. At this point, I don't know what I did that now I can't get to my log in screen and the screen I get is a picture of a phone, an exclamation, and a computer on my phone. I tried using odin again through download mode to go back to stock but under the message box on odin, it stops at cache.rfs. It has been stuck there for a long time and nothing is happening. I can't even get into recovery mode either.
Now I am not even sure if I properly disabled voodoo or deleted it which I thought the flashing back to jfd would do. I don't know if my partition is still rfs or ext4. I can't use my phone at all. Did I completely brick my phone? How do I fix the mess I got myself into? I really do appreciate anyone's help. I apologize for the length of this post. I wanted to be detailed as possible. Thank you.
EDIT: Spoke too soon. I used a different version of odin and now im back to stock jfd, but the original files are still there including the voodoo folder. I thought it wipes all the data. Also how do I know that the data partition is originally rfs and not ext4? I want to make sure before I root again. Thanks.
Can you get to recovery and restore your backup you created? I just read where you said you can not get in to recovery. What method are you using to try to access recovery?
well if you are back to stock, but just the folder is lingering around, cant you just reformat your sd card?
settings>sd card phone storage>format.
I did a back up using clockwork. I originally was trying to do to the recovery mode by pressing the vol keys and power and that didn't work. I actually got it back to stock jfd by using a different version of odin. My problem now is that I still have some original files on my phone including the voodoo folder. My understanding of flashing was that it wipes everything from your phone. I am not sure if i still have root access even after flashing back to stock jfd. Also if my partition is back to rfs or still stuck at ext4. I am a little confused here. I am afraid if i root again that the original files and folders from my first root will interfere with the new root method.
so If I format the internal sd card, will it completely erase all traces from my first root?
neotoky said:
I did a back up using clockwork. I originally was trying to do to the recovery mode by pressing the vol keys and power and that didn't work. I actually got it back to stock jfd by using a different version of odin. My problem now is that I still have some original files on my phone including the voodoo folder. My understanding of flashing was that it wipes everything from your phone. I am not sure if i still have root access even after flashing back to stock jfd. Also if my partition is back to rfs or still stuck at ext4. I am a little confused here. I am afraid if i root again that the original files and folders from my first root will interfere with the new root method.
Click to expand...
Click to collapse
When you flash a new rom, or back to stock, it does not (usually) wipe the contents of your sd cards (internal or external). And if you are successfully running stock 2.1, you can rest assured you're back to rfs - so if that voodoo folder is making you nervous you can just delete it (it's only relevant if you have voodoo enabled). You're fine to re-root with whatever method you prefer.
Sounds like the soft-brick you experienced was purely from odin hanging on you, and that icon you saw has become a frequent visitor on my phone since I routinely have odin hanging issues (hence my avatar). I've found that v1.3 treats me the best, but sounds like whatever version you updated to worked, so there's no reason to deviate.
Download OCLF from the market and you will find out if you are currently rooted still.
There are a few misconceptions on what the wipe is.
/sdcard and external SD card are user accessible areas of the phone, and when it states that the ROM wipes your phone it does not touch these (there was only one incarnation of TW ROM's that inadvertently formated the entire filesystem for some users).
If you must format the phone to its complete stock form in ODIN you can use re-partition check box - the results are still mixed if it formats the entire FS or not, but most probably it will for you. So all your pictures, etc. should be backed up no matter what.
I appreciate the help guys. Thanks very much. The version of odin I used originally was v1.00 and the one I used to fix the problem was v1.70. My question now is did I properly flash the JL5 kernel over the JK6 even though when I checked the information on my phone it still stated as JK6? Also how do you properly reflash to a different kernel as well as modems? Do you overwrite the kernel or do you have to go back to stock before trying a new one? Thanks.
neotoky said:
I appreciate the help guys. Thanks very much. The version of odin I used originally was v1.00 and the one I used to fix the problem was v1.70. My question now is did I properly flash the JL5 kernel over the JK6 even though when I checked the information on my phone it still stated as JK6? Also how do you properly reflash to a different kernel as well as modems? Do you overwrite the kernel or do you have to go back to stock before trying a new one? Thanks.
Click to expand...
Click to collapse
I'm not sure why you would flash the JL5 kernel. Does it have any added benefit over the JK6? If you want, you can flash the JL5 MODEM through clockwork using the JL5_modem.zip file posted in many threads.
You should not have to go back to a stock kernel before trying a new one, but if you flash a Voodoo kernel that converts your system to ext4, then you must convert it back to RFS before flashing another kernel. An easy way to be postively sure that you are in RFS is by getting "Terminal Emulator" from market, and type "su" press enter, and then "mount" and press enter. If you see rfs next to data, dbdata, datadata, and system, then you know your system is converted back to RFS. Otherwise, in Voodoo mode it will read ext4 next to those.
Also, if you are really paranoid about getting a fresh start, you can mount your internal SD on your computer and just delete everything on there. Don't worry, all the important Android system files will be restored upon each reboot. All the other crap on there will be erased.
i have a few technical questions about voodoo
1. i recently was unable to load widgets after restart, and i couldnt install apps, my available memory was 0.00. i got it fixed. my question is, is this related to voodoo? what causes this. how can i prevent it in the future?
2. lets say im on a voodoo kernel and i disable lag fix. if i dont flash a new kernel, i will still be using that voodoo kernel, just with rfs instead of ext4. it does not revert to a stock or default kernel?
3. if im right about question 2, and i think i am, do the sound enhancements require the lag fix to work? i wouldnt think they would, if it works on one filing system why wouldnt another?
gunnermike said:
1. i recently was unable to load widgets after restart, and i couldnt install apps, my available memory was 0.00. i got it fixed. my question is, is this related to voodoo? what causes this. how can i prevent it in the future?
Click to expand...
Click to collapse
You must have installed a non-Voodoo kernel over a Voodoo one. When you install a Voodoo kernel, it converts the file system(s) to EXT4 from RFS. If you then flash a non-Voodoo kernel, it can't read any of the EXT4 file systems because it doesn't support EXT4.
To avoid this problem in the future, you need to disable the lag fix and convert back to RFS *before* flashing a new kernel. You do this by going into the Voodoo options in the red Clockwork recovery, setting the lag fix to disable and rebooting. During the boot, it'll automatically convert back to RFS and then you can flash any kernel you like.
gunnermike said:
2. lets say im on a voodoo kernel and i disable lag fix. if i dont flash a new kernel, i will still be using that voodoo kernel, just with rfs instead of ext4. it does not revert to a stock or default kernel?
Click to expand...
Click to collapse
Correct, you'll still have the Voodoo kernel, it just won't be using EXT4.
gunnermike said:
3. if im right about question 2, and i think i am, do the sound enhancements require the lag fix to work? i wouldnt think they would, if it works on one filing system why wouldnt another?
Click to expand...
Click to collapse
I just tried disabling the lag fix, and the sound enhancements still seem to function, so it would appear they're not dependent on the lag fix being enabled.
You must have installed a non-Voodoo kernel over a Voodoo one. When you install a Voodoo kernel, it converts the file system(s) to EXT4 from RFS. If you then flash a non-Voodoo kernel, it can't read any of the EXT4 file systems because it doesn't support EXT4
Click to expand...
Click to collapse
i havent touched nonvoodoo kernels since i made that post on ac. i was thinking the same thing, so i disabled the lag fix, flashed a kernel i KNEW was voodoo, reenabled the lag fix. still had 0.00 available mem and widgets wouldnt load after a restart. for the trouble shooting part of the post on ac i flashed a nonvoodoo kernel over a voodoo kernel on purpose, and my phone wouldnt boot. the fix was simple for that. i got completely differant results this time. i KNOW i did not flash a nonvoodoo kernel over a voodoo kernel. i went through every kernel on my sd card and NONE of them are voodoo. just to be sure, after i got phone fixed i flashed everysingle kernel on my sd card, and they all worked fine.
is this chris3d? i couldnt get numbers for my name either.
well, im going to try a voodoo rom but my question is. how do i activate voodoo? ive seen voodoo option on clockwork? do i go there activate it,reboot then install sc voodoo rom? or do i need to take more steps then these? and yes ive lookd around.thx
Hello,
Voodoo kernels have to deal with the way the file systems is formatted. Samsung devices are formatted with the RFS filesystem and what the voodoo lag fix does is replace it with the Linux standard of Ext4 filesystem.
With that in mind, it helps fix the I/O speeds (reads,writes) of the file system. The current working clockwork recovery has the voodoo menus with it. It is meant to be used with both voodoo and non voodoo kernels.
You only want to activate voodoo if you have already installed a voodoo kernel. I am not sure where you are at in flashing a rom for your phone but just let me know and I can help walk you through it.
If you use one of JT's rom you will need to flash a voodoo kernel if you before you install a voodoo rom. If you use one of adyns roms he packages the kernel with the rom so all you need to do is wipe data/cache etc and install the zip.
But if you ever stop using kernel you will need to completely remove voodoo before switching. Besides you get to hear a chick talk while the voodoo kernel is installing lol. Usually when I get swap away to a non voodoo kernel I flash through Odin to get back to stock.