Database Users

Lets nail down the cause of JI6 soft bricks

Hey folks, I've read through all the JI6 OTA threads here and on the TMo forums and while I've seen a few people guess as to the cause of soft bricks, dosen't seem like anyone has nailed down the actual cause. I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN so knowing what if anything can be done to prep my phone before accepting the OTA (that is sitting in my notification bar as we speak) would be immensely helpful.
So far the two best guesses I've seen are the existence of other update.zip files on SD and removal of bloatware, specifically Media Hub and possibly edited startup/shutdown screens.
Since I've got all these going on, I guess I'm staring down the barrel of a brick. But obviously one of these is easily rectified while the others, not so much.
Aside from those claiming bricks on vigin phones. Can we hear from those who have made mods to their rooted devices and either did or did not experience an OTA brick? I think this info will be helpful to many in sorting out what exactly is going on here.

I have black bar mod, I have naked swype, removed most t-mob app except media hub no change to start up or shut downtried to update. 50 % through it said update failed. Then rebooted fine. But I had an extra update.zip on my sd so maybe that's why. But no firmware now? Maybe I'm sol.
Sent from my SGH-T959 using XDA App

Mine wouldn't complete the update Rooted, most of the bloat removed, had an update on the sd. Was able to get into clockwork after the failed update and am performing a nandroid restore now.

this is great, thank you. beginning to look more like an issue with extra update.zip files than media hub. any successful OTA's with media hub removed prior to accepting the update?
Sent from my SGH-T959 using XDA App

I never uninstalled Media Hub. I have seen a correlation of about 5 people who had ROM manager installed and used that to install Recovery. Whether it be the installation of Recovery or a possible permissions issue with how it generates the update.zip that may have caused my issue.

just a question, why do people remove media hub? Does the application make the phone slow?

iynfynity said:
just a question, why do people remove media hub? Does the application make the phone slow?
Click to expand...
Click to collapse
Because up until now, it was a non-functional app. I didn't remove it, I use LauncherPro so I just removed it from my drawer. I'm still not touching this update. I got my Vibrant used so I would be out of luck if it jacked my phone up and I hate using ODIN. Too much hassle when my phone runs great on Bionix 1.4 as it is.

Wife's phone was toasted by OTA. Stuck at Vibrant screen. Rooted, unlocked, she did have an update.zip, if that turns out to be the culprit. Also had some apps removed, replacement startup animations, and removed shutdown junk.
She was set for always-on WiFi, too.

My rooted Vibrant soft bricked yesterday and I had to flash stock with Odin. I had the (what seems to be infamous) update.zip, removed Kindle, Mobi TV, Avatar Icon, Gogo. I had RyanZAOneClickLagFixV1+ installed but removed it. I also had the EXT2 Tools installed. @ the time of the update I was @ work and had a full charge on the phone. I flashed back to stock last night after work, and I haven't recieved the update notificaiton again...maybe TMo crossed me off some type of "update list"?

There are also different possible symptoms.
In my case the update appeared to have completed its cycle, except the tail end of the download of the new update wnt really fast then the system rebooted. System came back up into the Black Vibrant screen. I could start 'adb logcat' and the system had SurfaceFlinger repeatedly crashing.
Attempts in Recovery Mode after this to reinstall files didn't resolve the issue, reboots would still lead to a crashing SurfaceFlinger.
2 separate users in a thread, 1 had removed Boot Animations + Sounds, I only had removed Sounds.
Quite a few people had Stock Roms + Root, but some with Root didn't have any issues. Only correlation was with Titanium + Rom Manager, which a lot of people would have installed since it's listed in the Tips and Tricks thread. Titanium shouldn't do anything to the system unless you generate a backup Update.zip or install LZO support busybox.
One guess is that ROM Manager and Titanium can create a update.zip file that doesn't have the proper permissions. An OTA update that attempts to overwrite this file may get confused. Simply removing the file in advance may alleviate this issue. Another issue is ROM Manager installs ROM Recovery, which may change how the OTA perceives the phone.

Bionix 1.4...
I was running Bionix 1.4 KK OC/UV yesterday morning... Was a little dumbfounded when I received the update message from Tmo. Figured it wouldn't show w/ modded handset. Delayed install until I could read everything on here about it. Tried installing over Bionix last night just to see, and had no joy. I had removed all crapware, mediahub included. Hit 50%, said flash failed, rebooted and was back to my homescreen in no time. No ill effects to phone except being denied upgrade.
So I Odined back to Stock JFD FW (and wiped device for S&G), rooted, and updated from JI6 tar posted. Flashed perfectly, no ill effects as I've noticed. Reception is improved (for me anyway), and GPS functions similar to Bionix... No real incentive for update, but was curious.
I see Bionix 1.7 updated so it was all for nothing.
Now to play with other stuff...
Cheers

My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?

I got the soft brick and had to flash back to stock via Odin and then I flashed the JI6 tar file from the forum. All is working fine now.
I had root but no update.zip file on the sdcard root, had removed startup an shutdown sounds, had used both ROM Manager and Titanium (with LZO compression turned on), and had removed bloatware including the non-functioning Media Hub.
Next time I'll flash back to stock before doing an OTA update.

I am rooted have Titanium backup, ROM Manager, and clockwork mod. I also had an update.zip but I think it was from OCLF not from another source. My update went fine and I'm running without any problems on the new update.

PepeLasNoches said:
My girl friends phone bricked the other night from the OTA, it's rooted(update.zip) and has the bloatware uninstalled, nothing else like lagfix/roms on it etc.
T-Moible is sending her a replacement phone, which im pretty surprised about. Now since we have to send the old phone back so they can check for damage or anything that would void the warrenty.
We get to keep the external SD card(Avatar), now im sure there is a pretty good chance they will find that its been rooted. So we would have to pay $400 they said if its voided.
Now I can't get this phone to boot into download mode or even mount it, so what should I do? I know about ODIN but have never used it, can it mount the phone?
Click to expand...
Click to collapse
Woo, got it unbricked! finally got into download mode and ODIN saved the day.
this video was helpful for me: http://www.youtube.com/watch?v=AnY7P14JSWQ
^ODIN walkthrough

paxton said:
I'm going to assume I'm not the only person out there with no access to a windows box to run ODIN
Click to expand...
Click to collapse
there is a cross platform tool being developed called 'Heimdall'. It is currently a command line tool and is in beta. however people are successfully flashing their phones using it. It is obviously not a 'one click' solution, so you will have to go find the proper files and type out the command.
It can be found here http://forum.xda-developers.com/showthread.php?t=755265#
If you are the type of person with access to both a windows machine and a linux machine, I suggest you check this out. Testers are needed. Of course you can test if you don't have windows, but it's nice to have Odin as a back up. ;-) just incase....
-p

I had a failed update twice using Odin. It wasn't until I went back to stock T959JFD for the second time and deleted update.zip and all clockwork back ups that it finally worked. Runs perfect with no issues.
Sent from my SGH-T959 using XDA App

Was rooted with OCLF, Captive camera, gps fix, rom manager, titanium backup and add removal. Removed the OCLF and unrooted, ran the update, looked like it got to 100% (not sure cause I looked away and then back at it right before reboot) but said update failed. Got stuck at the vibrant screen blah blah. I'm pretty sure I had an update.zip on the sd, but not 100% on that. After pushing the update with ODIN I have noticed my phone lagging quite a bit.... Thoughts?
Sent from my Rooted Samsung Vibrant using XDA App

Larger NAND Voodoo Fix

This will most definitely wipe all previous remnants of data, including any unlock codes that you may have on your phone!​
Update 10/11/10: This is now a confirmed fix for phones with larger NAND chips;
1. Download Eugenes 'Froyo that does not brick' file.
2. Extract the files.
3. Open Odin, plug in your phone, then put it into download mode.
4. load the PIT file in appropriate area.
5. load the .tar file in the PDA area.
6. DO NOT check 're-partition'.
7. Click start, let it finish. Your phone will load and reboot into stock recovery. It will error out again. DONT panic! This is what's supposed to happen.
8. Now, pull your battery.
9. Download the 'True stock 2.1 firmware for the vibrant'.
10. Extract the files.
11. Once again, open Odin, plug in your phone, put into download mode.
12. Load the PIT file into the appropriate area and the .tar in the PDA area.
13. Once done and phone has rebooted, root your phone & install Rom Manager.
14. Download & Install Bionix 1.7 with OCUV Voodoo
Click to expand...
Click to collapse
NOTE: The bootup sound HAS changed.. But if you hear Linda go through the process of changing the format then you can now run voodoo..
(Or if you don't know & you arent for sure, just download Quadrant & if your score is 1500+ voodoo is enabled.)
If you would like to know if you have a larger NAND chip, please follow This guide.
Credits: sombionix | SkOrPn | Master™ | JAC
If I forgot anyone in that list, I apologize. Please just PM me so I can add you to the list.

i think my vibrant has the larger nand chip, any way to make sure before i go through the steps above? using terminal on the phone would be best, it's just mount right? not sure what to look for after that

Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.

kangxi said:
Supercurio has already supplied JAC with the fix for the larger NANDS (I asked him). JAC just has to make a new kernel with it included.
BUT, JI6 is so fast that I don't think that it even needs a lag fix. I've been running it for a couple days with not one hiccup. Don't know what Samsung did but it worked.
Click to expand...
Click to collapse
Yeah I know, But until he makes it we can test this for a temp fix

Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?

kangxi said:
Ok well, I DOCan you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
We have no clue.. But we both have done this & for some reason voodoo works on both of our devices now

kangxi said:
Ok well, I DO have a larger NAND which is why I've been trying to follow the Beta5 development. Can you explain what doing all of this actually does and why it works?
Click to expand...
Click to collapse
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...

SkOrPn said:
I have been using voodoo for several weeks now. I kept getting the dreaded "this model is not supported" error when trying to apply voodoo kernels. I tried literally dozens of times if not more, I was on the verge of quiting but sombionix told me to try flashing to the froyo rom that does not brick, and then to the stock rom. I immediately rooted, installed Rom Manager and Clockwork recovery, and then flashed bionix 1.4 rom (might have been bionix 1.3 at first, but 1.4, 1.6 and 1.7 have all worked since) containing JAC's v1.1 OC/UV/Voodoo kernel with Voodoo beta4.
Voodoo has worked flawlessly ever since... My NAND is the larger 416MB NAND. Go figure....
All we are asking of you guys is to have a little faith and try this procedure. If it works, then you get voodoo bliss, and if it don't then we are back where we started. You have nothing to lose but a hour or less of your time. Give it a try and report back here please. Good luck...
Click to expand...
Click to collapse
+1
He didn't even tell me, lol

It'd be nice to see Bionix v1.8 come with Voodoo Beta5 since they're both so close at hand so we don't have to go through this crazy business. Good work and great find, though!

I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.

I second ji6 is impressive.
Sent from my SGH-T959 using XDA App

vdubgti08 said:
I followed this method and it allowed me to use the Voodoo Lag Fix. I was never able to get it to work before, would never hear the boot up sequence telling me my file system was being converted etc. After flashing Eugenes Froyo rom and flashing back due to stability issues I tried Bionix 1.5 and was able to flash the voodoo kernel. I checked before when it wouldn't work for me and found that I too also have the larger NAND chip. I upgraded to Bionox 1.6 just fine, not sure why it worked but Its been wonderful these past 2 weeks.
Click to expand...
Click to collapse
Yeah Voodoo beta5 was never needed, so a whole lot of people waited for nothing. LOL

So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?

2sh0rt said:
So i searched the forums and didnt find a definate answer, maybe i didnt search the correct terms or something, idk. My question is, if you have a larger nand and voodoo DOESNT install, do you still need to run "disable-lagfix" when flashing a backup or another rom?
Click to expand...
Click to collapse
No i do not believe so, BUT, I would still put that file into the voodoo folder anyway. There is no harm in doing so. When you get the other rom installed and setup how you like, then you can remove it. Voodoo can be enabled and disabled at will simply by removing/replacing the "disable-lagfix" file into the voodoo folder. Its just as easy as that really...
Hope that helps.

I Really think you don't need to since your file system is still rfs,

how do you totally remove voodoo? if i flash back to the last backup i have BEFORE installing bio1.7 voodoo will voodoo still be there or will it be gone?

I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done, then flash a kernal that isn't voodoo.After that then restore your back up. For some reason, I thought my back up was fine, but when I take the disable-lagfix file out, it would reinstall voodoo again when I boot. It might just be me, but I don't think nandroid back-ups restore the kernal. I could be wrong...

Daddy_617 said:
I think you would need to put the disable-lagfix file/folder in the voodoo folder. Then reboot wait until it's done then flash a kernal that isn't voodoo then restore your back up. For some reason before I thought my back up was fine and when I take the disable-lagfix file out it would reinstall it again when I boot. It might just be me but I don't think nandroi back ups restore the kernal. I could be wrong...
Click to expand...
Click to collapse
+1
Yes you need to put that disable-lagfix file into the voodoo folder on the sdcard. Reboot, it will tell you voodoo is being disabled/transformed back into rfs, once finished you can then proceed with your normal flashing routine.

Linda's beautiful voice!!!
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!

Orwell83 said:
I'm a long time lurker, but I've never had anything constructive to say so I've silently read, and slowly learned how to make my phone more awesome. I'm happy to say that I followed these directions exactly and voodoo finally enabled. What a great find! Thanks!
Click to expand...
Click to collapse
Glad to hear another happy voodoo user, and yet more proof that beta4 works on all vibrants including larger nand variants.
Your welcome Orwell

[Q] Help with flashing ROM

Hey guys, new to rooting and mods on phones. i have a samsung fascinate that i rooted on saturday. installed rom manager, root explorer, clockwork and ti backup. the problem i am having is that when i attempt to flash the super clean rom from jt1134, by using the rom manager. it keeps giving me a few different error messages. on is E: failed to verify whole-file signature and E:Signature verification Failed. Through my research i tried dl'ing the zip form to the sd card, and similar messages came up. please help. Thanks

Can I make a recommendation? Dont instal any roms as of now. None are true custom roms. All still have the touchwiz running. None of the roms run bug free and all see Force Close errors!!
Your better off...just rooting, Install lagfix from market, and use launcherpro.
Ive tried the custom roms and honestly not worth it till froyo comes.

stupid question but what exactly does lagfix do?

Ok ive noticed it fixes how slow the market reacts when opened, also speeds up when page loads somewhat.....if you use the LagFix in the market it has a option in the app to remove it if you dont like it , but im sure you will. Stay away from Voodoo LagFix it can be tricky.
Download oclf from market
give it root access
choose to install EXT2 Tools
Then go back and install Lag Fix V1+
This is the only lag fix i know of that be removed by the app itself no outside programs.
Trust me the roms that are out you wont notice anything special from them. all they do is remove apps!!! Wait till cyanogen releases his rom for Fascinate. He makes the best Roms period!!! And he just made a beta for the galaxy lineup....but the fascinate will not see any true roms untill froyo is released!!!

whats the eta on froyo? seems like it keeps getting pushed back.
the cyanogen rom was the entire reason i wanted to test it on the fascinate(i didn't know it wasn't available yet). i had a buddy with it and it seemed to be a super powerful rom.
thanks for all the info martyotaku

From the looks of it.... not till January! Was supposed to be this month. Who knows might still happen.
Honestly if I'm you if your in your 30 days return it and wait for something else. Samsung is known for horrible support.

It sounds like you haven't actually installed CWM... Did you just try to flash it via ROM Manager? Because that won't work. You actually have to flash it using Odin. Once you have CWM successfully installed, you can flash ROMS, kernals, etc...
And I would stay away from the OCLF. A lot of people have been having problems with it, just like VooDoo. Once I uninstalled it, I noticed significant battery life increase. All the lag fix really does is artificially inflate quadrant scores, which don't really count for much anyways.
I've been running JT's Super Clean ROM and I can easily go 48 hours without a charge... No where near that on the stock ROM

just bought cwm from the market and installed.
which i didnt do before. i assumed when i dl rom manager and did that recovery it was already installed.
went to see how super clean acted and tried to redo the flash. still gave me the same two error messages.

Again, you have to flash CWM through Odin, you can't just install it and it magically work

gotcha. ill research how to use the odin ect.... thanks kevin

No problem!
Here's the thread on how to do it

And I cannot stress this enough...
NEVER, EVER, EVER USE THE "PHONE" BUTTON IN ODIN!!!
ALWAYS, ALWAYS, ALWAYS USE THE "PDA" BUTTON.
You will have an expensive paper weight if you use the "phone" button.
Don't do it.

Well if that happens... I'm going straight to verizon and opsse sorry I dropped it in a lake... Haha
Sent from my SCH-I500 using XDA App

figured odin out... got it installed and did a back up... completely different process.. looks like it has worked. phone is rebooting right now. and ... its stuck on vz symbol for a few min... bammm...very nice!! recommendations from here... sweet themes maybe???
Cant wait to see how it goes from here on out... Thanks so MUCH Kevin. is there any way to give props on this website?

Not that I know of, other than the way you just did!
Glad you got it working.
I'm using JT's Super Clean ROM from ROM Manager with the Dark Gloss theme

i so far like the set up of revolutions v3 w/ circle battery. here in a few i am going to switch to dark gloss mod w/ slide animations...

[Q] D02 Voodoo Lag Fix vs DJ05 - Help needed

So, I'm pretty new w/ Android. Just flashed with voodoo lag fix D02-Kernel-LV-1250 using Dirrk's instructions. This means that I did the following:
- Rooted (was already done)
- Installed CWM (from instructions here)
- Downloaded D02-Kernel-LV-1250 and put on SD card
- Rebooted to CWM and did a backup
- Booted into recovery and flashed kernel
- Rebooted
Now, I see that DJ05 is released. (I even see stuff about voodoo lag fix for it...didn't know that was available.) So, now I wished I hadn't installed voodoo lag fix, because I hear it is difficult to uninstall.
I've tried to do my own research here, but I really don't want to change messing up my phone, so I'm asking for help here. Here are the threads I have sifted through:
- http://forum.xda-developers.com/showthread.php?t=805052
- http://forum.xda-developers.com/showthread.php?t=804784
- http://forum.androidcentral.com/fascinate-roms-hacks/34819-how-go-back-stock.html
- http://www.fascinateforums.com/foru...oms/685-instruction-remove-voodoo-kernel.html
- http://www.fascinateforums.com/foru...everything-you-wanted-know-about-kernels.html
Questions
What is the trade-off b/w D02 and DJ05?
If DJ05 really has the lag fix, is there any benefit of staying on D02?
For future reference, how do I know what kernel version I am using (Voodoo4 vs Voodoo5)?
Understanding what I've done above, what do I need to do to get to DJ05?
Do I really need to flash to stock and lose everything to get there?
And if so, can I use the backup I made in CWM?
If not, and I have Titanium Backup installed and all apps/data backed up, does it matter if I have to go back to stock?
Sorry for the newbie questions for help, but I really want to make sure I do it right. Any help is greatly appreciated.
FYI, this is what I've looked through for the new stuff available (should I go with the last link?):
- http://forum.xda-developers.com/showthread.php?t=869990
- http://forum.xda-developers.com/showthread.php?t=872378
- http://forum.xda-developers.com/showthread.php?t=874809&highlight=voodoo+lag+fix+vs+dj05
Thanks for any help you can give!

1. D02 is just the kernel version and DJ05 is a firmware update so there is really no comparison here.
2. updating to dj05 is worth it because it fixes several issues with the phone.
3. the only way to tell between voodoo 4 and 5 is to read which one you are downloading
4. it's a good idea to do a full wipe of the phone before updating to dj05 and your nand backup before the update will not work properly because the new kernel doesn't work with the old firmware.
5. if using ti-backup then yes wipe
to remove voodoo go to the voodoo folder on you sd and make a TEXT file called disable_lagfox.txt and reboot then LET IT FINISH COULD TAKE UP TO 20 MIN IN SOME CASES so wait it out don't pull battery no matter what.
when you update use the stupidfast kernels if your afraid of messing up your phone don't use voodoo it really is more of a power user option. didn't answer everything on order I know lol but think I coveted most of it
Sent from my SCH-I500 using XDA App

I'd like to add that in some cases the disable_lagfix method might not work. (It's supposed to be disable_lagfix, not .txt and not lagfox lol). In my case, it ran for nearly two hours without doing anything. Don't worry, if it takes that long just pull the battery and use ODIN to return to stock (from Adrynalyn's thread). But obviously make backups before you try to disable voodoo.

lol yea disable_lagfix sry swype error haha and the .txt will be added guess I just was thinking about doing it pc side I'm use to putting my own extension sometimes.
Sent from my SCH-I500 using XDA App

Thanks for the info! I've run out of time to do it before I leave for Christmas, but I'm going to do this first thing when I get back!

DJ05 fixed my GPS to the point of locking nearly instantly.
That's the kicker for me
everything else is gravy

Locked up my Fascinate--please help

I'm a relative newbie and not very tech-oriented, and I appear to have screwed up big time. I'd appreciate any help that can be offered. To cut to the chase, when I attempt to boot up my Fascinate, it gets stuck indefinitely on the Samsung logo.
Here's what I did to screw it up. I rooted my phone when I first got it last year and did a lagfix. It unrooted with the update to JD05. Yesterday I attempted to root it again using two different 1-click methods, neither of which worked. I then followed the instructions in the "Modified CWMrecovery for Odin" thread, not having it work until finally succeeding in getting root using CWM Red. The phone rebooted and was rooted, and everything seemed fine, so I used Rom Manager to Boot to Recovery. This did something strange--it took 15 minutes to get to the recovery screen, with a digital voice periodically telling me how much longer it would take. When I got to the recovery screen the first thing I did was to perform a backup. I think this effort to be safe did me in, because the phone must have already been screwed up then and I think I backed up the screw-up.
I then attempted to reboot and since then all efforts get me stuck on the Samsung logo. I've tried almost all options from the Recovery screen: reboot system now, apply sdcard update.zip, wipe date/factory reset, wipe cache partition, install zip from ascard, and restore. All bring the same locked up phone.
I'd appreciate any ideas to bring my Fascinate back to life!

First off the only way to get to red CWM is to install a voodoo 5 kernel. I'm thinking the voodoo kernel and the one click lag fix don't play well together. I'm sure someone else will step in with more info however I would start by looking for a thred called how to completely remove voodoo. Then try odin to restore. Good luck.
Edit. I read your post again and not sure if u did one click lag fix or just an older voodoo kernel. Either way same result u have to disable voodoo 4 and one click to install voodoo 5. Odin it. The voice u hear was the voodoo kernel converting your system to ext4 if this was the first time you've heard this I think your first lag fix may have been the one click.
Sent from my SCH-I500 using XDA App

Yes this happed to me too. If i take it to the Verizon store will they know my phone is rooted and moded? i need help ASAP

Search the forums on how to properly removed the voodoo lag fix. Then you need to reflash dj05. Voodoo doesn't really do much except for show you a higher quadrant score and limit to what roms/themes you can install. Same thing happened to me. Just do a quick search, I think its in the development section. The easiest way to remove it is with and. Hope this is somewhat helpful.
so fresh and so superclean.

Don't bring it to verizon because you would be defrauding them for your mistake. see if you can access your sd card through the computer and put either a file or folder in the voodoo folder called disable_lagfix and try booting again. If that doesn't help (it is probably too late for that) then you need to flash back to stock through odin. find the thread in development on how to do that. Good luck. Your phone is not broken. Breathe.
Sent from my sch-i500 using dl09 supah clean

Here is the ODIN back to stock if you don't want to bother with removing Voodoo. That should fix your phone with or without Voodoo. It's always worked for me.

THANKS SO MUCH its back to normal i cant thank you enough

Many thanks for all of the help.