Completely new to android. Regular mode, pc recognizes easily. Download mode, not at all. No unknown device. If on the Note I pick "upgrade from adb" then the pc devise manager shows a samsung device adb device. So, it sees it. but still Odin does not see it. Tried USB debug mode on/off on the tablet. Restarted PC and tablet several times. Using original usb cable, tried various usb ports. Am I missing something obvious? I feel that I am.
I would install kies from samsung. Completely reinstall drivers from with in kies and go from there. You could actually push the recent update from kies to your tab and that will do it in odin mode. Give it a try…
Sent from my SM-P600 using Tapatalk
Bizack said:
I would install kies from samsung. Completely reinstall drivers from with in kies and go from there. You could actually push the recent update from kies to your tab and that will do it in odin mode. Give it a try…
Sent from my SM-P600 using Tapatalk
Click to expand...
Click to collapse
Using Windows 7,
Uninstalled Kies 3, reinstalled, updated, uninstalled/reinstalled all drivers. Tried usb debugging on/off (which changed the drivers) Odin perfectly detects the tablet in regular mode. In recovery/download mode I still don't even get an unknown device. It sees the Samsung Adb device, but neither kies (though maybe it shouldn't) nor odin "see" the device. Tried various usb ports, multiple computers. I am on most recent firmware for the P600
Working with tablets (first ipad 2, now the new note) make me feel like I know nothing about computers.
beleghm said:
Using Windows 7,
Uninstalled Kies 3, reinstalled, updated, uninstalled/reinstalled all drivers. Tried usb debugging on/off (which changed the drivers) Odin perfectly detects the tablet in regular mode. In recovery/download mode I still don't even get an unknown device. It sees the Samsung Adb device, but neither kies (though maybe it shouldn't) nor odin "see" the device. Tried various usb ports, multiple computers. I am on most recent firmware for the P600
Working with tablets (first ipad 2, now the new note) make me feel like I know nothing about computers.
Click to expand...
Click to collapse
Recovery and download mode are two completely different things. If you are in recovery then Odin will not see the tablet. You have be in download mode. Power the device off and restart it by holding down the power button and volume down at the same time. If you hold power and volume up you will go into recovery which does you no good for Odin.
nrage23 said:
Recovery and download mode are two completely different things. If you are in recovery then Odin will not see the tablet. You have be in download mode. Power the device off and restart it by holding down the power button and volume down at the same time. If you hold power and volume up you will go into recovery which does you no good for Odin.
Click to expand...
Click to collapse
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
beleghm said:
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
Click to expand...
Click to collapse
Samsung is the only manufacturer I have used that does download mode. Most others have bootloader mode that works with adb. Though using Odin is easier for beginners than adb.
Sent from my SM-P600 using XDA Premium HD app
beleghm said:
Thank you, that is exactly what my problem was, as I said, I knew I was being an idiot, thank you. *slaps forehead* I had asked "that guy" at work and had been told recovery mode and download mode meant the same thing, so I didn't google it.
Click to expand...
Click to collapse
i don't know what the hell is going on here... mine won't work
i have the note 3 and it works fine, i just re downloaded and reinstalled kies 3, kies will recognize the tablet when it is booted normally
as soon as i boot into download mode, odin won't see it.
what gives? i have usb debugging on, i can't figure this out, what am i missing, as im sure it is super simple....
asaqwert said:
i don't know what the hell is going on here... mine won't work
i have the note 3 and it works fine, i just re downloaded and reinstalled kies 3, kies will recognize the tablet when it is booted normally
as soon as i boot into download mode, odin won't see it.
what gives? i have usb debugging on, i can't figure this out, what am i missing, as im sure it is super simple....
Click to expand...
Click to collapse
For me, I had to use the old Kies, not Kies3. I didn't even get a device showing up in device manager when USB Debugging was enabled, though if i switched USB mode from MTP to Camera, I would get a device Samsung_Android that looked like it wanted ADB drivers, but manually pointing it to the drivers included with Kies3 didn't work.
beleghm said:
Completely new to android. Regular mode, pc recognizes easily. Download mode, not at all. No unknown device. If on the Note I pick "upgrade from adb" then the pc devise manager shows a samsung device adb device. So, it sees it. but still Odin does not see it. Tried USB debug mode on/off on the tablet. Restarted PC and tablet several times. Using original usb cable, tried various usb ports. Am I missing something obvious? I feel that I am.
Click to expand...
Click to collapse
I have a sm-p600 that has been rooted and had a custom rom on it. I went to change the resolution and it rebooted and then i got a bootloop and now i am unable to get into my custom recovery and i cannot connect through adb or in download mode with no unknown device message as well. any suggestions to fix this would be appreciated.
Make sure Kies isn't running in the background, it screws with ODIN....
Related
So I have done something to my epic, I don't know if it would count as bricked soft bricked or whatever but when I turn it on it bootloops on samsung logo but I can still enter download mode, So I figured I would flash a stock rom with odin and start over.
I went to this thread
http://forum.xda-developers.com/showthread.php?t=1052813
downloaded necessary drivers
installed and tried to connect to odin
I've tried every combination of powering the phone with the computer, then putting in download mode
I've tried powering on with battery booting into download mode opening odin selecting pit and tar and then pluging it in and nothing.
when the pc does recognize the phone it says device not recognized or device malfunctioned.
I saw a post somewhere with someone saying I needed to "advanced install" the drivers. So whatever that means I tried to uninstall the device from device manager while plugged in in download mode and updating the driver to the 64bit samsung usb driver and it says "unknown device already has best driver installed"
the computer I'm using is an HP DM1-4010us not that I think it would matter.
If anyone has anymore suggestions, or can suggest a method or pattern of step by step what I need to do
maybe install the drivers in a different compatibility mode?
what about odin compatibility?
System UAC is turned off and firewall is off too just in case it may be blocking odin from communicating with comm ports so I know that can't be the issue.
Thanks for listening to my overly detailed and confused ramblings and thanks in advance for any advice or help offered.
Kcrick said:
So I have done something to my epic, I don't know if it would count as bricked soft bricked or whatever but when I turn it on it bootloops on samsung logo but I can still enter download mode, So I figured I would flash a stock rom with odin and start over.
I went to this thread
http://forum.xda-developers.com/showthread.php?t=1052813
downloaded necessary drivers
installed and tried to connect to odin
I've tried every combination of powering the phone with the computer, then putting in download mode
I've tried powering on with battery booting into download mode opening odin selecting pit and tar and then pluging it in and nothing.
when the pc does recognize the phone it says device not recognized or device malfunctioned.
I saw a post somewhere with someone saying I needed to "advanced install" the drivers. So whatever that means I tried to uninstall the device from device manager while plugged in in download mode and updating the driver to the 64bit samsung usb driver and it says "unknown device already has best driver installed"
the computer I'm using is an HP DM1-4010us not that I think it would matter.
If anyone has anymore suggestions, or can suggest a method or pattern of step by step what I need to do
maybe install the drivers in a different compatibility mode?
what about odin compatibility?
System UAC is turned off and firewall is off too just in case it may be blocking odin from communicating with comm ports so I know that can't be the issue.
Thanks for listening to my overly detailed and confused ramblings and thanks in advance for any advice or help offered.
Click to expand...
Click to collapse
Try a different USB port and cable the stock cable sucks azz try a blackberry cable.
Have you tried a different usb port?
I have always used the cable that came with my epic, are you using it?
I'd at least open odin, put your phone into download mode and then connect it to the PC and see if with the stock cable it is recognized. That will tell you perhaps the cable you're using isn't connecting right for odin's use.
do you have any other cell phone drivers on your PC? I've seen where they conflict. Remove all cells phone drivers, reboot, install the epic drivers for win7 64bit
EDIT: damn i type slow. someone got itn there already
jdelano said:
EDIT: damn i type slow. someone got itn there already
Click to expand...
Click to collapse
LOL it happens to all of us at some point
jdelano said:
Have you tried a different usb port?
I have always used the cable that came with my epic, are you using it?
I'd at least open odin, put your phone into download mode and then connect it to the PC and see if with the stock cable it is recognized. That will tell you perhaps the cable you're using isn't connecting right for odin's use.
do you have any other cell phone drivers on your PC? I've seen where they conflict. Remove all cells phone drivers, reboot, install the epic drivers for win7 64bit
EDIT: damn i type slow. someone got itn there already
Click to expand...
Click to collapse
I've got 2 usb cables, a motorola and a htc neither will work. both are really good condition thick and well made, ive tried all usb ports as well. odin does not recognize the phone at all. no other drivers are installed as I just reformatted my pc 3 days ago. all updates done.
Try hiemdall it uses its own drivers...
Sent from my SPH-D700 using xda premium
Big Goron said:
Try hiemdall it uses its own drivers...
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Heimdall fails to install drivers or detect the device, does this with AND without the samsung 64bit drivers installed.
Try downloading kies air to get drivers.
Sent from my SPH-D700 using xda premium
Make sure you downloaded the drivers named "Samsung_Mobile_Drivers_V1.3.8.." if not then that's the problem, if you need it I can email you the the file. Try all the usb cables in your house and all the computers as well, and take out sd card, I've also had this odin problem and I'm also sure it's your drivers since there are like 10 samsung drivers floating around lol.
Edit: nvm I downloaded the drivers from the thread you linked and they are correct.. try different cables, no battery no sd card, and different computers
Sent from my SPH-D700 using xda premium
I'm currently running CM 9.1.0, so it used to work. The phone charges just fine, and I can transfer files to and from my pc via windows explorer.
In my system tray, the phone shows up as "Android Device". I think it used to show up as "Samsung Galaxy S II", or something similar. Did it change when I installed CM 9.1? I can't pin it down.
Kies and all the drivers I could think of have been updated, including those for the mobo USB. Phone drivers I grabbed right from this site: T-Mobile_t989_GSII_ADB_Drivers.
I've tried different USB ports on my PC as well as different cables. Nada.
Any ideas? I'm at the end of my rope.
Maybe the build.prop changed?
Sent from XDA app
Anything other than stock won't be able to be identified on Kies. Odin try going into download mode maybe your phone will then show up on odin.
Download mode. That was the key. Thank you. That should have been obvious, but I'm not a regular twinker.
Hello, I'm the new guy, kind of (I'm new to this forum but somewhat a technological handyman, so to speak).
I had recently obtained a Samsung Galaxy Ace II, everything was going good on the phone, hell, it's what? Two years old now? Anyway, I noticed the immense trouble I've been having trying to get several Windows PCs/laptops to detect anything from the phone, no driver updates, installations, not even from the trustworthy SAMSUNG Kies application. It is becoming a real problem as I really want to keep this phone, root it, installing several ROMs as I go along, but no, the computers won't even allow me to access the contents of my SD card through USB.
(Note: I have manually downloaded and installed SAMSUNG USB drivers and pooft, still nothing!)
I have tried quite a few methods to allow the PCs to establish a connection with the phone e.g. Dialing "*#7284#*, accessing "PhoneUtil", choosing "PDA" as the good mode, even switching to "MODEM" then back to "PDA"; Uninstalling/Reinstalling drivers; Attempting Kies.
I guess I am on the look out for a new-ish phone to replace this, which saddens me as I love being able to root, install various ROMs, Kernels etc, personally I like this phone too, more than my Spica running ICS (couldn't be too hard though, it wasn't stable whatsoever).
If anyone on this board could find a solution to this problem for me, I would be ever so grateful, I don't doubt it though, I love the work of XDA. Thank you.
Turn off the phone with no cable attached, press volume down, home and power at the same time and then volume up to put it in ODIN mode and connect it to the PC (use windows vista or newer so it auto installs the driver) It should install something like Samsung USB serial device. Tell if it works
Do I have to load it into ODIN mode whilst Odin is running on my PC?
[/COLOR]
RyanCM said:
Do I have to load it into ODIN mode whilst Odin is running on my PC?
Click to expand...
Click to collapse
For this test you dont need ODIN on the PC. Its only to see if the PC recognizes the phone
Porobu said:
[/COLOR]
For this test you dont need ODIN on the PC. Its only to see if the PC recognizes the phone
Click to expand...
Click to collapse
I just tested this and it appears not to be working, whatsoever. Is it necessary to have all SAMSUNG USB drivers installed on the PC?
Thank you for the idea, though. I just really want to root/mod my phone, ugh.
RyanCM said:
I just tested this and it appears not to be working, whatsoever. Is it necessary to have all SAMSUNG USB drivers installed on the PC?
Thank you for the idea, though. I just really want to root/mod my phone, ugh.
Click to expand...
Click to collapse
Windows should auto install the drivers. Connect the phone to the PC and see in device manager if there is something like an unknoen device or Samsung USB device
Porobu said:
Windows should auto install the drivers. Connect the phone to the PC and see in device manager if there is something like an unknoen device or Samsung USB device
Click to expand...
Click to collapse
Thank you for the help, although my problem is not dealt with still. I have completed the steps that you had suggested, thoroughly and repeatedly, yet there is no hope for a permanent, or even temporary fix for my mobile.
Windows isn't displaying any correlation between my PC and phone, no driver software auto-installs and no sign of the device being located in the Device Manager, not even under an "Unknown device".
Is this a problem for most Ace II devices? Or am I missing something that is too obvious to consider so seriously?
Porobu once told me something like:
1. Uninstall kies and sammy usb drivers
2. Install kies again, it should promt to install USB drivers.
3. Plug in phone to pc in DL mode.
I'm not sure what you mean in your 1st post so im assuming you have yet to try this. Works for me
When do I plug the USB into the phone and boot my phone into download mode? As soon as the drivers are installed via Kies?
RyanCM said:
When do I plug the USB into the phone and boot my phone into download mode? As soon as the drivers are installed via Kies?
Click to expand...
Click to collapse
After kies installation complete(dont have to open), boot phone to download mode, connect to cable and plug to pc
It sounds like a broken microusb port but try something first.
Download ubuntu or any other live cd linux distro
Boot it on your pc. You dont need to install anything.
Open a terminal
*Plug the phone while it is turned on to the PC
Write in the terminal 'lsusb' without the quotes and press enter
Something like Samsung android device or MTP device should appear.
If it doesnt appear power off the phone and go to odin mode and repeat from the * the steps
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Have you tryed using a different usb port? How about using a different pc? Does it even connect when you tab s is on? My pc can detect my tab s fine but had some issues with windows 8.1 and odin crashing. My guess would be trying on a pc that can detect other devices in download mode just fine. Did you also enable usb debugging?
I'm stumped given what you have tried. I'm assuming you are using CF-autoroot. On Windows 7, Odin wouldn't see download mode until I installed the Samsung drivers downloaded from Samsung. Then everything went fine (after which I rolled Windows back to the previous restore point because the Sammy drivers messed up my Nexus 5 connection. Also, if it matters, I used Odin 3.0.9 but with Chainfire's Odin.ini file.
Are you waiting to plug the tablet in until after you have entered download mode? I don't know why, but the instructions for CF-autoroot were very explicit about that.
coolguycarlos said:
Hi All,
I recently purchased two Galaxy Tab S tablets (10.5, SM-T800) which I have been trying to root for the past couple of days but have been getting nowhere.
The issue stems from the inability of my computers being able to detect the tablets in Download Mode.
I have tried the following:
I have tried installing different versions of Odin
I have download kies.
I have tried re-installing the Samsung usb drivers on numerous ocations in two different computers.
I have tried different usb cables to include the cable that came with the tablet.
If Tablet is powered on however, the computer will detected it and thus so will Odin. This is only happens in Download Mode.
If googled this issue and it seems to be a none issue however I have yet to find a fix to this. I was hoping I would have better luck in this forum.
Click to expand...
Click to collapse
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
pdolton2000 said:
Dont mean to patronize...but you have enabled usb debugging in developer options and installed the adb driver right? Coz odin wont see anything until you do this.
Click to expand...
Click to collapse
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Yes I already tried different USB ports. Different USB cables. Different computers. USB Debugging is enabled.
Again Odin does detect the tablet as long as the tablet is booted up to Android. Odin detects is, Windows Detects it, Kies Detects it.
As soon as I reboot the tablet into Download Mode and plug it back into the computer, is as if nothing is plugged in. No driver gets installed. No new hardware is detected and thus Odin wont detect it.
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
coolguycarlos said:
FIXED!!!!!
Ok so what essential was happening is I was turning off the tablet. Putting it into download mode using VolDown+Home+Power. However that seemed to be actually taking me to recovery and now download mode.
I ended up booting back into android with usb debugging mode enabled and running the following adb command
adb reboot download
This rebooted the tablet into download mode which looks totally different than the recovery, it then installed the drivers and Odin was able to finally detect it!
Thank you all for your assistance!
Click to expand...
Click to collapse
Nice one pal glad it all worked, thought you might not of been in dwnload mode coz thw only reason odin wouldnt detect it is that reason....strange how vol down was taking you into recovery though, usually thats vol up...mad
---------- Post added at 07:35 AM ---------- Previous post was at 07:32 AM ----------
DUHAsianSKILLZ said:
You dont need adb as it worked fine without adb for me. Usb debugging does the trick. But installing adb could help
Click to expand...
Click to collapse
Adb drivers are active regardless when usb debugging is enabled ....some times though you have to install them manually....but as hehad installed samsung software the drivers got installed.
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Hi i have a similar problem as you, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
bigillz said:
I have an SM-P607T with an active T-Mobile plan - though I bought it from a third party then added it to my account. Previously everything worked fine, as I tried CM and a few ROMs on it, but ultimately went back to stock TMo ROM, 4.4.2, and just rooted it. Hadn't used it in awhile, grabbed it and thought I'd update to official Lollipop build.
First off, I disabled SuperSU and tried to apply the 4.4.4 update, assuming after that it'd offer me 5.1.1. Applying the 4.4.4 update failed. I factory reset the device in recovery mode (stock recovery), which of course fully removed SuperSU. Still fails updating. I downloaded the Lollipop ODIN tar, and that's where I started running into showstopper issues.
When I plug in a USB cable from a PC, the tablet starts charging, and that's it. There is no sign in windows that a device has been connected, no ding that something has been attached, no driver search. I tried this on 3 Win10 PCs. On all of them I installed Samsung Drivers, and even installed Samsung Easy Switch (new KIES). It would never register that it was plugged into a PC. I tried plugging my Note 4 in, registers and works fine (I read a thread on here by someone saying Win10 wouldn't recognize Samsung devices - not the case for me, phones work fine, just the tablet that won't show up). There is NO driver issue because the system never acknowledges anything is connected at all. I tried 3 PCs and 4 USB cables. I tried Samsung Easy Switch/KIES device recovery - tried putting tablet in download mode and tried putting it in recovery mode; neither ever shows up on PC. I tried using ADB, does not show up in devices (I have USB Debugging checked, Unknown Sources checked, etc etc).
I downloaded the Lollipop ODIN tar.md5 and put it on the microSD card. I loaded stock recovery, chose to flash from external storage, selected the .tar.md5, it said it was flashing it, said it flashed successfully even. Rebooted and it hadn't flashed at all.
Does ANYONE have ANY idea how to get my tablet updated? I can handle not being able to connect to PC, but I want to at least get OTA updates working. Factory reset, apply 4.4.4 OTA, fails after reboot every time.
Help?!
Click to expand...
Click to collapse
---------- Post added at 11:04 AM ---------- Previous post was at 11:02 AM ----------
I am confused what you mean by calculator, I am on Win 10 and have a similar problem, my Note is the SM-P600 that I rooted and has TWRP v2.8.7.0 and last time I went into recovery, the thing came up with a stock red upper left hand side text say "recovery in not seandroind enforcing" then ended up with the "Firmware upgrade encountered an issue please select recovery mode in kies and try again" but the damn thing will not connect. 2 usb 3 ports and 2 usb 2 ports multiplecables- anker, samsung you name it-musical ports, tried right clicking the 4 usb port hubs and unchecking power saving in power mgnt- nothing- yet my the usb drivers see my note 4 just fine, in device mngr, the note tablet shows up in usb at the bottom as samsung device, I am just perplexed as to how to un**** this thing. If you have any suggestions and can let me know I'd appreciate it.
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
shineliu said:
I have the similar problem as you. Someone said it could be easily resolved by enable CP logging in the recovery menu. I saw the solution after I got my device working so I did not try that.
My procedure is
1. Enter this using calculator (+30012012732+
2. enter *#0808#
3. switch to "DM+MODEM+ADB " option, OK, and reboot
4. until now, I could see the USB device in my Windows Device Manager, but MTP function won't work
5. repeat step 1 and 2
6. switch to "MTP+ADB" option, OK, and reboot
7. Done. Device could be identified. (Windows 10 x64 Pro)
Hope it could be useful for you.
Click to expand...
Click to collapse
thank you very much. it worked.