Fresh ROM install - Force closeing everything - Vibrant Q&A, Help & Troubleshooting

Hey guys,
Just Flashed to Bionix -V 1.3.1. Trying to restore all my apps and data with Titanium but it force closes pretty much anything i try and open. Is there something I have to clear before i can restore all my apps and data?

dont restore anything that has "SYSTEM DATA"

I dont think explained myself properly the first time. I mean anything i pretty much try and open that wasnt orignally on the phone gets forced close. Carhome, Opera mini, pingchat, reddit app, most of the games. Also id like to include that most of my apps were already restored when the phone booted up for the first time. Should I just reflash the rom?

if your apps and everything were there upon first boot it sounds like you had a bad install, something in the updater script got messed up when you downloaded. Redownload and Reflash sounds like your best option.

Yeah, something is not right there. A good install would wipe your phone (none of your apps should be there).
I would personally suggest going back to stock and then flashing. Its a super easy process and I wrote a guide in my signature, may help.

OK so ive redownloaded bionix and ive put it on the internal sd card. I rebooted in recovery. disable lagfix and rebooted. now its just sitting on the Vibrant boot up screen.... for about 15 minutes now.
I thought this **** was supposed to get easier..
NVM its rebooting now. Im reflashing it now, ill let you know after the reboot how it went.

Fixed.
Just restored 229 apps. **** me.

So is everything good?
Note that usually before flashing you are supposed to do a factory reset was it? I forget but the EDT Roms had the correct procedure to do in clockwork right before you flash a ROM so that you don't get issues like this. If your issue is still not resolved, look up an EDT ROM page and look the installation procedure.

Related

just attempted to flash 1200.zip and am getting tons of forced closes

very odd ... nandroid restore i have a feeling its gonna be
Well good luck with a nandroid if it's voodoo.
As a last resort...
theres a "Odin Restore files to get you to stock - xda-developers" thread, sorry can't link yet but yeah you can find that one easily
try wiping and see what happens
Clearing delvik cache normally helps with force closes in my experiences with clockwork and android.
Sent from my SPH-D700 using XDA App
So basically I factory restored and I'm doing okay now. I tried to go into clockwork recovery and restore my latest backup and I just get the force closes again but I'm safe to assume I do not have root currently so should I re root them try to restore my backup?
Did you flash a regular kernel over voodoo without disabling?
Same Problem.
I had this problem. Unfortunatly I did not have a backup, no biggie for me. I had to restore to stock using ODIN, then wipe data and had a brand new phone. I attribute it to the fact that I started changing Kernals more than my underware. After re-rooting I am ready to start flashing Kernals again, which means I will more than likely be restoring to factory again..... Maybe I should back-up current ROM. Oh, and I did flsh a ROM over Voodoo, don't do that.
well i have a backup but yes i tried to flash the 1200 zip over a deodexed system with voodoo lag fix ON so im guessing i shouldnt of done that. im getting super slow boots and still a **** load of force closes ... so im thinking the odin fix and starting fresh is the way to go for me.
so i flashed the restore through odin and i think im okay ... normal boot time and everything seems to be working fine ... had to format my SD card and everything. im gonna reroot and start everything over .. wish me luck!! haha
EDIT: well i spoke too soon im not getting any cell service on my device now hmm
EDIT: nevermind i do have service google just isnt connecting hmm this is ****ty
I just want to stress out how important it is to read every single word in the instructions and follow every single word....please check the stickied thread at top on how to install voodoo kernels...it has all the links you need....but seriously, many people have flashed tons of kernels and did many changes without a single hiccup... If things went wrong, then you misses an important step.
tats_06 said:
I just want to stress out how important it is to read every single word in the instructions and follow every single word....please check the stickied thread at top on how to install voodoo kernels...it has all the links you need....but seriously, many people have flashed tons of kernels and did many changes without a single hiccup... If things went wrong, then you misses an important step.
Click to expand...
Click to collapse
+1
Sent from my SCH-I500 using XDA App
I followed everything and when I disabled it, like have 15 times before, it just got caught in a bootloop and I had to restore yesterday. I think the voodoo fix we have now is just really touchy.
Same deal with mine
I've been swapping the voodoo kernels like crazy the last couple days and just found JT's "1200_interactive_bfq". Figuring I was running voodoo kernels and not that bogus lagfix junk, I used CWM and loaded JT's kernel. When it booted I got tons of the force closes and was unable to absolutely anything with the phone. Here's the simple way I got mine back to operating...
-Shut off phone
-Hold down volume key while powering up to get into factory boot loader mode.
-Once in, run update.zip to get into CWM
-Once in CWM installed the last voodoo kernel I had been running and rebooted the phone.
-Good as gold.
Now...in order to install the new JT interactive kernel do I have to disable the voodoo kernel or do I have to go back to a stock kernel first?
~Johnny

How I fixed my phone

So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.

[Q] 1st day with Vibrant lots of questions need some OCLF ROOT help

Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.

galaxy Note Force close Cant unlock

Alright So I am new to this forum but Im not new to the scene. I cant figure this problem out after days of searching and restoring. So I just got my note last week been loving it coming from my old 4s. Anyways My problem is I did a fresh factory restore rooted with dags kernel (tried both stock root and Oc kernel). I have clockwork recovery installed btw. So usually everything goes smooth. I clear all caches phone boots up runs smooth, I install root then my basic apps. Now I was doing them one by one and restarting.
Well long story short. At random any one of these times I reboot the device I come back into the lock screen Ill unlock and it force closes everything and just keeps rerunning media scanner looping. (force close twlauncher calenders google sync etc like really anything usually its twlauncher thats first I click ok it goes back to lock screen freezes for a second then reboots media scanner. It doesnt find service or even attempt it. The only thing I can do is restore and try again. I have done this over 10 times just this past week. I have fixed permissions in both rom manager and clockwork. Though it was good until last night it just completely restarted on its own and when I booted back up it was force closing.
I even did a fresh format wiped everything reinstalled stock att unrooted Rom then rooted and I have to be afraid of my phone dying or just randomly crashing and that when I restart its not gonna make it back into gingerbread without a restore. Now this will happen whether I have no apps or some apps. I can seem to find anything triggering it. Is this a defect in the phone maybe? Should I restore to stock and exchange at at&t or am I missing something? Please help guys. Ive only been able to get about a day before everything force closes. And that is unacceptable for an 700 dollar phone when all these others are running smooth.
Did you happen to mess with any overclock values? I had the problem you explain only after I overclocked to much and it was unstable
Solution: put into download mode and flash back to total stock with odin and start over. It worked for me. Restoring backup did not work
Sent from my SGH-I717R using Tapatalk
It is a problem with CWM. You should look for and download darkside super wipe. If I were you I would probably flash the stock Odin tar and start fresh. Make sure you install the latest CWM.. I believe beta4. You should not have to reboot your phone after every new app install.
Use the super wipe from in CWM (install from zip) and then use Odin to get back to stock.
You most likely have an older version of the CWM, I don't think anyone has reported any problems with beta 4 and force closing issues.
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
h3r3tic said:
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Click to expand...
Click to collapse
The version of CWM you were using was most likely for the international Note and therefore incompatible with the Note you have.
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
h3r3tic said:
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
Click to expand...
Click to collapse
You may want to join the IRC channel and see if anyone there can offer you a solution.
irc.irondust.net
#attgalaxynote
Just for Clarification
I too had the TwLauncher issue and tried clearing the Dalvik cache, cache, etc. This then sent me into a boot loop into recovery. (My CWM is the 5.0...version too). Tried the restore, no luck, wipe, no luck etc.
My PC doesn't see the phone, so I need to basically start the root process over again and install the Beta4 CWM. Am I understanding correctly?
I have the same problem and its driving me crazy. Can some one please help me out step by step Im new to this any help would be gratefully appreciated

[Q] Custom roms - I might have messed something up

I only recently got into the whole rooting deal, but i followed the instructions precisely double checking and everything went along well , after that i installed most of the apps from here, made a full backup with titianium backup, but then i decided to try and install a custom rom, which was where i made my first mistake, i made a backup of the current(stock) rom and then went straight on to downloading cyagenmod 7.2 to try it out on my phone.
When i started the install i obviously had the pre install options, i only left the one check there which was wipe delvik cache i think figuring that was all i needed to do. Phone rebooted and the loading logo started but didnt go past it and after it had reappeared for 3 times the screen just went in a white screen with differently colored horizontal stripes, i thought my phone was now bricked, but i managed to turn it off and turn it back on and get into recovery mode. I tried to do a recovery which didnt do anything, after that i just selected factory reset thinking it will get me back to the stock rom, but instead CM worked and finally got past the loading logo, i checked in the CWM if i had the backup i had made before trying to install CM and it was gone.
I want to know what i have done wrong(i obviously have), how can i reverse it and how to install roms properly(preferably in simple language). I already found this thread.
Phone: LG Optimus Hub (E-510)
P.S. I am missing the Play store app, is this normal for CM?
1. You got into bootloop because you didn't do factory reset/full wipe (the /data partition wasn't wiped, files on this partition were from stock ROM and weren't compatible with CM) -> this is the reason why it booted after full wipe. Full wipe only deletes data, it will not restore stock ROM.
2. '... i checked in the CWM if i had the backup i had made before trying to install CM and it was gone'
Are you sure you made a backup? Or didn't you delete it?
3. For the Play store - CM ROMs ussually don't have Google Apps in them, you have to flash them after CM installation (look in the ROMs thread for Google apps/ GApps)
1. Thanks for the explanation, im defineatly going to keep in mind to wipe the next time i attempt to install a custom rom. Is the stock rom still in my phone or do i have to look online for one?
2. I belive you are right, i do remember wanting to do a backup, but i might have forgotten about it, i did one now so i can have something to go back to just in case.
3. Dont really understand this, can you please direct me to a thread for this? I tried doing the flash CWM recovery which didnt do anything, could i try using my backups from titanium backup to get the apps back on the phone? It would be quite a mess to get all of it downloaded again.
Edit: i tried installing google play downloaded from other sites and whenever i go into it, it asks me to add an account, but when i press yes, it just closes.
|Madman| said:
1. Thanks for the explanation, im defineatly going to keep in mind to wipe the next time i attempt to install a custom rom. Is the stock rom still in my phone or do i have to look online for one?
2. I belive you are right, i do remember wanting to do a backup, but i might have forgotten about it, i did one now so i can have something to go back to just in case.
3. Dont really understand this, can you please direct me to a thread for this? I tried doing the flash CWM recovery which didnt do anything, could i try using my backups from titanium backup to get the apps back on the phone? It would be quite a mess to get all of it downloaded again.
Edit: i tried installing google play downloaded from other sites and whenever i go into it, it asks me to add an account, but when i press yes, it just closes.
Click to expand...
Click to collapse
First things first. Before you do anything else you need to do some reading in order to understand the Basics of Android. Otherwise your going to get yourself in a bind again. In my Signature your going to see some links if your on a PC. You should check them out, they will help with answers to a lot of your questions.
I cant thank you enough, i was looking for something like this! :good:
I will have something to read in my spare time, as little of it i have trough.
Your welcome . Glad I could help.
TEAM MiK
MikROMs Since 3/13/11

Categories

Resources