Here is a little background;
I'm new to the android world and this is my first tablet using it. I received the tablet under the terms that its mine, if I can fix it. THE TABLET So the research begins. The original problem with the tablet: everything would crash after unlock screen, including loader. The tablet does not have any kind of visual recovery mode using the hard buttons. At this time I did not know about any of the tools that I probably could of used to save the stock firmware. When I hit Google with "Cruz velocity micro t510" not much came up, so I spent about a day trying all sorts of different terms with that. There was not even a place to download firmware from cruz, they say wifi is mandatory to upgrade, from within the tablet... I finally ran into a post somewhere where someone said the cruz t510 is an allwinner a10 in disguise. They went on to say that all you need to do is use Livesuit and flash 'sun4i_crane_T05a_v1.5_mxc6225' img from eken website then from there you can use the compatability zip and upgrade to cm10.
So all was good. The t05a firmware there works perfect on it, like the guy said. I kept that on there for a day before I went on to CyanogenMod.
Here is where I am stuck; (Tired of googling, please help )
I decide to try AOKP and CM10 using http://forum.xda-developers.com/showthread.php?t=1821398 and one for AOKP too with t05a-v1_compatibility_1.2.x.zip. And http://forum.xda-developers.com/showthread.php?t=2189640 for recovery mode. I learned how to setup and use ADB with command prompt here.
So I install CWM using ADB shell and reboot into recovery using the sh file. I first folowed the steps to install AOKP and all goes smoothly until I reboot.
I get a notice saying "Damaged SD Card, You may need to reformat" and I realize that it is talking about the internal disk space. I try to reformat and the same notice will appear again or I will have to go in Settings>Storage and Mount SDcard, only to be told no, it is damaged. So I got scared and re-flash back to the eken stock firmware with livesuit. Guess what, sdcard mounted and working again. Then I go on to repeat the upgrade but with CM10 this time. Same result.
I have gone back to the stock image and retried many times. I tried with all three partition versions of that CWM I use, even though I knew it was 10, or so adb shows. I also tried partitioning and formmating with CWM, many times, each a little different.
Short, Sweet, and Simple version;
THE TABLET
Eken a90 stock firmware using livesuit -> SDCard works fine
CM10 or AOKP with t05a-v1_compatibility_1.2.x.zip using CWM 6.0.2.8 -> SDCard damaged
If anyone could help I would very much appreciate it. I need a break from all the research, I'm going to play gtav and hope someone has a solution for me.
I'm trying to upgrade my T510 from original manufacturers specs and could sure use whatever files uou have
Related
So, after owning my Transformer Prime for about a month now, I decided to take the plunge and root it. I followed the instructions for ViperMod and had it rooted in no time. I then followed the instructions of unlocking the bootloader and finally installing OTA Rootkeeper.
I've had rooted devices in the past (Droid Incredible) and am familiar with RomManager. So I installed RomManager on the Transformer Prime. I then attempted to create a backup of my "current Rom", which is just stock ICS. RomManager prompted me to update Clockworkmod Recovery, which I did (I now have 5.8.2.0 installed). It then rebooted...acting like it was backing up my current Rom, but when I got back into RM, and clicked "Manage Backups" and there was nothing there. I tried once more with the same result, and ultimately gave up on backing up my current config.
I then downloaded Cyanogenmod 9 (nightly). I selected Google Apps and it proceeded to download. I got an error that the Google Apps portion had an error, but it seemed to work when I attempted to download it again.
I then proceeded to attempt to install the new Rom. The menu came up, asking if I wanted to wipe data and cache, wipe dalvik and backup current rom. I selected all three and hit ok.
My tablet rebooted...quickly, and did not show any signs of installing Cyanogenmod. Sure enough, I got my stock ICS...no Cyanogenmod. I tried again...same thing. I tried a third time, and RomManager hung when I tried to select Ok after the options of backing up, etc. Ultimately I got the error popup, asking if i wanted to wait/report/ok. I hit ok.
I then...very stupidly in retrospect...performed a factory reset from within the phone's settings menu (something I've later read is a big no no). This time, when my phone rebooted, it went straight into Clockworkmod Recovery, which is where I am now. Stuck. I've read a ton and tried everything but had no success.
Strangely, I can find the cyanogenmod file by navigating through "install zip from sdcard", then "choose zip from sdcard", then "clockworkmod", then "download", then "get.cm", then "get" and finally "update-cm-9-20120301-NIGHTLY-tf201-signed.zip". And it allows me to update using this file...even giving me the message "Install from sdcard complete"...but nothing happens. I'm still stuck in Clockworkmod.
If anyone has any advice, I'm begging for your help. Really hoping I didn't ruin my brand new tablet...
Thanks.
only thing rom manager is gold for on the prime at the moment is getting the latest CWM version. other than that, trying to flash a rom, reboot into recovery, or backup doesn't work in rom manager for prime. everything needs to be done through CWM itself. whether flashing a rom or making a nandroid backup. so you have to manually go into CWM and try flashing from there. did you make sure the roms were stored on internal memory to flash(I believe it can only be done on prime this way at the moment)? try a different rom as the CM9 has alot of bugs n issues at the moment. try flashing virtuous rom or a stock modified rom from developement.
also check out developement section for a thread called the Di's n Donts of unlocking and thread called how to or not unbrick your prime. answers you seek are in there.
See my unbricking thread
http://forum.xda-developers.com/showthread.php?t=1514088
Thanks so much for your help guys!
to demandarin: Unfortunately the only ROM I downloaded before everything went haywire was the nightly cyanogenmod 9 from yesterday. And as I explained, that ROM doesn't seem to be flashing for me... I've tried downloading other ROMs onto my SD card, but I can't seem to get my Prime to recognize the SD card in CWM, and I can't figure out any way to get ROMs onto my prime...now that its stuck in recovery. Do you know if I can load ROMs onto my Prime at this point?
to Diamondback: I read your unbricking thread and its given me some hope. It sounds like I'm falling into the "1a" category. I'll have to bunker down tonight and see if I can work through those instructions (I have no familiarity with ADB at this point, which is my main concern). Anyway, I very much appreciate you pointing me in the right direction.
I am curious though, is there some place I can look for clarification on what works in RomManager and what does not? None of that was made clear in the app itself, so I just assumed it was fully functional, like it was on my Dinc. Now I'm paying the price...
Thanks again.
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
demandarin said:
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
Click to expand...
Click to collapse
Thanks, but I actually do have the latest version of CWM (5.8.2.0), according to the link you provided. The thing is, I'm just very unfamiliar with CWM, or really any recovery software. The link you posted notes the following improvements:
-Possibly fixes bricks (by properly restoring boot.img)
-Correctly comes with Staging/System unmounted
-Nandroid Restores properly the boot.img (of backups created with this CWM). This means no more issues when restoring a Rom if you are coming from another from (for example, if you are restoring Virtuous after wiping cm9)
Which all sounds great, but I have no idea how to really use any of that... Does "possibly fixes bricks" apply to my situation? I've tried selecting restore and advanced restore through CWM, but in both situations it says "cannot find files", which I'm assuming are the "boot.img" being referenced. So again, it seems like I'm hosed...
I'm just really hoping that Diamondback's unbricking method works for me. Though, I'm having a hell of a time finding instructions on how to setup ADB on my PC (Windows 7). Do you know where I can find good and current instructions?
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
demandarin said:
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
Click to expand...
Click to collapse
Thanks again! I think I need a tutorial on how to search XDA more effectively
SUCCESS!
Well, it took some jumping through hoops, but once I got ADB set up successfully, Diamondback's instructions worked like a charm!
For anyone encountering this thread with the same issues as me, I've included links to all of the sources of data I ultimately used.
Thanks so much for everyone's help!
Installing ADB
http://forum.xda-developers.com/showthread.php?t=1427008
http://www.youtube.com/watch?v=ZY4KSrgi-rE
I had to use the PDANet method, referenced in the Youtube video
http://junefabrics.com/android/download.php
Diamondback's Instructions for Unbricking the Prime
http://forum.xda-developers.com/showthread.php?t=1514088
Perhaps I spoke too soon...
My device is no longer bricked, but now I can't access CWM, can't factory reset...can't do anything. I'm stuck with a very broken build of Cyanogenmod 9
Here's the link to my new thread:
http://forum.xda-developers.com/showthread.php?p=23349041#post23349041
I started the process of flashing CM7 TeamWin and the Gapps, it worked just fine. As I downloaded Goo Manager app in Google Play Store, I quickly jumped to install CM10 and the Gapps and the Nook wouldnt come out of TeamWin Recovery. As days pass by reading and reading forums about common problems I start acting. I did all the possible ways to make it work, but its not doing anything. All the Tablet does is go to Cyanoboot and says N for menu, then the screen goes static like if the channels on the TV were not working. Can someone show the way to save this Tablet cause I hate to throw away a good tablet.
My experiences from TWRP are not good! Every time (well, the grand total of two times...) I have involved it in the process there has been trouble! So I go with CWM exclusively!
Can you make a bootable CWM card and maybe try using that? You need CWM 6.x.x to flash CM10, but you can use an earlier version CWM to flash a CWM 6.x.x internally if you want to (I think that's very convenient).
I describe a "cheat" for those that are worried about setting up an sd card from scratch. It's in the steps under "C" in my post that I link to below. In short: I use the regular root card (Albert's or Brian's), boot into the CWM on that card and use it to install CWM 6.x.x
Link to my post: http://forum.xda-developers.com/showthread.php?t=2081981
The first time I got stuck in some sort of bootloop after using GooManager i resorted to the unbrick repart.img you will see mentioned here and there and got my NT back tou out of the box state. In hindsight maybe I wouldn't have needed to do that, but it worked, and also had the extra benefit of performing the BN repartition scheme.
Been there, done that. TWRP has only been trouble for me too. But I also learned from it. Follow Asawi directions. I believe CWM 6.0.2.8 is the latest version. I also succesfully used Succelent's flashable_fix_bootloop.zip. I think what is happening is TWRP sets the boot pointer to one place and CMW 6.x.x.x points to a different place and goes into a loop. I have been able to stop the loop and end up in CMW's boot loader and then used it to flash the zip file, then rebooted back into CMW where I factory reset, then loaded the ROM and GAPPS without a hitch.
You should skip CM10 and go to CM10.1 or equivalent. The jump in features in Jelly Bean 4.2 is worth it and there is no loss of reliability. Check out Succulent, Kirb3y and Meghd00t builds. Right now I'm a kid in a candy shop, they are all wonderful. Props to Succulent (iamafanof) for all the Droid flavors. I've tried them all and feel like a cat surrounded by mice -which one? Be sure to get the latest 4.2 gapps to go with them.
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
Hi all
ok so i'm a bit nervous writing this expecting all manner of attack in that i may be posting something that's been posted before lol, i've been working on this phone from start to finish about 9 hours, over two days..... i've googled just about every combination of words to do with the title and everything in between but nothing seems to come close to what i actually need to do as nothing works
i have an LG Optimus 2x / p990, it had ICS on it but was far too slow to handle this, it needs something a bit less hardware intensive to run smoothly, so i went ahead an found cyanogenmod stable ...... 7.2 i installed sdk after an hour of finding out how it works i finally got adb and fastboot working, i then needed this, that, this, that, etc etc etc.....
to cut a 9 hour story short, i've managed to get myself to the point where i wiped the phone of everything but CWM partioned for ics via the AIO software but CWM will not let me install any ROM onto the phone. to be more precise it says i have installed CM 7.2 successfully! (i've tried this via the CWM via external SD card and sideload) i reboot the phone it's as if i've never done a thing, no trace or suggestion i've even attempted it on the internal card... nothing
i'm at the point now where i'm quite happy to just have my phone back now and install ICS 404 but can't use the LG kdz install software as the pc doesn't see the phone as an LG p990 because it's recovery and i can only get it to come up as internal and external memory cards
i'm not really a noob when it comes to tech stuff but this little phone has me stumped.... please, i'm begging you, help me any operating system that can get my phone working will do, preferably the CM 7.2 if not back to ICS 404?
and i know, i know i should have backed up but i had no idea it could be so complicated just to put an OS on a tiny computer
ETA i've tried that exitrecovery.zip thing and it did nothing :/
It's quite simple
Try to reset and unroot/re-lock the phone then unlock and root, then what you need to do is get ROM Manager and get the Clockwork Recovery and the version that supports your device, although you might need to hook up your phone to your computer for the process to work.
Also put back in ICS 4.0.4 when unrooted and re-locked again like stock and make sure it's the stock file for your phone.
And after you got ROM Manger and the Clockwork Recovery
Then just in Clockwork wipe out all data on the device and don't do a factory reset in Android just with clockwork and delete everything that was made on that phone then install CyanogenMod.
After that it will seem to take a long time or just a while to boot up and then it boots faster then the original ROM.
If you have Clockwork Recovery just wipe out all the data while it's still in there and you should be set.
When it was my first time putting in CyanogenMod it was 10.1 RC1 on my Nexus 7 and it didn't work and forever bootlooped, and that was because i forgot to wipe the device. Then after going into Recovery with Clockwork I deleted all the data of my tablet and it worked but took 5 mins. to boot up which is nomal.
And if Clockwork doesn't work, do the same with TWRP (Team Win Recovery Project) and download that which can be found here teamw.in/project/twrp
If you don't want to get ROM Manager or that one isn't working then try this website to get Clockwork because it has the whole list of devices and I recommend downloading from the website instead of their app. clockworkmod.com/rommanager
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
twelfty said:
cheers for that, i've tried all of the above still to no avail, having a think about it the phone is partioned for ics, i'm trying to install CM 7.2 which as i understand isn't ICS so.... maybe the error is that it's a different partioning sequence/setup i'm gonna go for CM 10.1 and see if that makes a difference.
to add i'm not sure why everyone rants and raves about CWM, TWRP seems much more complete and advanced do you (or anyone else) know the main differences?
Click to expand...
Click to collapse
TWRP has a completely touch driven interface that is 100% themeable, while CWM has a touch version and non-touch version. Also TWRP has a built in file manger and terminal emulator where as CWM does not. A lot of people like TWRP because it provides a lot of good features with a simple and straightforward yet powerful user interface. I would recommend taking a look at this guide if you want more information on the differences between the two http://www.droidiser.com/2013/04/twrp-vs-clockworkmod-recovery.html?m=1.
Sent from my SCH-I535 using xda premium
ok i managed to do it i can't remember exactly how but some good links and info for anyone who stumbles across this in need of help
i went for cyanogenmod 10.1 to make this work i used this AIO tool - http://forum.xda-developers.com/showthread.php?t=2020737
repartioned with OLD partion layout and BL
installed TWRP (included in the aio)
if you need to reinstall the google play store make sure you have right version if you flash it and get "unfortunately setup wizard has stopped" repeatedly you have the wrong version see this link for which one you need http://wiki.cyanogenmod.org/w/Gapps
obviously make sure you have adb and fastboot setup and drivers too.... it's a long process installing the entire sdk, personally for flashing this once and most definately not inclined to do it again i'd go with just the adb and fastboot rather than the whole sdk
also i found a keyboard error with 10.1 where i'd type 1,2 or 3 characters and the keyboard would minmise not sure if there's a proper fix (i found one thing where you disable the autocorrect but didn't want to do that) so i decided to download and install hackers keyboad which is based on the gingerbread keyboad and is much better and comes with full features and integrates nicely
coupled with the info above from YoyoscratchMC and you should be in the field
good luck to all i was ready to jump out my window with my phone first so i could land as hard as possible on it last night but i got there in the end lol
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Thank you
asawi said:
Run CM10 from sd card and flash the original firmware whle running it. Ready-made image tthat you can just download and burn http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Click to expand...
Click to collapse
That should work excellently, thank you very much.
Nookuser19 said:
I am in charge of several nook tablet (16gb) devices, these devices all run on the cyanogenmod nightlies. I fixed a problem with one of them recently, After fixing the problem I noticed it needed an update. After performing the update the tablet refused to boot (either shutting down before or sometimes during the bootloader).
Rather than flash back to the previous update my genius mind decided to try flashing the acclam_update zip and then flashing back to cm. The first half of this worked out well enough and I got the tablet on stock B&N software. However when I loaded the device I realised my error. some time ago I had flashed the updated touchscreen firmware that was included with the rom. Before flashing acclaim I should have flashed stock touchscreen firmware but did not, rendering the nook's touchscreen useless on the current software. Additionally (though I was aware this would happen) I now have the stock recovery mode instead of CWM.
I have struggles with adb as it is (I originally used a bootable CWM sd card for these devices but have since cleared that sd card) and I'm fairly certain I need access to the screen to use it on this device (I believe I need to activate something in the developer settings.)
So that's my problem. If anyone knows what I should do please help me out. If you need more info tell me what you need and I'll do my best to put it up here.
Click to expand...
Click to collapse
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
topdawg7793 said:
Just now experienced the same problem. I've been trying to get my nook to boot from SD for the last couple hours and nothing. Tried booting tethered to my laptop, the factory wall charger, etc. It's a stock Nook Table with the 10point touch driver...meaning completely unusable. Could you post what tools you used if you get it working?
Click to expand...
Click to collapse
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
asawi said:
What sd card are you using? Do you have another one to try? Are you using the image I linked to or something else?
Sent from my BNTV400 using Tapatalk 2
Click to expand...
Click to collapse
Just used a 4gb class4 through a memory stick reader. It's working beautifully now, except I need to repartition it.
Interesting bug though, the home button won't take it out of sleep any more. Only the power button..?
Hey, guys, I made a mess.
A long time ago I decided to try out CyanogenMod for my S3 and then everything went well. I got it up and running and it was a cool ROM but I decided to stick to stock at that time. So I looked for a tutorial online and managed to get it back to stock 4.1 Android running well and as usual.
The issue I had then was that I couldn't update my phone from Google's servers anymore. Every time the phone tried to update the firmware I'd get an error, no matter if I tried it through Kies, the phone or whatever. So I decided I'd just install a ROM for a more recent version.
I found a post on a tech blog here in Brazil saying that OmniROM promised they finally had a somewhat stable version of KitKat 4.4
I went on to install it to then find a beautiful, but still very glitchy ROM. My phone froze all the time and it was starting to bother me. My initial plan was to stick to it until it got better, get the daily updates and stuff, but my phone was way too unstable for that too. So I said to myself: "Okay, no problem, so let's get a stable ROM on this little guy."
I downloaded PA 4.3 and proceeded to get it on my phone. That's when the issues started happening. I couldn't find the .zip from CWM no matter where I put it, and my sdcard1 was full because of the previous backup I created (there was a problem with that too, MD5 mismatch, but I didn't lose anything important so that's okay).
Then I did something even more stupid. I figured, why not clean up the backup and get the .zip there, so maybe it'll show up? At that point the sdcard0 (internal storage) was all different and I couldn't find the .zip for the OmniROM, but when I was on CWM it showed up instead of PA's. The problem with that is that I somehow wiped out CWM and now I can't get to recovery. If I boot up my cellphone through OmniROM, it loads up fine but I can't download the ROM Manager or the superuser from the Play Store. I'm trapped with OmniROM and it's working even less well than at first.
What should I do? Is there a way back from this? I'd really like to have my phone running again soon, I need it to keep in touch with my parents since my grandma died recently.
Thank you in advance.
EDIT: Okay, some progress. I remembered that I got CWM on the phone through Odin and went through that again. I have CWM back but still, my internal storage fails to recognize the new .zip files and only shows OmniROM's. The folder is completely different when I connect the phone to my computer. I got to see the .zip files at the sdcard1 but CWM says they're bad files. I'll trust it and redownload/transfer again. We'll see what happens.
EDIT 2: Trapped again. Can't find anything on Google. It sure sucks to be me. I can't even figure out how to get everything back to stock so I can try again. Tried turning USB debugging off but it didn't make a difference. The CWM shows me the two OmniROM .zip files and my computer shows me the PA .zip files. I'm just...
first- try to flash newer cwm based recovey. I suggest philz (is has both Odin / cwm based install):
http://forum.xda-developers.com/showthread.php?t=2002953
after flashing is complete- try to download this rom:
http://forum.xda-developers.com/showthread.php?t=2060403
and check if you can see it.
(you can put it in your internal or external sd, philz can access them both)
Before installing the new rom, I strongly recommend doing a 'wipe to istall new rom', cache wipe and delvik.
good luck
Sent from my GT-I9300 using Tapatalk
Yay, thank you! I'm not trapped anymore. The PA rom I downloaded is still "bad", but that's probably its own fault. I'll wait until NeatROM's download is complete and try with that. I'll edit this if things turn out well.
Thanks again!
EDIT: So, I tried with NeatROM and it also says it's bad. But I only tried on the external storage, so maybe that could be it. My sdcard has been returning some really funky errors when I get it on my computer so I'm worried it might be a bit compromised (and I actually found it at a bus terminal, so it never really worked properly even after formatting).
Thing is when I did the wipe I picked the option that wipes it for a new ROM, so OmniROM is gone. Is there a way to get USB connection through CWM so that I can transfer NeatROM to the internal storage? I only have this one sdcard.
EDIT 2: Finally got it! Thanks so much, amirTor, my S3 is back on track! The sdcard was the bad one, not the file. But the PA ROM didn't work anyway. I might stick to NeatROM or maybe look later. I'm gonna take a week off of all this after so much trouble.
Glad I could help (even though it seems that you pretty much helped yourself...)
1)If you got Sandisk SD card, make sure to follow my post on thread: http://forum.xda-developers.com/showthread.php?t=2614170
2)You can mount your phone to be shown in your pc even when in recovery mode: Mounts and storage-> moun usb mass storage
3)You should definitely stick with neat- the best stock (and aosp) rom there is :good::good::good:
ps- hitting the 'thanks' button will be appreciated :angel:
Done and done!