Related
im trying to enter fastboot from bootloader but every time i select it, it just reloads the bootloader. everything else works fine.
the bootloader IS fastboot mode.
Well when I run fastboot protocol nothing happens
strker45 said:
Well when I run fastboot protocol nothing happens
Click to expand...
Click to collapse
Get into Bootloader. (I use ADB command: ADB Reboot Bootloader)
Use the volume down button to select "Fastboot Protocol."
It is deceptive as the screen on your Shield won't change.
Use your fastboot commands now. See if that works.
You need to make sure your fastboot and adb drivers are installed and recognized.
Also need fastboot on your pc of course. Good luck.
Once again, the bootloader is fastboot on your tablet, if you are on that screen then you can use fastboot if the above conditions are met.
Same symptom here.
When Android is loaded, Win10 finds it as both MTP and USB debugging device. adb is reporting back. All well.
However, when shield is in fastboot mode, fastboot finds nothing.
In my case reason was driver:
when connected in fastboot mode, win10 wants to install an
Android Device -Android Bootloader Interface
=> you see this in device manager
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Reconnect your shield.
In my case this worked.
Hope this helps
vrmuhr said:
To satisfy Win10, download NVIDIA USB driver from here
https://developer.nvidia.com/shield-open-source
hence point the driver install in Win10 device manager to the driver download/extract location
Click to expand...
Click to collapse
Thank you, worked very well for me.
When I try to install the USB Drivers It fails with an error message.
ADB devices works, but fastboot devices doesnt.
I'm on Windows 10.
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
redpoint73 said:
Are you in bootloader-fastboot mode, when trying fastboot command? Since you need to be, for fastboot commands to work.
Fastboot commands only work in bootloader-fastboot mode.
adb commands only work when booted to OS, or alternately booted to custom recovery TWRP (when applicable).
Click to expand...
Click to collapse
Yes, I'm trying fastboot from the bootloader screen.
On windows 8.1 it works, I can install the needed drivers, on windows 10 I cannot. Doesn't work. I wonder why adb works but fastboot doesn't.
I had this exact issue up until today, and this what I did to get fastboot on my shield tablet:
1. Uninstall all adb usb drivers just to make sure you start from a clean slate.
2. Then go to Nvidia (https://developer.nvidia.com/gameworksdownload#?search=SHIELD Family Windows USB) and download their Nvidia shield tablet drivers.
3. While plugged into the computer (have the tablet set to transfer files or mtp) go to the Bootloader menu on your shield tablet and then on your computer go to device manager and update the drivers. For me the device showed up as Fastboot, right click and select update drivers from the folder that you unzipped your nvidia shield tablet drivers to. When I did this I actually got an 'This device cannot start. (Code 10)' error message but I think this is okay because when I looked at the device manager again a new listing had appeared near the top called Android Composite Device.
4. Now go through the exact same process to install the drivers that you did for the 'fastboot' device but now for the 'Android Composite Device', you should also still get the 'This device cannot start. (Code 10)'. After you've done all that reboot the Shield Tablet.
5. Once the tablet has rebooted go to command prompt with Administrator Privledges and type ADB devices and your device should show up, then type adb reboot bootloader and the tablet will reboot into the bootloader menu. I this point I did not select fastboot protocol and I'm not sure if this made a difference, but in any case in the command prompt type Fastboot devices and at least for me this finally worked.
I hope this helps.
Thank you Captain_FSU! :good:
I had the same problem. My Shield K1 was showing up on adb devices but not at fastboot devices. I was unable to update the driver. In Win 10 Device Manager my Shield was showing up at Portable Devices and it was impossible to install the driver there. So finally I am able to unlock bootloader and install TWRP.
usb debugging is enabled on device. running latest version of adb, fastboot. Have tried on both mac and win10 but same issue on both.
Oneplus 7 pro is running 10.3.0GM21AA
>fastboot devices
>adb devices
List of devices attached
966c8016 device
Trying to use fastboot to flash patched magisk img and install magisk.
Do you enter in fastboot in phone?
Sent from my GM1910 using Tapatalk
Yes tried from bootloader as well
fustyler said:
Yes tried from bootloader as well
Click to expand...
Click to collapse
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
redpoint73 said:
bootloader-fastboot mode is the only time fastboot commands will work. I know you tried this "also". But I feel you are wasting your time trying to run fastboot when phone is booted (instead of focusing on the situation where fastboot should actually be working). adb and fastboot will not work at the same time by definition. Also, debugging does not need to be enabled for fastboot (only for adb).
Click to expand...
Click to collapse
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
fustyler said:
I have tried it from bootloader and still the same on my pc it just says waiting for device.
What else can I try?
Click to expand...
Click to collapse
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
redpoint73 said:
Try a different cable, different USB port. Fastboot can be finicky sometimes. You can also go to Windows Device Manager, find the device, and see if you can manually select the drivers. There is a generic Android device driver that sometimes gets fastboot to work properly on some of my past devices. This is on Windows 7, haven't done this on WIn 10 yet, so not sure if it is exactly the same.
Click to expand...
Click to collapse
Have tried different cables and different machines both pc and mac
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
mnemesis said:
Since adb is working, do an adb reboot bootloader and it'll then boot into fastboot. If you can't get a return on fastboot devices at this point, it could be you haven't oem unlocked your phone yet.
Click to expand...
Click to collapse
I ran adb reboot bootloader from pc to boot phone into fastboot.
In the bootloader it states device state is unlocked
However fastboot devices ran from pc still shows no device.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thanks this fixed it.
Issue fixed by billyt1's comment above. case closed.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Giri Prasad said:
This worked for me as well. Just to make it clear, rephrasing his reply. After disabling signature verification on windows 10, connect your phone in fastboot mode & open Device Manager on Windows & look for Other > Android device.If it is found, This means Windows 10 is not having proper drivers to recognize fastboot device. Now install "OnePlus_USB_Drivers_Setup.exe" & it will show pop up for installing driver & after accepting(this is blocked due to signature verification in normal situation), Android device will be recognized in fastboot mode.
Click to expand...
Click to collapse
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
I have a similar problem. I tried to disable the signature. Installed a new Redmi Note 7 driver. The phone is recognized as an Android phone in the device manager. In Orangefox recovery it is recognized with ADB command. In fastboot it is not recognized. In Orangefox I can't format data. So my ROM is not booting up. So I want to flash fastboot ROM with Fastboot but in Fastboot device is not even recognized.
t
puyow18 said:
ugh. I've tried all of these suggestions and still can't get the device listed in adb while in fastboot.
I even used the TOOL ALL IN ONE without success. Funny thing is, that program recognizes my phone being in fastboot and has it listed. But if I try to flash a recovery from there, it opens a command window and ultimately says there was an error in connecting to the device.
Any help is appreciated.
Click to expand...
Click to collapse
Sorry on the late reply. Pretty sure you can only do fastboot boot boot(recovery).img or\and boot_a or boot_b. Wont let you fastboot flash boot.img.
billyt1 said:
What's you gotta do is look up how to disable signature verification in Windows 10. Then once you done that stuff put your device in fastboot mode then on the window 10 PC open of device drivers find Android phone then bootloader update driver. There will be 2 choices for updating pick the on device one. Should do you right.
I had to do this after flashing the T-Mobile version to my international version with the msmtool and it locked my bootloader for me
Click to expand...
Click to collapse
Thank you so much!
I also had same issue. my redmi note 6 pro and asus zenfone max pro m1 can be detected in adb but not in fastboot. tried everything. changing driver/disble signature verification. also tried virtual box ubuntu/window 7. but not succeeded. It is actually an issue with usb 3. so I bought usb 2 hub. now everything works fine.
Thank you Thank you Thank you Thank you Thank you Thank you...I have been fooling with this all day
Hi, I already solved this issue (but this only works for xiaomi phone (Redmi Note 7 to be specified), for other brands I think need to download your devices flasher/driver tool)
For Xiaomi user only
1. Download Mi Unlock Tool (https://mi-globe.com/download-xiaomi-mi-unlock-tool-all-versions/) (Version 4.5.813.51)
2. Extract the files anywhere you like
3. Run MiUsbDriver.exe to install the driver
4. Try fastboot devices command
I hope this helps you guys. The Mi Unlock Tool also useful to unlock device locked bootloader.
For other devices maybe can follow this tutorial
Fixed: Fastboot not detecting your Android device
Fix the Fastboot not detecting your device. If your device is not detected by the Fastboot then these tricks will really help you.
www.qasimtricks.com
Hi guys,
Looking for a genuis here...I've spent the last few days trying to work this puzzle out:
Installing GrapheneOS onto Pixel 3 phone using Windows 10, using command line tools only. Android Studio is not installed on the PC.
Here's what I've done so far...downloaded:
The Pixel image - GrapheneOS stable channel for Pixel 3
ADB & fastboot
First we downloaded fastboot (ADB, Android SDK platform-tools for Windows): https://developer.android.com/studio/releases/platform-tools - had an issue with the fastboot flashing unlock command...it doesnt unlock the device, instead says <waiting for any device>
Then we deleted the SDK platform tool and installed Minimal ADB & Fastboot and the same darn issue happened - the fastboot flashing unlock command doesnt unlock the device... command prompt says <waiting for any device>
The device is carrier unlocked, OEM unlocking enabled, USB debugging enabled, File transfer (MTP) mode on.
The following commands work with the SDK platform-tools & minimal ADB & Fastboot: adb devices, adb reboot bootloader
The block is the command: fastboot flashing unlock as we keep getting <waiting for device>.
Tried to fix this myself, here's what has been tried so far (not necessarily in this order):
Checked Fastboot version... fastboot --version works for both downloads so it's recognising it! Wahoo.
Used command prompt & powershell - when it gets to the fastboot flashing unlock command the response is always <waiting for device>
Checked the PATH (in control panel / advanced setting) and made sure environmental variable goes to the right folder
Downloaded Google USB Driver - nothing changed, we already had up-to-date drivers
Tried to change the fastboot script, click to open the fastboot file, when I click "open" the command prompt pops up, red error message flashes then the command prompt window closes in the blink of an eye. I then turned off Windows secuirty setting for app, same thing still happens.
Tried all USB ports with USB-C cable - same error <waiting for device>
Tried all USB ports with anotehr USB-C cable - same error <waiting for device>
Please help!
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
jwoegerbauer said:
The ‘waiting for device’ is generated by Fastboot on PC when it can’t detect your device / can't communicate with phone's bootloader.
If the matching "Android USB Driver" got installed on PC, if latest Fastboot driver got installed on PC, too, and if you have rebooted PC afterwards at least once, then Fastboot should work if USB-cable that came with phone is used.
Hint: Try a different USB port on PC.
Click to expand...
Click to collapse
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Redsquirrel77 said:
Thansk so much for your reply! I have a few questions though...
I think it can communicate with the device as "adb reboot bootloader" turn the phone off and puts it into fastboot mode?
What is a macthing Android USB Driver? In Device Manager the pixel 3 appears under "portable devices" so I assume that means we have a driver for the device?
Thanks again!
Click to expand...
Click to collapse
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
jwoegerbauer said:
Whether phone got booted into fastboot / bootloader mode via command
Code:
adb reboot bootloader
or not can only get verified by command
Code:
fastboot devices
Your Google Pixel device is based on Qualcomm SDM845 Snapdragon 845 chipset, hence the "Android USB Driver" I mentioned must match this chipset.
Download Qualcomm HS-USB QDLoader 9008 Driver (2022)
Want to connect your Qualcomm powered phone to computer? Here you can download Qualcomm HS-USB QDLoader 9008 Driver with installation guide.
www.ytechb.com
Click to expand...
Click to collapse
Thanks so much, I think we are getting closer to success!
Qualcomm USB driver downloaded and successfully installed.
Update since the Qualcomm USB driver download:
adb reboot bootloader command works - phone goes into fastboot mode
fastboot devices - no response (new command line)
fastboot - -version shows version and installation
fastboot flashing unlock response is still <waiting for any device>
Used command adb shell getprop ro.boot.cid and response is 00000000
Response should be 11111111 if it's a Google phone...is this my issue? Or does it help explain why fastboot isn't working?
Fastboot operates on device's bootloader only if unlocking bootloader isn't denied. Makes sense,, doesn't it?
Me and all my friends always test this by running
Code:
adb devices
adb shell "getprop ro.oem_unlock_supported" <- on some devices: adb shell "getprop sys.oem_unlock_allowed"
If returned value is 1 - or true, then it's supported otherwise it's not.
Hi,
I don't know if it will help but try this.
PROBLEM
I tried all manner of ADB drivers and fastboot drivers for the last 4 hours just so that I am able to oem unlock this OnePlus device.
I have all OnePlus drivers installed. I have the ADB drivers installed from here. With all these I was able to run adb commands on the phone when it was on including commanding the phone to enter into EDL mode, commanding the phone to reboot into bootloader (fastboot mode). However in once in Fastboot mode, I could not communicate with phone and all I got was "waiting for device".
SOLUTION THAT WORKED FOR ME
It could be a computer brand model. Turns out the problem was not Windows. The problem was not Oneplus. The problem was my Lenovo Thinkpad which apparently requires its own Lenovo USB drivers.
If at all you're on Lenovo machine and you're stuck on "waiting for device" in Fastboot mode despite trying everything, then try installing Lenovo USB Drivers. I would recommend installing the generic ADB drivers first from here. Then installing the Lenovo drivers that are specific to you machine from here. Mine is Thinkpad.
I really hope this helps if not you, then someone else just about to pull their hair out.
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
I had the same issue with my op9 unlocking bl.
ADB and Fastboot 29.0.2.zip | by evildog1 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Use these and open your command window from this . Makes a shortcut on your desktop. I did and unlocking bl worked perfectly.
cass89 said:
searching all over the internet on how get my computer to recognize my device in fastboot..
I already had universal adb drivers installed, along with android studio.. so adb worked out of the box. I tried to root, got to where I need to unlock the bootloader but no fastboot..
Tried reinstalling universal adb drivers, also tried a few other downloads from google with no luck on anything..
Searching the forums it seems like fastboot 'just works' for everyone else, so maybe something on my computer is messed up..idk
device manager just shows 'unknown android device'
my phone is oneplus 9 unlocked version, model LE2115
any help is appreciated
Click to expand...
Click to collapse
Double post
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Make sure you enable oem unlocking in dev options first and reboot.Reboot to bootloader,issue command $fastboot flashing unlock..
cass89 said:
ok now I'm confused.. those drivers didn't work. following the root guide on here it says 'unlock the usual way''boot to bootloader''issue command 'fastboot flashing unlock''
so I decided to try rebooting to fastboot instead, which brought me to fastbootd
fastboot does recognize fastbootd, but the unlock command "flashing unlock" is unrecognized
So do I use bootloader or fastbootd to issue the unlock command?
if the latter, why would fastbootd not recognize the command?
the 'oem unlock' option is ticked on...
Click to expand...
Click to collapse
Are you a carrier variant or global unlocked 9/9pro?
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
cass89 said:
OEM unlocking is enabled, reboot to bootloader, command 'fastboot devices' shows no devices
Still have unknown android device in device manager
It's a global unlocked 9
Click to expand...
Click to collapse
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
mattie_49 said:
Did you create a shortcut to those adb driver's when you installed; on desktop. And open cmd window in that spot. ?
Click to expand...
Click to collapse
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
cass89 said:
I'm not sure what you mean by shortcut
I unzipped the file to my desktop, then tried installing driver through device manager, but no driver was found.. I then tried installing the driver with the "DPInst_x64.exe" file, but it says install failed with no other explanation
I tried just opening a command prompt in that folder, but with no driver installed, it still isn't recognized
Thanks for helping, I'm lost at this point lol
minimal_adb_fastboot_v1.4.3_setup.exe | by shimp208 for Utilities
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
Click to expand...
Click to collapse
Try one more thing. Install these and creat shortcut on desktop and try opening cmd in this. We gonna get you unlocked.
One last thing. You have also went into developer options and tic'ed "USB debugging on then ok on device when it asks if you wanna allow phone to communicate.
tried that, still nothing. usb debugging is on.
all I need is a working driver, everything else should be good..
one thing which i'm not sure if it's an issue, I'm using an old usb c to usb 2 cable, I'm not using the cable that came with the phone because my computer doesn't have usb c ports.. but adb and mass storage/file transfers work with no issue
Hate to say it, but it still COULD be your old USB cord even with file transfer and adb functionality preserved. I had a cord that did do file transfer but not adb. You should try another cord...
Here's another driver source to download:
Universal ADB Drivers
2 new cords, and also tried multiple driver downloads, but still nothing... i was really hoping to root this phone and it seemed so easy for everyone else, thats why i bought it.. but I guess I'm stuck with a locked bootloader...
I could try factory resetting windows or the phone, but would that even make a difference?
..rereading the root guide, at the beginning it says "if you're on global and want root, flash the eu boot.img" but I'm not sure if he means do that first or use that for the guide.. I'm assuming I need the bootloader unlocked in order to flash it first, but maybe not..
..also should I have just commented in the root guide post, instead of making a new post?..
I'm sure you've tried another usb port on your computer.
Last thing to try: another PC.
Shouldn't come to that, but that's where you look to be.
Got it!! Someone posted about the op6 not working either and the fix is turning off windows driver signature, not sure why but that worked for me..
Thanks, now on to root lol
I just had some serious fastboot driver issues when setting up my oneplus. Not sure if this helps but can you at least find the driver folder that was installed on your c:drive when you initially installed the drivers. Then check your device manager when your phone is in fastboot and update the device (usually under portable devices) through that path?
If you get a tampering /corrupt error when you do this you can disable driver signing in windows which is what worked for me thanks to this saint.
[Guide] Fix Device Not Showing Up In Fastboot Mode (Windows 10/11)
You sir are saint...I've been trying to get fastboot to recognize my OP6T for the last 8 hours. Thank you so much!
forum.xda-developers.com
Edit: you solved it while I was responding....I had the same issue..congrats...I know the feeling!