OPT connected via USB is not detected by PC or Mac

Hi all,
I am having issues connecting my OnePlus 2 to my windows 7 using the original oneplus type c usb cable. Whenever connected the phone is charging only. No option to select any mode what so ever.
I thought it may be drivers or OS issue, so then I tried connecting with my MacBook Pro but it's still the same.
USB debugging is ON. Even installed android SDK, platform tools, Android File Manager on Mac but nothing changes, it's Charging and shows no devices in Android File Manager as well as Terminal adb
Settings > storage > USB connection option says to make USB connection to PC even though it's connected

Flashed Custom Rom over stock q700. Phone not detected.

Hello ,
I was wondering if anyone could help me with a problem I am facing. I was on Q700 stock rom. I flashed cwm via mobile Uncle. Then I mistakenly flashed Xperia Z2 rom on top of that after doing a factory reset via cwm. I forgot to flash Q700i rom prior to installing the Xperia z2 rom. The problem is that now the phone wont boot up past the boot screen. There is no bootloop. The recovery is working. But, the main problem that I am facing is that my phone is not detected by the computer. It is not detected when I plug it in while powered off even though I have proper VCOM driver. It is not detected when I plug it in when the phone is in CWM. I want to go back to stock. Is there any way anyone can help me ?

S5 (T-Mobile) SGH-G900T Tap-Pay wallets not detected by payment terminal

I cannot get any Payment Wallet to work on my Galaxy S5 from T-Mobile. Prior to February 2015, I used both Google Wallet and SoftCard successfully. In February I added a 3rd party Wireless Charging Receiver which obscured my NFC antenna. This was while using KitKat.

When Lollipop was released, my phone was updated, still with the NFC out of commission due to my charger, so I don't know if Google Wallet or SoftCard worked after the update. I lost Softcard the end of March due to it merging with Google Wallet. On Lollipop my phone was overheating and running the battery down so I downgraded to G900TUVU1CNK2 KitKat and then upgraded again when the new more stable release of Lollipop came out. Early in September I upgraded Wallet to Android Pay and replaced my Charging receiver with a different model that didn't cover the entire battery, and NFC worked a bit.

Android Pay would not work - The phone doesn't see the terminal and the terminal doesn't react to the phone. I then replaced the second charging receiver coil with an OEM Samsung charging phone back which has an integrated NFC antenna. Still no life from Android Pay and the terminals. Google support has had a service ticket since early September on this issue.

Yesterday I installed "Capital One Wallet", a new payment Wallet for Capital One customers, but today I found the same result when putting my phone on the terminal. No response at all.

Could one of my downgrade/upgrades broken the Host Card Emulation and does anyone have an idea what I should try next? I'm tempted to downgrade to G900TUVU1CNK2 again to see if it works. One other thought is that I had USB Debugging mode turned on and I'm wondering if this might have prevented the secure connection between the devices.

Rear camera-hardware detected, yet black image. Camera "bus" malfunctioning?

Hi

Half a year ago my girlfriend accidentally gave my Z3 Compact a rollercoaster ride in our washing machine (full tour). The screen broke, but it could turn on and everything looked fine (gave no errors) when connecting to HDMI.

Yesterday I received a replacement LCD, which gave it a new life. It seems that everything works except for the rear camera. When opening any camera-app, the HUD is visible, but image is black, and no error. If i switch to front camera, which works, and back to the rear camera, it shows a freezed image of the last image from the front camera.

I checked some debug-apps to see if it detects the camera-module, and it does. If it's connected, alle the specs of the camera is listed, and if disconnected, the module is not listed.

I then got a broken Z3 Compact from a friend, and I tested both rear camera modules in both phones. The modules are working in his phone, both doing the same black screen in mine.

I tried hard reset, PC Companion-repair, updates, clearing camera cache etc., but with no luck.

Do you have any suggestion to how I can fix this?
Do you know where on the motherboard I could look for dirt in relation to some "rear camera bus/chip"?

Thank you for any help!

LGE AndroidNet Driver detected only - Download Mode not Detected - Bricked D801

So I bought this secondhand G2 and it said on the cover it's D802T (Australia Model) while inside it was D802 (International). For sake of generosity I tried to flash it with D802T .kdz file and got it bricked, when I opened the back cover it was D801 model (Freaky right?).

So basically I'm stuck with:

1. LG BootLoop with constant waving Blue and Green LED
2. Download Mode - Turns on but doesn't get detected by Computer (using Windows 10 and trust me Windows 7/8 didn't detect it either)
3. Vol Down + Power takes me to Factory Reset cuz no recovery installed
4 LG BootLoop detected as (LGE AndroidNet) driver on device manager

I've tried the following methods for it's recovery:

1. Tried another .kdz but failed since download mode doesn't detect
2. Tried .tot method in LGE AndroidNet mode (COM41) using "BIN_LGD802AT-00-V10b-SEA-XX-SEP-04-2013-32G+0.tot" stock but it gives some Failed to Read model error
3. Tried LG Support Tool (B2CAppSetup) to download online stock but it asks for Serial No. and I don't have the IMEI because the back casing seems to be replaced by some other phone

The repair center puts up the lame excuse that the charging port is faulty thats why Download Mode is not being detected but that cannot be mode lame cuz that port was the reason it got into Download Mode Duh.

I'm a student and in my place buying phone is basically as expensive as buying a car and even though it's secondhand, it got bricked not 24 hours after I bought it and the shopkeeper won't take it back cuz he says it's my fault I wanted to be generous and try original roms, so I'm sitting in shivers and trembles here.

Any help would be greatly appreciated.

Note: If this threat has been discussed already please send me the link to it cuz I couldn't find any. And please try not to feed me anger by asking if I re-installed drivers or did I try another computer or did I try adb or fastboot method cuz if you're experienced enough, you'd already know those considerations would've been taken and been failed to help so far. Thank you and please help.

Keyboard Cover Detected Bug, anyone else experiencing this?

I've had 2 note 5's now, an N920A and an N920c and this same bug has appeared on both, but I want to see if;

a) anyone else has this?
b) anyone knows of a solution?

If I open an app running in the background in landscape (weird conditions, but this the only way I replicate it), so any game, or as it just was, Pokerstars. I get a popup message, saying Keyboard Cover Attached and then it changes the theme back to default.

As someone who hates Samsung's weird blue and green theme, its annoying to have to keep changing my theme every time I open certain apps

Edit: Video https://sendvid.com/69kse11c (sorry for the sound, forgot to turn it off when recording, but couldnt be bothered resetting the theme to re-record)