Database Info

[Q] Sticky Bit Fastboot

So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.

fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.

KitsunePaws said:
Mine did that for a short while after I screwed up a flash, I reflashed boot and while running tossed the adb command to get into fastboot and then left it properly. Haven't seen it since.
Click to expand...
Click to collapse
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.

fallnSaint said:
To clarify... Flash boot from recovery, while that is running adb reboot bootloader? If that is the case I have a different set of problems to "boot", I can't get my pc to recognize the phone while in recovery. Everything else is recognized, even reinstalled drivers to be certain, pc doesn't even try to install a driver for recovery. Tried both TWRP & CWM.
Click to expand...
Click to collapse
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.

KitsunePaws said:
Memory is fuzzy but I'm pretty sure I did it from fastboot, this happened to me about the time shabby was trying to fastboot boot boot.img and I ended up flashing it instead.
Click to expand...
Click to collapse
I had this same issue when porting TWRP ^^^.
I can't seem to find my posts on it right now, but someone just said do a clean flash. No problems since

how did you do this please!

fallnSaint said:
So... Anyone have any experience getting sticky bit turned off on fastboot? My phone boots to it anytime I try to reboot or do a regular boot up.
Click to expand...
Click to collapse
Okay, this will probably help you...while your device is in Sticky Bit Factory Fastboot, open up a command prompt and connect to your device (given you know how to do so in your folder containing your fastboot app and drivers). Then type "fastboot oem fb_mode_clear" This command will allow your device to boot into system normally. Problem is (I think) when a failed flash occurs sometimes it sets your device in that mode and the above command clears it. Another way to manually place a device in the same state you described is to enter this command using fastboot: fastboot oem fb_mode_set. I believe that is how RSD Lite automatically reboots your device into factory fastboot mode after flashing partitions (.mbn) on your system so that it may resume flashing the boot, recovery, and system images, etc. Let me know if it helps.....
Sent from my XT897 using xda premium

TF300t constantly booting into recovery

I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?

tjk639 said:
I have a TF300t that I have been doing custom ROMs on for over a year now. Not to long ago it messed up and I ended up doing a ADB side load of the the current software from ASUS to recover it. I wanted to try CM11 so I followed the directions to get the right version of TWRP installed. I noticed that it was really slow at stuff like wiping cache and dalvik, so I decided to reflash TWRP through ADB instead of a zip file.
All went well and I got into android and went into TWRP to see if everything went okay. I'm in TWRP, but I cannot do anything. Only system will mount and it says I am not rooted and wants to install supersu. If I reboot or power off it just goes back into recovery. Doing the power + vol down will not get me into the bootloader and will instead just power cycle at the ASUS logo.
Any idea on how to fix this, or did I just royally brick my tablet?
Click to expand...
Click to collapse
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.

cmendonc2 said:
When you first reboot back into TWRP, try running fastboot commands. You may be able to reflash your recovery, or follow Buster's recovery method from there on.
Click to expand...
Click to collapse
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.

tjk639 said:
I just get stuck at waiting for device. Is there a section I am supposed to be in? Or do I do it from the home screen for twrp? I checked device manager and it does have Transformer listed in other devices.
Click to expand...
Click to collapse
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"

cmendonc2 said:
Use the reset pin on the SD card side and then reboot back into TWRP and try with "fastboot devices"
Click to expand...
Click to collapse
Where do I find "fastboot devices"?

tjk639 said:
Where do I find "fastboot devices"?
Click to expand...
Click to collapse
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.

cmendonc2 said:
As in the command:
Code:
fastboot devices
Else you could try:
Code:
adb reboot bootloader
from the ADB in TWRP and then try fastboot commands.
Click to expand...
Click to collapse
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.

tjk639 said:
It's not finding anything and ADB sideload fails. I'm doing the fastboot commands from the fastboot folder I have been using with other fastboot stuff for the TF300.
Click to expand...
Click to collapse
hmm idk. Im guessing you flashed the wrong version of TWRP, which has ended up in a brick for most users, but they had fastboot access and could later recover it using this: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. You dont seem to have either ADB or fastboot, and TWRP is in a non working state. You could try reinstalling your fastboot and ADB drivers with the universal naked drivers, and then retrying ADB reboot bootloader and fastboot.

All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.

tjk639 said:
All fixed!
Here is what I did.
1.) Installed naked drivers following the guide at the link provided above. This allowed me to get into the bootloader, but I was unable to successfully flash anything.
2.) So, I followed this guide: http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Probably lost all my user data, but worth it for a working tablet.
HUGE thanks to cmendonc2 for the help and ultimately leading me to the correct solution.
Click to expand...
Click to collapse
No problem, glad I could help!

Unable to root after OTA update

Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?

arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?

No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).

arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049

Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.

fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk

Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation

arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app

arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7

Trying to flash TRWP Moto Z recovery - not working

Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork

spacezork said:
Hey everyone, longtime lurker here finally going to try to get involved more since I just got a new Moto Z and I don't have much of a background with motorola hardware/software. I'm trying to flash recoveries through fastboot and I can't seem to get it working. I'm probably going to wait a while before I try again since there is not much support for the moto z yet. I am running MPL24.246-45 v6.0.1 XT1650-03, I have unlocked the bootloader through the instructions on the motorola website.
On the bootloader screen I can confirm it is now unlocked, but everytime I flash the TRWP recovery through fastboot I get the error message: "<bootloader> img not working or corrupt". I am trying to flash the most recent twrp recoveries for moto Z (twrp-3.0.2-0-griffin.img) but wasn't able to successfully flash it.
Coming from a samsung background, I might be skipping a step or doing something wrong. I am running the bell canadian firmware. Since I messed up my partitions on my last phone I want to be careful with this one, I mostly want to figure out why I am getting this error while trying to flash the recovery when
my bootloader is unlocked and when I check "adb devices" my moto is being read.
Thanks!!
szork
Click to expand...
Click to collapse
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar

the ljubich said:
didn't try it yet, but did you try renaming it to recovery.img (if on windows be sure extenstions are shown so it is not actually recovery.img.img) and run (didn't see which command you are using:
Code:
fastboot flash recovery recovery.img
but search around forums about encryption thing and similar
Click to expand...
Click to collapse
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork

spacezork said:
I've tried both with the original twrp name and extension as well as with renaming it to recovery.img, didn't seem to make a difference. If I am connection to the device itself does that mean that adb/sideload is installed properly? I mean I was able to unlocked the bootloader so I would assume so.
szork
Click to expand...
Click to collapse
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.

the ljubich said:
i really don't know then.. if you successfully unlocked bootloader then fastboot should be ok. you can check in device manager. it should be bootloader iterface not adb interface there (you got me confused with mentioning adb so I am just writing to be sure).
also check if your device is shown when typing
Code:
fastboot devices
or try redownloading twrp.
otherwise I am out of ideas, sorry.
Click to expand...
Click to collapse
Sorry for my confusion with adb/sideload - from what I understand I need both to be able to connect to my device (correct me if im wrong). In the bootloader menu I see "flashing_unlocked" which I believe confirms my bootloader being unlocked, but then at the top of the text right under the dead android guy I see "AP Fastboot Flash Mode (Secure)" could that be an issue?
I can retry downloading the recovery from the TWRP site, but I know I'm downloading the official one already, just can't put my finger on why I'm getting that error message if others are doing it successfully.
thanks for helping :good:

Do you have the Verizon model?

samwathegreat said:
Do you have the Verizon model?
Click to expand...
Click to collapse
I have the canadian BELL model XT1650-03

spacezork said:
I have the canadian BELL model XT1650-03
Click to expand...
Click to collapse
You're at the bootloader, it says Flashing Unlock so yes your bootloader is unlocked and you should be able to flash TWRP no problem.
Did you recently install this .45 firmware? Are you sure that TWRP wasnt actually flashed? I see lots of errors like this from the bootloader and its usually just rubbish.

The twrp does not show the actual memory value of my cell phone and does not let me paste ROM backup, from insufficient memory? how to support it?

I updated my phone to .45 when I bought the phone I believe 1-2 weeks ago, it's definitely NOT flashed as the flashing process runs for 0.2 seconds and fails. I can even boot in the stock recovery afterwards confirming that nothing flashed. I wish I knew what I was doing wrong? possibility of drivers not installed properly?
Before I try and flash recovery I check USB debugging, OEM is unlocked, don't verify ADB files and accept Unknown sources. Is there anything I'm missing?

What if fastboot boot twrpname.img
It's really weird anyway...

enetec said:
What if fastboot boot twrpname.img
It's really weird anyway...
Click to expand...
Click to collapse
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.

spacezork said:
I've been doing fastboot flash twrpname.img after opening cmd terminal with SHIFT-MOUSE2 in the designated folder. I have not tried that command specifically what's the difference between doing fastboot flash/boot as far as flashing a recovery.img
edit: I've read on different articles that people sometimes try and flash from the recovery menu? I understood it has to be while your are on the bootloader screen, could it be something to do with that? Or is it still a possibility the drivers may not be installed properly.
Click to expand...
Click to collapse
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...

enetec said:
With fastboot boot you send recovery to your phone and ask it to boot on it without really flashing it...
It's useful e.g. to take a full stock backup including original recovery, to test a recovery prior to flash it or to use TWRP to root BUT remain on stock recovery...
Not on all phones it works, but on Moto Z should....
P.S.: you have to be on fastboot screen not on recovery when flashing...
Click to expand...
Click to collapse
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.

spacezork said:
by fastboot screen you mean the bootloader menu right?
I've been accessing cmd from designated folder with .img file in it
- adb fastboot recovery
- fastboot flash recovery.img..
and I get the "img not working or corrupt" after it tries to flash it (lasts 0.2 seconds) and nothing is done.
Click to expand...
Click to collapse
Right, bootloader screen. Enter on it by key-comb... not by command...
Even the real flash take same time... Sending seems to work, is something on verify that doesn't "like" it...
Try to download again recovery and/or check its MD5...

if reading correctly (and what I told you yesterday) command is
fastboot flash recovery recovery.img
and not
fastboot flash recovery.img

hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????

Troll amiga said:
hi can any one help me i need to get back to stock and lock boot loader to update i have eu any one please ???????????
Click to expand...
Click to collapse
try following this instructions: http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
and download eu rom from here: https://mirrors.lolinet.com/firmware/moto/griffin/official/RETEU/
i don't know from which ROM you are coming, don't know if downgrading works, but this was onl RETEU ROM i could find.

I have the exact same phone and I've upgraded to Nougat but I got my TWRP working. You need an unlocked bootloader and after upgrading to nougat, the option "unlock OEM" need to be enabled again.
I've used this TWRP : https://dl.twrp.me/griffin/twrp-3.0.2-0-griffin.img.html
Also I tried to only boot on it at first with the command fastboot boot twrp.img then I saw it was working, I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.

cilk said:
...I flashed it with fastboot flash recovery twrp.img but got the error : (bootloader) image not signed or corrupt . But I booted the recovery from the bootloader and TWRP was working even with this error.
Click to expand...
Click to collapse
Yeessss... I don't know how could I forgot it!!! :silly:
The message (I forgot I received too...) is *only* to indicate that recovery is not signed! But before there is a clear "Done" confirming the flash!
Just boot on it!

Stuck in Bootloader (Solved)

So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
EDIT: Solved it by using Fastboot and flashing the stock firmware without the -w so far everything is back to normal....know to get that dern kernel again

gears177 said:
So i recently tried flashing a new kernel and for whatever reason my pixel 2 did not like that at all. Upon reboot after flashing it now just goes into the download mode where i have the option to reboot bootloader go into recovery and go into download mode. Normally not a big issue at all but this time when i go to load into recovery or load into Download mode its says Operation Denied. Upon a reboot or trying to reboot into safe mode it says ERROR: Slot unbootable: Load Error. Will ADB still work to flash this? not really sure what to do at this moment.
Click to expand...
Click to collapse
First off, does fastboot recognize the device?

DuckRuckus said:
First off, does fastboot recognize the device?
Click to expand...
Click to collapse
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface

gears177 said:
It does not under adb devices nothing shows up. In device manager it does show up as Android bootloader interface
Click to expand...
Click to collapse
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.

DuckRuckus said:
ADB=system. Fastboot=boot. You can't boot your phone, so you're not in android, thus no ADB devices. Type "fastboot devices" and see if it's recognized.
Click to expand...
Click to collapse
Ah nice didnt even realize its recognized under fastboot ive tried flashing the stock recovery but it just gives me an error

gears177 said:
Ah nice didnt even realize its recognized under fastboot
Click to expand...
Click to collapse
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?

DuckRuckus said:
Good news! So, your best bet at this point would be to re-flash your current factory image, with /w removed. If you still want that same kernel, flash it before Magisk.
Just out of curiosity, what method did you use to flash it in the first place?
Click to expand...
Click to collapse
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Nevermind got it flag responsible for deleting userdata thanks alot for the help appreciate your time

gears177 said:
Flashed it through twrp aroma installer.
What does the -w do in the fastboot command just curious
Click to expand...
Click to collapse
It wipes all your data, that's why you remove it from the flash-all.bat script, unless you need to perform a full wipe. Telperion has an excellent guide for installing the lastest software, if you haven't already read it.
I've heard users having back luck flashing kernels in TWRP, as the kernel has something to do with recovery. I always use the method of booting the TWRP image in fastboot, use ADB to push the files to /tmp, and then do an ADB shell TWRP install of those files. TWRP, kernel, then magisk, in that order. I always reinstall all three, just to be on the safe side, and have never had any issues. Takes a little while, but not as long as redoing the whole freaking thing:silly:
Looks like you figured it out, before I finished my reply