Related
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Good write up!
The procedure worked fine on my laptop. When I did it on on my home PC I forgot to disable auto-mount and the Nook installed itself as mass storage. I was able to right click -> un-install all the USB Mass Storage entries (with the Nook unplugged), disable auto-mount, plug the Nook back in, and have it show up correctly.
In short, I did not need to use "USBDeView" as I was able to remove the diveres manually. I suppose if you have more than a handful for USB devices (I just have a Mouse, Keyboard, and printer) "USBDeView" might be helpful to determine which drivers to un-install...
The device manager is enough for most people, but there is a somewhat large number of us that are having trouble still. Possibly because of other devices we have installed before. (I dont understand how all the drivers work and I wont pretend to)
Some people have go so far as putting a fresh install on Windows on a partition of a PC.
I had this problem with both my laptop and my desktop, which surprised me. This worked on both the laptop and PC, so hopefully it can help other people.
I cant wait to get my own tablet on the 12, I will take lot of pictures and make this process more user friendly.
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
mtelesha said:
I did all of the steps several times and I still get WPD Driver for the portable device and mass storage for my Nook Tablet. I am guessing I am up a river without a paddle right now.
I will try it in Linux and/or try it on someone's Windows machine.
Click to expand...
Click to collapse
Did you sort by last time plugged in and delete all of those too? Have you re-checked and then re-un-checked automount/usb debugging and such?
This is interesting, you'll have to come back and let me know if you ever get it working on your PC. Maybe its a good excuse for a nice healthy re-format and reinstall of windows?
l3ft3r1s said:
I am trying to install the drivers from Google's SDK package. So I browse to the correct folder, but device manager says "windows could not find driver software for your device".
Any suggestions? Is there any other set of drivers specifically for NT?
Click to expand...
Click to collapse
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
The_Joe said:
I don't know if they are different, but I used the drivers specificly from the thread about rooting the NT. [I would post a link, but I'm typing from my phone]
You have the yellow error mark next to your device? If so you've almost got it!
Click to expand...
Click to collapse
Yeap, that did the trick, thanks. Drives installed successfully this time, but adb devices still returns nothing.
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
adb error: device offline
This drove me nuts for at least a day. Turns out it is what happens when you are plugged into a USB 3.0 port on your PC side. Find out which USB is 2.0 (Front Panel for ZT Systems), use it and life suddenly gets really good.
The_Joe said:
Thats very odd. It shows up in device manager as an ADB device?
If so, please try the NookandZergy file, then copy the results so we can try to farther assist
What devices have you rooted before?
I cannot help but feel I will be 100x more useful in a week when I have my device in hand...
Click to expand...
Click to collapse
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
l3ft3r1s said:
At last, after many different things I tried, I am getting a response to adb devices!
I tried disabling and uninstalling usb devices, uninstalling java 7 and installing java 6, re-installing android sdk, at last it worked. Sorry, I can't guess what the problem was :/
Click to expand...
Click to collapse
The problem is sdk uninstall and use ccleaner to clean your PC and registries. Use the drivers provided in this forum
Sent from XDA using one of my Android Toys
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
LadyPenley said:
Edited post to: Sorry to bother anyone, I found the problem. Thank you all for helping!
Click to expand...
Click to collapse
In the future don't delete your original, just post an edit with the fix. That way when someone else has a similar problem your post can help.
Sent from my BNTV250 using xda premium
mtelesha said:
Well I have done everything and still get permission denials for copying and chmod on my Nook Tablet.
Took the Nook to work and tried it on a fresh machine. Everything went great. Drivers installed and everything ready for usb debug and non-automount and then I run into the same permission errors and being denied access to the folder for Zerk and no chmod.
Same issue no matter what machine. What is wrong with my tablet? I am re-rooting it from being automatically upgrade to 1.4.1. I get it to 1.4.0 with the SD card restore.
Click to expand...
Click to collapse
Did you find a solution? Thats a problem I sadly dont know how to help with. I would start with:
-Check USBDeview and delete anything android/Nook/usb related. Delete just about everything.
-Restart the device
-Uncheck and recheck the USB Debugging boxes
-Recheck and uncheck the auto-mount box
-Test
-Try a different USB Port
-Try another PC
Thanks but didn't work.
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
The_Joe said:
(I cannot post links at this time, a quick Google Search or a look at the Topic titled "Full Root")
The goal of this guide:
I rooted my family members Nook last night but got hung up for a few hours trying to get the ADB Drivers enabled. This is how I made it work. This guide will be expanded and improved once I have my own Nook Tablet (Jan 12th).
Things you need:
• Nook Tablet (Duh)
• USB cord to go between NT and Windows PC
• PC with Windows installed (Tested on XP and x64 Windows 7)
• TGPS_Launcher.apk Installed to your Nook
• ADB USB Drivers for Nook Tablet Extracted to C:\Ntroot on your PC
• USBDeView open on the Windows PC
Step 1:
Ensure that your Nook is version 1.4.0 and not 1.4.1. (I will expand this step later when I have a nook in my hand, I suggest a Google search if you do not know how to do this)
Step 2:
Find this thread on your Nook and download the TGPS_Launcher.apk to your device, then install it. This is well covered in many other threads. (Will expand this step when I have a nook in my hand)
You should now be able to allow USB Debugging, and disable Auto Mount. These settings can sometimes change without your permission, so always uncheck and recheck them to ensure they are properly set.
Step 3:
Plug in your Nook to your PC. Your nook should still respond to your commands, if it tell you in USB Mass Storage mode, then retry Step 2.
Go into your Device Manager. If your Nook shows up with a yellow explanation mark indicating an Error, then you’re in business and really don’t need this guide. All you need to do is update drivers from the file C:\Ntroot. However, assuming that your Nook shows up under Disk Drives and USB Mass storage, then ADB wont be able to see your Nook, please keep reading.
Step 4:
Time to start the USBDeview utility. This utility will open to a list of almost all the drivers your computer has for USB Devices. We are going to uninstall a few of them, namely anything that says “Android” “Nook” or in my case, “Motorola”. You do not need to remove any that specify ADB.
Near the top right hand side, you can sort drivers by when the device was last connected. Do this, then remove any utilities used when you plugged your nook in. Done? Ok, time to see if your work was for nothing.
Step 5:
Make sure once again that USB Debugging is turned on for your Nook. Unplug the Nook, then Unchecked USB Debugging and Check it again. Now plug your device back in and check in Device Manager. You will hopefully see one of two things:
A: You will see your nook with a yellow error icon next to it, which means you just need tell it to update from C:\Ntroot.
B: At the top of the device manager you will see Android Devices, and your nook will show up as Android Composite ADB Interface
If your Nook is still showing under disk drives and mass storage, then try steps 3 and 4 again. Still having trouble? Do a factory reset and try again from step 1.
You should now be able to run your rooting program!
(I feel this should be in the Dev forum, but this is my first post and I was not allowed. Perhaps a mod would like to move this topic?)
I plan on purchasing my own Nook on the 12th on Jan, at which point I will add pictures and expand on my guide. This guide is written from memory and will be edited and improved.
Please consider this guide an Alpha Version
Click to expand...
Click to collapse
whitets said:
thanks, Joe. I did exactly as you mentioined below and had the Android/Nook appear at the top of the Devices listing. However, the adb command still can't find the device. Any suggestions?
Stan White
*****************
Click to expand...
Click to collapse
I had literally this exact same problem the 6th time I restored and flashed. IF im right, you just need to uncheck then recheck usb debugging.
Let me know if it works!
Hey there,
Here is a list of what I have before I get started.
Samsung Galaxy Tab 10.1 Wifi (P7510)
Android Version - 3.2
Kernel Version - [email protected]#1
Build Number - INFAMOUS TAB 0.1 P7510UEKMM
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
I bought this tablet from a friend who rooted and flashed with the INFAMOUS mod.
I have searched all over the web for an answer and cant find something for this case specifically.
Each time I plug in my tab, my PC tells me that the Hardware ID is missing.
I can see the tablet in my Devices and Printers (displayed as SAMSUNG_android) as well as in my Device Manager. In device manager it says the drivers are up to date and functioning.
What have I tried?
USB Debugging (On and Off)
Clearing cache via recovery mode
Updating drivers via W7 and KIES via Samsung
I have tried following a few threads on installing the KIES software without internet connectivity. However I would rather not use the KIES Software anyway as it is kind of garbage.
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Can anyone point me in the direction of help and me being able to enjoy this tablet?
I hope I have provided enough information. I am a pretty techy person and I understand how to do all of this but it seems like I am missing something really big.
Something to take note of, whenever the tab is plugged in (PC or Wall) there is a red x over the battery symbol and the tab charges very slowly.
Cheers
B
Snugglebutt said:
Basically I have no access to my tablets internal SD card via my PC (Windows 7 and KIES)
...
I am looking to have access to the internal SD card so I can flash a new Rom on the Tab, however I would first like to even just have access to the file transferring.
Click to expand...
Click to collapse
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
hope this help
FIXED
k1mu said:
The Galaxy Tab doesn't expose the internal "sdcard" as a device that you can mount on your PC. If you enable it, it shows up as a MTD device.
The sdcard partition is formatted using a Linux native filesystem, not FAT, so Windows can't recognize it.
I use adb to push files onto the sdcard. ADB comes with the android SDK.
Click to expand...
Click to collapse
To build on the above, if you have uninstalled Kies but also the Samsung USB drivers, you will be unable to connect the tab. Reinstall (or maybe uninstall and reinstall if you still have them) the drivers. A lot of the times that is the issue.
Click to expand...
Click to collapse
Ahhh ha! As soon as I uninstalled the driver that windows found and used the Google Driver that came along with the Android SDK, the tablet was recognized. Alas, I can finally use this tablet.
In the end it was as simple as a driver error, I spent a very long time searching last night and now I just feel silly.
The tablet still shows the red X over the battery symbol, whether I have MTP with USB Debugging on or off. I guess this can be avoided with certain ROMS. Anybody know of a ROM that avoids this?
Thank you all for your immediate responses!
B
Tid bit of info
H. Ess said:
As stated, make sure you have your tablet in MTP, and if so, make sure to update your drivers.
Settings > Storage > Additional Settings (top right) > MTP
Click to expand...
Click to collapse
Go to Settings>Storage>Options/Info (The one on the upper right)>MTP(Check this one)
Click to expand...
Click to collapse
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Snugglebutt said:
By the way you two, there is no option in 3.2 for this.
In 3.2 its Applications/Development/USB Debugging
In storage there is no option to choose MTP, it seems that it always has been enabled and I cant find it anywhere in the settings to change it.
Thanks for the input though
Click to expand...
Click to collapse
For honeycomb and many others, debugging is always there. Under the storage option, you have an Additional Settings button usually and it should be present in there. I was always running3.2 until like a couple days ago so surprised its not there. Oh well problem solved lol
I'm having a similar problem with my tab not being recognised by my pc (win7 64) or in kies. It was originally an M380W (Korean) model, which I updated to a P7510. That all went fine, and the tablet works perfectly, except for the fact that my pc no longer sees it when it's plugged in. I tried uninstalling and reinstalling the drivers, but no dice. I'm going to see if adb works.
I have a NT 16 gb from stock with my smartphone usb cable but not the charger.
I connect the usb cable to an international adapter via its usb port so I think I get 1.6A: and judging by how fast I charge the NT, I would say it is right.
I want cm10.2 or cm11 [preferably of course] but I cannot install cwm.
I cannot get usb debugging on by downloading an apk and lunching it: I must choose between the app installer or the package installer and then get the error: only from NB we can install apk's, great.
I have 1micro sdhc class 4 of 4gb and one class4 16gb, none of them permits to boot up which incredibly sucks, idk why.
I configure them with minitool, 300mb space, and my put img of cwm 6.0.4.6.
Every time I end up with the reset factory choice from NB after I perform pwr+home then power alone; whether I connect the nt to the power adapter or not.
When I connect the nt to windows, it is seen only as a drive.
ADB does not recognize the device of course.
Is there a way to install CM ? without a bootable SD ?
This is unbelievably frustrating and since I am a complete noob to android and all that, pls level with me
this guide is quite helpful: http://wiki.cyanogenmod.org/w/Install_CM_for_acclaim
if i were you i'd throw the ROM and Gapps that you want on the internal storage if you can get into USB mode, then look at this and use this guide to flash CM: http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14
yeah it says how to root stock firmware but it's the same process, just different zip files.
yes I have seen the wiki and I am stuck at Boot to recovery mode since my nook always shows the BN recovery:
from your second link, it is this line
You will see a picture of N on the screen followed by a box with a white background followed by CWM booting up.
CWM does not boot. Is it possible that the problem is from the SD cards ?
I tested a sandisk 32gb class10, it still shows the factory reset screen
Regarding the USB mode, the NT says I must install the apks from BN only, so I do not not know how to active it.
i'm assuming you know how to connect the tablet to a computer... try that.
blue whale said:
I have a NT 16 gb from stock with my smartphone usb cable but not the charger.
I connect the usb cable to an international adapter via its usb port so I think I get 1.6A: and judging by how fast I charge the NT, I would say it is right.
...
Is there a way to install CM ? without a bootable SD ?
This is unbelievably frustrating and since I am a complete noob to android and all that, pls level with me
Click to expand...
Click to collapse
Have you tried the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163?
Note that many NT will boot off SD only from power-off state and upon insertion of a powered USB cable (regular mini-USB cable connected to PC or powered USB Hub should work fine).
Success CM11 is installed \0/; My partition was of type 0b not 0c...
I do have a problem now when I plug in the tablet on windows xp sp3: windows cannot find the drivers with or without debugging on.
Is it possible to see the device as a storage space in general and also being recognized by adb when debugging is on {i believe it is how this work, is it not ?} ?
blue whale said:
Success CM11 is installed \0/; My partition was of type 0b not 0c...
I do have a problem now when I plug in the tablet on windows xp sp3: windows cannot find the drivers with or without debugging on.
Is it possible to see the device as a storage space in general and also being recognized by adb when debugging is on {i believe it is how this work, is it not ?} ?
Click to expand...
Click to collapse
By default the NT should automatically show up as an MTP device when plugged in via USB.
You only need to enable USB debugging when using adb access over USB.
digixmax said:
By default the NT should automatically show up as an MTP device when plugged in via USB.
You only need to enable USB debugging when using adb access over USB.
Click to expand...
Click to collapse
Well, via a software, I removed all the usb drivers connected to an android tablet. Then, the first time I plug in the NT, I have an OMAP443 install [for I do have these drivers] and windows then searches for the "BN NT" but cannot find the drivers. It's quite puzzling.
For the MTP, as far as I understand, I must install windows mediaplayer 11, is there not an alternative >?
blue whale said:
Well, via a software, I removed all the usb drivers connected to an android tablet. Then, the first time I plug in the NT, I have an OMAP443 install [for I do have these drivers] and windows then searches for the "BN NT" but cannot find the drivers. It's quite puzzling.
Click to expand...
Click to collapse
Did you switch the NT to USB mode (Settings->Storage->Settings->UMS)?
For the MTP, as far as I understand, I must install windows mediaplayer 11, is there not an alternative >?
Click to expand...
Click to collapse
MTP on Win PC requires Windows Media Player 10 or later.
it did work after disabling the debuging
Hey guys.
I have Samsung galaxy ace 5839i (stock for 5830i) and I am using it for a few years, but this problem came for the first time.
Always, when I try to connect my mobile to pc using cable, it just won't connect, it won't even show me the notification of connecting.
Before this problem, I connected it to fedora linux and it was succesful, but now? It won't show me that USB sign even in windows.
Any help?
Thanks in advance
@LiQuDiAk, basically s5839i and s5830 i are identical in many areas ,, few questions though,, did you root your device or you are on android 2.3.6 stock version / kernel 2.6.35.7 ?
when you are in your windows device manager ( while you are connected , do you see any exclamation / question marks in front of the corresponding driver), you can always uninstall your old driver, reboot , then try compiled driver in attachment , and reboot to take proper effect in your registry (tested on win xp/7 -32bit) . Also check your device settings>Application>Development > USB Debugging and make sure the option is checked. now lets check your debugging mode through ADB command and see if your device is being recognized. download platform zip attachment, unzip it and put the folder someplace like your desktop. Now open your command prompt (cmd) through whatever means you are comfortable and change directory (cd) to the unzip folder or simply open your folder and drag/drop adb.exe into your CMD to be in the right place very fast. Then type "adb devices" without quotation marks and report for more troubleshooting .Assuming your Samsung cable is not faulty of course.
@ehsanotaku Yes i did root my phone on pheonix fire rom. No i do not see any. And debugging is checked, that was my first guess why it was causing this. I was checking, whether my device is recognized in linux (only available OS in present) and it was NOT, but the cable is not faulty, because it was charging my phone... but i will do recognize process on windows, hope it will get better. But thanks so far!
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
LiQuDiAk said:
so, the driver didnt help, but the adb devices got me something long which i do not completely understand (i am a girl and not IT) so...
Click to expand...
Click to collapse
off topic though, gender discrimination is prejudice,, sorry if you are offended . Learning from each other despite your gender,does not undermine your knowledge EVER mate You might find it hard to believe, but I am quite novice in android stuff myself ( learning a great deal from some female members though ).
Back to topic at hand now,,,So let Perfectly Clear take away the time-consuming tasks and fix some stuff ..1. so you can not access your sdcard's content from either systems,, even if you try some live bootable Ubuntu disk/flash into your system and boot it up,, you can't access the mount drive content , right?
2. screenshot of your device manger while you are connected always help mate
3. those long streams of numbers and words is supposed to be your device name , it means your device is communicating with your pc ( /sdcard/ should not be corrupted). You can push (copy ) some vital files to your device with following command :
again same path >> put some file into your desktop (drag/drop to cmd)
i.e: "adb push C:\Users\ehsanotaku\Desktop\test.txt /sdcard/"
back to your device and check root of your files with whatever file explorer you got to approve the theory
4. forgot to ask , just to be on the safe side your device is not in boot loop process, stuck on samsung splash screen or something like that, right?
okay, thanks!
1. I cannot access it trough USB to mobile way, but from SD card adapter, yeah I can (it is just the weird feeling, when you always have to put out your sd and do it that way, i would like to sort this out)
2. http://s1.postimg.org/nkta50u3x/Untitleddas.png I suppose the unknown device is my phone.
3. Just a question, my phone is not connected, i cannot access it and this doesn't help
4. Nope, it is working, i can access everything, just this connecting problem i have. anything else is running smoothly.
Let's say any of this will work, do you think flashing a stock rom will help? I am not sure, if this is problem of rom or not, so...
And maybe i wasn't clear (my bad if not) but when i plug the cable in my device and pc, pc will make this sound of new device found, but it wont show me anything, so my phone. It will charge, but it wont connect, it is behaving like it is on a charger and not connected to the phone.
@LiQuDiAk, Hasty actions are done in a hurry, sometimes without the necessary care or thought. Now let's not leap to any conclusion about your Android custom Rom and flashing back to stock. lets focus on your first most obvious problems,which is driver related.
You didn't declare your flavor of windows: i.e: Windows x86 based-PC;professional 7
Not so sure of your OS Name/Version and System Type, search "system information" in your search box.
Your task manger depicted ACPI x64 ( 64-bit system, no wonder previous 32-bit compatible didn't work out for you ).
Symptoms observed so far:
1. USB cable only charges ( remember your USB cable data line might be the culprit. Just in case of only charging,checking with another set recommended. Your USB port might be problem, some dirt or faulty data line, checking with another USP port doesn't heart though.
2. Windows recognizes something more (like in your case, struggling to find proper corresponding driver), but cannot see it as a Samsung android device (cannot allocate the installed USB drivers to the device).
-If you got Kies (Samsung proprietary software) installed on your PC, delete it with a descent uninstaller program such as CCleaner free version .Kies might cause driver conflict , use it as only last resort , if all drivers failed to communicate with s5830i device.
-Also Uninstall your previous given driver same way, now restart , back to system and grab set of universal Samsung Drivers from attachment .
3.Can't see your "USB connected" in Android notification bar, so you cant click on it and mount your storage data part while you are connected to your PC.
-Normally, when you plug in your Android device, Windows will recognize it as an MTP (Media Transfer Protocol) device and quietly mount it.
However, if you’ve ever attempted to unlock your device such as to install a new ROM or root it, then such miss behaviors might be expected occasionally .
Before i go for more troubleshooting , please provide a full screenshot from your "About Phone" page in your settings . I am quite curious about this phoenix Rom you have mentioned though . I am quite familiar with at least dozen of discontinued/ported projects, but never heard of such ported Rom from other models into s5830i .
Couple of solutions :
Navigate to your settings,Storage and touch the upper-right corner for the “USB computer connection” options, if you have this part available.
make sure “Media device (MTP)” is selected. ( if you have USB Utilities section or whatever added section in your custom settings go there . Selecting that will do the trick. If it does not, then you likely have a driver problem.
Open your device manager, Right click on your unrecognized device in question,choose update driver software, choose Browse my computer,find it through given x64 drivers in your package ,Restart. ( After a successful installation, restart your PC, you must have something like the picture in attachment ) .
Problem was not resolved, Uncheck your debugging option,power off your phone. Now hold Volume(+) + Home + Power for a couple of seconds simultaneously to get to your Samsung Recovery or your Clockwork Recovery, choose Reboot( might be some process/service in your background, which interfere with your Auto USB connected feature of your device. See if the problem is being resolved .
Problems have been persisting, we might need to format your SD card, but before that, insert it into your card reader, in your file explorer window choose Tools>Folder options>select view tab> tick your select hidden file.folders. Now copy all of your SD card's contents into some folder, safe inside your PC.
We can format your card through your clockwork mod recovery console, or some partition tools such as free mini partition wizard,,
problem still persist? let me know
Hey
After some rest with this, my mobile got it solved (dunno why, just once tried to do it and it works.)
So, thank you very much with your answers!!!!
And about that screenshots, I will PM you
But, really, thanks a lot, mate!!!!
Hello. I'm a happy (?!) user of Win 10 Pro x64 since few days.
I want to connect my RN4X Snapdragon to PC, using usb on my pc's motherboard.
However, despite setting option, that I'll listed below, my phone is still not recognisable as useful stuff.
Without changing anything on my phone since my last flashing topics (Feb and March this year), I was fully able to connect easily to pc with win7 x64. I also was able to connect (using Xiaomi's cable, cheap replacement does not seem to work) phone to win 8.1 x64, where only the basic adb fastboot were installed. But, I cannot do the same on newest Windows.
I've done:
1. Installing minimal adb and fastboot 1.4.3. for all users (I'm the only one account here, but not sure if that's matter)
2. Having programming option enabled, usb debugging enabled and all that good stuff.
3. All four elements on that list - https://************/how-to-fix-mtp-devices-not-connecting-on-windows-10/
4. I've tried to install it as adb interface, installing it manually, installing it by using *.cat files from xiaomi_usb_driver archive, that contain that kind of stuff for newer windowses (it's from this side, if I remember it right - https://www.xiaomiusbdrivers.com/2018/02/download-xiaomi-usb-driver-2018-for_4.html)
5. Almost all stuf from here - https://www.jihosoft.com/android-tips/windows-10-cannot-recognize-android.html. Because I do not have Samsung, Odin mode is not an issue
6. I've tried to install my Redmi 4X as MTP device. However, my phone during each connection to PC started himself in charging mode (I can change it). Even changing it doesn't changing anything, though.
7. Editing the bulid.prop, adding there few lines describing how the phone should behave. I've saved it, but my original version of bulid.prop does not have anything in there about types of connection. I don't remember it word by word, but I've could check in history if anyone will find it interesting.
Drivers for usb 3.1 are pre-installed with mine version of win10 (I cannot install drivers given on my motherboard's dvd attached, system says that I'm currently having them).
When I try to install it manually via device manager, on the first time it says, that is other device, identifed briefly as MTP. However, installing it either as Android ADB interface, fastboot interface or third option does not give me anything. What's worse, even when I've pick windows/INF as my source of drivers for this device, it does not list on "lemme pick ddevice type" MTP type devices. I'm using win 10 in polish, so it might be that I'm blind or does NOT understand translate.
What else could I do? I can of course use wife's laptop with 8.1, usb sticks or other stuff, but I would like to have it sorted out.
Does otg still works to your device?
whatpigs said:
Does otg still works to your device?
Click to expand...
Click to collapse
Not sure. How to check it? We use to have 16GB OTG to USB2.0 (other end was micro usb B), but we must have put it somewhere during moving out to new flat, cause I cannot find it now.
gonna bump it, cause there's not any clue yet.
Same here.