hello everyones,
I'm new to the forum just openned account, I'm looking for a confident tips, help, etc. I heard it's right place.
So, lets start with most importly question for me.
Can anybody tell me how can I connect my ace2 to laptop for data transfer (internal&external memory), sync, back up? I running linux crunchbang x64bit and what I know is that samsung pc suite called kies is not compatibile with linux and linux itself do not really recognize phone after plug in... so my only option is virtualbox with windows on it but it's not the way we should managing our mobiles, are we!
thanks for any tips and coments.
write "lsusb" on terminal and post the output
the lastest kernels (2.6+) must recognize the device. if lsusb doesnt work try it as root
lsusb done
kentone said:
the lastest kernels (2.6+) must recognize the device. if lsusb doesnt work try it as root
Click to expand...
Click to collapse
Sorry for delay
lsusb gives me this:
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0c45:7428 Microdia
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 004: ID 04e8:6860 Samsung Electronics Co., Ltd
Bus 002 Device 003: ID 04f2:b008 Chicony Electronics Co., Ltd USB 2.0 Camera
Bus 002 Device 002: ID 174c:55aa ASMedia Technology Inc.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
and my phone is already connected, same as external HDD and logitech speakers. oh, and wireless dongle for mouse, that's it.
On phone display, there is an usb connection symbol but still cannot see'em on my lap...
For the storage try that enable usb storage for the contacts go to Contacts>Click the option button>More>Import/Export>Export to SD and for the messages try that "SMS Backup & Restore"
I think there is nothing like kies for linux, but this can be a solution
To go faster to USB Utilities try with an app called anycut, longpress on the main screen and select add a shortcut>anycut and search for USB utilities
Sry about my bad english
VirtualBox?
kentone said:
For the storage try that enable usb storage for the contacts go to Contacts>Click the option button>More>Import/Export>Export to SD and for the messages try that "SMS Backup & Restore"
I think there is nothing like kies for linux, but this can be a solution
To go faster to USB Utilities try with an app called anycut, longpress on the main screen and select add a shortcut>anycut and search for USB utilities
Sry about my bad english
Click to expand...
Click to collapse
Maybe Installing win7 on virtualbox will be better option for backup, update sync through kies. If U properly configure virtalbox to use USB and share folders it might be faster and safer, what you think mate?
can be an option, but... only if you dont have any problem configuring and installing the SO on virtualbox, and you have the time needed for configure all, my options are faster
Galaxy Ace II connects automatically in Ubuntu 12.04 or 12.10 - you can use it to access the internal storage and sd card.
I have contacts and calendar synchronized with my google account.
A good backup tool which can handle also sms history, call log, contacts etc... is My Backup (from rerware, I cannot post external links...) - you can back up to a file on SD card or upload the backup to their server.
Btw, Dropbox is also good for uploading your photos automatically.
AirDroid may be a solution, besides USB mass storage.
wanakutia said:
hello everyones,
I'm new to the forum just openned account, I'm looking for a confident tips, help, etc. I heard it's right place.
So, lets start with most importly question for me.
Can anybody tell me how can I connect my ace2 to laptop for data transfer (internal&external memory), sync, back up? I running linux crunchbang x64bit and what I know is that samsung pc suite called kies is not compatibile with linux and linux itself do not really recognize phone after plug in... so my only option is virtualbox with windows on it but it's not the way we should managing our mobiles, are we!
thanks for any tips and coments.
Click to expand...
Click to collapse
You might want to take a look at Heimdall, which can replace Odin for a lot of things (mostly flashing), and is running on Linux and OSX as well:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
See also this thread for more details, which features an overall description including video tutorial on Heimdall.
As you didn't mention flashing, but data transfer: I found the Ace 2 a bit strange in selecting its connection mode. By default, it connects using MTP, which would require special packages to be installed on your Linux PC to be useful. However, if you go to Settings -> Wireless & Network -> USB Connection and activate USB Mass Storage prior to connecting your USB cable, the Ace 2 will show up on your computer like any external USB drive (or stick). Unfortunately, the device seems not to remember this for subsequent connections (and I found no way yet to make this the default -- hints are welcome!).
With my other devices, I love to use QtADB (together with a minimal ADB package: you don't need the complete SDK for this, on Linux the "adb" and, optionally, "aapt" binaries should be sufficient). While this works fine with my other devices, on the Ace 2 it unfortunately simply crashes. But you still could use the command line to explore your device: "adb shell" gives you a shell on it, using "adb push" and "adb pull" you can transfer files. And do a couple more things.
Related
Hi,
I have a European SGS for a couple of day's now. I have flashed it with JG5 and mimocans lagfix. I have done this with a WinXP virtualbox on an Ubuntu desktop. This worked perfectly. But what I like to do is to work with ADB straight from my Linux box. The problem is that it won't detect my SGS (I have the 'USB Debugging' option on off-course).
When I type prompt> adb devices , my device won't show up. In the WinXP virtualbox it does show up. Can anybody help me on this one?
Kind Regards,
D.
You have to:
sudo adb start-server
adb devices #It works!
adb shell #Or whatever you want.
Hi,
Just tried that but still not working for me? Any other ideas?
Regards,
D.
I didn't have a problem under FC12.
I note you said you were using VirtualBox - you aren't doing something stupid like forwarding the USB port through to Virtual Box so it's not accessible to the base OS?
Cheers
Simon
No my Virtualbox is not running at the moment, so the USB port is not forwarded to the Virtualbox. I'm able to mount the device and copy files to it etc. But ADB doesn't recognize it. With my HTC Hero it worked perfectly. :-(
denvro said:
No my Virtualbox is not running at the moment, so the USB port is not forwarded to the Virtualbox. I'm able to mount the device and copy files to it etc. But ADB doesn't recognize it. With my HTC Hero it worked perfectly. :-(
Click to expand...
Click to collapse
You need to enable debug mode.
lenrek said:
You need to enable debug mode.
Click to expand...
Click to collapse
But if he can see it in XP, when it's started, maybe it's already enabled.
Run a
'lsusb' in the command line, is Samsung device there?
japanfred said:
But if he can see it in XP, when it's started, maybe it's already enabled.
Run a
'lsusb' in the command line, is Samsung device there?
Click to expand...
Click to collapse
Hmm... Maybe he should just disable/delete the USB device from the virtual box. Maybe the service has reserve the device even when the guest is not started?
lenrek said:
You need to enable debug mode.
Click to expand...
Click to collapse
When you've read my initial post you could have read that USB debugging is already enabled.
japanfred said:
Run a 'lsusb' in the command line, is Samsung device there?
Click to expand...
Click to collapse
This is the output of 'lsusb' when the device is connected:
Bus 001 Device 016: ID 04e8:681c Samsung Electronics Co., Ltd
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 002: ID 04a9:172b Canon, Inc. MP140 ser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The Samsung device is showing up.
denvro said:
When you've read my initial post you could have read that USB debugging is already enabled.
This is the output of 'lsusb' when the device is connected:
Bus 001 Device 016: ID 04e8:681c Samsung Electronics Co., Ltd
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Hi-Speed 21-in-1 Flash Card Reader/Writer (Internal/External)
Bus 001 Device 002: ID 04a9:172b Canon, Inc. MP140 ser
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
The Samsung device is showing up.
Click to expand...
Click to collapse
Maybe you want to try disable USB in your virtualbox setting.
Deleted USB settings in Virtualbox, disabled USB in all my Virtual machines but no luck. My device still doesn't show up in ADB.
Hope somebody else has some tips?
Problem Solved
I solved the problem by updating to the latest Android SDK. Thanks for helping everyone.
i have always had to sudo gedit etc/udev/rules.d/51.android.rules and individually add my device by USB code (ie. SUBSYSTEM=="usb", ATTRS{idVendor}=="04e8", ATTRS{idProduct}=="681c", MODE="0666" or similar)to get it to work
hi together,
at first, sorry for my bad english, ...i'm from germany.
some time, i was owner of a rooted and flashed KF which worked fine. 6 days before, i installed google play and the keyboard was offline. i went back in twrp 2.2.2.1 and make a wipe and forgot, that i need the software to flash it again. i'm an idiot, i know.
now, i only have twrp in recovery and don't know what to do. i'm not confirm with linux/ubuntu and the handling of soupkit.
facts i have at the moment:
- a KF with twrp 2.2.2.1
- my 2nd pc with a brandnew ubuntu 12.10
- information, that my KF was found on usb in bootloop and twrp, see below:
[email protected]:~$ lsusb
Bus 001 Device 006: ID 18d1:d002 Google Inc.
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb
Bus 001 Device 009: ID 1949:0006 Lab126
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$
"Google Inc" and "Lab126" ist the same. google in bootloop and lab126 in recovery mode.
can anybody help me with ubuntu and soupkit, that i can transfer a flashfile to my KF ?
with best regards, stefan
PROBLEM SOLVED - THX
Does your computer recognize the kf? If it does, then why not transfer a rom to it & flash it in twrp?
BrooklynNY said:
Does your computer recognize the kf? If it does, then why not transfer a rom to it & flash it in twrp?
Click to expand...
Click to collapse
thanks a lot :angel:
five minutes before, i found a threadto do just this :good:
at the moment ii try it and i hop it works with aliendroid v8, ....now i will see if this rom has german language.
and a question: whats in your opinion the best rom for a KF ?
das_es said:
hi together,
at first, sorry for my bad english, ...i'm from germany.
some time, i was owner of a rooted and flashed KF which worked fine. 6 days before, i installed google play and the keyboard was offline. i went back in twrp 2.2.2.1 and make a wipe and forgot, that i need the software to flash it again. i'm an idiot, i know.
now, i only have twrp in recovery and don't know what to do. i'm not confirm with linux/ubuntu and the handling of soupkit.
facts i have at the moment:
- a KF with twrp 2.2.2.1
- my 2nd pc with a brandnew ubuntu 12.10
- information, that my KF was found on usb in bootloop and twrp, see below:
[email protected]:~$ lsusb
Bus 001 Device 006: ID 18d1:d002 Google Inc.
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$ lsusb
Bus 001 Device 009: ID 1949:0006 Lab126
Bus 001 Device 002: ID 0bda:8187 Realtek Semiconductor Corp. RTL8187 Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
[email protected]:~$
"Google Inc" and "Lab126" ist the same. google in bootloop and lab126 in recovery mode.
can anybody help me with ubuntu and soupkit, that i can transfer a flashfile to my KF ?
with best regards, stefan
Click to expand...
Click to collapse
Actually, your problem may be easier to fix than you think.
1) Download a ROM of your choosing to your computer (for stock, choose MoDaCo).
2) Boot the device into recovery (use SoupKit if you need to) and select the "Mount" function.
3) Make sure there is an [X] next to Mount SDcard (you should actually see "[X] Unmount SDcard" when it's selected)
4) In Linux, you should get a prompt asking what you want to do with the mounted volume. Select "view folder" or something similar. Or you could open your file manager and look for it under devices.
5) Transfer the ROM to your sdcard.
6) Wipe system, factory reset then install the ROM.
only TWRP on my KF - PROBLEM SOLVED
thx to all, it was easier to solve this problem as i thought.
i'm really happy now
my wife is happy too. now it's her's and i can by an galaxy note 10.1
First of all, I've spent many, many hours reading everything and trying everything I could find so sincere apologies if I have missed the solution to my problem.
So I have a Kindle Fire which I got months ago and have never been able to make work. It appears to have been almost completely wiped. It can do two things as of now:
1. Be stuck in a bootloop: displays FireFireFire logo, restarts, rinse, repeat.
2. Get into TWRP
Regardless of which of these states the device is in, neither my Windows PC (which has drivers, SDK, tools etc installed) OR my Ubuntu machine (on which I used SoupKit to install the necessaries) can see the device. It doesn't show in Device Manager in Windows and neither fastboot nor adb show any entries for the device when I run them on EITHER platform and in either of the states I can get the device into.
Any input from people more experienced than me would be appreciated. I got a factory cable in the post today so if that will help I have that option available to go. Oh and finally solutions using my Ubuntu machine rather than the Windows one would be strongly preferred although I can do either if I have to.
Boot into TWRP and see if your device shows up under 'lsusb'
...if it does, then use TWRP to "reboot bootloader" and check 'lsusb' again.
Thanks for the quick reply, and sorry for my slow reply back
The device isn't showing when I run lsusb - I assume you would have mentioned if it was not going to obviously be the KF. Anyway just in case, here is the output:
Bus 001 Device 003: ID 0ac8:c33e Z-Star Microelectronics Corp.
Bus 003 Device 002: ID 04f3:0234 Elan Microelectronics Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Anybody got any insight as to what I should do next?
kindlesean said:
Anybody got any insight as to what I should do next?
Click to expand...
Click to collapse
Is it safe to assume you don't have a factory cable?
Also, does the usb cable you're using seated tightly or is it kind of loose?
If it's loose, try this...
Enter the following command in the terminal (Linux) and try to finagle the USB to see if it is a bad connection:
Code:
while true; do lsusb | grep 'Lab126'; done
If you have a bad connection, due to the cable or USB connector, as soon as a good connection is made you will see it output to the terminal. Just remember to ctrl+c to end the loop when you're done with it.
some inforeff
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.
kindlesean said:
Hey Thanks for the very quick reply!
I actually do have a factory cable, I bought one this week So if the factory cable is likely to be the easiest way to fix things then I have it ready.
I used multiple different USB cables on the two different machines. Should I still try the thing you mentioned or is there something else I should proceed with using the factory cable?
Thanks for the help Soup.
Click to expand...
Click to collapse
Before I switched to the black USB cables from Amazon for their quick chargers, my device would do sort of the same thing. I had to pull up or push down on the connection before it would detect. If you have a factory cable made by Skorpn try that one to see if a connection is made. IIRC, Skorpn's factory cables fit very tightly so it might make a difference. Either way, try what I suggested earlier to rule out any hardware based issues with the USB.
I just tried what you suggested with both two different regular USB to Micro USB cables and also with my factory cable. In all cases there was no output in the terminal. I tried it both from TWRP and from the FFF logo screen (which no longer bootloops btw, it seems to just be hanging at the FFF logo now if I don't press power to get into TWRP).
Thanks again
Anyone able to help further? Situation is still the same as in my last post.
kindlesean said:
Anyone able to help further? Situation is still the same as in my last post.
Click to expand...
Click to collapse
You can try to usbboot, but it would require opening your device.
soupmagnet said:
You can try to usbboot, but it would require opening your device.
Click to expand...
Click to collapse
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?
kindlesean said:
Thanks for the response.
I can open the device if necessary, right now I have a very expensive paperweight so it's not as if I have anything to lose
I assume that there are guides available for the whole procedure i.e. from opening up the device to doing the usbboot?
Click to expand...
Click to collapse
Check the Firekit thread in the Dev section
soupmagnet said:
Check the Firekit thread in the Dev section
Click to expand...
Click to collapse
Will do, thanks again Soup!
Hello,
I've been looking into rooting my phone and I have ran into a problem.
I've downloaded everything. adb the files to root my phone etc. But im stuck on trying to find my device
(running kali linux )
i enter the command to locate it in terminal but nothing shows up:
[email protected]:~# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~# adb devices
List of devices attached
<----- (is just blank)
ive tried running [lsusb] and it doesnt show up either:
[email protected]:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:d213 Suyin Corp.
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
it seems like my machine doesnt even say its there. Debugging has been checked off, ive changed the usb input or what ever from charge only to mtp to ptp and none of those work either.
first time posting ever on the form since ive spent three days trying to trouble shoot this but yet to come up with something. please help so i can run my phone as root lol!
nieev said:
Hello,
I've been looking into rooting my phone and I have ran into a problem.
I've downloaded everything. adb the files to root my phone etc. But im stuck on trying to find my device
(running kali linux )
i enter the command to locate it in terminal but nothing shows up:
[email protected]:~# adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[email protected]:~# adb devices
List of devices attached
<----- (is just blank)
ive tried running [lsusb] and it doesnt show up either:
[email protected]:~# lsusb
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 004: ID 064e:d213 Suyin Corp.
Bus 001 Device 003: ID 04ca:3005 Lite-On Technology Corp.
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
it seems like my machine doesnt even say its there. Debugging has been checked off, ive changed the usb input or what ever from charge only to mtp to ptp and none of those work either.
first time posting ever on the form since ive spent three days trying to trouble shoot this but yet to come up with something. please help so i can run my phone as root lol!
Click to expand...
Click to collapse
EDIT: I hit enter WAY too quick lol
Do you have the proper USB drivers set up?
Check out this link. It probably has the instructions you need, even though it is for Ubuntu.
EDIT#2: I haven't used Linux in forever, but someone I was just talking to said "shouldn't it be sudo adb devices? I think he was right.
Seems like you have a lot of devices, and possibly a USB hub? Make sure you haven't connected through a hub, which can cause issues.
You're booted into OS when trying to issue adb command (which is required) or alternately custom recovery? Some folks mistakenly believe they can connect adb with phone in bootloader (only fastboot works in bootloader - and it has to be in fastboot mode).
woo hoo stupid fix
I figured it out. Anyone who has this same issue as me sometimes switching usb cords works thanks guys
hi, I just installed the beta build of the AOSP Oreo Rom and soon after finding working-ish gapps twrp was gone, and I hadn't had a chance to root yet, and so i went to my computer to manually flash recovery but my device refuses to get recongized, i have installed latest google and universal drivers, but they dont show up for me to set them to my nexus. Im running Latest win10 on my desktop, using a known good usb cable and have switched between the only usb 2.0 ports i have (2) i've tried in normal boot state and in fastboot, but the drivers wont match up to proceed. does anyone know anything about this, is this an issue with win10 or is it something else?
Do assuming that no one has encountered this before I guess I'll just wait until a app that can root comes out for Oreo and hopefully that can get me fixed up but if in the meantime someone comes across this and actually has some insight any help would be very much appreciated.
deathblade said:
someone comes across this and actually has some insight any help would be very much appreciated.
Click to expand...
Click to collapse
Since fastboot does not work then do the following:
win10 may be broken, check for flo ID = 18D1:4EE0 using alternative OS - if it still does not work then...
repair broken N7 USB port or re-seat the wide silver cable to fix USB data lines
:good:
Thank for your suggestion, I'm downloading the iso right now, will post back after following instructions, hope this works
ok, just followed your instructions, and this is what i got
[email protected] ~ $ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 13fe:5500 Kingston Technology Company Inc.
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 004: ID 04f2:b40e Chicony Electronics Co., Ltd HP Truevision HD camera
Bus 002 Device 003: ID 1a40:0101 Terminus Technology Inc. Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[email protected] ~ $
I dont see the ID you are referring to
Also I reseated the cables with no change and visually inspected the port and solder joints and all seem ok, here are a few pics ( I apologise about any quality issues, I'm not a photographer) EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive, is there anyway to use an otg flash drive to force auto install a custom recovery?
deathblade said:
EDIT: so I verified the data connection works just fine, was able to view contents on an otg flash drive
Click to expand...
Click to collapse
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.
Had a comparable issue recently due to win10 preferring some default driver over Google driver for fastboot.
k23m said:
I see that your laptop has both USB2 and USB3 ports. Please boot N7 in fastboot mode, connect it to USB2 then USB3 while checking lsusb for the ID. Note that the ports use different PC hardware and drivers and one of them appear to be either unsupported or faulty.
Also "a known good usb cable" may be good for charging but not for data transfer so just try another one.
Click to expand...
Click to collapse
Ok just tried with usb 2 and 3.0 ports same result, but oddly the listing does differ from my previous, it is now show an Intel device (I assume my CPU or a chipset) that wasn't listed before. But still no Nexus. Will try with a different cables later today as I have to hunt one down (just moved)
ok, so i just found another cable (with builtin otg usb port ) and even in windows 10 it worked just fine, thank you so much for your help. the cable i was using before was an anker gold tipped nylon braided 10ft usb cable, my guess is that at 10ft it has too much resistance to actually work properly for such data based tasks. I will at some point get another (smaller) anker cable to test this theory