So I have come to the decision that I am going to remove root from this phone. I think that no matter what I do, something always happens to the recovery partition, getting a little tired of having to put it back on as it also removes my memory card from use as well.
I am not sure where the problem lies that causes the memory card and the recovery partition to go missing, my first thought would have been the Xposed framework, but I ruled that out as I installed that, straight after the pre-rooted Rom. That would leave it at either the Xposed APK install, any xposed modules or another APK. I like messing around with the idea of a rooted phone, but with having to redo the recovery install, its annoying, I have done it for the 4th time in 2 days.
If anyone has any suggestions to why this is happening, I am happy to listen, as I don't want to go back to stock ROM, but find that its just to troublesome to keep root on.
demon148 said:
So I have come to the decision that I am going to remove root from this phone. I think that no matter what I do, something always happens to the recovery partition, getting a little tired of having to put it back on as it also removes my memory card from use as well.
I am not sure where the problem lies that causes the memory card and the recovery partition to go missing, my first thought would have been the Xposed framework, but I ruled that out as I installed that, straight after the pre-rooted Rom. That would leave it at either the Xposed APK install, any xposed modules or another APK. I like messing around with the idea of a rooted phone, but with having to redo the recovery install, its annoying, I have done it for the 4th time in 2 days.
If anyone has any suggestions to why this is happening, I am happy to listen, as I don't want to go back to stock ROM, but find that its just to troublesome to keep root on.
Click to expand...
Click to collapse
The easiest way I guess is to flash the FTF again and uncheck the Wipe Data option (to maintain you data).
I know how to remove it, just wondering if anyone has any idea why I keep having the problem.
Sent from my C6903 using XDA Free mobile app
Well, I've done some testing here and if I remove the SD Card I can't boot to recovery too. Maybe the SD Card is where something crucial to it lies. The fact that your SD Card keeps being removed is another question. Maybe a faulty unit? Did you try with another one? Or even maybe some water have reached the SD slot and there's rust there...?
Rhadamg said:
Well, I've done some testing here and if I remove the SD Card I can't boot to recovery too. Maybe the SD Card is where something crucial to it lies. The fact that your SD Card keeps being removed is another question. Maybe a faulty unit? Did you try with another one? Or even maybe some water have reached the SD slot and there's rust there...?
Click to expand...
Click to collapse
The first time I did the root for my handset I was using a 2GB San Disk SD card, it happened on that one too, that is one of the reasons I purchased a Class 10 Samsung SD Card. So therefore I am thinking that there is something that I am putting on whether it be Xposed or an APK, I am fairly certain that it has to do with one of those.
So I've worked out that it had to be either an apk or xposed or a module that's causing the recovery and sd card to go missing, as I put everything on first and then put the recovery back on and so far no problems and is been about 12 hours (touch wood)
Sent from my C6903 using XDA Free mobile app
Related
i wanted to know if you can install dreaimg.nbh through android sdk without using the sd card? i want to know this because i cant use my sd card at all and all of a sudden ive been getting force closes for every single action i make on the phone (main one i get is process com.android.inputmethod.latin and i cant text or go to my contacts. in short it force closes everything). i want to bring it back to factory and was thinking that might fix my sd problem. so please help, im getting annoyed with this and i dont want to go back and use my crappy samsung mysthic.
bluizzo said:
i wanted to know if you can install dreaimg.nbh through android sdk without using the sd card? i want to know this because i cant use my sd card at all and all of a sudden ive been getting force closes for every single action i make on the phone (main one i get is process com.android.inputmethod.latin and i cant text or go to my contacts. in short it force closes everything). i want to bring it back to factory and was thinking that might fix my sd problem. so please help, im getting annoyed with this and i dont want to go back and use my crappy samsung mysthic.
Click to expand...
Click to collapse
does anyone know how to plz i have the same problem wit the sd card reader i wipped my phone and its not allowing me to flash anything from the zip card and its ot the card its the reader so does anyone know how to fix??
First, both of you need to rule out SD card falilure/user error. Does your card work in your computer? Can you format it to FAT32? If you can and your phones can't see it or any other cards.... you might as well get a new phone. As far as LatinIME FCs, go download any VK from the market or install HTC IME (which is way nicer anyway), go into settings-locale&text and uncheck stock VK, check whatever new VK of your choice is. That will stop FCs
borodin1 said:
First, both of you need to rule out SD card falilure/user error. Does your card work in your computer? Can you format it to FAT32? If you can and your phones can't see it or any other cards.... you might as well get a new phone. As far as LatinIME FCs, go download any VK from the market or install HTC IME (which is way nicer anyway), go into settings-locale&text and uncheck stock VK, check whatever new VK of your choice is. That will stop FCs
Click to expand...
Click to collapse
thanks that fix one of my issues. know i cant txt or go to my contacts without them FCing, dammit i do need a new phone
borodin1 said:
First, both of you need to rule out SD card falilure/user error. Does your card work in your computer? Can you format it to FAT32? If you can and your phones can't see it or any other cards.... you might as well get a new phone. As far as LatinIME FCs, go download any VK from the market or install HTC IME (which is way nicer anyway), go into settings-locale&text and uncheck stock VK, check whatever new VK of your choice is. That will stop FCs
Click to expand...
Click to collapse
but is their no way that i can install a rom or anything thru adb or sumthing cuz like my phone doesnt have any rom on it right now so yeaa i havent used my g1 in like maybe 2 weeks=( so like i just wana load a rom and be able 2 use my phone i really dont care for da sdcard
If your SD card is broken, get a new one.
How can you logically expect to use the phone without one? I'm aware you CAN, but I mean there are so few ROM's out there that don't use A2SD, let alone you can't make nandroid backups, and some apps can't store data. Maybe I missed something, but is there a reason you can't just use a different SD card? You can buy an 8gb class 6 MicroSD for under $20. If you can afford the $200-500 phone....
Crazydrumerkid13 said:
but is their no way that i can install a rom or anything thru adb or sumthing cuz like my phone doesnt have any rom on it right now so yeaa i havent used my g1 in like maybe 2 weeks=( so like i just wana load a rom and be able 2 use my phone i really dont care for da sdcard
Click to expand...
Click to collapse
It is possible if you unpack the update.zip and manually copy everything over to the right place, then flash the boot.img with fastboot.
Surely it's simpler to just buy a cheap card though? Without a2sd your choice of what to flash is going to be severely limited.
the sd slot does not work at all. i have 2 sd cards a 1gig and a 4 gig(class6), the problem is the rom is acting up and i cant correct the phone without reverting back to stock, but in order to do that i need the sd card slot to be working. thats why i want to know if you can push the file to the phones ram and try booting it from there or even do it from the computer. and i also wanted to see if bringing the phone back to stock would probably fix the sd slot. so if someone has an idea im open to trying it out
I am having issues with my phone. I flashed the SlideItUp beta rom and it loaded fine. However when I wiped to flash another Rom, I get a bootloop for any rom I flash. I am not sure why. I have several Nandroid backups and I have been able to get 2 of them to boot up completely. However, I am not able to modify any files on my SD card. I cannot download anything, I get message that memory is full. I cannot delete anything, it shows deleted, however if I reboot the file is back and untouched.
What suggestions does anyone have to resolve this issue?
beamer069 said:
I am having issues with my phone. I flashed the SlideItUp beta rom and it loaded fine. However when I wiped to flash another Rom, I get a bootloop for any rom I flash. I am not sure why. I have several Nandroid backups and I have been able to get 2 of them to boot up completely. However, I am not able to modify any files on my SD card. I cannot download anything, I get message that memory is full. I cannot delete anything, it shows deleted, however if I reboot the file is back and untouched.
What suggestions does anyone have to resolve this issue?
Click to expand...
Click to collapse
I experienced the same issue (but with what ROM I can't recall). I got different error messages though.
I had to backup my files to my computer, complete wipe of phone, reformat sdcard, repartition mysdcard, put files back on sdcard and then flash the ROM of my choice. No problems since.
Thanks! That was what I was thinking my next step would be. Just do not like doing it!
beamer069 said:
Thanks! That was what I was thinking my next step would be. Just do not like doing it!
Click to expand...
Click to collapse
Same here.
But just like everything in life....you gotta do what you gotta do.
SD card connection
I have heard of a few people having a dirty connector in their SD socket. My problem was that after less than a year, something physically broke, so my socket wasn't making a good connection to the card consistently. So I got the whole phone replaced and it works great now.
I would start with cleaning the files and repartitioning. If that isn't working, maybe blowing the dust out or cleaning the contacts somehow.
I will try this next if repartitioning does not work. I have removed my memory card maybe 3 times since I have gotten the phone.
schnogg said:
I have heard of a few people having a dirty connector in their SD socket. My problem was that after less than a year, something physically broke, so my socket wasn't making a good connection to the card consistently. So I got the whole phone replaced and it works great now.
I would start with cleaning the files and repartitioning. If that isn't working, maybe blowing the dust out or cleaning the contacts somehow.
Click to expand...
Click to collapse
So, I was using a 4gb SD card class 4 and it worked flawlessly, but a few days ago i bought a 32gb class 10 Sandisk SD and it worked just fine for a day, after doing http://acetips.wordpress.com/2011/09/19/how-to-force-install-apps-to-sd-card-without-root/ process. The next day, my cellphone got stuck and it restarted a few times, and every time it turned on it recognized some apps and others not. After that I formatted it from both my cellphone and from my pc and it kept happening. Sometimes, after turning on the cellphone it says the SD is damaged and asks me to reformat it again. I even reverted the process mentioned before and rooted the cellphone, but the SD is still buggy as hell.
Anybody has any idea as to why this might be happening?
Im using the Galaxy Ace s5830L with stock rom and kernel.
Moxxxi said:
So, I was using a 4gb SD card class 4 and it worked flawlessly, but a few days ago i bought a 32gb class 10 Sandisk SD and it worked just fine for a day, after doing http://acetips.wordpress.com/2011/09/19/how-to-force-install-apps-to-sd-card-without-root/ process. The next day, my cellphone got stuck and it restarted a few times, and every time it turned on it recognized some apps and others not. After that I formatted it from both my cellphone and from my pc and it kept happening. Sometimes, after turning on the cellphone it says the SD is damaged and asks me to reformat it again. I even reverted the process mentioned before and rooted the cellphone, but the SD is still buggy as hell.
Anybody has any idea as to why this might be happening?
Im using the Galaxy Ace s5830L with stock rom and kernel.
Click to expand...
Click to collapse
You can't force move apps to the SD without root cleanly. You'll get problems. That's the whole point of rooting and what it stands for. If you're still after your warranty, there's an unroot file with the rooting one depending where you got it from. There's a thread here on XDA with both files. Then you can just install your carrier's rom and you're good to go.
You will need root for A2SD, and even then you gotta be careful how you do it. There are some apps and scripts that do better jobs than other ones.
SuperAce609 said:
You can't force move apps to the SD without root cleanly. You'll get problems. That's the whole point of rooting and what it stands for. If you're still after your warranty, there's an unroot file with the rooting one depending where you got it from. There's a thread here on XDA with both files. Then you can just install your carrier's rom and you're good to go.
You will need root for A2SD, and even then you gotta be careful how you do it. There are some apps and scripts that do better jobs than other ones.
Click to expand...
Click to collapse
Yes, I reverted the process mentioned before and I rooted my phone and moved apps with Link2SD and the same thing happened. After rebooting my phone once it stopped recognizing some apps randomly (it says the ones that the phone doesn't recognize are not installed). But when I switch to my 4GB SD card it works fine. Then I formatted the card and the phone and tried to make a partition but as you know it didn't work.
Maybe it's a size problem, I don't know. It's not that I need that much space but I will not even think about space with that SD card and also I've already bought it, haha. I'll go to the store where I bought it tomorrow anyway.
Thank you again for your time!
Maika7 said:
Yes, I reverted the process mentioned before and I rooted my phone and moved apps with Link2SD and the same thing happened. After rebooting my phone once it stopped recognizing some apps randomly (it says the ones that the phone doesn't recognize are not installed). But when I switch to my 4GB SD card it works fine. Then I formatted the card and the phone and tried to make a partition but as you know it didn't work.
Maybe it's a size problem, I don't know. It's not that I need that much space but I will not even think about space with that SD card and also I've already bought it, haha. I'll go to the store where I bought it tomorrow anyway.
Thank you again for your time!
Click to expand...
Click to collapse
Oh alright. Good thing you solved it. Also, I don't recommend Link2SD as it doesn't free that much space compared to better alternatives like INT2EXT+ or DT's A2SD.
SuperAce609 said:
Oh alright. Good thing you solved it. Also, I don't recommend Link2SD as it doesn't free that much space compared to better alternatives like INT2EXT+ or DT's A2SD.
Click to expand...
Click to collapse
Still didn't solve it
Yes, I know that now. When I change the SD card or find what's the problem I'll start from the beginning and I won't use Link2SD.
what partition type did you put on your sd card? n its possible that the partition is corrupt i had a similar issue not so long back
i formated the whole sd card using minipartion tool then made a 2gd ext4 split works fine now
I followed this tutorial to make the partition http://forum.xda-developers.com/showthread.php?t=1477996 (not sure what type of partition it is). But the SD card had been working bad before I tried to make the partition.
Sent from my GT-S5830L using xda app-developers app
Anyone else experiencing an issue with the micro sd slot after rooting? it wont read the cards, but it does notice when you remove an sd card. Is there a fix for that issue and has anyone else encountered it?
dcoke said:
Anyone else experiencing an issue with the micro sd slot after rooting? it wont read the cards, but it does notice when you remove an sd card. Is there a fix for that issue and has anyone else encountered it?
Click to expand...
Click to collapse
How do you know it is not reading the card? Have you looked at ext_sdcard to see of it is there?
And how did you root 2.0.4? Most folks get automatically updated to 2.0.5.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
leapinlar said:
How do you know it is not reading the card? Have you looked at ext_sdcard to see of it is there?
And how did you root 2.0.4? Most folks get automatically updated to 2.0.5.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
Click to expand...
Click to collapse
feel free to steal this little tip from me:
When starting from scratch after purposefully activating the 8 Boot Fail Safe, when it gets to the part where it's looking for an update, while its looking hold down "Power" and select OK to turn the device off interrupting the update process. When you turn it back on, you'll have to start the whole thing over again, but when it gets to the Update step it bypasses it thus cancelling out the 2.0.5 mandatory update. Now that you have 2.0.4 you can run your all-in-one and update cancel program before it has a chance to try updating again.
-Another helpful hint after reverting to stock firmware, turn off your internet until you run all the rooting software.
No I didn't check to see if it showed up in a root explorer.I'll check that out.
.....
Just checked and no it doesn't come up. I even removed and reinserted the microSD in question and still nothing. The little SD logo pops up on the screen (the big blue vector image one) but it never gets read in the device in system or root explorer.
Is there a way to fix it on test disk for windows?
dcoke said:
feel free to steal this little tip from me:
When starting from scratch after purposefully activating the 8 Boot Fail Safe, when it gets to the part where it's looking for an update, while its looking hold down "Power" and select OK to turn the device off interrupting the update process. When you turn it back on, you'll have to start the whole thing over again, but when it gets to the Update step it bypasses it thus cancelling out the 2.0.5 mandatory update. Now that you have 2.0.4 you can run your all-in-one and update cancel program before it has a chance to try updating again.
-Another helpful hint after reverting to stock firmware, turn off your internet until you run all the rooting software.
No I didn't check to see if it showed up in a root explorer.I'll check that out.
.....
Just checked and no it doesn't come up. I even removed and reinserted the microSD in question and still nothing. The little SD logo pops up on the screen (the big blue vector image one) but it never gets read in the device in system or root explorer.
Is there a way to fix it on test disk for windows?
Click to expand...
Click to collapse
Your system after an 8 failed boot reset and before an update is 2.0.4? If it is, PM me as I would like to get a copy of your factory zip.
And you looked for ext_sdcard in /mnt?
Sent from my Galaxy Tab running Tapatalk
Mnt, but of Course
leapinlar said:
Your system after an 8 failed boot reset and before an update is 2.0.4? If it is, PM me as I would like to get a copy of your factory zip.
And you looked for ext_sdcard in /mnt?
Sent from my Galaxy Tab running Tapatalk
Click to expand...
Click to collapse
I found it in mnt, man they really do everything strange on Nooks, haven't had one since the original Color. I see the problem. It's lacking any sort of permissions (read, write or anything). How do I get those to stick? since I've noticed things in Root tend to not stay permanent. and as for the PM, I'll get right on that. Thanks for all of your help.
dcoke said:
I found it in mnt, man they really do everything strange on Nooks, haven't had one since the original Color. I see the problem. It's lacking any sort of permissions (read, write or anything). How do I get those to stick? since I've noticed things in Root tend to not stay permanent. and as for the PM, I'll get right on that. Thanks for all of your help.
Click to expand...
Click to collapse
SD cards do not let you make permission changes. I'm not sure why. Are you sure it does not have read write permissions? Can you create a file there?
Read my section on data structures in my HD/HD+ tips thread linked in my signature. It explains why the HD's are structured the way they are.
And thanks for working on the PM.
Fixed?
leapinlar said:
SD cards do not let you make permission changes. I'm not sure why. Are you sure it does not have read write permissions? Can you create a file there?
Read my section on data structures in my HD/HD+ tips thread linked in my signature. It explains why the HD's are structured the way they are.
And thanks for working on the PM.
Click to expand...
Click to collapse
I think I figured it out. It seems that the cwmearly builds damage the sd cards, but once reflashed with the ones on your post it gets read just fine. I wanted it fixed since I couldn't find my other SD cards and had to resort into turning a 32gb into a 4gb card to install some zips (lame) and I wanted to get it back to its 32gb glory. So by rewriting my card with your 4gb image and putting it in my nook it got read and then I just formatted it on the nook and it was back to normal, though I had another card with the cwmearly img on it and it was going back to its old ways and repeated the previous steps and it was fine. so CWMearly was the problem.
I don't know how to make a clean back up without my data on it so this one will have my personal info (no credit card info, obviously) but maybe with your skills you can scrub it out of it. I'm not that well versed in this kind of stuff. I have an above average knowledge of android, but not any real knowledge of developing or ADB.
dcoke said:
I think I figured it out. It seems that the cwmearly builds damage the sd cards, but once reflashed with the ones on your post it gets read just fine. I wanted it fixed since I couldn't find my other SD cards and had to resort into turning a 32gb into a 4gb card to install some zips (lame) and I wanted to get it back to its 32gb glory. So by rewriting my card with your 4gb image and putting it in my nook it got read and then I just formatted it on the nook and it was back to normal, though I had another card with the cwmearly img on it and it was going back to its old ways and repeated the previous steps and it was fine. so CWMearly was the problem.
I don't know how to make a clean back up without my data on it so this one will have my personal info (no credit card info, obviously) but maybe with your skills you can scrub it out of it. I'm not that well versed in this kind of stuff. I have an above average knowledge of android, but not any real knowledge of developing or ADB.
Click to expand...
Click to collapse
No I don't want your backup, I want your factory.zip from partition 7. It won't have any of your stuff on it, it is just what comes from the factory. If you don't know how to get that, I can give you instructions.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
Are you sure it's 2.0.4? Any particular reason you don't want to update to 2.0.5?
leapinlar said:
No I don't want your backup, I want your factory.zip from partition 7. It won't have any of your stuff on it, it is just what comes from the factory. If you don't know how to get that, I can give you instructions.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
Click to expand...
Click to collapse
Any progress on getting that factory.zip? BTW, you did not say which device you have.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
:crying: Yesterday I spent almost 24hrs battling problems while downgrading to kitkat and installing a pre-rooted zip of 5.1.1 lollipop.
Eventually, with the help of the good people here at xda, I got it done and working fine, or so I thought.
After installing the pre-rooted zip, everything seemed good but after waiting a while I restarted the phone, to make sure everything was OK before I started re-installing stuff.
I restart the phone and BAM "Damaged SD Card. SD Card is damaged, try re-formatting it".
So I let it Format - doesnt try to format it.
I Physically remove and re-insert the card, and THEN it lets me format it and it starts working. Then I restart the phone and BAM, same thing.
***After Lots of trial and error, I have narrowed it down to something which is happening at system startup.***
I know this because If I remove the card while the phone is off, then start up, then reinsert the card it works fine!
If I remove the card before the phone switches off, and insert it BEFORE I switch the phone on I get a 'damaged' sd card.
I have tried chkdsk, formatting, partitioning, formatting through windows(quick and normal format), nothing helps. IF MY CARD IS IN THE PHONE WHEN I START/RESTART THE PHONE, IT SAYS 'DAMAGED' - even though its not.
If I start the phone with it inserted it says'damaged'... but If I then remove the card, restart the phone and then re-insert IT WORKS FINE.
When It says 'damaged' I can remove and re-insert and it still says 'damaged' BUT If I remove, then reboot, then re-insert it works again.
IF I BOOT INTO SAFE MODE WITH THE CARD INSERTED I GET SAME ERROR/BEHAVIOUR
So something is happening on system startup which is causing this problem. Does anybody here know whats happening? After so many problems with the downgrade/root process, this is driving me crazy. And to top it all off, My XZ Dual recovery no longer works after that first reboot - WTF (I'm hoping a re-install will solve this but for now I need to fix the SD Problem )
Any help would be greatly appreciated, thanks for your time.
EDIT: KitKat install was clean, wiped everything. While on kitkat I installed 2 busybox installers, root checker basic and busybox itself. After flashing the pre-rooted 5.1.1 I DID NOT wipe cache/dalvik as I was afraid of losing root :embarassed: sureley this is not the problem?!? as booting into safe mode doesnt help!?
I think the two problems are probably not unrelated (SD card problems and XZDR not working). Obviously, XZDR runs on every boot and it does try to touch the external SD card. It could be breaking something.
What brand and model and size SD card? Android, and specific phones, can be very finicky. It's possible (but not likely) that 5.1.1 broke support for your SD card somehow.
Did you have to format it specially the very first time you used it with the phone? For example, I had to hack my 64GB SDXC card to be a bigger-than-actually-allowed FAT32 partition for the phone to play ball.
Can you reproduce any weirdness with the card in a PC? Maybe the card actually has a problem and you can RMA it.
What happens if you format the SD card after boot so that it works, then eject it, then reboot the phone without the card in, and insert the card after install? It should mount fine at that point if it really is something in the boot process. If it does work, without rebooting, reinstall XZDR and see how that goes.
xasbo said:
I think the two problems are probably not unrelated (SD card problems and XZDR not working). Obviously, XZDR runs on every boot and it does try to touch the external SD card. It could be breaking something.
What brand and model and size SD card? Android, and specific phones, can be very finicky. It's possible (but not likely) that 5.1.1 broke support for your SD card somehow.
Did you have to format it specially the very first time you used it with the phone? For example, I had to hack my 64GB SDXC card to be a bigger-than-actually-allowed FAT32 partition for the phone to play ball.
Can you reproduce any weirdness with the card in a PC? Maybe the card actually has a problem and you can RMA it.
What happens if you format the SD card after boot so that it works, then eject it, then reboot the phone without the card in, and insert the card after install? It should mount fine at that point if it really is something in the boot process. If it does work, without rebooting, reinstall XZDR and see how that goes.
Click to expand...
Click to collapse
First off... thanks again for the help.
Secondly, I just got a chance to re-install xzdr and....*drumroll please* ...IT WORKED
:highfive: :good: :good: :good:
I cant believe this whole process went so smoothly; usually I run into a few little problems
Anyways, I'm not sure what went wrong with XZDR... it installed and worked fine on kitkat and the pre-rooted 5.1.1 included XZDR flashable which also installed and worked fine but only on the first boot.
Regardless...recovery installed fine again and now my sd card mounts fine on startup. rebooted a dozen times, switched off and cold booted a few more times... no problems with SD Card on boot. well happy.
Thanks again for all the tips and advice mate, much appreciated.
As you suggested, I'll pay it forward as my knowledge improves/returns and if and when my money situation improves: I'll chuck a couple of beer tokens your way.
cheers fella
thesweeney80 said:
First off... thanks again for the help.
Secondly, I just got a chance to re-install xzdr and....*drumroll please* ...IT WORKED
:highfive: :good: :good: :good:
I cant believe this whole process went so smoothly; usually I run into a few little problems
Anyways, I'm not sure what went wrong with XZDR... it installed and worked fine on kitkat and the pre-rooted 5.1.1 included XZDR flashable which also installed and worked fine but only on the first boot.
Regardless...recovery installed fine again and now my sd card mounts fine on startup. rebooted a dozen times, switched off and cold booted a few more times... no problems with SD Card on boot. well happy.
Thanks again for all the tips and advice mate, much appreciated.
As you suggested, I'll pay it forward as my knowledge improves/returns and if and when my money situation improves: I'll chuck a couple of beer tokens your way.
cheers fella
Click to expand...
Click to collapse
:highfive: blame the blood moon, eh? glad it was so simple.
xasbo said:
:highfive: blame the blood moon, eh? glad it was so simple.
Click to expand...
Click to collapse
ha. didnt see that 'blood moon' thingy... too busy going nuts over a 'simple' problem.
Last night shall from this point forwad be known as... 'The night of a thousand formats'
:good: