So recently flashed CM 10.1 FUSION. Nexus battery drains, I end up turning it back on while on the charger. Then, it shuts down on me.. so I let it charge overnight. Turned it back, and I get stuck at a boot screen (FUSION). I attempt to turn my device off, and it just restarts. I have to turn it off from the bootloader (P+Up+Down).. I tried using the toolkit, but I freeze in the bootloader when I plug my device in.
Help.
Running 4.2.1
Yes I'm aware of the common problems, none of the solutions seem to be working.
Rovon said:
Yes I'm aware of the common problems, none of the solutions seem to be working.
Click to expand...
Click to collapse
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
bftb0 said:
Rather than say "yeah I'm aware of a bunch of different things", it would be better for you to state what you actually tried. That way nobody is guessing at what you attempted, and it will eliminate a bunch of back-and-forth Q&A. We don't know what you do and don't know.
It's clear from your description that you can get to the bootloader. What happens if you DO NOT connect the device to a computer, and try to start the recovery? (Note you also didn't bother to mention which recovery is on your device)
If the recovery starts, have you tried doing a factory reset? (I would say, make a backup, but that will only make a backup of your bootlooping OS).
cheers
Click to expand...
Click to collapse
I tried watching a majority of the "unbrick nexus 7" vids on youtube. They didn't get me too far
Holding power for a long time
Restarting bootloader
Root toolkit
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Rovon said:
If I don't connect it to a device, I can move through the bootloader but can't access recovery
Click to expand...
Click to collapse
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
bftb0 said:
What happens when you try that? Does it stay frozen on the bootloader screen? Does the screen go dark and nothing seems to happen? Does it get partway into the recovery boot and then freezes up?
No communication with the PC evidences a driver problem; partial communication (meaning, simple commands seem to work, but commands that move data fail or seize up), generally indicates a problem with the USB port being used or a crap cable.
When you are in the toolkit, does the toolkit show you a device ID when the device is on the fastboot screen?
Click to expand...
Click to collapse
Sorry, I meant its frozen on the fastboot screen...
I can scroll through the fastboot, but that's it. None of the commands work, unless I hit power off. The toolkit tells me "fastboot device not found", when I try the Flash Stock + Unroot button. There is no device ID I can see on the toolkit. Also, drivers fail to install when I plug it in to my computer.
Rovon said:
None of the commands work, unless I hit power off.
Click to expand...
Click to collapse
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
bftb0 said:
Ummmm...
In fastboot that is exactly how you start different modes; you move through the menu items with volume Up/Down, and then you use the power button to select that menu item. That is certainly the way it works with the most recent (v4.13) bootloader, anyway.
Eh?? Maybe I misunderstand...
In your Device Manager on the PC, what is the Hardware ID for the Device(s) that show up when you plug the tablet in, and does your PC report it as an "unknown device", or something else?
Click to expand...
Click to collapse
I should've been more specific. When I say none of the commands work, I mean they don't do what they're supposed to. So if I hit "recovery mode" it will not go into recovery mode, it just stays stuck at the Google logo when it restarts.
As for device manager, when plugged in to the computer with Fastboot, I do get "android" under other devices. However, when I'm booting the device up regularly, the computer attempts to install drivers and fails. I do get "MTP USB Device" under portable devices. I have an unknown device under portable as well.
All 3 seem to have error symbols next to them.
Rovon said:
All 3 seem to have error symbols next to them.
Click to expand...
Click to collapse
Well, if you can't communicate with the device successfully, there's no hope of doing something correctly from the PC. So, try a few simple things on that angle of the problem first. The problem you are seeing could come from any number of places:
- damaged USB (or other) hardware on tablet
- bad / cheap USB cable
- damaged USB port on PC
- driver install issues
The symptoms you describe for fastboot sound a bit like the custom recovery got damaged or erased, although more severe (and not fixable) problems are also a possibility.
Since you previously installed a ROM, I would take it to mean that at one time you had at least one driver working (fastboot at a minimum), and possibly also ADB mode (in the OS and/or in the recovery). That's why I put "driver install issues" last in the short list above. If you never touched any of the drivers after you did your initial ROM installs, I would not expect driver issues ... but I don't know what you might have tried subsequently with the toolkit (which does fool around with drivers).
Are you using the OEM cable? Some aftermarket/charger cables have a short mini-USB connector, and one dollar cables off of eBay can be poorly constructed (bad shielding or impedance control, so they cause data errors at high speeds).
If you have an 2nd cable, I would try to see if you experience a different set of symptoms with that; same goes for trying a different USB port on your PC.
If you see errors in the Device Manager associated with fastboot I certainly would not be attempting any operation from the PC until you get that resolved. Note there is a huge difference between "unknown device" and a device showing errors - the latter suggests that the OS is aware of a driver which is supposed to be loaded when the tablet shows up on the USB bus, but then some malfunction occurs. That malfunction could either be hardware or an inappropriate driver.
Drivers
http://www.asus.com/Tablet_Mobile/Nexus_7#support_Download
http://forum.xda-developers.com/showthread.php?t=1426502
Note that you should be able to use the Asus driver for every mode of your Nexus 7 (except MTP and PTP, which are handled by Windows generic class drivers), including your custom recovery by doing the following:
A) Download the Asus Driver and unzip it someplace.
B) make a backup copy of the "android_winusb.inf" file (for instance "android_winusb.inf.backup")
C) Open up the "android_winusb.inf" file with the Notepad program (Note: not Wordpad!)
D) Find the ";Google Nexus 7" stanza in the [Google.NTx86] section and add this line:
%CustRecoveryADBAdbInterface% = USB_Install, USB\VID_18D1&PID_D001&REV_9999
E) Add the same line (step D above) in the [Google.NTamd64] section
F) At the very bottom of the file in the [Strings] section, add the line
CustRecoveryADBAdbInterface = "Nexus 7 Custom Recovery ADB Interface"
G) Save the file and then proceed to do a manual de-installation of the drivers for fastboot and ADB.
H) Disconnect from the internet and then re-install the Asus driver for fastboot and ADB using the "Choose Location" method.
Don't know if that will work, but it's something to try; the problem you are having might lie outside the scope of what all of the above deals with
good luck
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Rovon said:
Unfortunately, you're method didn't work. However, it did lead me to another solution and seems like everything is working beautifully now.
I do appreciate your help. Hopefully, your solution will work for others.
Thank you!
Click to expand...
Click to collapse
Please describe what you found out and what DID work for you. Even if it was just a simple mis-understanding. It might help others in the future.
Probably you should also alter the title of your thread to be something much more descriptive - and add the keyword "[SOLVED]" to the title as well.
Related
Just ran into a problem which took me some time to solve. Thought I would share it to save other people some frustration.
After an adb reboot the i5800 got stuck in "modem" mode. i.e. android booted fine but gave a modem and a serial port over usb rather than adb. Reboots did not solve the problem.
The solution is to enter recovery screen:
reboot recovery
OR
press proper buttons to get into recovery mode
And then perform a reboot from there
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
miki.antena said:
Is this the same as *#7284# and selecting "PDA" on UART and USB, or just on USB? Or is this a completely separate thing?
Click to expand...
Click to collapse
Thanks so much for this!!!! After helping hack a friends build.prop to enable Apparatus compatibility in the Market, I found USB wasn't working properly anymore. Resetting changes in the phone didn't help (I had to do this via the phone terminal) although I at least managed to buy Apparatus before the sale ended.
After initially getting confused due to a lack of drivers and the occasional 'nH' showing up devices without drivers which made me think something was borked, I worked out from the VID & PID it was just the lack of drivers making (well I'm not sure why it did the 'nH' sometimes it got serial something instead), once I installed the drivers all was fine.
Except still mass storage wasn't showing and the Samsung connect manager didn't show up on my phone when I connected USB, nor did ADB work at all. In fact, it didn't even show up in the phone menu as debugging mode if I didn't start phone with it connected (or something like that). Funnily enough when I did get it the debugging to show up I did get the USB mass storage to show up in the phone, but it didn't help (it just unmounted the card which I think is all it ever does).
Anyway after a bit more fooling around I eventuall came across http://forum.xda-developers.com/showthread.php?t=1215103 and the stuff about modem and mkasick's post which sounded a lot like it could be my problem. The code for that Samsung phone didn't work so I searched for the 5800 and came across this giving me the right code. Sure enough UART (but not USB) was set to modem instead of PDA. I was unsure whether that was wrong but changed it anyway and yep that fixed it!
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times. In fact most of the stuff except install a superuser update has been more or less repeated. I guess it was just some strange rare occurence that it somehow got changed. I did have to reconnect the USB while working the first time, not sure why but ADB lost connection then I found couldn't connect. Perhaps that's somehow related. Now that I know what to do, it's trivial but very annoying when I didn't. I still don't get why Samsung decided to make the connect manager (my phone doesn't have that) only to have some hidden option where it can be set to modem or USB.
Partially because of this, I never got to get Tilestorm HD become compatible in time for the sale although my friend wasn't so interested in that. (Eventually I worked out using the THC Tattoo modded market which reports a fake resolution enables it. Well, I also modified the build.prop but I don't know if that was necessary. I wasn't able to do it solely by the build.prop. But it was way too late by then to buy Tilestorm HD cheap.)
Nil Einne said:
I still have no idea what went wrong. I had thought may be the phone didn't like me rebooting via ADB but I've now done that several times.
Click to expand...
Click to collapse
This may sound like crazy idea, but is your USB port/connector clean?
(The USB port allows for dozens of different phone functions when using very specific resistance between data pins.)
i bought a LG D802 32gb last night as i was using a 16 gb before i wanted to flash cloudy g3.. so i tried to install custome recovery twrp...
now i am in fast boot mode..
it says :
[880]fastboot mode started
[910]udc_start()
when i attach usb cable
[1100]-reset-
[1110]-portchange-
[1120]-reset-
[1130]-portchange-
[1140]-fastboot: processing commands
i tried holding volume + and and attaching the usb cable but no luck ... so now i have NO RECOVERY, NO DOWNLOAD MODE, AND MY WINDOWS PICKING UP MY PHONE AS "USB MODEM PHONE ADB PORT"
please help
I can't enter fastboot mode. I haven't done it before so maybe I am just doing it wrong, but all the instructions I found and all the threads I read don't help.
When I start the tablet pressing power + volume down I don't get the menu with the Wipe, the USB icon and Android. I end up in a menu with (from left to right) RCK, Android and Wipe.
Can somebody tell me what I am doing wrong?
compact_wisdom said:
I can't enter fastboot mode. I haven't done it before so maybe I am just doing it wrong, but all the instructions I found and all the threads I read don't help.
When I start the tablet pressing power + volume down I don't get the menu with the Wipe, the USB icon and Android. I end up in a menu with (from left to right) RCK, Android and Wipe.
Can somebody tell me what I am doing wrong?
Click to expand...
Click to collapse
You have a different bootloader version. Just start it up connect to the PC with adb running and it will automatically begin fastboot.
cmendonc2 said:
You have a different bootloader version. Just start it up connect to the PC with adb running and it will automatically begin fastboot.
Click to expand...
Click to collapse
And by just start up you mean starting by holding power and volume down?
I tried that too, but when I then try "fastboot devices" I just get an empty line. Tried that on two windows and one linux machine. I also reinstalled the different drivers for the tf300t several times.
Fastboot is very sensitive to connection method. You shouldn't use any usb hub or keyboard dock. Also try different usb ports. And check port on tablet, may be it caused by slightly bended connector.
Graiden05 said:
Fastboot is very sensitive to connection method. You shouldn't use any usb hub or keyboard dock. Also try different usb ports. And check port on tablet, may be it caused by slightly bended connector.
Click to expand...
Click to collapse
I tried different USB ports on 2 different notebooks...
And normal connection (MTP for example) is working fine.
How it presented in device manager? May be is limited access issue(e.g. on linux fastboot usable only with root access).
Graiden05 said:
How it presented in device manager? May be is limited access issue(e.g. on linux fastboot usable only with root access).
Click to expand...
Click to collapse
On device manager it is shown as Asus Android Bootloader Interface.
But I'll try with an admin account...
edit: Same with admin account.
I figured that it looks like a problem with the drivers (at least concerning Windows) and decided that updating Ubuntu to 13.10 might be worth a try (since I was planing to do that anyway).
And it worked. I have know idea what was wrong on Linux before, but now i get:
015d15b4d964120d fastboot
when I do "fastboot devices".
Looks good. Now I have to charge the pad since it is running low on battery from trying so hard
Hi all!
First of all I would like to give small heads up - I've been searching XDA and web for two days and ended with no working solution.
Situation:
Suddenly my Nexus 7 (2012) just died. No charging signs, nothing. So i tried Google described and random hardware resets using buttons with no luck.
I ended with situation:
device is not turning on - no screen flickering, not even small amount of pixel light visible,
ADB - no devices found,
fastboot - no diveces found,
nvflash - only my GeForce PC card found
when I connect device to PC I have to hold power button for ~10sec and there I hear "boing" (USB dev. disconnected), "boing" (USB device connected) sounds.
device is visible as APX device with "!" mark
I've tried:
hardware reset by pressing: power button, power+volume's buttons for different amount of time,
taking back and disconnecting battery,
using different software to discover device,
editing driver .inf file to recognize my device as ADB device. It did but still no visibility via ADB or fastboot (URL: http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/),
read and tried to use things from: http://forum.xda-developers.com/nexus-7-2013/general/rd-thread-trying-to-solve-ota-brick-t3117495.
No result at all...
One more - when I unplug and then plug in battery while having back taken I can hear sound that something is "running".
Please help!
@kepisty89 You can check here. Install the driver and check your device is detecting or not, actually you've a fried bootloader.
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
kepisty89 said:
Tahnk you @DutchMan_1990, I tried this and now ended with my device recognized as "Asus Transformer Prime APX Interface". Nothing else happened.
Any ideas?
Click to expand...
Click to collapse
Hi, kepisty89...
Unfortunately, APX mode is generally never good news .
It usually indicates that the Nexus 7's bootloader has either become corrupted or has been erased, and effectively hardbricking the device.
-----
See here, for a post I wrote for another XDA member with similar issues to yours, back in December 2014, where I elaborate further on this problem.
-----
I suspect your Nexus 7 will require a motherboard replacement .
Rgrds,
Ged.
I have similar issue, but mine I can get to bootloader but that's it, if I try to power it on all I get is the Google and unlock padlock, can't get to recovery, but my device is seen via fastboot ADB Wugfresh NRT, but as soon as I try to write to it ie flash files or try to restore device, ADB locks up, and when it says rebooting device my nexus tries to reboot but I get a black screen and Wugfresh says waiting for device, I have to force reboot bootloader hold power button vol down for NRT to see it again in fastboot. I can also boot tempery recovery via NRT but when I select mount it pops up on PC but I can't copy anything to it, also it says I have no OS installed.
Sent from my Nexus 6 using Tapatalk
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Phil01234 said:
MSM8994DownloadTool.exe Won't Work For Me
I need help.
My phone is stuck on the fastboot screen, meaning I can only Power if off and into Fastboot (using the Vol+ and Power buttons). Other than that, it does nothing. I cannot get into the OS at all, which means I can't enable USB debugging or anything. Fastboot recognizes my device, which is a OnePlus Two), but ADB won't, nor will my Windows 7 PC as a USB device. With that in mind, I followed all the steps in the posted guide. I get all the way to running the "MSM8994DownloadTool.exe" and nothing happens. Its as if the Recovery Tool doesn't even see my device. So, I'm really stuck and don't know what to do.
For clarity, here's exactly what I did (see below). I get all the way to Section B, Step 2 and that's where it breaks down. There's no different line, and no process ever runs, even after waiting 30 minutes. I ran the tool as Administrator, but still no luck. Can anyone help me? Just as additional info, my Mac also does not recognize my OPT as a USB device. Also, I tried my backup USB-C cable from the OEM, with the same results.
A. Install the Certificates followed by the Qualcomm drivers.
1. Restart your computer with Driver Signature Enforcement Disabled (Advanced Startup) Let me Google it For You
2. Open the folder "qc" and install the Test Certificate in the following Stores: Trusted Root, Trusted Publisher, Third-Party Root and Personal
3. Run the Qualcomm setup wizard (also located in the qc folder)
4. When completed, restart your PC again with Driver Signature Enforcement Disabled (Advanced Startup)
5. Turn off your phone and disconnect the USB cable from the phone.
6. Hold vol-up and plug in the USB(Do not press Power button). The screen will stay black but you will hear a sound from windows that a device is attached.
7. The driver should now automatically install. If not, go to device manager and right click "Unknown Device" and click "Update Driver" Search up the QC folder and press ok. The driver should now install. (Got the RELINK issue? Take a look here: http://forum.xda-developers.com/show...1&postcount=46)
B. Flashing Process
1. Open the OnePlus2_14_A.11_151211 folder and open "MSM8994DownloadTool.exe"
2. Look if your phone is detected in the list. everything is Chinese but you will see one row with different chinese text from the rest within the list. If not, recheck if driver is detected in Device Manager (If not, go back to Step A - Line 4).
Click to expand...
Click to collapse
I've bricked my op2 a while ago. I'm a real noob so I don't know if it will work but have you installed the adb mac drivers or try "fastboot continue" while in fastboot. Just don't give up and keep try. You have absolutely nothing to lose.
chintu1234 said:
I think you have a bad download, try downloading it again and download the 3.0.2 version if you can.
Click to expand...
Click to collapse
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Phil01234 said:
Thank you very much. I have the latest version, but still nothing. I don't know if this has anything to do with it, but my OPT wasn't being recognized as a USB device even before I screwed up. That leads me to believe my OPT USB is maybe not functional. ADB doesn't recognize it at, nor will the MP...DownloadTool.exe. I'm guessing it is just hard-bricked since I have no other way (besides USB) to interface with the device.
Click to expand...
Click to collapse
Try connecting your OPT to some other guys pc and see, it may be because of your pc's end that its not getting connected.
And if the same thing happens with a different pc then yeah your usb port or something is fried. Try going to service center if the same thing happens again.
Hey there guys, so as the title suggests, i'm having a bootloop problem on my m30s sm-307f, i can't access recovery mode, and i'm unable to start the flashing process because i can't even install the usb driver, i've tried several drivers, using several cables, on several systems (windows 7 / windows 10 / windows 11), and i always get that infamous yellow triangle on the SAMSUNG Mobile USB CDC Composite Device in the Universal Serial Bus Controllers section in the device manager, the phone was operating normally one day, and the next day when i try to power it on, i get this, i'm absolutely certain that i did nothing to the phone, not even an update, and it most definitely didn't fall to the ground, please respond, i have really important data there, and it would devastating to lose it, and thanks a lot.
Can you access Download Mode?
UniX1803 said:
Can you access Download Mode?
Click to expand...
Click to collapse
Yes i can.
Ok. Can Odin detect your phone?
UniX1803 said:
Ok. Can Odin detect your phone?
Click to expand...
Click to collapse
No, unfortunately it can't, which is to be expected since windows itself can't detect it.
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
UniX1803 said:
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
Click to expand...
Click to collapse
I do know how to get to download mode, i did of course try, and although it does appear on the phone that it's working, the computer doesn't detect the latter as i explained, and as such, odin doesn't detect it as well.
I was talking about Recovery Mode.
UniX1803 said:
I was talking about Recovery Mode.
Click to expand...
Click to collapse
Sorry, i didn't notice that, i'm unable to access recovery mode either because the phone just keeps rebooting.
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
UniX1803 said:
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help, i really appreciate it, some people are saying that it's a motherboard problem, what do you think ?
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
UniX1803 said:
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
Click to expand...
Click to collapse
You're right, again, thanks a lot for your help.
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
treety said:
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Click to expand...
Click to collapse
I've already tried them, they didn't work as intended unfortunately, thanks for the reply though.
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
stoag said:
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
Click to expand...
Click to collapse
Unfortunately, i wasn't able to, but i think it's most likely hardware related.