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.
Related
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
I have the official Samsung USB Connection kit. Both connectors work fine immedeately after boot, but once the device has 'slept' they do not work anymore. I get a notification that the USB Connector is connected, but whatever I insert nothing happens. LEDs (on USB sticks, mice, ...) do not light up which seems to indicate that no power is applied to the port.
I'm running stock Android, rooted. Booting into safe mode makes no difference.
Any ideas what's going on?
You're not the only one, except that in my case USB sticks do light up. IMHO Samsung seriously botched up the automounter in their last update. I wonder how long it's going to take them this time to get their act together and produce a bugfix.
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
SpicyKiwi said:
I have exactly the same problem, wich really annoying as I bought this tablet in order to work on it (with a keyboard). I'll try Samsungs suport...
Click to expand...
Click to collapse
Good luck with that. I contacted Samsung support Benelux and was told it was because Amazon Germany had installed "German software" on my tablet.
Trust me, that is NOT the case...
karel jansens said:
IMHO Samsung seriously botched up the automounter in their last update.
Click to expand...
Click to collapse
I'm not sure it's the automounter. Keyboards and mice show the same problems.
sciurius said:
I'm not sure it's the automounter. Keyboards and mice show the same problems.
Click to expand...
Click to collapse
You might be right, I haven't tried one of those yet. Of course, that would mean Samsung botched up the entire USB subsystem of our Note, which is kinda even worse.
Seriously, is anything done about this usb c**kup, or what? I bought my Note, expecting it to replace my venerable Archos 101 which, incidentally, had excellent usb connectivity three blooming years ago and on Android 2.1, only to find out that not only did I have to buy motherloving adapters for the Note, but on top of that that they don't even work properly.
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
sciurius said:
I also came from Archos 10.1 IT so I know your pain...
My only hope is that we will soon get the 4.2 update, and that it will fix this problem.
If not, I'll probably going to flash CM on it to see if this works better.
Unfortunately, I've seen no CM reports that USB host works flawlessly.
Click to expand...
Click to collapse
Quick question, has anyone has the adapter problems while on Android 4.1.1? I tried my adapters on a shop showroom model of the Note 10.1 and they worked perfectly, but only afterwards I noticed that Note was running 4.1.1, while mine is up to date with 4.1.2.
I'm just trying to avoid having to send back a piece of equipment that, despite everything, I can barely miss.
One of the USB OTG tools (forgot which one) had a table of functioning USB host versus Android releases and last time I looked the number of 4.1.2 devices that hat USB problems was significantly higher than the 4.1.1 devices. So I have all reason to believe it is a software problem, introduced in 4.1.2.
EDIT: The tool is USB Host Diagnostics from ChainFire.
So, is there an easy way to go back to 4.1.1 on the BigNote? Mine came with 4.1.2 installed anyway and something tells me that, if I ask Amazon to downgrade for me, I'll be answered with a deafening silence, probably with a "Duh?" In there somewhere.
On second thought, scratch the easy part; is there any way to downgrade a BigNote without losing any of Samsung's added value (yes, I happen to consider most os what they added actually valuable).
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
The purpose of this poll is to collect data about the 'sudden battery loss' issue that some Moto G owners have encountered.
People who are certain that the problem occurred the moment they disconnected USB; choose the last option and add a comment please.
If you choose option #1 but later experience this issue, post a comment saying this. Thanks.
The more accurate the information, the better chance of a solution being found quickly. Please post if you have experienced this problem on a US GSM (XT1034) or Brazil GSM (XT1033); also stating if it's a 8GB or 16GB version.
Affected Models:
XT1032: EU/Global GSM - 8GB/16GB
XT1033: Brazil Dual-Sim - 8GB/16GB
XT1034: US/Global GSM - 8GB/16GB
[All Variants apparently]
This issue occurs on both Android 4.3 (Jelly Bean) and 4.4.2 (KitKat).
Related thread: Battery from 74% to 0% in 1 second
I would suggest making the answers more precise, like change the PC chatrging one to "When you disconnected the phone from PC". As I remember noone reported having it drop to 1% WHILE connected, only on disconnecting or later on the desk without cable.
<removed>
Chose last option - battery suddenly dropped to 1% the moment I pulled USB cable out of PC. I wonder if it could be PC-related, because during over a month I own the device, this never happened either on my home or work PC, both are double-boots W7/Linux and I usually connect to them couple of times each day. The only time it happened was on my friend's PC to which I connected only this one instance and sadly I won't have oppurtunity to come back to any soon to try to reproduce. I only remember it was some windows, probably 7, maybe even Vista - ask no more, it was New Year's Eve !
Got mine's two days ago, no problems.
I had such issue using Brazil GSM (XT1033)
Ok, today I got that problem, my telephone was at 15% and when I plugged the USB it drops to 1%.
I don't know what was that but I'll never connect USB while using the phone, never!
manudo said:
Ok, today I got that problem, my telephone was at 15% and when I plugged the USB it drops to 1%.
I don't know what was that but I'll never connect USB while using the phone, never!
Click to expand...
Click to collapse
Unfortunately, avoiding USB will not protect you; it can happen even when the phone is not connected. The poll and the main thread support this. USB will often trigger it however.
lost101 said:
Unfortunately, avoiding USB will not protect you; it can happen even when the phone is not connected. The poll and the main thread support this. USB will often trigger it however.
Click to expand...
Click to collapse
Crap, man.
Is this a hardware problem?
manudo said:
Is this a hardware problem?
Click to expand...
Click to collapse
Unknown at this time. Hopefully Motorola or someone here can figure out the cause. I suggest you contact Motorola Support (webchat) reporting the problem.
Maybe it was a mistake to put the first option in this poll. Just because someone hasn't had this happen, doesn't mean it won't. As far as I can tell, all models, from all regions are susceptible.
In the beginning I had similar probleme couple of times. When phone was disconnected, had 80-90% and after reboot it dropped to about 30-40%. After recharging all was fine again.
Walliser said:
Try to remove battery reinsert it after several minutes and see if there is any change.
Click to expand...
Click to collapse
Moto G has a non-removable battery.
Can anyone trigger this issue in a reliable manner or encounters it a lot? Most forums seem to say that it only happens once and then never again.
I have had this happen several times, usually only when connected to a PC. On both 3.4 and 4.4.2.
I've posted in the other thread theorising that the trigger might be voltage / current, but the poll so far suggests many people have experienced this issue even when not charging.
Three devices (Tesco, Amazon UK, Amazon UK.) hasn't come across it yet.
Happened when I disabled usb debugging while the device was connected to the laptop. 4.4.2 DE (originally UK)
Can anyone try to reproduce it?
This has happened twice to me within the past 3 days using the stock Canadian 4.3 firmware. No issues so far with the 4.4.2 OTA.
Narwhal73 said:
This has happened twice to me within the past 3 days using the stock Canadian 4.3 firmware. No issues so far with the 4.4.2 OTA.
Click to expand...
Click to collapse
Can you try making it happen as I described?
Sent from my phone
miklosbard said:
Can you try making it happen as I described?
Sent from my phone
Click to expand...
Click to collapse
Using the official USB cable provides with the phone and my Windows 8.1 laptop, I was not able to reproduce your results, sorry :\
The battery seems to just do it randomly when it feels like it. Though I've only had this happen when charging via wall charger.
Suddenly OTG and Gear VR are not working on my S8 plus. no water, drop or anything. I have the device for only 2 weeks. No OTG device works (tried with genuine type c to usb adapter). It used to work like two days ago. I did factory reset and reinstalled firmware using smart switch. In addition, Gear VR is not being recognised anymore. PC connection and data transfer using the cable work ok. I believe OTG uses different pins. May it be a hardware issue? I remember getting some high-powered device connected before it stops working at all (using just a simple mouse). I tried everything.
I saw that a number of people have the issue on samsung support website. I hope it is not a known issue and samsung just does not state it officially (like the S7 edge pink line).
Please help or let me know if you have the issue too.
Arismfg said:
Please help or let me know if you have the issue too.
Click to expand...
Click to collapse
Lengthy discussion here > https://forum.xda-developers.com/galaxy-s8/help/usb-otg-longer-galaxy-s8-t3640216
cam30era said:
Lengthy discussion here > https://forum.xda-developers.com/galaxy-s8/help/usb-otg-longer-galaxy-s8-t3640216
Click to expand...
Click to collapse
thank you for your reply. I have already checked the thread above. However, no working solution. Is there anyone who managed to figure out if it is a software or hardware issue? I wonder why it is stated as solved. I dont think the guy with the issue fixed it
I contacted oculus support about this issue. Seems to be a widespread software issue that happens with certain models+updates but they aren't doing anything to fix it for unlocked phones as only phones locked to a carrier are supported by gear vr.
povotron said:
I contacted oculus support about this issue. Seems to be a widespread software issue that happens with certain models+updates but they aren't doing anything to fix it for unlocked phones as only phones locked to a carrier are supported by gear vr.
Click to expand...
Click to collapse
Thanks for the reply. Does this also have to do with OTG devices not recognised? Do you have this issue too? What is strange is that Gear VR used to work. At least for a while on my unlocked S8 plus. I cannot understand how this may block the OTG devices. Is there something left in the settings that may block OTG?
By the way, I hope you are not referring to the network issue. My Gear VR is not recognised at all.
I'm having the same problem as you. I hadn't tried otg before the VR wasn't recognised but I can't use it now. Could be my adaptor though. People seem to have the issue appear following phone updates
povotron said:
I'm having the same problem as you. I hadn't tried otg before the VR wasn't recognised but I can't use it now. Could be my adaptor though. People seem to have the issue appear following phone updates
Click to expand...
Click to collapse
Well I gave my phone to the official samsung service and waiting for their reply. I don't think I installed any updates before and after the issue appeared (at least not firmware updates but not sure about oculus or other apps) . By the way it is not the adaptor that has the issue. I tried many others on my phone. And the adaptor works with a friend's S8 (not plus). Only one works (well not really). It iss an OTG type-c to micro usb (bought from ebay) which comes up with a notification that high powered device was connected but then nothing happens whatever option I choose. And it is not a high powered device because it used to work. I tried even a mouse with its own battery. But if it was a phone update, I think a factory reset should fix it? It did not for me.
Do you think of taking your phone to the official service too?
A full factory reset also didn't work for me. From other forums it seems that other people who have taken them in for service receive a replacement phone. Some people however then mentioned that they encountered the same issue a few months later with the replacement. I would take mine to Samsung but it's a grey import and Samsung refuse to touch them even though it's the same model sold locally. If it's definitely a hardware fault I'll consider sending it away but it would be an international service which would leave me without a phone for quite some time.
Yes, you are right. Some people saw the issue after a few months of getting the replacement phone or even after restoring their google account and settings (without being able to get it fixed by factory reset). This is what actually scares me the most because it looks like hardware issue of the phone in general. It looks like a well known issue which samsung does not officially accept. SiImilar to the pink line on S7 edge I had before. Anyway, as charging and connection to pc still work, I can give my phone and get a new model later cheaper. The last two samsung flagships came with issues that (the most important) samsung does not accept officially. Maybe it is time to change brand (always android though).
I got my phone back from samsung service. They did not replace my phone but they replaced both the logic board and the type-c board. As expected, it works again with OTG devices and Gear VR as it is like a new phone after replacing all that. Installed all apps again one by one (not restored from backup) and everything still works. Hope it stays like that. So hardware issue? Looks like it.
I know this is an old thread, but I replaced just the USB board and it didn't fix anything. So maybe it's a motherboard issue?