I looked everywhere and tried all i could find but my phone wont be recognized in fastboot.
Sideload works though.
Device is recognized as "bootloader device" which seems good, but the fastboot devices gives nothing...
I am on windows 10, tried different drivers, force driver, uninstall and then reinstall with driver verification disabled.
Almost gave up on rooting for this device, never had this much trouble since galaxy S1!
I checked windows updates and got nothing.
Really lost here, anybody have more suggestions?
After looking at other options it seems windows 7 install is the way to go... Really freaking annoying, will try on a vm first. Not really in the mood of doing a second OS just to root the phone lol..
Sent from my ONEPLUS A3003 using Tapatalk
You can install the driver after disabling the driver enforcement..
Sent from my Xiaomi Mi 5 using XDA Labs
Gugus38 said:
I looked everywhere and tried all i could find but my phone wont be recognized in fastboot.
Sideload works though.
Device is recognized as "bootloader device" which seems good, but the fastboot devices gives nothing...
I am on windows 10, tried different drivers, force driver, uninstall and then reinstall with driver verification disabled.
Almost gave up on rooting for this device, never had this much trouble since galaxy S1!
I checked windows updates and got nothing.
Really lost here, anybody have more suggestions?
Click to expand...
Click to collapse
You can try to live boot Ubuntu on your PC with a USB drive and attempt it with that. I haven't had any issues with adb or fastboot on the newest Ubuntu. It would be worth a shot before downgrading your OS or installing an alternative.
mapolidori said:
You can try to live boot Ubuntu on your PC with a USB drive and attempt it with that. I haven't had any issues with adb or fastboot on the newest Ubuntu. It would be worth a shot before downgrading your OS or installing an alternative.
Click to expand...
Click to collapse
Seems like a good idea, thanks ! Will try that
Sent from my ONEPLUS A3003 using Tapatalk
Related
I am stuck trying to unlock my boot loader because I cannot get the drivers for fastboot to install. As soon as I try to update android 1.0 in device manager I get a windows error stating 'windows encountered a problem installing the driver software for your device' and i get the error code: This device cannot start. (code 10). At the same time as the driver install fails a error comes up on the bottom of my galaxy nexus while in fastboot mode stating: Fastboot command error -2147483647. Below is a list of things i have tried.
- Ensured USB debugging is enabled
- Tried different USB ports/cables
- Tried separate computers running Win7/XP
- Tried installing drivers using another Galaxy Nexus
- Tried installing and uninstalling drivers from different sources such as tool kits
I would be highly grateful if someone could help out this is driving me mad. Does anyone have suggestions? Thanks in advance
http://developer.android.com/tools/extras/oem-usb.html
DynamicRam said:
http://developer.android.com/tools/extras/oem-usb.html
Click to expand...
Click to collapse
Thanks but Ive already tried that and still no luck. Its still got a yellow triangle on the SAMSUNG android adb interface in device manager.
ttm94 said:
Thanks but Ive already tried that and still no luck. Its still got a yellow triangle on the SAMSUNG android adb interface in device manager.
Click to expand...
Click to collapse
Have a look at the "basics" link in my signature. There is a link to drivers that work and how to install them.
efrant said:
Have a look at the "basics" link in my signature. There is a link to drivers that work and how to install them.
Click to expand...
Click to collapse
Just an update I tried on a third computer and everything went well must be something odd since I tried it on two different operating systems before. Thanks for the help anyway guys
Sent from my HTC One X using xda premium
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
dnpmoney45 said:
Hey guys i've been looking through alot of google and can't seem to come up with anything so i turn to you awesome people.
My friend got a Galaxy Nexus GSM and he bought it with a boot loop problem. The phone is rooted and bootloader unlocked. I know because i can go to CWM recovery and also theres the unlock sign on it. However I can't get my computer to recognize it what so ever not even mount the storage. I figure i need to get the drivers to install but i need it to be recognized in device manager to do it through a rootkit. I tried to install the ADB drivers but also got no luck. I then tried to get to ODIN for it to work but ODIN won't recognize it either. Is there any way to install the drivers so i can put on a ROM on this. I think the person he bought it from formatted everything and messed it up. Is there anyway i can install the drivers without getting it to recognize first? I tried it in windows 7 and in windows 8. ANY HELP IS GREATLY APPRECIATED!!!
Click to expand...
Click to collapse
read the stickies
http://forum.xda-developers.com/showthread.php?t=1626895
Pay attention to Section A. Forget Odin, no need to be using that.
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
dnpmoney45 said:
First off thanks so much for the reply and help it is very aprreciated!
Secondly i did come across this sticky however like i stated the phone is in a boot loop which means i cant get past the google logo in order to set it in developer mode and set usb-debugging neither can my computer recognize the phone when i plug it in, using the original cable i've tried every port there is on my desktop and laptop and nothing comes up in device manager. The phone is completely wiped and no OS is on it. Is there any way i can get a ROM on the phone?! This is one idea i have but i don't know if it'll work, I was thinking of buying a another working nexus install the drivers with that one and then i can get the bootloop one to get recognized? and return the new one. Will that work?
Click to expand...
Click to collapse
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
cupfulloflol said:
You need to get adb to work with your device, which you can do in a custom recovery. You don't need to have USB debugging enabled, you would if you were booting into the OS, but not the recovery.
You can get drivers setup while in recovery or fastboot just as easy as if you were booted into the OS, so no you don't need another device.
Click to expand...
Click to collapse
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
dnpmoney45 said:
thanks thats great news cause i dont have that kind of cash but how do i get ADB to work with the phone every installation guide i've looked at requires that i have the phone recognized om device manager. Is there anyway to install adb without having the device to recognize?
Click to expand...
Click to collapse
again, read the thread i gave you. if you're still asking this question, read it again.
Isn't that for the nexus 4? And I did pay attention to section A but it told me how to install the drivers which is the same way as every other tutorial I've looked at. My device doesn't show up on my computer and I can't install their way. As for the fastboot driver installation idk what their talking about. I followed the instructions though and got no results. I didn't do the whole thing cause for part C I need the original rom for galaxy nexus and also I don't know if the platform tools zip is for my device so I haven't gone through with it just yet. I'm sorry it's not my phone so I don't want to mess it up even further. I've read about the part with it being in recovery mode with the volume up + power option but I'm at work and haven't tried that yet but I doubt that will work since the phone is clean. Can u please be a little more specific there's 99 pages that I have to go through for that sticky. If u can't it's ok I'll just have to go through it next week. Once again thanks for pointing me in the right direction and giving me some hope.
Sent from my Nexus 4 using xda premium
WTF, how in the hell did that thread get here, sorry man
This is the right one
http://forum.xda-developers.com/showthread.php?t=1626895
a maguro wrote this.
Oh ok thanks this makes a lot more sense. Sorry for not telling u that earlier lol.
seriously thanks ill try it tonight.
Sent from my Nexus 4 using xda premium
ok so i tried the link but im always stuck with part A. When i go into fastboot and then try the command "fastboot devices" it hangs on waiting for the device. I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Am i missing something here? i did everything in the other steps such as downloading all the files into the same directory and everything. Im using windows 7 and i updated all my drivers for usb and even tried different usb cables including the original and usb2.0 and 3,0 ports but still no dice. I also tried it on windows 8 and got the nada.
dnpmoney45 said:
I can't see the device anywhere on my computer to install the fastboot drivers as instructed by 1wayjonny in this post http://forum.xda-developers.com/showpost.php?p=20058157&postcount=1
Click to expand...
Click to collapse
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
bk201doesntexist said:
You reboot the device into bootloader/fastboot mode, then you connect the USB, and there's no sign at all that a USB device has been installed?
Remove all drivers, reboot, and start over. Get a tool for Windows that allows you to really dig on all of the installed drivers and remove all Nexus devices drivers permanently. Rant: Umm, Windows sucks bad. Thanks Linus!
Click to expand...
Click to collapse
I've done it both ways just to ensure it wasn't something that simple. I uninstalled all drivers i can possibly find theres non no where i used CC to look for more and device deview and even unistalled the java se and eclipse and android SDK and all the packages and installed them again and still nothing. My nexus 4 however recognizes both in adb and fastboot ......
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
dnpmoney45 said:
Anything at all? Anyone?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
bk201doesntexist said:
Well, maybe you could try omapflash. If you can't get several PCs to see the device, then something's wrong with the USB port?
Not even on Linux?
a manta wrote this.
Click to expand...
Click to collapse
I did a little looking up about omapflash and from what i can see so far there needs to be drivers installed first. I may be wrong but i have to do some more research on it and i dont have a linux pc my laptop is down thanks to a power pin connector pin being pulled out. and i dont know if the device port is good or bad i can get a charge but that doesnt mean its fine. What if i get another device and install drivers via that and then try to get it to recognize? would that work?
dnpmoney45 said:
What if i get another device and install drivers via that and then try to get it to recognize? would that work?
Click to expand...
Click to collapse
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
bk201doesntexist said:
To really make sure that the issue isn't on the host side but rather the USB port on the device? Yeah, that would rule it out.
Also, I just remembered: you're not using the USB ports of your PC case are you? Make sure you're using the motherboards' own USB ports.
a maguro wrote this.
Click to expand...
Click to collapse
Thats all it would do?! What about making me able to install the drivers and get the phone to be recognized? No wont work im dreaming?
And no im not using case ports at all i use them for charging and thats all i know at least that those arent reliable.
Windows 8 64-bit...drivers install...stuck
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
rej_ares said:
even I am stuck on the same roadblock. have my GNex stuck on the google logo. can access recovery mode though (TWRP 2.5.0.0). Now i just upgraded my PC to Windows 8 64-bit and cant seem to be able to install drivers.
the problem is that almost all the methods require:
1. GNex to be connected with USB Debugging ON
2. install ADB Drivers
3. get into Fastboot or Recovery
4. install Bootloader Drivers
since i cant get past the Google logo on my GNex...i cant perform Steps 1 & 2.
and if i directly try to install the bootloader drivers the OS returns an error (yellow exclamation next to the installed driver)
Added pictures to help explain better.
Thnx in advance.
Click to expand...
Click to collapse
SOLVED (Dont know how but it worked):
1. Factory reset (TWRP)
2. Installed an old ROM which was already on the GNex
3. Restart...it gets stuck at the Google logo...remove battery
4. TWRP - Factory reset
5. reboot...
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
MightyChigger said:
OK so I am using windows 8.1; have searched everywhere and tried just about everything imaginable but I still cant get fastboot to work with my HTC One. The phone is recognized fine when I type adb devices on the main screen, however, when I boot into fastboot the phone is simply not recognized by Windows any longer. I get the message USB DEVICE NOT RECOGNIZED. I am currently looking to update my HBOOT which is 1.54.0000 and was under the impression that I need to do a fastboot flash to do this. I am currently running Viper Rom 5.8.
I am desperate here and am willing to make a donation to the person who solves my issue.
Click to expand...
Click to collapse
You need a Windows 7 pc.
Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Chilidog said:
You need a Windows 7 pc.
Click to expand...
Click to collapse
well unfortunately for me, I dont have one... can this be done on Windows 8.1?
jpradley said:
Come on. There are other choices.
Download Ubuntu. You can run it from an installation medium without actually installing it.
Click to expand...
Click to collapse
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
MightyChigger said:
Don't know anything about Ubuntu....would probably create more issues trying to figure this out. One way or another, I need to get fastboot working on my machine right??
Click to expand...
Click to collapse
After sending to HTC to have the camera sensor fixed I could no longer get fastboot to work and I had to suffer with stock for a couple of months. I finally resolved this by updating sdk having read recent Windows 7 updates could be the culprit, maybe it was a usb driver update, but was still having issues.I read to try turning usb debug off and on which in the end may have been all that was required. Finally back to S-off running Viper 6.1 which team Viper deserves major props on for a brilliant job. BTW I'm on Windows 7 Ultimate with usb 3 ports only.
Go here and watch the first video: http://forum.xda-developers.com/showthread.php?t=2703585
Hi everyone,
I am trying to update my (unrooted and unlocked) Nexus 7 2013 wi-fi to Marshmallow via OTA. I have installed adb on my system and download the update package file.
When I connect my Nexus to Windows 10, the system recognizes the device as Android ADB Composite and everything seems to be working as it should. I open a command prompt and type:
Code:
adb devices
and the device along with its id is correctly shown. At this point I reboot to bootloader, so I type
Code:
adb reboot bootloader
the Nexus reboots, enters in the bootloader and the following happens:
adb can't find the device anymore
the device manager puts the Nexus among the Other devices and so it appears no driver has been installed for it.
As suggested on numerous tutorials, I right-click on the device and choose to manually install an appropriate driver. And I expect to find Android ADB Composite in the list and instead the only possible choice is Samsung Android ADB Interface — which does not work, because, naturally, Nexus 7 is not a Samsung device.
I have tried to solve this issue by installing the google usb drivers using the 15 seconds install and it didn't help at all.
What can I do to overcome this issue?
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
UncleMike said:
Once you're in the bootloader, adb will no longer be able to see the device. You need to use fastboot to carry out any commands while in the bootloader.
Sent from my Moto X using Tapatalk
Click to expand...
Click to collapse
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
haunted85 said:
Hi UncleMike,
thank you for your reply. I am a bit confused: (once the Nexus is in recovery mode) how do I initiate sideloading if adb can't find the device?
Click to expand...
Click to collapse
I'm only familiar with flashing images while at the bootloader. I've never had to side load anything, so I don't really have an answer for you.
Sent from my Moto X using Tapatalk
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
haunted85 said:
What can I do to overcome this issue?
Click to expand...
Click to collapse
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
jslanger said:
I had a similar issue myself when I started using ADB.
What I found happened, is that once you send the tablet into bootloader, you have to go into Device Manager on your windows machine and tell your computer to install the driver for your Nexus. Why it does this, I don't know. I had to do it yet again once I moved the Nexus into recovery mode to flash the OTA update as well. Good luck. Let me know if you need help with what I (poorly) tried to explain above!
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
nhizzat said:
Adb only works when in recovery or Android. Fastboot only works when in bootloader.
If you have to go through all that, something is broken with the Android driver setup on your computer. I plug any of my Android devices (N6, N7, Moto X, LG G3, Xperia Z3v, or Moto Xoom) into my laptop and they're automatically recognized.
Click to expand...
Click to collapse
If I am just accessing my Nexus 7 in Windows, yes, the tablet is normally recognized. However, once you send it into bootloader and recovery, the computer recognizes the tablet, but it knows it is not in its normal setup...I guess. It just needs some prodding to install the driver at each stage. The only reason I knew how to do this is because I followed directions on this online somewhere.
Hey guys I suggest using this tool called universal adb driver it will install all the drivers for the n7, I had problems sideloading marshmallow because of the recovery mode not being recognized by windows however this tool fixed it right up. It installs drivers for I believe the Galaxy nexus? But they work perfectly fine for the n7.
TL;DR: drivers fail in recovery mode this fixes it.
Here is the link: https://plus.google.com/103583939320326217147/posts/BQ5iYJEaaEH
Sent from my Nexus 7 2013 using Tapatalk
I will send you $50 via paypal if you can either instruct me how to fix it, or if i can mail you the phone and you return it back to me in working order.
I just got the phone. And i have spent the whole weekend reading and following what others have suggested in this forum to no avail.
I wanted to install TWRP onto it. I followed the instruction to unlock the bootloader first int the dev settings, then in the fastboot screen. When i unlocked it i got the yellow triangle, telling me to relock it, that the system cannot check for corruption, etc. It would not move past this screen. I had to reboot. It would not enter any recovery.
I tried flashing back the stock recovery from fastboot, from the stock images, i would not go past this screen. It would not boot into the system.
I then went to try to get back to stock with the instructions from this thread:
http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
Phone will not boot, it hangs at the "google" start screen. I can not unlock bootloader from fastboot now. It gives a "DENIED" message, unable to oem unlock bootloader.
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load. Under download mode, the LG drivers will work. I can only get in download mode on a Windows machine. I can only get to fastboot on a MacOS machine through terminal.
Please help, i am going to throw this phone in the trash otherwise. I will answer any questions you may have that will help solve this.
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
since you have installed TWRP do as written HERE.
It is confirmed that is working for nexus 5x too, read the whole thread anyway!
Caligula36 said:
In a windows machine, the phone will not be recognized. Under device manager, its listed under 'other devices' as 'android' and the driver fails to load.
Click to expand...
Click to collapse
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Sent from my Nexus 9 using Tapatalk
ritchea said:
Wug's may work for you. It may not. I've used it since its inception but have found issues with it off and on. As far as drivers go, my Windows 10 machine seems to have issues since last few updates. So far, (I have a rooted N5, N9, and complete stock 5X) updating the drivers through device manager has worked every time. Choose update from on drivers on PC then run through update on both drivers shown under android interface (or similar). Be sure the device is awake and connected when updating, of course.
Click to expand...
Click to collapse
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
Which stock image should i be using? The .tot file? The OTA or factory image?
Matt__BB said:
Turn on your windows machine
Download the tool in this link http://forum.xda-developers.com/nexus-5x/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258492
Put your phone in download mode
Open the tool, click on the home button "Flash stock + unroot" and check the box under it that says "bricked"
Problem solved
Click to expand...
Click to collapse
NO PROBLEM NOT SOLVED.
I cannot get a connection to fastboot on Windows. Only on Mac through terminal. I can only get into download mode on windows. When i try to unlock bootloader on my Mac, it give a DENIED error.
Stevica Smederevac said:
First of all, no need to pay anything, at least to me. Where are you from? We can try with TeamViewer but i don't have pc right now so if you don't find a solution, i can help you from Wednesday evening onwards.
Sent from my Nexus 5X using XDA Labs
Click to expand...
Click to collapse
Thank you, i will take you up on that offer.
This is the only thing that comes up when i connect via fastboot, this and a drivers not installed alert. I CAN NOT install them manually, the dialog just says the Windows could not find the drivers.
Issue resolved. Mods can remove this thread.
Caligula36 said:
Issue resolved. Mods can remove this thread.
Click to expand...
Click to collapse
Nice:good:
Sent from my Nexus 5X using XDA Labs
Great!
Sent from my Nexus 9 using Tapatalk
What did you do to fix this?
Sent from my Nexus 5X using Tapatalk