Database Info

[Q] pretty sure i have a dead USB port.. any advice?

so i recently came across a used Infuse (at&t model) from a friend, and wanted to do my part on fixing it up from the way he had it.
that meaning of course, flashing a new version, rooting, the basic good stuff we all love to do.
to change to my plan from his, which he didn't have it running under a contract or anything, was slap my SIM card in, and tweaked the APN settings a bit
to work with my Straight Talk plan. it's worked flawlessly and the speeds are way better than what my modded A953 can push through.
as i plug it into my laptop, it reads it can't be recognized and will only charge. not a problem. i Google how to fix this and to try workarounds.
nothing seems to work, and i'm stuck at the rooting process. after rooting, i can workaround to actually flashing and whatnot.
-i've tried Odin and a few other similar programs listed, but need Mass Storage/Download Mode and actual connection to work properly.
-z4root and Gingerbreak, only lag and freeze up my device, causing it to reset/restart with no changes.
-tried using 5 other USB wires, all act the same way.
-won't be recognized by other PCs/laptops, not even my PS3.
-uninstalling and reinstalling the Samsung drivers didn't help.
i've been using it as-is with barely any issues, but the feel of being held back of great roms and goodies.. it's almost disappointing.
this is by far the best phone i've been able to get my hands on and i just want it to work 100%, my way.
so my question is this; are there any other ways to root this Infuse without having to buy a whole new device or USB port/piece for it?
kind of running low on funds due to real life issues and such, so i have close to nothing to spend.
any other root apk's i could try other than what was listed above? any help is greatly appreciated.

Try a dab of alcohol and toothpicks to clean the contacts in the phone. Then try a different 2 or 3 cables. Some cables don't contact correctly. Some don't have data capabilities. Depends on your cables. Also try pushing the cable up firmly or down firmly to ensure contact.
Don't panic till you have done all this.
Sent from my SGH-I997 using xda app-developers app

[Q] Can anyone help with getting my tablet to recongize a pc connection?

Current info on it - Android 4.1.1 and stock build - epad-10.4.4.23-20121127
I was rooted for about 2 months and had the tracking cilents frozen in titanium. About 2 weeks ago I saw a thread about the update for .23 firmware. I went and unfroze the clients and did a reboot with no problem getting the OTA update and restoring root. Before this I was able to hook up my tablet to a pc and transfer files. I didn't have need to use this function until last night when I discovered that it will no longer recognize being attached to the pc.
Essentially nothing happens. There is no sound and notification icon on the pc that a device was attached. Nothing shows up in device manager. The tablet doesn't show the USB connection icon. To make sure the usb port was good i connected my cell phone to it, bluetooth dongle, and a thumb drive. It works fine. This system runs XP with the drivers previously installed and working. I tried my laptop that runs Vista and worked fine previously when connected. Again I get the same issue. Even their Asus sync software on the pc shows no device attached. Just now I tried hooked up the tablet to my work pc and no change. That makes 3 pc's that I've attempted.
I can only think it was the firmware update. That was the only change I made to the system. Last night I did a factory reset of stock to see if a setting got messed up somewhere but there is still no connection. I probably lost root in that process and since it won't connect to the a pc, I doubt I can get that back. That is the least of my concerns though. I fear that something physical with the connector went bad that tells the OS a pc connection is occurring. Would that even be possible to happen yet work fine for charging the tablet?
Thanks for any suggestions or comments.

Yes, it is the JB update if your PC is running XP (not sure about Vista, but it's probably the same). You probably noticed that the options for USB connection in JB are limited to Media and Camera? Under JB the tablet sadly does not connect as an external drive to a XP PC anymore.
The Infinity does shows up under Windows 7 as an external device. I looked high and low, but there does not seem to be a fix for XP.
My work-around for anything I do not want in my Dropbox (which is by far the smoothest way to get something from your PC to your tablet) is using Airdroid from the play store. That app uses your WiFi network to transfer files. Works great! And no cables!
Larger files, like movies, I transfer via SD card. Truth be told - I do not really miss the USB connection anymore.
Sent from my ASUS Transformer Pad TF700T using Tapatalk HD

It's odd that it won't recognise a connection at all. Have you tried reflashing the full stock firmware?
Under JellyBean, XP, Vista, 7 and 8 recognise it as a Portable Media Device. My main PC runs XP SP3, so no, it's not an XP-issue.
With ICS it used to be an external drive, but sadly that ended with JB. (Which is a feature I thoroughly detest on every device including my sgs3, but alas.) Originally they deleted the feature in ICS to begin with, but for some reason it continued to work on some TF700's. Not all of them, though.
I miss UMS.... MTP drives me insane on any device. It keeps whining about literally every file format that it "is not natively compatible with the device [insert 16 more lines of text I have stopped reading because it is actually longer than the dialogue window...]" . Even .jpgs.... Which is ridiculous, as stock gallery recognises .jpgs just fine.

I mailed the tablet in for RMA and they, well someone at the center, signed for it on Friday. I tried doing the wipes and even downloaded the firmware from Asus and reinstalled it from the sd card. Nothing happens when it's connected. I got it working originally under XP following a guide somewhere on here. You have to update windows media player or something like that to end the failed driver update error. It will install the MTP support or proper drivers that are not included in XP. But yeah, now in Vista or my XP machines nothing happens and I can only assume it's hardware with the connector not recognizing a pc signal. It was working fine with JB installed before.
When I called into support their answer was RMA anyway. I had already done everything the support person was going to ask; reboot, factory reset, try different pc, make sure the usb ports work. Aside form a little screen bleed the tablet has worked without a problem until this last firmware update. There other ways for getting media to the device and that didn't concern me. It is the inability to connect the device to the pc for actions such as rooting, unlocking, or other similar functions that bother me. I had it rooted (lost now that I kept trying different wipes etc) but feared something going wrong later if I unlocked it and lost warranty. Once warrant is up this device is fair game and going unlocked for sure.

In case anyone else encounters the same problem, apparently the connector went bad on the tablet. They replaced the part under warranty. Took about 10 days in total and so far the only issues I see with the tablet is bent metal where the connector and one of the prong holes for the dock is and the screen. I assume the bent metal is from the tools used to pry open the case. The glass over the screen seems mushy and a bit popped up now on the edges. Don't know if that is something I should worry about or just expect since it was opened.
It did come back with 10.4.4.16 firmware. I was real tempted before to unlock and really let the tablet shine but hesitant now. They may not have covered the warranty repair if I did and I don't have another $500 to drop if something else goes bad that isn't minor.

No pc recgnized
I had this happen a few days ago after rom-ing ..... In win 7......
2 thoughts
1. Check in settings mk sure pc sync / connect to pc is enabled...
2. Install asus sync on ur pc
good luck
---------- Post added at 02:33 PM ---------- Previous post was at 02:24 PM ----------
Here in the usa most states have warranty laws that void their claim that unlocking it voids the warranty...and last year the supreme court ruled that jailbreaking was legal in all 50 states, this claim by asus is clearly seen for what it is....a veiled attempt to not have to honor warranty on zillions of devices...to save their scamming butts alot of money
on std warranty repairs. Its a scam, they know it.....and now u know it....
If u unlock, your state warranty laws will in most cases still enforce your warranty...
If u threaten to file a class action suit agianst them for it, they will back down and honor your warranty....or they loose bigtime......
Asus corporate is not...your friend

[Q] Unique tf300t Issue

Hello folks!
I purchased a bricked TF300t from ebay. I knew it was bricked when I bought it, but I asked the original owner a bunch of questions before buying and it seemed like I could fix it. Well he wasn't completely honest about the issues it had and now I am stuck in a bootloop. It will load the ASUS splash screen, then it will begin to load the rom by showing the metallic looking asus splash screen with the spinning circle. It will spin for a little while, freeze, then reboot.
I was able to flash the stock JB 4.2 rom via the sdcard and the stock recovery (yes it is the JB bootloader) and this is where it lands me. I was hoping to use a TWRP or ClockworkMod recovery, but when I boot to the bootloader and it says fastboot protocol is on, neither of my Windows 8x64 pc will recognize it. Not just that it can't find the right driver, but that it doesn't see anything at all has been connected. Nothing in the device manager, no sound effects, nada. I have no blobs, so APX is worthless to me (and it doesn't find anything in apx mode either). I have used universal ADB drivers, Naked drivers, Driving Ms. Daisy, all to no avail. I have also tried to connect it to a 64 bit windows 7 machine with no luck. I am using the stock USB cable as well.
Basically I need a way to get out of the bootloop, a way to make fastboot work, or to flash a new recovery via sd-card (which I don't even think is possible). Any suggestions would be appreciated.
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.

brandonharrison10 said:
Hello folks!
Oh, and before you give me the standard forum-snob response, "Google is your friend. Search the forums. Your issue has been answered," I have been wrestling with this problem for over a month, and have Googled my brains out. I have dome my due diligence. If you think the answer is out there, put up or shut up. Give me a link.
Click to expand...
Click to collapse
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.

graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.

brandonharrison10 said:
First off, thanks for your reply! Secondly, I am sorry that my original post came off sounding so harsh! It didn't sound so bad in my head (but rereading it I think you are right). Sorry if I offended. I have edited my original post to remove some of the snarkiness.
Also, it may be a bad IO port, but when I plug it into the computer while on the bootloader menu, for example, the tablet freezes for just a moment as if it is getting ready for communication with my pc.. I hope the IO port is not bad, but even if it is, any other ideas that anyone can give me would be welcome.
Click to expand...
Click to collapse
I read your OP again. Your problem is interesting. I assume at this point your tab is stuck at the bootloader with at least 2 icons (RCK and Wipe Data), since if you can load the 4.2 rom, you can use Goo manager to download the custom recovery. But even if stuck at fastboot page, you should be able to select RCK and flash back to 4.1 with the official zip (104220 unzipped once) on SD card. I've done this after selecting the wipe data icon (while you're on official rom with no custom recovery installed, it's safe to wipe data). Once you succeed at downgrading to 4.1, you can work your way back up to 4.2. Have you tried this?

graphdarnell said:
If they know, they wouldn't give you the Google-is-your-friend thing. But sarcasm won't get you far either, I'm afraid. People are willing to help, but nobody owes anybody anything up here. Your due diligence is for your own good, and counts for little here. No need to remind them to put up with you. You're asking for help you're not paying for, remember?
Now to the matter at hand: is it possible that the cable and/or the I/O port is bad? That takes place quite often. A wrong push might bend the tiny pins inside (happened to me, I had to replace the ribbon cable ). Some have gone through 2 or 3 USB cables before getting the thing to work. There have been cases where the PC couldn't connect with the tab in fastboot mode because the drivers did not install correctly or it's Win 7 64, etc... But if you can verify software validity PC-side, then it can't be anything other than physical non-connectivity. You might be barking up the wrong tree by focusing solely on firmware tab-side.
Click to expand...
Click to collapse
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?

TwStD said:
Emphasis is my own. Sorry to go grave digging but I'm running into issues with my tablet trying to fastboot with win 7 x64. Is this a known issue or was that just a dig at Microsoft?
Click to expand...
Click to collapse
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.

graphdarnell said:
There were reports of people running into problems using W7 64. I've used it, and it's not so much problems as it is it'd act weird sometimes. So I mostly used W7 32. Hope that answers your question.
Click to expand...
Click to collapse
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.

pyraxiate said:
I only use X64. No issues here, I just use the drivers posted on the sticky ( http://forum.xda-developers.com/showthread.php?t=1697227 Post 2 Under "Utilities 300T 300TG" ). I didnt have any luck with the universal drivers though. One thing that DID make a difference for me was whether I plugged it into a USB port on the front ( from the motherboard header ) or directly to the motherboard in the rear. Rear worked where front didnt ( on 2 different computers ). It might have something to do with the length of the cable + connecting in multiple spots. My external USB drives / Wireless adapters work perfect on the front ports, and one computer is brand new ( Intel extreme board + 3770K ). The new rig has USB3 on the front as well.
Click to expand...
Click to collapse
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.

TwStD said:
To be fair, I am on a ME301T but the hardware and most of the software is nearly identical. I'll try the drivers you recommended.
Click to expand...
Click to collapse
Also try different usb ports as well. Its weird, but fixed my issue. Also on laptops, some have daughterboards or small ribbons connecting to some of the USB ports. Its worth a shot trying different ports on a laptop as well.
Let us know if it works !
If not, it could be your dock connector as mentioned earlier. Luckily, they are cheap though.
http://www.ebay.com/itm/OEM-ASUS-TF...216?pt=LH_DefaultDomain_0&hash=item1e7a699730

OK, will do. Thanks!

try using a Linux. and install adb and fastboot drivers. win8 is a pain in the butt with android. i switched to Linux mint as a main os for everything android. also check the forum here. I posted a guide to reflash from a softbrick as long as fastboot is working.
Unrecoverable bootloader error but not Bricked!
http://forum.xda-developers.com/showthread.php?p=44244313
Unrecoverable bootloader error but not Bricked!
gl
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app

[Q] phone not being recognized at ALL as usb? (cm11)

hi..
after installing cm11 it would appear my phone is not being recognized as usb device at all? neither as usb mass storage device or as mtp , i does charge the phone, but that's it.
i've enabled MTP in usb comptuer connection, and tried to connect it to 2 different computers.

Hmmm. I haven't seen an answer to this question posted yet. Emaayan, did you ever get a resolution to this? I actually have run into this twice in the past, and the answer is to shut the phone down, and do a battery pull to reset the hardware completely. Had me scratching my head for months, and even had me develop a way to do a full unroot and return to stock without ever touching USB or terminal, until I took the battery out of my fiancee's phone since we were planning on returning it, and using it on what would've been her backup phone. When I returned the battery to it, the USB worked again. It's not a CM issue, or a software issue at all. It's definitely a Samsung not-initializing things properly issue. I've seen it happen on stock, I've seen it happen in the old 4.3.1 FatToads, and the 4.4.X FatToads.

Let me know if the above works (battery pull).
I had this issue too, didn't realize it until I tried updating different roms...
I put on Carbon after OmniRom ... OmniRom was overheating my phone and battery and it was at that time I actually pulled it apart and wrapped it in a gel ice pack to cool it down.
I don't recall if Carbon had worked, but I'm back on CM11 now and am getting USB working.
I also updated to the latest CWM per OmniRom thread in development forum.
I trust Magamo, though, in providing the right diagnosis and solution.

mod please delete

REV3NT3CH said:
i believe OmniRom caused my phone to brick...flashed it to see the issue people were having to help with a fix....apparently lbcoder is breaking stuff again lol...when i get either a new relay somehow or fix mine..i may look in their code to see what it is...im almost assuring its how MTP is not being handled correctly.... i respect @Magamo and most the other devs.. but all i can do is suggest a fix and get disrespected by lbcoder
Edit: like this for example https://github.com/TeamApexQ/androi...mmit/b9d389cca9f241d778f1d8206195e16dfcb3dee8
Click to expand...
Click to collapse
OmniRom was not the cause of your bricking, I hate to break it to you. The commit you just linked actually has very little to do with the kernel. It was an update to fstab to match a change in paths. There was no driver functionality change in anything that was dependant upon. If you respect me, I would appreciate it if you were to stop spreading FUD about us, and my work. I'm starting to become personally insulted here. Bricks more often happen due to faulty hardware. No properly booting kernel would have been the cause of what happened to you. I assure you, our kernel is working properly.
This is also completely off topic to the question asked. As stated, I've personally seen this happen on several images, Stock included. This particular issue is a Samsung hardware initialisation issue, and is resolved by a battery pull.
Since it is off topic for this question, I will not ask here what you feel is wrong with our MTP code. We can start another thread, and stop hijacking this one. Better yet, as always, the best place to discuss this with us would be on IRC.

Surprisingly, pulling the battery fixed the problem!
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.

Autolooper said:
After spending the last few days without my phone being recognized by multiple computers and considering a factory reset on a Samsung Galaxy Relay, I came across the post here mentioning that pulling the battery worked to fix the problem with phones not being recognized through USB.
I can vouch that pulling the battery does fix the problem with devices not being recognized.
Perhaps these devices should have a more convenient way to pull the battery if doing so makes them work properly.
Click to expand...
Click to collapse
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?

xob3444 said:
It's not working for me. I have the MTP available, but not simple USB Mass Storage with CM11. Any other ideas?
Click to expand...
Click to collapse
Android 4.0+ no longer supports USB Mass Storage out of the box for the internal storage, and neither do any of the custom images that I can think of. MTP is the answer here. The fact that you are getting MTP means that the device is talking over USB, which means that you are not suffering from the problem described in this thread.

[Q] USB stopped working, can't see files on PC

Has anyone had the problem of USB no longer working? It charges the device, but PC will not recognize the device - no icon or ability to see it as a drive in the PC. I've tried different cables and laptops, but same problem. (And the old cables & laptops work fine with my other USB devices). The phone & USB worked flawlessly the first 4 days I've had it - no problems transferring files from PC to phone & back.
Bone stock Galaxy S6 128 GB on Verizon.
Win 8.1 on Yoga 13 and Win 7 on Latitude 6400.
Thanks for any guidance.

Check to make sure the drivers are on the computer and try a different USB ports

stantaur said:
Has anyone had the problem of USB no longer working? It charges the device, but PC will not recognize the device - no icon or ability to see it as a drive in the PC. I've tried different cables and laptops, but same problem. (And the old cables & laptops work fine with my other USB devices). The phone & USB worked flawlessly the first 4 days I've had it - no problems transferring files from PC to phone & back.
Bone stock Galaxy S6 128 GB on Verizon.
Win 8.1 on Yoga 13 and Win 7 on Latitude 6400.
Thanks for any guidance.
Click to expand...
Click to collapse
Make sure USB debugging is checked. Go to about phone. Go to "build". Tap on it rapidly until it says you now are a developer. Back out of about phone and go into the new option "Developer Options" and check USB debugging. When you hook up your phone you may get a popup that asks if you want to trust this computer. Say yes. On your notification page, it might say you are connected as an installer. Change it to media. Sometimes you need to toggle back and forth from camera and media.

Tulsadiver said:
Make sure USB debugging is checked. Go to about phone. Go to "build". Tap on it rapidly until it says you now are a developer. Back out of about phone and go into the new option "Developer Options" and check USB debugging. When you hook up your phone you may get a popup that asks if you want to trust this computer. Say yes. On your notification page, it might say you are connected as an installer. Change it to media. Sometimes you need to toggle back and forth from camera and media.
Click to expand...
Click to collapse
Thank you. Yes, tried Dev mode and USB debugging, but no luck. Phone double-beeps when I connect the USB to it (and begins to charge), but no pop-ups on either phone or laptop in relation to storage / ability to manage files. No drive shown for the phone (whereas Thurs-Fri the phone showed up as an extra drive when I plugged it in.)
I also did a Factory Reset, just to see if going all the way back to square one would help. No luck there either. Phone still won't recognize laptop, laptop doesn't recognize phone.
That leads me to think something died in the hardware, firmware or something. This Win8.1 laptop works great with all my other devices.
I'm in the 10 day trial/return period (and coming from 2 yrs of flawless-except-****ty-camera HTC One M7 experience) - so if this is the "crap" quality people say is endemic to Samsung (srsly, 3 days and the phone does this? WTH), please let me know so I can get a G4 or Nexus 6 (can't go back to HTC M9 since the M7's camera was a 2 year prison sentence).

stantaur said:
Thank you. Yes, tried Dev mode and USB debugging, but no luck. Phone double-beeps when I connect the USB to it (and begins to charge), but no pop-ups on either phone or laptop in relation to storage / ability to manage files. No drive shown for the phone (whereas Thurs-Fri the phone showed up as an extra drive when I plugged it in.)
I also did a Factory Reset, just to see if going all the way back to square one would help. No luck there either. Phone still won't recognize laptop, laptop doesn't recognize phone.
That leads me to think something died in the hardware, firmware or something. This Win8.1 laptop works great with all my other devices.
I'm in the 10 day trial/return period (and coming from 2 yrs of flawless-except-****ty-camera HTC One M7 experience) - so if this is the "crap" quality people say is endemic to Samsung (srsly, 3 days and the phone does this? WTH), please let me know so I can get a G4 or Nexus 6 (can't go back to HTC M9 since the M7's camera was a 2 year prison sentence).
Click to expand...
Click to collapse
I've read some horror stories but I love mine. I have two and no problems at all. See if you can get a new one with another trial period.

Tulsadiver said:
I've read some horror stories but I love mine. I have two and no problems at all. See if you can get a new one with another trial period.
Click to expand...
Click to collapse
Been on the line with Verizon Tech Support for 2 hours as of this writing. Re-did all the diags, reset, Kies, etc. that I did Sunday from the VZN and Sammy websites. Combined with the re-setting of folders, Peel remote, TouchDown, etc. I'd done on the first phone, I'll have wasted a full day just fixing the phone.
Wish the HTC M9 had a better camera, G4 had better battery life or Nexus 6 had a better audio chip. If they send me a new GS6 and it flops again, does anyone have a recommended fallback phone to get as a placeholder until something better makes it to market (M9+ with fingerprint reader, better CPU, better camera)?

stantaur said:
Been on the line with Verizon Tech Support for 2 hours as of this writing. Re-did all the diags, reset, Kies, etc. that I did Sunday from the VZN and Sammy websites. Combined with the re-setting of folders, Peel remote, TouchDown, etc. I'd done on the first phone, I'll have wasted a full day just fixing the phone.
Wish the HTC M9 had a better camera, G4 had better battery life or Nexus 6 had a better audio chip. If they send me a new GS6 and it flops again, does anyone have a recommended fallback phone to get as a placeholder until something better makes it to market (M9+ with fingerprint reader, better CPU, better camera)?
Click to expand...
Click to collapse
NO HELP FROM VERIZON "TECH SUPPORT" OR "WARRANTY" having spent 3 hours on tech support with Verizon...
Our Samsung GS6 failed Saturday (USB won't connect to any laptops using any cables) and I spent Sunday doing Verizon's online fixes (including safe mode, factory reset, Kies, etc.) and 3 hours with Verizon tech support this morning with no resolution.
Verizon is calling Samsung and "will get back with me later this week" if and when they find or make sense of other field failures that match my phone. (Really? And how would Zappos, Amazon and other customer service benchmarks handle it? Yep, overnight a new one after 5 min call and issue RMA for the defective item to be overnighted for tear-down / fault analysis). And by the way, my wife and I are paying for "next day" replacement and within the 14-day trial period...
So one would think Verizon would overnight ship a new GS6 out to me immediately and have me ship the defective GS6 to Samsung for tear-down analysis.
That's not the case. How Verizon is handling this frankly has us spooked that Verizon does not in fact stand behind either their products or "warranty" services.
I'd hope that our 14-day return-policy time-clock be reset and a new GS6 black 128GB be overnighted to me, or find some way of extending the return window (since the device, and its "warranty" and the customer "service" have all failed within 2 days of receiving the phone).
Think I'm going to be stuck with the LG G4 or maybe even swapping carriers.

Go to a store. If they can't do anything ask for a refund.

stantaur said:
Has anyone had the problem of USB no longer working? It charges the device, but PC will not recognize the device - no icon or ability to see it as a drive in the PC. I've tried different cables and laptops, but same problem. (And the old cables & laptops work fine with my other USB devices). The phone & USB worked flawlessly the first 4 days I've had it - no problems transferring files from PC to phone & back.
Bone stock Galaxy S6 128 GB on Verizon.
Win 8.1 on Yoga 13 and Win 7 on Latitude 6400.
Thanks for any guidance.
Click to expand...
Click to collapse
It's not a work/corporate PC, is it? I had a similar issue, and turns out that USB storage devices were disabled by Windows policy.
Have you tried to use ADB with the phone? If you install ADB drivers, you could verify that you can at least connect...

VZN and Samsung tech support / customer service FTL
jimbobtexas said:
It's not a work/corporate PC, is it? I had a similar issue, and turns out that USB storage devices were disabled by Windows policy.
Have you tried to use ADB with the phone? If you install ADB drivers, you could verify that you can at least connect...
Click to expand...
Click to collapse
One of my laptops is personal Win 8.1, the other is corporate Win 7. Neither laptop recognized the Samsung GS6 after day 2, but worked flawlessly up until that time.
Still nothing back from Tech Support / Samsung "researching" the problem. Total WTF with those yaboes.
Monday I engaged the team who originally sold us the GS6 at our local store, and they're saying my new phone (replacement) will be in the store by Sat 6/27. 5+ days without a phone, but if this replacement doesn't suffer any issues, great.

Have you solved this issue? My wife's meet the same issue. And we did a lot ..... But it still no work.

This happened to me today. Computer would not recognize device. I toggled USB to camera mode then back to media device in phone settings and my pc recognized it again.