So I just bought a brand new Nook HD+ from best buy. It is in shrink wrap so looks factory new.
I first turn it on and it gives me the select the lanuage and country page (No wifi selected). I do not proceed. Press volume down and tap lower left hand corner. If gves me the Enable ADB button. I do not press it yet. Instead I plug it into computer, which then puts it in MTp mode.
I unplugged cable and now press the Enable ADB button. I plugged it back in and same MTP mode.
I then decided to skip OBE. So I press lower volume button and then lower left screen followed by lower right screen. Then I press the Factory button. Then the Skip OBE option.
Now I am at home screen, I go to settings, then developers, and I confirm the ADB status. just to be sure, I uncheck ADb and then rechecked it. Plugged it back in and same result. It puts it in MTP mode.
I then confirm by going to Device Manager and see no entry for Android Composite device.
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Need Windows Driver for Nook
I believe you need a windows driver for the Nook HD and HD+ on Windows. On Ubuntu, I just do "android update device && adb kill-server && adb start-server && adb devices"
I can't post links. google usb_driver_r04-windows
superflysocal said:
I do notice out of the box, it is 2.0.2 not 2.0.0? Does this mean it is a customer return? Even though it was shrink wrapped?
Click to expand...
Click to collapse
They could be working now on out of the box 2.0.2 now. Don't know.
You are not telling us much about your PC, which we need to know to help you. What version of Windows are you running? Have you got ADB running on any other devices?
No other new devices are showing? Did you follow the B&N trouble shooting guide section 4.6 which I reference in my HD+ tips thread linked in my signature.
Sent from my Nook HD+ Running CM10 on SD
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
superflysocal said:
I have win xp, but I have also tried it on win 7 machine and win mce2005 machine.
I am not sure if i ever had adb working for other devices but I think i have. Actually pretty sure I have.
I do know for absolutely sure I have had multiple android phones connected to this machine and in usb debugging mode, they show up as Android Composite Device.
I also have Android SDk installed on this machine (but not in the win 7 machine)
Click to expand...
Click to collapse
Well, since you had other devices using ADB, then go to device manager and look under USB controllers. Uninstall any USB composite device there, especially any that has the device id under properties and details listing 2080 as part of the number. That will force the system to re-recognize and reinstall the right driver you can get from my HD+ tips thread.
Sent from my Nook HD+ Running CM10 on SD
There was a usb composite but it was for my wintv usb, I uninstalled it anyways. Nothing else, still not doing anything. Any chance this is a new hardware version that has this locked down?
It did come with 2.0.2 instead of 2.0.0
I don't see a reason for a hardware revision, and there is no reason for 2.0.2 instead of 2.0.0 other than bug fix since you can still root with 2.0.0 - 2.0.4. The inability to ADB is on your part. Seriously I don't see why would B&N lock down people ability to ADB since it's a requirement for people to develop for Nook platform. It's not like B&N will make 2 different versions of each device, one for developers and the other for consumers. I can still see B&N may lock down ability to root with current method on future revision (say 2.0.5+) but as of now it's open. ADB will never be lock. I think the fact that ADB for Nook devices are hard to get to will not only deter people from root but people to develop for the platform as well. Personally I think it's a bad choice on B&N part to have it hard for people to ADB.
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
superflysocal said:
I do agree with you, but I am open to any suggestion.
I have a win7 64-bit laptop that I can use. Should I try that? I thought win xp machine would be easier.
Should I reset nook hd+ and NOT skip OOBE?
I was hoping to avoid wifi so that I don't update to 2.0.4 which was reported to have corrupt microsd card writes.
Click to expand...
Click to collapse
I just bought a HD+ from Walmart. It was 2.0.2 out of the box and I was able to root the device successfully after OOBE was completed. I don't remember if the device upgraded itself to 2.0.4, I'll check later. I did the all in one root process on a Win7 64bit lappy so try it and see if it works.
IMO the person who posted about the sdcard file corruption has hardware issues but who knows? No one else is reporting having this issue afaik.
There are people that report a success ADB driver install on win7 64bits via my method. Check the tips thread.
someone0,
just curious, what firmware are you on? 2.0.4? Are you having any sd card write issues?
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
superflysocal said:
So I reset the nook hd+, then registered (did not skip oobe) and it updated 2.0.4, but still same issue. It will not recognize device as Android Composite USB device, only as MTP media device.
i am beginning to think I got defective unit.
Click to expand...
Click to collapse
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
leapinlar said:
No, I don't think so. If you read through the posts on the other threads you will see about half the users have a very difficult time making adb work. And it is never anything wrong with the HD, it is always something with your PC. There are so many different setups for windows that it is very hard to advise people. Just keep trying things others have. I still have problems and I have been doing it for weeks and each time it fails it is a different thing. The only thing I can advise you is to keep uninstalling things because something that is installed is blocking your PC from recognizing the new device. I would uninstall any device under portable devices, other, android phone and any device under USB controllers that has 2080 as part of the device id.
Click to expand...
Click to collapse
Oh you are so rght. I never did figure out what is blocking it, too impatient to uninstall stuff.
BUT, I did find an old seldom used laptop with win 7 32-bit. When plugged in it gave me error that drivers could not be installed!. Went to device manager, found the device and updated driver. Adb achieved and all in one root done.
No, I'm on 2.0.0
Related
Hello, I have CM 7.0.3 encore with the overclocked kernel on my nook. Lately I have not been able to get the thing to connect to my computer in either windows or Linux. (It's XP and "Lucid Lynx" 10.04 Ubuntu if that helps)
If I connect my cable to either the front of back USB ports (because I have tried both under both OSs) at best I get my windows install to see and start to run auto hardware install. This, of course does not work and the machine will inform me that my new hardware (which it correctly ids as a nook until this point) may not work correctly. And, it does not. It displays as 'removable drive' and clicking on it pulls up an 'insert disk please' message.
In Ubuntu the Nook will show up as B&N Ereader. Both SD cards (the internal and the card in slot) show as the same thing. Clicking on them brings up a message that this drive is not a folder and cannot be opened as such.
This thread leads me to think that there should be a notification in windows about the usb being connected...and as soon as I post this I will be restarting to check that... but I really rather do this under Ubuntu. ETA. This does not work for me. Canceling the install software wizard does not work either. (I have been uninstalling the faulty installs each time and rebooting the comp without the nook attached. Oh, and the Nook IS awake too. )
Searches bring up nothing, and I'm a bit lost.
I must be missing something so basic and simple no one has had this issue but me. I mean, Android is a Linux variant, right? They should be able to talk to one another!??
If your trying to accomplish what I think you are then it doesn't matter what your computers says. Plug your Nook into the PC and open your notifications window. There should be a USB icon on the status bar waiting for your input. Just follow the prompts.
Given you have gone through the process of installing the Android SDK, in Linux, from the terminal you need to change to your target folder to
Code:
~/android-sdk-linux_86/platform-tools
then you need to log in as root and kill, then start the server. make sure to exit root when you are done.
Code:
su : enter password
# ./adb kill-server
# ./adb start-server
# exit
then it should pick it up.
I have the same problem as OP and went crazy trying to figure out what I was doing wrong. It's not as simple as everyone suggests.
To be clear I'm using Linux, Ubuntu Natty. I have a Samsung Vibrant also running CM7 nightlies. Start adb, plug in Vibrant, shows up in adb devices list without any problem. Plug in the NC no device in adb. running lsusb there is no android vendorID for the NC but there is for the Vibrant. The NC only shows a vendorID for the mass storage just like the OP says.
The NC is booting with CM7 nightlie on the SD card, not eMMC. Will that make a difference?
IFLATLINE, Thing is, there is no notification popup on my Nook for me to tap.
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
I did manage to brick the nook trying to update the build last night so I'm in the middle of reflashing it. So, as soon as I finish making a boot micro SD (I know, I should just have one I keep for this but I don't) I will be flashing phiremod's version of CM7 on the nook.
digver, I did find somewhere on here that the OC kernel was causing some people grief and that once they removed it they had no issues connecting the the computer... but I think they were windows. I'm not sure if that will fix this very annoying little problem.
katsrevenge said:
neidlinger, I will be trying that ASAP. I do not have that installed... I'm rather new to Linux.
Click to expand...
Click to collapse
personally i <3 linux. It's the only way to fly esp with dealing with Androids. Android Central has a GREAT write up on how to install the SDK on your Linux unit.
I'll have to look up the link @ home. I'm at work and WebSense blocks 99% of everything.
Does anyone use the micro usb port? I have yet to find a use for it. I can't transfer files with it, charge with it nor are there any peripherals (that I know of) that can use it. I searched around but couldn't find much useful stuff on the port. All I found was this useless video:
**Ok I can't post the video because of more stupid forum rules but just go to youtube.com and append this after the url: /watch?v=1xBVu-IatDQ **
Anyway, if someone has ideas on how this port can be used I'm all ears... Thanks.
dq
It is a file transfer port. you plug a cable into it and into your PCs usb port. works like the ones on your phone.
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
What OS are you using on your computer, and have you installed the drivers for it?
don quixada said:
Does it work for you? Because it doesn't for me. Nothing happens when I plug it into a computer. No automounting on the computer side or indication on the tablet that I can put it into "usb storage mode" like the 2.X Android versions do.
dq
Click to expand...
Click to collapse
Computer OS? i just plugged it into my Win7 system and it was there instantly. 3.0 shows up as a media device, which allows both the tablet and the computer to talk to the sdcard at the same time. So you won't see a mount prompt on the tablet. BTW my Incredible2 is running 2.3 and also lets me access the SD card on it and the computer at the same time.
I'm still using an old tiny xp and it worked fine for me just plugged it in and there it was
I tried Gentoo Linux and XP and neither worked. What drivers do I need to install?
I also have access to a Win7 system so I'll try that.
dq
Drivers from acer website.
I have adb installed should this not be enough?
You need none installed. ADB if its running in some form might be interfering. its just a basic driver in windows it uses.
I only run adb-server when I need it and not all the time. I thought that any needed drivers would have been installed when I installed adb.
For my Gentoo machine what should I do? It's not detected at all if I plug it in. My x10 mini and Nexus One are detected no problem and I can mount them and everything so what's up? Is there a kernel module that I need to build?
Thanks.
dq
I had to download these drivers for my xp netbook ,,
http://global-download.acer.com/GDF...A Tab&Step3=A500&OS=a05&LC=en&BC=Acer&SC=PA_6
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Yes, well I only really use adb in the same capacity as what you describe-- to root a device. After that busybox can be installed and I can either ssh into the device (which I prefer) or use the terminal on the device itself.
But my problem is the detection of the device once it is plugged into my Linux box. I'm not sure if I need a special driver for that and I'd rather not aimlessly search through the kernel config in order to build one (I've done that before and it's painful!). It's good to know that one can mount it on an external device and still use it simultaneously though. That will save me time in trying to fiddle around with settings in the tablet itself...
dq
don quixada said:
I have adb installed should this not be enough?
Click to expand...
Click to collapse
If you are not able to transfer files Try enabling usb debugging before connecting to pc.
If the tab is not in the usb devices list and it doesn't show up as an unknown device, you might want to try another usb cable. Or another port if you have the Windows and Linux on the same machine and you are trying to connect on the same port.
Sent from my A500 using XDA Premium App
gradyzero said:
I agree with Nova 5. The Windows drivers for USB come with the SDK and while you might not think you will have use for the SDK you will. It makes the process of installing custom ROM,s and Recovery Kernels a breeze. You download your zip flashes or recovery images to Win 7 and then you adb push your downloads to the tablet. The alternatives, unless soneone was nice enough to compile you an apk, which most advanced system developers don,t bother with, unless their app is destined for the massees throug Andriod market, is to install a terminal emulator and enter native Unix/Linux shell commands manually. If you aren't a shell cmd expert I suggest you immediatly download the latest Android SDK for Windows and start learning what it can do for you with just 2 or 3 adb push commands which can help you advoid 10's of lines of manually entered Linux shell commands that can do some real damage to your system if you are copying someone elses terminal emulator sh install instructions, don't understand what they do and make 1 simple typing mistake. With adb push you don't even have to get involved in Linux's complicated bit based permission changes to install something at the system level.
Sent from my A500 using xda premium
Click to expand...
Click to collapse
Not nearly what I was saying. Not even close enough that a bomb would touch it.
Simple answer is my vista and win7 systems accessed the iconia as a media player device requiring no drivers as they are a common system driver. My only comment about ADB was that it might be interfering if it somehow was left running in the background.
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
sandiegoan said:
I'm not sure what the problem is, but I had to play around with the settings and plug it in several times and finally it showed up. Now I plug it in and the dialog for auto play shows up instantly. When I choose to view files, I get a window with two drives. One is the internal storage and the other is the sd card.
Click to expand...
Click to collapse
Sometimes mine gets a bit wonky as well. Every now and then, I'll plug it in, get the windows dialogue box asking me what I want to do. I open it up and the box is blank, no drives, nothing. Unplug it, wait a few seconds, pop it back in, and everything is OK. No rhyme or reason, and it doesn't happen all the time.
Quick trick for win7 .
Plug in the device.go into device manager delete its entry and the USB controller it resides on.unplug device.install driver from acer web site.then try the device again.
This works on several USB type issues
Good luck if you don't understand don't try
Yeah, its another 'ADB not working on device xxx' thread.. but this one really has me stumped.
Device in question is a TF101, PC in question runs Windows 7 64-bit.
PC has been used successfully to develop android apps. for a Samsung S Plus, with the entire toolchain working.
Same PC, running VMWare, virtualizing XP (32-bit), has also been used to develop/debug with the TF101.
Now the problem. Natively (without VMWare), I have been completely unsuccessful getting the TF101 to be recognized by ADB.
What has been tried:
- TF101 USB drivers from Asus
- TF201 USB drivers from Asus (which also include the TF101 drivers from the look of the .inf files)
- Hand-edited .inf file from the standard android ADB driver
- Adding the VID (0x0b05) to adb_usb.inf
- Uninstalling (and deleting the driver) for anything related to android devices (Samsung, and Asus)
So what happens is that the device does appear in device manager, with 'USB Debugging' checked on the Android device.
With one of the driver combinations I end up with 'Android Composite ADB Interface' in Device Manager, but for some reason its under a 'Samsung Android Phone' Folder, this may well be part of the problem.
No matter what I try, 'adb kill-devices/adb usb' always shows 'error: device not found'
I am two solid days into this now, after reading just about every TF101/ADB thread that google knows about.
Anyone else experienced this?, and might know how to resolve it?
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
baseballfanz said:
Have you looked at this thread?
http://forum.xda-developers.com/showthread.php?t=1071584
Click to expand...
Click to collapse
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
FWIW, I had the same issue. I installed the USB drivers from Asus and could never seem to get ADB to "see" the TF101.
So I ripped them out and installed the full ASUS desktop PC suite from their website. ADB now sees my TF101 just fine. I uninstalled the suite after I had the connection working and ADB still connects to my TF101 without issue. The Transformer PC suite is on the same download page as the stand alone driver.
If you can't find it, PM me and I'll get back to you with a link.
Col.Kernel said:
He's made it pretty clear that he uses ADB with other Android devices, so I don't think that a guide to installing ADB is going to be particularly helpful to him.
Click to expand...
Click to collapse
I too was using ADB already on my N1 but couldn't make it work with the TF.
After reading and following directions on that thread I got it working.
He might not need instructions to set up ADB from scratch but there's good infos about the Asus PC Suite.
Step 7
Basically same as what you just posted and same as what I did to get it working.
I can confirm that too that installing ASUS SUIT works better than just installing drivers, I don't know why but it does. It's the same with my phone. Sometimes installing usb drivers do not work but when I install Samsung kies then somehow that works better even though it includes the same drivers I am installing as stand alone which do not with properly.
Sent from samsung vibrant
Same thing happened to me had to buy a new cord.... does the computer recognize it at all
Sent from my Transformer TF101 using Tapatalk
im not sure if it would help but everyonce in a while ill have a hard time with my adb connection and ill start up wireless adb and can conect fine from that. i dont know why i think in wireless you use ip address on wifi so it might recognize and connect different.. of course this depends on if you want to use it and is alos hardware dependant mainly wifi.
I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?
xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium
Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.
I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
I did remove the SM Bus Controller from device manager and then re-installed the LG device driver. It did not attempt to reinstall SM Bus drivers, but instead installed MTP drivers successfully. I had high hopes after that, but it's still not working. Sigh.
bgibson72 said:
I'm trying to use LG PC Suite and LG Bridge on a laptop running Windows 7 x64 Pro. I have updated the chipset with the latest driver, but every time I try to install the LG drivers, the SM Bus Controller fails to install. The PC cannot see the device, even though I have switched USB mode to file transfer. I have a Mac as well, and the same thing happens there (not recognizing the device is connected via USB). Is the software just way out of date and not yet compatible with the V20, or is there a fix that needs to happen. I'm perfectly comfortable using the command line/terminal or hacking the registry, if that's what it takes...
Thanks to anyone that can help!
Click to expand...
Click to collapse
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
elijah420 said:
What are you trying to accomplish?
Have you installed minimal adb\fastboot?
Frankly, I don't use Windows or Mac so I am next to no help there.
'Sudo pkg install android-tools-adb android-tools-fastboot' was all I've needed to do.
Is your usb a known good cord? Verify this first. Then, Windows device manager, plug in your phone, watch for something to show on device manager. Click on device, double check there that everything shows as working properly?
If phone is not showing up on a number of computers, make sure USB cable is good.
Click to expand...
Click to collapse
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
bgibson72 said:
I have adb and fastboot both. I want to connect to the PC/Mac for purposes of synching/sharing music, photos, etc. I could use linux too, but I don't have an VM's or a box spun up with anything atm. Yes, the cord I'm using is a good cord. I can see the internal and SD card when I connect, just can't use the LG apps. Oddly enough, there wasn't anything showing with the yellow sign under Device Manager. I'm guessing it's just a compatibility issue and I should just forget about it and just push files to my device with adb. Oh well--I thought it was worth a shot.
Click to expand...
Click to collapse
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
elijah420 said:
I understand now. I don't think I can help you there. I run an owncloud instance, and just back all my hooey up there.. manually tho. Sorry dude.
Click to expand...
Click to collapse
It's cool, thanks anyway. Just trying to simplify things. Don't ask why I thought the OEM's software was gonna solve that, lol.
Well, tbf, even though I don't use it (simply because I dislike vendor lock in - owncloud or a sftp session is mostly hardware agnostic.) I do understand the idea that one should expect the **** that come on the phone to work properly. It *should* be a selling point - 'our apps work for their stated purpose!'