Database Users

I may have killed my Vibrant (i kno...wrong sec but my thread is in the rom bible)

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/

[Q] Stuck on samsung mobile screen

Ok i'm running froyo dk28 i installed it using odin,so i wanted to go to a custom rom just to play around a bit but when i try to install the rom when it boots back up it gets stuck at the samsung mobile screen please can someone help me

Maybe its still loading. If not Odin back to stock
Sent from my SPH-D700 using XDA App

datboychuck said:
Ok i'm running froyo dk28 i installed it using odin,so i wanted to go to a custom rom just to play around a bit but when i try to install the rom when it boots back up it gets stuck at the samsung mobile screen please can someone help me
Click to expand...
Click to collapse
Did odin say pass when done? Are you flashing a dk28 rom?
Sent from my SPH-D700 using XDA App

There was an issue. Re odin
Sent from my CyanogenModded (now much more) Epic. (Much thanks to Noobnl)

Yeah odin said past when it was done i have no problem using the tar file but when i'm trying to us an zip file it doesn't go threw and i waited almost 15min and nothing.so then i put my epic in download mode and install dk28 back on it and it works.it gets stuck on all my zip files

what method did you say you were using to install the .zip files?

clockworkmod

Which ROM are you trying to install? Sounds like you might be installing a ROM for DI18 or DK17 (I did something like this the first time I tried flashing).

Quantum ROM v2.5.0

Quantum 2.5.0 is modified to use the ext4 file system, and to be able to use it, you need to do other stuff first to convert it to ext4 from rfs before you can flash and use Quantum 2.5.0. If you dont want to deal with all the extra work, just flash Quantum 2.1.0 or some other DK28 Froyo rom.
If you do feel like messing around with all the extra steps, go to this thread [MOD] Epic4G EXT4 Support [Froyo Only] [No More RFS!][Updated/Fixed] (also accessible through the Epic 4G Development section) and follow the steps there

Problem after installing the wrong Voodoo version

My brother and I both have a Vibrant. He broke his so I loaned him mine for a week. While he had mine (which I've upgraded to 2.2), he installed Android 2.1 Voodoo 4 on it. Little to say, after rebooting, the phone wasn't booting past the boot screen.
I've now followed some instructions from the forum, and have reflashed my phone with Eugene's non-bricking ROM through Odin. The phone boots up just fine now. However, I am trying to install ROM Manager on the phone, so I can reflash my recovery ROM (non Voodoo) - and the Android market tells me it can't install the app due to not having enough free space - though I have over 1GB.
I am guessing this is because the internal disk is still setup in the Voodoo file system, and just enough space was repartitioned for the OS to go back on.
Can anyone help me restore my phone?
EDIT: I've also tried flashing a different recovery ROM through ODIN (with repartition), which also wouldn't let me get past the bootup screen.

I'm taking a wild guess here, I seriously don't know, but did you click repartition in Odin? I think that's would work, but like I said, I'm not completely sure.

I didn't repartition for the Eugene rom fix (as per the instruction I read), but did when I tried to load another version ontop of that.

I was in the Voodoo chatroom, and was able to get some help. It sounds like I need to download a stock ROM and then reset my file partition to get rid of the EXT4 partition, and reset it all to the default.
I have Eugene's "non bricking" rom, but I don't think that's what I need. Can anyone point me in the right direction of what I need and how to do this?

Just search for the stock Odin images and flash back. They should be in a sticky. I would repartition as well.

I am trying to find a stock version I can ODIN flash. Do you know where I can get one?

http://forum.xda-developers.com/showthread.php?t=848737

I've gone through ODIN, done a reflash to the stock firmware, and repartitioned the phone as well.
Now, when I boot the phone up, I get the T-Mobile screen and the Galaxy S screen, and then the phone goes black (with no lights on) and doesn't go any further. My phone has been sitting on the desk like this for 20 minutes now.
I am wondering if this is like when moving to Voodoo, it takes a while to change the format to EXT4, is the phone having to go back to the default?

I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App

this thread might help
http://forum.xda-developers.com/showthread.php?t=848737

fatboy547 said:
I 1am into the same problem with the old voodoo. What you'll need to do is flash back to stock via odin. Ur apps memory will be real low. Flash an old 2.1 voodoo. Let it do its thing once booted put a disable voodoo file into the folder and reboot. It will be ok after that. Hope that makes sense.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Thanks fatboy, but I can't even flash back to stock. The phone won't boot up.

[ROM] Bonsai User Discussion

This post is only for discussing all issues regarding the use of the Bonsai roms. We can talk here about any version from 1.0.0 to x.x.x
Due to some political issues please do not post any links to the Bonsai website! This thread is just for us users and don't expect the developers of Bonsai to ever visit here.
One last thing >
nor

Yes this try to keep this thread open.
Sent From My Evo Killer!

So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Sent from my SPH-D700 using XDA App

I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Were you using CWM 3.0.0.6 or 3.0.0.5 ?
Sent from my SPH-D700 using Tapatalk

Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?

abrcrmdl23 said:
So is there a way to get a 600mhz step in the kernal for bonsai 4.0 last i heard he was going t put it in back in 3.0.1 but still not there. Or is there an easy way to included it in the kernal page file or something that set cpu uses? Also is there a way to get the voodoo color fix or a tweak that works that will make the brightness lower at the lowest setting for 4.0 becase the brightness on this screen is way to brght at night time. I used to have a tweak like this in syndicate rom for 2.1 it was great. Any info would be great thanks guys.
Click to expand...
Click to collapse
I can't remember what stepping is on the kernel as we have been beta testing 4.0.1 and have been mainly dealing with a new setCPU governor called interactive. Were also still working on the other governor called smartass as well. I think that the stepping goes directly from 400 to 800, but we are always looking to go faster and with better battery life. I'll bug Randy and Mammon about it.
The sound will be Voodoo version 7, but I don't think the Voodoo color fix is going to make it into 4.0.1. Sorry, but we can't do everything...at least not all at the same time.

forcelite said:
I installed bonsai 4.0.0.1 and it flashed fine, then it tried to restart and got stuck at the samsung boot screen, would not go past that.
So I battery pulled and tried to install another rom (verion 4) and it had an error in CW installing,
Then I tried installing a rom I have used before (epic experience) and CW would not install that one either.
So I used Odin to go back to stock everything and then unlocked it and now I am on a stock rom rooted.
Why do you think it is hanging there? I am scared to flash again as I think it will do the same? But if the forum needs the exact error msg I will install it again as I really want to get this rom working.
Thanks,
Force
Click to expand...
Click to collapse
Did I see a similar post on the Bonsai website earlier today? I just want to verify that you were using CWM 3.0.0.6 as anything else will cause problems like that. Also when you get to these kinds of problems you should attempt a second flash of Bonsai before going to the trouble of a ODIN job. A second flash seems to fix a whole variety of odd kind of problems.
As you can imagine with all the beta testing I do I'm always finding ways to corrupt my phone. Some days I have managed to bork it 3-5 times.
I decided to test out today a 4.0.1 install directly from DI18 > CWM 3.0.0.6 > Bonsai 4.0.1 full rom. It went great with no problems at all and running just fine, so far

I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0

bluetooth
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?

forcelite said:
Good question as i was just going to as a question about EXT4 and CW.
The rom manger is version 3.0.1.4
however the CW mod flashed is version 3.0.2.4
It only has 2 to choose from in rom manger, 3.0.2.4 or an older 3.0.1.4
Not sure were people are getting these other versions from.
Force
PS I booted into CW and saw it was v2.5.1.0
am I way off?
Click to expand...
Click to collapse
Do not use Rom Manager to be installing the beta CWM files. The correct way is with one of the 1 step CWM tools in the development forum. 3.0.2.4 is half-finished and is very difficult even to navigate through the various menu's. I know this because I tried out that CWM version for some grins one day. It will majorly screw your Epic if your not extremely careful. When DI18 was prevalent Rom Manager worked great to root your phone. When we started the move into the Froyo roms Rom Manager quit working and that is why the 1 click then became more prevalent.
Just follow the directions posted all over the place and Bonsai will install just fine and you will be a happy camper.

I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Thx All,
Force

forcelite said:
I think that is my problem, I am using a the CW that came with the one click unroot.
So I guess I need to do this, even if I am already rooted?
http://forum.xda-developers.com/showthread.php?t=897612&highlight=EXT4
PS
I booted into CW and saw it was v2.5.1.0
Click to expand...
Click to collapse
The linked one is the correct one for Bonsai version 4.x.x.

olddocwhite said:
I could not get bonsai 3.0.1 or 4.0.0 to pair with my bluetooth headset. Tried pairing on an epic with acs 1.1 and paired fine. Anyone else have a pairing problem?
Click to expand...
Click to collapse
Some people do and some don't I do know that Randy has instituted quite a few bluetooth linux upgrades into 4.0.1 rom. Some people are able to clear the data, but the problem usually reappears. Mattalica76 has the link to a more permanent fix to this problem, give him a PM.

Duplicate... Sorry

forcelite said:
I am installing it now after updating to CW3 (from CW2.5) . I think it will come out fine now, I am an idiot and didn't realize the original one click root installed an older version of CW.
Click to expand...
Click to collapse
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.

Actually it didnt boot this time either, it installed the firs ttime fine, then kept booting after samsung in a loop,
So I went into CW3 and tried to flash bonsai 4.0.01 again and it gave me this error. It is long, however I shortened it, I have the whole error photo copied)
Finding package
Opening package
Install update
Assert failed getprop (“ro.product.device)”)
Sph-700
E:error in /SDcard/bonsai……….
(status 7)
Installation aborted

Top Nurse said:
Don't beat yourself up as we all have been there. It's a process of learning new skills and a new language. Give yourself a pat on the back for getting through this when 98% of the world would have said screw it or not even tried at all.
Click to expand...
Click to collapse
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
CWM3 will convert your filesystem to ext4 the first time you boot into it. It won't touch the sdcard so that won't be converted. After CWM is finished with the conversion, do not reboot the phone, you will then flash Bonsai.

forcelite said:
Thanks for the support T Nurse,
I loaded the EC05 stock from Odin as I still dont have a grasp on EXT4 file system.
last thing I tried was cw3.0.0.6 and loaded Bonsai and it installed, just hung at samsung screen. might be a corrupt rom file.
1) So after flashing CW3, bonsai is supposed to change the file system over to EXT4 automatically after flashing, correct?
2) will windows 7 be able to read the sd card after it is changed over to ext4 (by bonsai), or will it have 2 partitions, one windows can read fat32 and the other ext4 it cant.
Click to expand...
Click to collapse
After flashing the boot script of cwm 3.0.0.6 you then have to power off. Then hold down the camera button, vol down, and power keys at the same time and the EXT4 script will automatically start to format your system. Please keep in mind that it is not formatting the SD card, but only the read only memory of the phone.
After you finished a few beers it will be done and will drop you back to cwm. Do not reboot, but flash bonsai. After bonsai is finished then reboot.
Sent from Bonsai 7.0.3

help(resolved)

Hey I just seriously screwed my self over bassicly I tried to get miui to boot from the samsung fascinate however when I installed it in cmr it spassed out then powered of then went to the bootloader and I get a red error message saying can't mount data or something so then I tried to reinstall Eco 3 Odin using Odin and it worked it booted but it says I have zero data on my phone and I can't install anything. I also tried the oneclick soft unbricker but it fails saying adb divers are not installed when they are. I'm doing this on my phones browser witch is the only thing that seems to be working right now I also tried a band restore but I got the same data error message.

Have you tried restoring to DL17 and then re-upgrading to 2.2?

And how about a good old odin flash?
In worst case, I would ask imnuts for the full odin package, or use a fascinate full odin package to get you off your feet, then reflash the modem, and recovery, then wipe In recovery cyan cwm... Then flash ec03
Sent from my SCH-I400 using XDA Premium App

wait wait, is this on a Continuum or Fascinate?

Nuckin said:
wait wait, is this on a Continuum or Fascinate?
Click to expand...
Click to collapse
He is on a Continuum, but you can use a fascinate Odin package to reformat partitions if they get messed up, then just reflash recovery and start fresh if you can get in then... That wasn't a really good thing though to suggest to a newcomer necessarily, so thank you for pointing that out

okay heres what happened firts i wanted to see if i could get the miui rom for the samsung fascinate to boot on the continuum there pretty much the same phone minus the ticker and screen size so i went into clockwork mod and wiped everything then went to install zip from sd card and clicked on the miui rom witch was the process we always used on the hero. then after i clicked on it, it started to install then my screen started shacking and my phone turned off. when i turned it back on it when to the bootloader and a red error message poped up saying
e:cant mount /dev/blockstill(invalid argument
and when i go to recovery it says the same thing when i try to wipe/restore nand it says the same thing. so at that point i powered off and went to download mode and reinstalled eco3 odin using pda mode on odin and it worked then it rebooted and i got to the set up screen and i got 2 force closes daily brefeing and something else i went ahead and skipped all that stuff and it loaded fine after that. however now for some reason it says i have zero system memory so i cant install any apps or save data however it does recognize my sd card but i cant install to sd card. so bassicly the phone functions just no internal memory. at this point i honestly dont know what to do everything on the hero was simple and straight forward and we never ran into these kind of problems. ive also tried to restore my nands and reinstall clockwork mod but still no dice. what i need to do now i guess is get the necessary files to go completely stock and see if that helps. and if someone could point me in the direction to those files i would really aprechiate it. oh and i tried the one click unbricker it sayed success but didnt really do anything.
oh and i know trying to install miui was stupid but i was just wanting to see if it would boot lol.

Download the PIT file in the Development forum, as well as the DL17 Odin package from the FAQ of the EC03 post I made. Flash the DL17 in PDA, with the PIT, and re-partition selected. After that, you should be back on DL17, and can do whatever you want from there.

huzzza!!!
thank god that worked thank yall so much i still cant believe that just happened but restoring the stock odin image worked and all is well. so i guess tommorow i can reroot and restore my nand.
once again thank yall for the help.