Related
[Q] Stuck in "Starting Fastboot Protocol Support" when trying to flash stock images
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
philski421 said:
When i punch in adb reboot bootloader i get starting fastboot protocol support, i used the rootmyxoom procedure which does unlock my bootloader.
im using this method:
http://forum.xda-developers.com/showthread.php?t=1075260
Please Email me with responses, [email protected]
Click to expand...
Click to collapse
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
bwcorvus said:
I don't understand, when you type in adb reboot bootloader you should get fastboot...whats the problem.
Click to expand...
Click to collapse
thats where I have no clue what hell is going on, if I type in flash blah blah it says waiting for device
i have the same issue, I'm I reboot via adb and then my xoom reboots and says starting fasboot protocol support and just sits there. Any help or idea why?
answered my own question. This is because my device has not been unlocked yet.
I had to do the fastboot oem unlock found here.
http://forum.xda-developers.com/showthread.php?t=967065
Only thing I can suggest is to check to make sure you have your drivers installed and ready for fastboot. I think one of the commands you can throw at it is fastboot devices which should do the samething as adb devices but use for fastboot (but can't remember, been awhile since I've had to do anything with fastboot). If that is an acceptible command then you should see your device listed, if not then your computer isn't seeing the device which is why it's saying waiting for device.
You might also want to try throwing the fastboot oem unlock command again and see what happens (it's possible that you've never actually unlocked the xoom).
This is only a few suggestions I can give you for now as I'm not at home to try throwing some of those commands myself to confirm they're valid commands or not, sorry.
drivers are installed that's how I did the original unlock. and I'm sure I hit accept. I went through the whole process of losing everything when doing so. no dice on being able to flash . and the weird thing is this. when I type in adb reboot bootloader it reboots to the fast boot protocol screen but when I type in the info to flash the recovery I get the error of can't load
I'm having the same problem, I simply can't boot into FASTBOOT. I've got the latest USB drivers, I've updated ADB, but it just won't work. It just sits there telling me "Starting fastboot protocol support".
Very frustrating, nothing I do seems to fix it - I've even done a factory reset.
Edit: Now it won't even respond to "fastboot oem unlock", it just sits there saying "<waiting for device>" even though the device shows fine when I do "adb devices" and the device also shows in Windows. (Is this simply because the device is already unlocked)
Are you sure USB debugging is enabled?
Sent from my GT-I9000 using XDA Premium App
Yep, it is
Edit: By the way, if I do "fastboot devices" nothing is listed. If I do "adb devices" it lists the XOOM just fine.
Edit again: Just noticed that the OP also used the "rootmyxoom" process, which is exactly what I used and I'm having the same issues he's having... hmm.
A few days ago I tried getting my phone to s-off using the "[how to] manually achieve s-off,simunlock,supercid for Inspire 4g/DHD" guide on the Android forums. (Sorry, I can't post direct links.)
I got to the part where I was supposed to type in "fastboot flash boot boot.img" to the command line but I accidentally skipped that part and typed in "fastboot boot recovery recovery.img". I stopped everything and tried to start over but when I turned my phone back on I was stuck in a boot loop. Going to hboot and trying to choose Recovery or Factory Reset only results in more boot looping.
I've tried putting PD98IMG.zip on the SD card and booting it, but it only reads it and says "Parsing..." before doing nothing. Attempting to enter recovery mode after this makes it enter the boot loop again.
I've also tried using the HTC Sense and RUU from AT&T on my computer to fix the issue. My phone can connect to my PC after choosing fastboot from the hboot menu. The RUU can see the device and it starts recovering it, as my phone shows a black background with HTC on it. But the RUU stops after trying to update the signature saying "The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again." I am 99% positive I am using the correct RUU.
I've searched high and low on the internet for a similar situation, but everyone else seems to have their problems solved using either of these steps. Thanks for any help.
Without knowing what you did (since you haven't given us a step-by-step and can't post links), we don't know how to help.
Sorry about that. I'll try to explain what I did the best I can.
Before using the guide, I managed to root my phone and used it for a few days, so everything was fine then. I later decided to s-off it so I could flash a custom ROM to it. Using the guide I mentioned above, I created a mini-adb directory in my C: drive with the ace-tools.zip that I downloaded. Using the command line I copied my stock boot image, though to where I do not know. (I feel like a fool for doing all this without being sure of what I was doing exactly. I deserve what came to me.) Then, using the command line I made my SD card a gold card. After that I changed the "misc version" (?) to allow installation of the downgrade firmware, and then relocked the boot loader and booted back into fastboot. Then I flashed the downgrade software and unlocked it again. It's here that my phone was supposed to be unable to boot, and I was supposed to flash the boot image but skipped that step.
Now I'm unsure of what I have to do, and I only want to get my device working again.
I wish I could post the link to the exact topic, but since I can't I guess you'd have to search the topic name to see exactly what the directions were trying to get me to do.
Thanks again.
Can you boot the phone into fastboot and flash the boot.img from fastboot?
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
SammichMonster said:
No, with the PD98IMG.zip file it simply says "Parsing..." and stops there. With any other boot image it doesn't acknowledge it at all. Even though the computer makes the sound that it's connected to the device when it's in fastboot, adb can't recognize that's it's there in the command line.
Click to expand...
Click to collapse
Wait. What? Not PD98IMG.zip from hboot. Extract the boot.img and flash from fastboot, not adb.
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
SammichMonster said:
Ah, thanks for the clarification. I'm supposed to extract the boot.img to the SD card and enter fastboot on my phone, correct? Because I've just done so and nothing happened. I have the options Bootloader, Reboot, Reboot Bootloader, and Power Down, and the Bootloader option only takes me back to the hboot screen.
Sorry if I've misunderstood you.
Click to expand...
Click to collapse
No, the boot.img needs to be on your computer. Your phone needs to be in fastboot mode. From the folder where the boot.img is saved,
Code:
fastboot flash boot boot.img
I can't use the command prompt to connect with the device because it can't see it. I always get an "error: device not found" instead.
Is your phone in fastboot mode?
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
SammichMonster said:
Yes. It's odd: the RUU software identifies it and knows it's there, but can't actually fix the issue. The command prompt just doesn't notice it at all.
Click to expand...
Click to collapse
So you're booting into hboot, navigating to fastboot with the volume buttons, and selecting it with the power button? What does fastboot devices say?
I'm assuming by "fastboot devices" you mean what it says in the command prompt.
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
I'm assuming I have to load the boot.img now?
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
SammichMonster said:
...Well what do you know, it recognized it. I was typing in "adb devices" instead of "fastboot devices". So it can recognize it after all.
Click to expand...
Click to collapse
That's what i figured you were doing, so that's why I clarified.
SammichMonster said:
Hey hey, wa-hey!
That was much easier than I thought it would be! A simple "fastboot flash boot boot.img" followed by a fastboot flash recovery recovery.img" using some image files I made before messing everything up did the trick. Thank god I did so.
Everything's back to normal; my phone escaped the boot loop. And last but not least, I don't have to buy a new phone.
Thanks so much for helping me out, even if it was clearing a few things up for me. I appreciate it.
Click to expand...
Click to collapse
You're welcome. You could also have fastboot flashed any custom recovery image, flashed a ROM from recovery, and fastboot flashed that ROM's boot.img. So you weren't too badly off.
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
then go back into volume up + power (fastboot mode)..... fastboot flash recovery <recovery-name>.img while the recovery file is in the fastboot.exe folder. then boot into recovery.
zephiK said:
Turn the phone completely off. Hold volume up + power, plug the phone in via USB (ensure that you have the drivers installed for the phone)
fastboot oem unlock
fastboot reboot
Click to expand...
Click to collapse
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
lemonspeakers said:
You see, I cannot even get to the part where I reboot the phone myself because the phone automically does it for me and jumps itself into TWR recovery and does not unlock the bootloader for me.
It takes less than a second from when i run the command "fastboot oem unlock" to when the phone reboots. Then it take about 15 seconds to get to the TWR recovery.
The only drivers I've installed on my Win8 (tried Win 7 as well) are these:
http://forum.xda-developers.com/showthread.php?t=2588979
Any other drivers I'm missing? I do not want to do download the full SDK.
Click to expand...
Click to collapse
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
zephiK said:
I actually had that happen to me too. When I typed fastboot oem unlock, my phone just instantly rebooted. But the bootloader was still unlocked. Use http://forum.xda-developers.com/showthread.php?t=2788632 and start from scratch. Use Universal Naked Drivers 0.73, they work amazing. I had these drivers installed before so I didn't even need to install drivers.
Click to expand...
Click to collapse
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
tkdsl said:
I tried your method but I keep restarting to the twrp recovery.
and specific thing that made the device unlock the bootloader. Fastboot OEM unlock just restarts my device
I have the correct drivers the win 7 pc does recognize the device in fastboot mode.
thank you
Click to expand...
Click to collapse
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
teh roxxorz said:
Silly to ask, but you unchecked the cm update in dev settings and enabled debugging?
Personally, my second lappy didn't even list the device in fastboot, but the commands still worked.
I would just boot into fastboot and run the all the commands in series.
Click to expand...
Click to collapse
I've already tried this on 3 different computers.
I don't see how having dev mode would affect bootloader if I never boot into the OS.
Someone had the same issue and had found a fix. I will give this tampering fix a try:
http://forum.xda-developers.com/oneplus-one/help/locked-bootloader-totally-locked-t2817735
lemonspeakers said:
Two days ago, I unlocked my bootloader and it wiped everything. After that, I installed TWR and rooted the device with a toolkit.
Now I don’t know what went wrong, but I would like to flash CWM recovery instead of TWR, but...
it’s now showing that my bootloader is LOCKED.
And I cannot unlock after I’ve tried using adb, cmd, or the toolkit.
I will hold Vol Up+power to enter fastboot and as soon as I hit “unlock bootloader” or enter “fastboot oem unlock” in command, the phone immediately starts into TWR.
Without an unlocked bootloader, I cannot flash anything via the bootloader.
Any help would be appreciated. Thank you!
Click to expand...
Click to collapse
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Dr.Linde said:
Hi lemonspeakers,
sadly I don't have a solution, but the same problem.
Current state:
Bootloader locked
TWRP installed
no root
Sending "fastboot oem unlock" causes reboot to recovery.
Besides that the phone is fully working. (My friends thing I'm crazy because I'm sad about a fully working, "normal" phone
I hope somebody have suggestions to fix the issue.
Update:
I've just seen the tamering fix thread and I'm going to try that, too,
Did it work for you?
Click to expand...
Click to collapse
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
lemonspeakers said:
I haven't tried it because i'm out on vacation for a few days. I didn't want to bring my new oneplus with me.
If you tried that fix, let me know how it went. thanks!
Click to expand...
Click to collapse
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Dr.Linde said:
Actually, I tried it and... It works!
I flashed the script, than used this guide (again):
http://forum.xda-developers.com/showthread.php?t=2788632
Than it looked like the only improvement is, that the bootloader is now unlocked. Root didn't work.
I could fix that by going to Recovery, factory reset, reinstall SuperSU an reboot. My phone now is finally rooted.
I think the factory reset part is strange, but I'm so glad I now have a rooted OPO.
When you try it, please let me know if you also have to do a factory reset.
Click to expand...
Click to collapse
That is sooo SCHWEET! I can't wait to try it on my phone when I get home! Woot!
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
cm recovery
WunderWuffle said:
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
Click to expand...
Click to collapse
uncheck update cm recovery under settings..developer option..
WunderWuffle said:
First problem: when I do "adb devices" in command prompt, there are no devices listed. I am pretty sure I have installed all the proper drivers.
Second problem: I don't know if my boot loader is unlocked. The reason I think this is because when I used the manudroid19 toolkit to unlock the boot loader, it restores my system, but when I try to flash a custom ROM, nothing happens. People I've talked to say that its supposed to stay in fast boot mode for about a minute before it actually boots into TWRP, but nothing actually happens.
Third problem: when I press the root button in manudroid19, nothing happens. The cmd prompt just pops up for a split second then nothing. Plain out nothing happens. Root Checker says my phone is not rooted.
How would I resolve all of this?
Click to expand...
Click to collapse
My first piece of advice: stop using a toolkit, it's clearly creating more confusion than it's actually helping.
When you're issuing the 'adb devices' command are you booted into Android? What happens when you issue 'fastboot devices' when you're in fastboot mode?
Transmitted via Bacon
paztine said:
uncheck update cm recovery under settings..developer option..
Click to expand...
Click to collapse
Its always been unchecked.
timmaaa said:
My first piece of advice: stop using a toolkit, it's clearly creating more confusion than it's actually helping.
When you're issuing the 'adb devices' command are you booted into Android? What happens when you issue 'fastboot devices' when you're in fastboot mode?
Transmitted via Bacon
Click to expand...
Click to collapse
When I did adb devices, I was in Android iirc. I can't remember since the last time I did it was a day or two ago. Sorry. I am not very knowledgeable in this area. I have not done the fastboot device command.
WunderWuffle said:
Its always been unchecked.
When I did adb devices, I was in Android iirc. I can't remember since the last time I did it was a day or two ago. Sorry. I am not very knowledgeable in this area. I have not done the fastboot device command.
Click to expand...
Click to collapse
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
timmaaa said:
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
Click to expand...
Click to collapse
I just did that. Here are my results. It says that my device has been tampered with, and my boot loader is unlocked. And now, for some odd reason (I guess I was in fastboot while I was doing adb commands), it not detects my One. Thank you!
demkantor said:
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
Click to expand...
Click to collapse
Since I am not on my computer anymore, I will check these out and I will get back to both of you in a bit. Thanks!
timmaaa said:
Ok, adb commands will only work while you're booted into Android or booted into recovery. Similarly, fastboot commands will only work while in fastboot mode. Let us know how you go, and if you get your serial number turned from the 'fastboot devices' command, issue this one:
Code:
fastboot oem device-info
And post the results.
Transmitted via Bacon
Click to expand...
Click to collapse
demkantor said:
I would start by reading up on fastboot, this phone is as easy to root as they come so as mentioned earlier a toolkit just ads to the hassle
http://forum.xda-developers.com/showthread.php?t=2277112
Here you will find information on how to get adb and fastboot working properly, my guess is its a driver issue right now. So check device manager and manually update to the appropriate drivers if needed
And here you will find the steps to manually root
http://forum.xda-developers.com/showthread.php?t=2788632
Best of luck!
Click to expand...
Click to collapse
I rooted the phone manually using command prompt and everything worked! I got TWRP recovery, and Root Checker says I'm rooted! Thank you very much! Doing it this way took my less than 7 minutes while using the toolkit took me more than three hours, and that didn't even work!
So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to fastboot and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even reinstalled android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?
ian_99 said:
So I'm trying to re-lock my bootloader,
I already looked up how to lock the bootloader and you can do that by booting in to bootloader and locking the bootloader from there. My OP6 was rooted but I removed all root related applications, I even wiped android.
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command. I tried reinstalling the ADB, fastboot and OP drivers a couple times but it doesn't help. I tried everything possible but I can't lock the bootloader.
Could somebody please help me with this?
Click to expand...
Click to collapse
You have to be in fastboot mode ( power off phone, hold power and volume up til you see fastboot on screen) on your phone to do want to want, if you cant do it that way,you can try this tool, https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892 , it will return your phone to stock factory fresh. It will be back on 5.1.5 software. Good luck
in fastboot mode just type without quote"fastboot oem lock"
MrSteelX said:
in fastboot mode just type without quote"fastboot oem lock"
Click to expand...
Click to collapse
I can boot into fastboot mode (I said bootloader instead of fastboot, my bad), but the command promt does NOT show any devices, so I can't use this command. All drivers are correctly installed.
Did you enable USB debug?
whizeguy said:
Did you enable USB debug?
Click to expand...
Click to collapse
Yes I did
And I tried updating to android P but now I can't even access fastboot!
[UPDATE:]
I can finally boot into fastboot again, the only way to do this was to first boot into recovery and restart to fastboot from there.
And my device is still not detected by adb in fastboot
u do fastboot devices not adb devices
I just tried doing this in a Windows 7 virtual machine, but it gives the exact same results, I really don't know what is cousing this
Then take tool all in one
Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.
whizeguy said:
Well.... Use msm download tool then.. Since you can go to fastboot, it will reset everything and lock the BL.
Click to expand...
Click to collapse
What a coincidence, I am watching a video on how you can fix a bricked OP6, wich does exaclty what you said.
Thanks!
ian_99 said:
I tought it would be as simple as unlocking the bootloader, but whatever I try I can't get my device to show up in the command promt when using the "adb devices" command while in fastboot.
Click to expand...
Click to collapse
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.
rhai said:
You should do "fastboot devices" in fastboot mode!
I see thay you're doing "adb devices" instead which is wrong.
Click to expand...
Click to collapse
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:
ian_99 said:
Oh god that actually worked, how could I have forgotten I had to use the "fastboot" command.
I can't thank you enough :victory:
Click to expand...
Click to collapse
No worries. Cheers!