Database Info

[Q] Please Help! Phone Bricked (Noob Problems)

Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!

Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app

luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.

Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!

fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.

Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!

fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.

Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?

fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.

Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again

fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?

Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.

fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.

Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?

fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?

Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!

fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.

Photon Failed to hab check for recovery: 0x56

So, I got my Photon Q today and I've already unlocked it and I was trying to install TWRP but I messed up somehow.. It still boots into the stock Android ROM and works fine but whenever I try to go into the recovery/Fastboot (Whatever it's called) I get this screen with some info text. At the bottom it says this:
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Whenever I try to flash a recovery with an app it always succeeds but I still get this screen when I try to go into the recovery. Help me.

Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?

arrrghhh said:
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
Click to expand...
Click to collapse
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.

Cwazywazy said:
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Click to expand...
Click to collapse
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?

arrrghhh said:
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
Click to expand...
Click to collapse
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.

Cwazywazy said:
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Click to expand...
Click to collapse
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!

arrrghhh said:
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
Click to expand...
Click to collapse
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..

Cwazywazy said:
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Click to expand...
Click to collapse
I've heard of other people complaining about this on TWRP.
You should either a) use OpenRecovery or another recovery... or b) use an older version of TWRP. I'm on 2.6.3.1 and it works _flawlessly_.
I haven't had time to update to the latest versions of TWRP to investigate this issue.
As for your CM issue, make sure you wipe (using a recovery that works haha) and also make sure you give it plenty of time to do the first boot - there is sometimes a fsck process which runs at boot and takes a lot longer than usual for the device to actually boot up.

Please help me. I can't find any solution and I can't boot into CMod.

Cwazywazy said:
Please help me. I can't find any solution and I can't boot into CMod.
Click to expand...
Click to collapse
I gave you a solution, please at least try it.

arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Oh. I didn't see that, sorry. Trying it now.

arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.

Cwazywazy said:
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Click to expand...
Click to collapse
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.

arrrghhh said:
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
Click to expand...
Click to collapse
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)

Cwazywazy said:
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Click to expand...
Click to collapse
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by. I was hoping for a logcat from the CM11 failed boot.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
TWRP is failing to mount a lot of partitions, which is obviously unacceptable. I'm still not sure why the older version wouldn't work for you...

arrrghhh said:
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
Click to expand...
Click to collapse
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..

Cwazywazy said:
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Click to expand...
Click to collapse
OpenRecovery?

arrrghhh said:
OpenRecovery?
Click to expand...
Click to collapse
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...

Cwazywazy said:
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Click to expand...
Click to collapse
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.

arrrghhh said:
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
Click to expand...
Click to collapse
Ugh. Not working.
It says failed to mount /whatever (Invalid argument)

Please help me! Cant install any ROM on my OnePlus!

Hi Everyone!
Because of having issues i can´t fix on my OnePlus, i´m finally asking for some professional help here, as it´s getting more and more complicated and i don´t want to ruin my phone.
What was my plan?
Installing CM11S 44S on my OPO, which had the 05Q Version as factory setting.
Also i wanted to install a franco kernel.
I hoped, if i do both steps successfully, my OPO will have a good battery life (44S seemed to be the most efficient version, according to some forums).
What did i do so far?
First i set up an adb backup for my data, but not for the OS. However, i installed SDK plus tools and drivers.
Next step was installing a new recovery, which is able to flash a new version of CM11S, so i set up TWRP with fastboot, which means my device is "unlocked" now.
Everything worked well so far, i also made an backup in TWRP.
The problem:
I wanted to reboot my OPO at some point and TWRP asked me for rooting my device. Accidentally i swiped over so it started rooting process, but i didn´t want to root it, so i immediately shut the device down.
By now TWRP recovery/fastboot is working, but my OS 05Q is lost and i can´t install a new ROM because im getting the Report:
--
Checking for MD5 file...
Skipping MD5 check; no MD5 file found
Error flashing zip /<path to .zip file>
--
Can anyone help me to get 05Q back or the 44S with the franco kernel?
I know there might be some other threads that deal with similar problems, but actually none of them helped me so far. For example: do i need a fastboot image or signed flashable zips (which i have)? In which order do i install the kernel and the ROM?
Some Information:
I can access my device via fastboot and my OPO is also shown as a adb device on my MAC.
When starting in TWRP, i can also access the device in USB Mode, transfering files is also possible.
I´m not really competent with android modding or programming, so i will need some noob-friendly answers, but i bet you guys know how to help me out here.
Thank you very much for your help, i really don´t know what to do anymore.
EDIT:
I found out how to place a md5 file to the referring version, but it still sais: MD5 does not match.
I´m so done with it right now that i wish i had my OPO back as it was few days ago.

Well, i cant really help here as i have not face this problem but ur mistake was that u Immediately shut the device down the moment it was installing root. It may have corrupted the partitions of the phone and left it at that state, so maybe restoring the partitions of that section may help. Like i said im not knowledgeable about this

Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471

Heisenberg said:
Agreed, you shouldn't have shut down the phone while it was modifying a partition. The root wouldn't have mattered anyway because you were about to overwrite the system partition by flashing a ROM. Go to my guide thread and look at section 8 to flash the stock images for the build you desire:
http://forum.xda-developers.com/showthread.php?t=2839471
Click to expand...
Click to collapse
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.

Thyrix said:
Can i follow all these instructions altough im using a mac?
I will try it out today, hopefully this will fix the problem.
Click to expand...
Click to collapse
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.

Heisenberg said:
Yes you can still use fastboot on a Mac, but you'll need to Google how to set it up on a Mac first.
Click to expand...
Click to collapse
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?

Thyrix said:
Alright, so fastboot is ready, but i need to know, if i will need one of those "unofficial stock rooted fashable zips" a fastboot image. or anything else? sorry to ask for
Can i trust an android version anyone rooted...?
Click to expand...
Click to collapse
You need the fastboot images.

Heisenberg said:
You need the fastboot images.
Click to expand...
Click to collapse
Got stuck at step 2: It Terminal said error: cannot determine image filename for sbl1.mbn - although the name is correct and the file is in the correct folder :/
EDIT:
Fixed it, forgot to type sbl1 2 times, im sorry
And it worked, thank you sooooo much!!!

YOG4PAS2QL bricks my OPO

Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.

erdeebee said:
Hi
Since updating my OPO to YOG4PAS1N0 I couldn't reboot my OPO. Since the last update it won't even boot any more. I've reflashed to stock 4.4.4, installed every update and had the same issue. I even tried to flash the zip true recovery, but i got an error while doing it. So, after three times of updating, I'm back to square one.
After going back to stock I have to factory reset in recovery, otherwise the OPO won't boot.
But of course I'd like to install Lollipop (and later Marshmallow). What can I do? I have a Mac with OSX 10.11 and a laptop with Windows 7, so I'm able to use both.
I did the flashing on my Macbook with the Toolkit found here. But I don't think there's an issue with this, as it uses the terminal. It's just easier then to type it all myself
Thanks in advance.
Click to expand...
Click to collapse
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471

The only error I got, was that it's impossible to boot. I'll try your guide asap

Heisenberg said:
It'd help if you actually posted what errors you're getting, without information like that it's virtually impossible to troubleshoot. Anyway, your best bet is probably just to flash the stock images with fastboot. Back up anything important first as this will wipe your device. See section 8 of my guide:
http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Click to expand...
Click to collapse
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.

Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.

erdeebee said:
I unlocked the bootloader.
I installed the latest fastboot image.
Now my OPO is stuck again at the 1+ / Powered by Android-screen. I can't boot into recovery, but fastboot mode is still possible.
Click to expand...
Click to collapse
erdeebee said:
Everything up to cm-12.0-YNG1TAS2XK-bacon-signed-fastboot seems to work fine.
Click to expand...
Click to collapse
Is there a reason you're using that particular build instead of the latest? How are you installing it?

Heisenberg said:
Is there a reason you're using that particular build instead of the latest? How are you installing it?
Click to expand...
Click to collapse
I'm sorry, I thought my message was clear. The latest build gives the same problem. With this build, I'm able to boot. I installed this in terminal as a fastboot-images.

This guy has the exact same problem.

erdeebee said:
This guy has the exact same problem.
Click to expand...
Click to collapse
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip

Mr hOaX said:
Assuming that you want to upgrade your OPO to latest available version of Cyanogen
- Flash latest *fastboot* image from here http://forum.xda-developers.com/oneplus-one/general/official-cm11s-roms-ota-updates-t2906746
- If you have already tried above step, flash cm-12.0-YNG1TAS2I3-bacon-signed-fastboot.zip and then upgrade via OTA incremental update zip
Click to expand...
Click to collapse
I've tried the first, didn't work. I've tried flashing 11S and started upgrading. I didn't have issues until 12.0. When I got to 12.1 I couldn't reboot (but I could shut down and boot). With the latest update I couldn't even boot normally.

Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk

erdeebee said:
Anyone has some idea?
Verstuurd vanaf mijn A0001 met Tapatalk
Click to expand...
Click to collapse
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough

playya said:
Not sure if its a language barrier but first of you are going to have to supply more information than that. Secondly what have you tried to fix it and especially since there are tutorial out the waaaaahzooo in here on how to repair your "bricked" phone.
Please research make some attempts and if any issue please document in full what your issue is. I guarantee you though whatever it is someone here has gone through it already so search thorough
Click to expand...
Click to collapse
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.

erdeebee said:
What I have tried is on page 1 of this thread.
I tried to install 4.4.4 with a flashable zip and then installed all updates. I installed the 5.1.1 zip. I installed the fastboot 5.1.1 and 4.4.4 and installed all updates.
Now I'm on 5.0.
On the last update I couldn't update reboot or boot anymore. The update before that I couldn't reboot, bu I could boot.
Click to expand...
Click to collapse
My bad on that did not even realize there was another page.. dont know how that happened... Wow I say just start from scratch and go to cm page and download the latest stock software. I am sorry I see others have tried to help you and to be honest your breakdown is a lil confusing. NO worries though hopefully someone will come along to help

Nexus 5 blue circle (doesn't start).

Hi, my nexus 5 (16gb) is not starting. I get the Google logo and after it, a blue circle going smoothly from right to left, again and again. I can start bootloader and recovery (TWRP). I know I did something wrong years ago, maybe flashing a ROM, but I didn't need the Nexus at the time and I let it be. I don't remember what I tried or changed when it happened.
I don't know how to search for a solution since I don't know what the problem is. Does anyone know a solution?

That's the LineageOS 14 boot animation, sounds like a bootloop. If you want to go back to stock, flash the factory image from here https://developers.google.com/android/images#hammerhead
Keep in mind that factory images wipe all data on the device, backup things you want to keep if any from TWRP.

goo.gle said:
That's the LineageOS 14 boot animation, sounds like a bootloop. If you want to go back to stock, flash the factory image from here https://developers.google.com/android/images#hammerhead
Keep in mind that factory images wipe all data on the device, backup things you want to keep if any from TWRP.
Click to expand...
Click to collapse
Thanks for that! When trying to flash I get the error "E: unknown command [log]" (with LineageOS) and just flashing error (with factory image).

CincoNuestro said:
Thanks for that! When trying to flash I get the error "E: unknown command [log]" (with LineageOS) and just flashing error (with factory image).
Click to expand...
Click to collapse
Try flashing a newer version of twrp, and then LAOS. If it doesn't work then sorry, I won't be of help

goo.gle said:
Try flashing a newer version of twrp, and then LAOS. If it doesn't work then sorry, I won't be of help
Click to expand...
Click to collapse
That worked!!! Thanks :good::good::good:

CincoNuestro said:
That worked!!! Thanks :good::good::good:
Click to expand...
Click to collapse
Great, glad to hear it.