I have found a way to connect any modem to the tablet even if the tablet does not recognizes it. your device must be ROOTED to do so. I am not a developer, i just found out somewhere and modified the instructions to make it easy. i am not responsible to any thing that happens to your device (however this method isn't risky at all).
Just follow the instructions and enjoy. First download the attachment...
. First you need to move the modem to "modem only" for this you will need a terminal, you can use Hyper Terminal on windows.
Google search for AT commands for your modem to make it modem only mode and how to do that.
All right .... transferred the modem to the modem-only mode ....
Then note the vid and pid of your modem. one way to do this is to connect the modem to computer then go to device manager, expand modems, right click your modem >properties>details.
2. Next we need ES File Explorer
Install it on your tablet ... Open, go to settings -> Root rights, and tick all checkboxes.
3. Then go to /system/bin/preinstall.sh on your tablet and add a line to the file using es file explorer echo "19d2 1176" > /sys/bus/usb-serial/drivers/option1/new_id (see my preinstall.sh in the archive).
here 19d2 is my modem (vodafone K3370-z) vid and 1176 the pid. replace the vid and pid with your own.
REEBOT YOUR TABLET
4.There is a folder peers in the archive you downloaded. open conf-chat in the folder with es file explorer and replace your apn here with the apn of your service provider .
When the tablet does not recognize the modem it will not generate ttyUSB files which are needed to communicate with the modem. In Step 3 you made the tablet to recognize the modem and it now generates the ttyUSB files. You can check that in Terminal emulator(download from play store) by typing "dmesg" command(without qoutes). scroll the output down, you will see the generated ttyUSB ports as given in attached screenshot Pic1. It also gives the number of ports genetated. If you see these lines you can Connect your modem to Internet. But wait a minute you have additional things to do in order to get connected.
Now you need to find which port is pppd port because we need it to insert in the file Conf-pppd in peers folder of the archive you downloaded. (open the conf-pppd using wordpad you would see ttyUSB1 on the top because pppd port of my modem is 1, those modems who has pppd port at 1 would be able to connect without any modifications, if the pppd port of your modem is not 1 you would have to edit it e.g if the pppd port of your modem is 2, the top line in conf-pppd would look like ttyUSB2 and so on)
To determine which is pppd port follow the below steps...(see the attached screenshots)
Open 2 windows in terminal emulator. (you can copy paste the commands in terminal emulator)
(1) In first window type busybox tr -s "\n" < /dev/ttyUSBx (Pic2)
where x is the first port generated by your modem.(this command opens the port)
(2) Now in window 2 type echo -e "ATi\r" > /dev/ttyUSBx (pic3)
Here x is the same you typed in window 1.
You would see OK in WINDOW 1(Not in window 2). IF YOU DONT SEE ANY OUTPUT IN WINDOW 1(pic4), YOU HAVE TO UNPLUG YOUR MODEM AND PLUG IT AGAIN AND THEN USE NEXT PORT. yOU HAVE TO DO THIS EVERY TIME YOU DONT SEE ANY OUTPUT. IF YOU DO SEE AN OUTPUT PROCEED TO NEXT STEP.(pic 5, 6, and 7)
(3) Again type echo -e "AT+CGDCONT=1,\"IP\",\"www\"\r" > /dev/ttyUSBx in window 2. (Pic8)
Here replace www with your apn
You will see the OK again in window 1.(pic9)
(4) Again type echo -e "ATDT*99#\r" > /dev/ttyUSBx in WINDOW 2(pic10)
You will See the output in window 1. if you see ERROR in window 1, then it is your AT port not PPPD port. Unplug your modem and try next port untill you get CONNECT message in window 1(pic11). If you get Connect Message the at any port then it is your pppd port. IF you get these messages at port 2, then replace 1 in ttyUSB with 2, ehich then reads ttyUSB2 at the top of conf-pppd file.
Now copy the folder Peers in /etc/ppp/ in your sd card.
Install the application GScript_Mod.apk lies just in the archive .... open it and add the two scripts in the folder gscript of your sdcard : inet-ON.sh (Which brings up connection) and inet-OFF.sh (which disables the connection)
5. REBOOT TABLET. insert the modem. Start the application Gscript and run inet-ON.sh(pic12)
If you do everything on the instructions, your modem will connect to the Internet, although you will not see the 3G connection on the tablet...(pic13)
Thanks for reading..
Great Work..
A person who never made a mistake never tried anything new.
- Albert Einstein
Dear Bhaskar1109,
Kindly tell me how to use Hyper Terminal and make it a modem only mode. I have Micromax 310G modem with aircel connection and Micromax Funbook Infinity P275. I am unable to connect my modem as it says damaged sd card.
Thank You for your wonderful guide.
Micromax 310G..
manb7 said:
Dear Bhaskar1109,
Kindly tell me how to use Hyper Terminal and make it a modem only mode. I have Micromax 310G modem with aircel connection and Micromax Funbook Infinity P275. I am unable to connect my modem as it says damaged sd card.
Thank You for your wonderful guide.
Click to expand...
Click to collapse
Select COM port in HyperTerminal and try AT Commands.. i know AT commands to disable Emulated CDROM for few modems. Try it otherwise google commands for your modem
Huawei AT^U2DIAG=x command to control emulated CD-ROM and Micro-SD card
values of <x>:
0: disable CD-ROM and Micro-SD
1: enable CD-ROM only
255: enable CD-ROM and Micro-SD
256: enable Micro-SD only
ZTE AT+ZCDRUN=x command to control emulated CD-ROM and Micro-SD card
values of <x>:
8: disable autorun (modem appears when plugged in)
9: enable autorun (only CD-ROM appears when plugged in)
E: enable download mode (CD-ROM does not appear when plugged in)
F: disable download mode (CD-ROM appears when plugged in)
ZTE(ICERA chipsets) AT%USBMODEM?: to check the actual state
AT%USBMODEM=x command to control emulated CD-ROM and Micro-SD card
values of <x>
0: modem only mode
1: modem + CD-ROM + microSD
Great work.Usefull
Instructions added...
oops, i forgot some vital instructions earlier which i have added in bold letters now. Please view those if you were not able to connect to internet earlier and give your experiences.
great work, now i can connect any dongle to my tab. took some time though to make the dongle to modem only mode.
thanks.
Hi there,
I have checked the presence of ttyUSB into the /dev, but when I run the inet-ON I get.
Waiting ttyUSB1
Starting pppd
stderr: pppd: in file /etc/ppp/peers/conf-pppd unrecognized option TIMEOUT
Connecting....
Can anybody help me on this issue?
Thanks.
siraci said:
Hi there,
I have checked the presence of ttyUSB into the /dev, but when I run the inet-ON I get.
Waiting ttyUSB1
Starting pppd
stderr: pppd: in file /etc/ppp/peers/conf-pppd unrecognized option TIMEOUT
Connecting....
Can anybody help me on this issue?
Thanks.
Click to expand...
Click to collapse
which sim r u using? and what are the settings for the connection? these problems arise due to incorrect settings. check pm
Hi Bhaskar1109,
thanks for your reply. As you suggested, I have check all installation and I found the mistake, using the adb command I pushed the conf-pppd file but with the conf-chat's file contents .
So now "almost" it works fine. Almost because I have to give manually from adb shell or terninal:
echo "1ee8 0014" > /sys/bus/usb-serial/drivers/option1/new_id
in order to create the USBtty
and when the connection is on
setprop net.dns1 208.67.222.222
to set the dns server, because when I run the inet-ON.sh i get the error:
stderr: usage: setprop <key> <value>
This time I have checked the preinstall.sh and inet-ON.sh contents and permissions.
Any clues?
siraci said:
Hi Bhaskar1109,
thanks for your reply. As you suggested, I have check all installation and I found the mistake, using the adb command I pushed the conf-pppd file but with the conf-chat's file contents .
So now "almost" it works fine. Almost because I have to give manually from adb shell or terninal:
echo "1ee8 0014" > /sys/bus/usb-serial/drivers/option1/new_id
in order to create the USBtty
and when the connection is on
setprop net.dns1 208.67.222.222
to set the dns server, because when I run the inet-ON.sh i get the error:
stderr: usage: setprop <key> <value>
This time I have checked the preinstall.sh and inet-ON.sh contents and permissions.
Any clues?
Click to expand...
Click to collapse
Maybe that you have done some typing mistakes like extra spaces etc. and have you restarted your tablet?. you can set dns in inet-on.sh file. Are you able to browse internet normally after these commands?
p.s Google play and internal download manager may not work. You can browse play market but cannot install any apps(probably). UC browser download manager works fine. Use 1 mobile market instead of google play.
I have done other tests and now the only small issue is that I have to run the
echo "1ee8 0014" > /sys/bus/usb-serial/drivers/option1/new_id
into a separate sh file because seems that doesn't work into preinstall.sh file.
Anyway all works fine and let me say that you have done a great and clever job.
Thanks
it s cool
Hello Bhaskar1109,
I have the tablet N101 by Yuandao and I was successfully using PPPwidget with a Huawei E173 stick for 3G browsing.
Recently it stopped connecting, so after searching new alternatives, I found your very useful topic. I would appreciate your help, since I am trying now to find a way to make it work with your way.
I started using your guide, but I cant pass Step 4 with the terminal emulators.
First of all in Terminal Emulator, when I run dmesg command I get "converter now disconnected from ttyUSB0" and I get this for all USB (0,1,2)
Then when I run busybox tr -s "\n" < /dev/ttyUSBx ( I tried with USB0 till USB2), I am getting a message "cannot open /dev/ttyUSB0 (0,1,2)"
Any help?
RASTAVIPER said:
Hello Bhaskar1109,
I have the tablet N101 by Yuandao and I was successfully using PPPwidget with a Huawei E173 stick for 3G browsing.
Recently it stopped connecting, so after searching new alternatives, I found your very useful topic. I would appreciate your help, since I am trying now to find a way to make it work with your way.
I started using your guide, but I cant pass Step 4 with the terminal emulators.
First of all in Terminal Emulator, when I run dmesg command I get "converter now disconnected from ttyUSB0" and I get this for all USB (0,1,2)
Then when I run busybox tr -s "\n" < /dev/ttyUSBx ( I tried with USB0 till USB2), I am getting a message "cannot open /dev/ttyUSB0 (0,1,2)"
Any help?
Click to expand...
Click to collapse
the ports will be available only when the tab recognizes it as a modem. Following questions might help-
Is your tab Rooted?
Is your modem OK?
Is you modem vid pid correct?
Have You followed step 3 Correctly?Can You see the new line in preinstall.sh?
Have you restarted the tab?
Have You given su permissions to the scripts?
Bhaskar1109 said:
the ports will be available only when the tab recognizes it as a modem. Following questions might help-
Is your tab Rooted?
Is your modem OK?
Is you modem vid pid correct?
Have You followed step 3 Correctly?Can You see the new line in preinstall.sh?
Have you restarted the tab?
Have You given su permissions to the scripts?
Click to expand...
Click to collapse
Since I mentioned before that this dongle was working right for some time with PPP widget, I think most of your questions are already covered.
From your experience, could the Otg cable have started to fail and create these problems that never had before?
The command dmesg is showing that first these ports are available and after they are not.
Also, I think its important that I get this ""cannot open /dev/ttyUSB0 (0,1,2). No such file or directory"
Unleashed by my rooted Nexus 4
Gscript is not working .and from step 4 my confusion starts.
RASTAVIPER said:
Since I mentioned before that this dongle was working right for some time with PPP widget, I think most of your questions are already covered.
From your experience, could the Otg cable have started to fail and create these problems that never had before?
The command dmesg is showing that first these ports are available and after they are not.
Also, I think its important that I get this ""cannot open /dev/ttyUSB0 (0,1,2). No such file or directory"
Unleashed by my rooted Nexus 4
Click to expand...
Click to collapse
Sorry i didnt notice the ppp widget thing.
It may be otg problem, otherwise why would ppp widget failed suddenly at the first place. i suggest u to replace the cable and try again.
Devarishi said:
Gscript is not working .and from step 4 my confusion starts.
Click to expand...
Click to collapse
Can you tell what exactly is the problem/error with Gscript?
Error i faced...
I installed Gscript apk from your download link from your thread. I put that two script under sdcard/"another folder"/gscript. I opened gscript application and it says "process.android.com(alike this) stop working". What happened to my tablet. Im using micromax funbook p300. Is there is any way or the other to let it work ?
Related
The xoom can mount just fine on Linux but it is an MTP not a Mass Storage device.
Disclaimer: I am not responsible for any damage to your device, computer, relationship, etc.... The following is meant as a guideline and worked for me but as always use your head.
I did this on my Kubuntu Maverick laptop, but it should apply to most *buntus plus debian. Other flavors should be similar, post a request and I will help if I can. I am familiar with Suse and RHEL/Centos as well but beyond those it will be guess work.
The first thing I would recommend doing is making the device read/write to normal users.
Code:
sudo touch /etc/udev/rules.d/51-android.rules
echo "SUBSYSTEM==\"usb\", SYSFS{idVendor}==\"22b8\", MODE=\"0666\"" |sudo tee -a /etc/udev/rules.d/51-android.rules
sudo /etc/init.d/udev restart
NOTE: This also "fixes" adb so it is useable with the xoom as a normal user. If that is all you want you can stop here.
NOTE 2: You could also set an OWNER rather than changing MODE but I chose the most common route for this example/
Now install either mtp-tools or mtpfs for mounting using FUSE. Since I went the fuse route that is what I will conver here. (I installed the mtp-tools package but beyond using it to debug getting mtpfs to work I have never used it before.)
Assuming you already have fuse configured, for (k|x)ubuntu or debian :
Code:
sudo apt-get install mtpfs
If you do not have fuse already configured then do that first. Look it up online if you have any questions. If you get stuck I will try and help but this post is not about how to configure FUSE.
After that it is simple. Plugin your xoom and from the command line type:
Code:
mtpfs mountpoint
and to dismount it
Code:
fusermount -u mountpoint
so in my case I mount it in a subdirectory under home called xoom
Code:
mtpfs /home/janetpanic/xoom
fusermount -u /home/janetpanic/xoom
I have confirmed moving files to and from the actual directories but not from the meta "playlists" directory. I hope that helps...
EDIT: Fixed Typo... had "(idVendor)" instead of the correct "{idVendor}"
Thanks for sharing your workaround. Unfortunately, it's no joy here. After following the procedure described, the terminal returned no error, but on trying to open the Xoom directory via Nautilus, I received the following message:
Code:
Error: Error stating file '/home/sog/Xoom': Transport endpoint is not connected
Please select another viewer and try again.
Unmounting proceeds without error.
Distribution: Ubuntu Lucid x64
Did you connect your xoom before or after you mounted? The most likely problem is the undeveloped configuration .
Change the line in 51-android.rules to
Code:
SUBSYSTEM=="usb", SYSFS{idVendor}=="22b8", SYMLINK+="libmtp-%k", MODE="0666"
[\code]
Restart udev and then do a "ls -lah /dev/libmtp*" with the device attached and list the output. I need to figure out if the problem is the udev rule or elsewhere.
If the ls does not show any files then send the result of "lsusb |grep Motorola" which better list a line or there is something weird going on.
Sent from my Xoom using XDA App
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Wait, you aren't able to get the Xoom to mount as a mass storage device?
ed. The leaked Xoom manual suggests it support mass storage. Phew. You were scaring me there a bit.
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
sogrady said:
as far as I know, it's been confirmed that the current stack does not support mass storage, only mtp.
Click to expand...
Click to collapse
Which stack, Linux or Honeycomb's? Where is it confirmed?
Non-working mass storage is a potential deal breaker.
honeycomb's. see here or here for details.
Thanks for the links.
This is a real WTF.
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
Relevant code snippet for those interested:
Code:
StorageManager s = (StorageManager)getSystemService(Context.STORAGE_SERVICE);
Class c = s.getClass();
Method m = null;
try
{
m = c.getMethod("enableUsbMassStorage", (Class[]) null);
m.invoke(s);
}
catch(Exception e)
{
// TODO Auto-generated catch block
e.printStackTrace();
}
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
ydaraishy said:
Can someone try running this attached apk to see if it enables mass storage? (It just runs enable, it won't run disable, so I don't know what will happen, it might cause apps to crash but rebooting should fix it, standard disclaimers apply, you run this at your own risk, etc., etc., etc.)
I don't have a Xoom, otherwise I'd try this myself.
There may even be an easier way to achieve this -- I can't verify for myself because Honeycomb isn't in AOSP -- it doesn't work in the sim, but it might on a device: run adb shell, then run "am start -n com.android.systemui/.usb.UsbStorageActivity".
Click to expand...
Click to collapse
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
sogrady said:
Updated 51-android.rules as directed, then:
[email protected]:~$ ls -lah /dev/libmtp*
lrwxrwxrwx 1 root root 15 2011-02-27 19:59 /dev/libmtp-1-4 -> bus/usb/001/004
[email protected]:~$ lsusb | grep Motorola
Bus 001 Device 004: ID 22b8:70a8 Motorola PCS
Click to expand...
Click to collapse
Well that is interesting . You have read write privileges on the xoom. Sounds like it is a fuse configuration issue. Do you have any other fuse file systems you run?
Sent from my Xoom using XDA App
bigrushdog said:
I ran the activity manager command and it brought up the usb mass storage screen but did not mount on computer. Also ran the apk but did not mount. Awesome job though. keep fighting the good fight
Click to expand...
Click to collapse
Damn it. Looks like I actually need a device to get it working, and the AOSP drop. It's so moronic why they disabled mass storage.
Hmm. Can someone run, from adb shell, the output from "mount", and "ls /sys/devices/platform" for me?
Never mind. Mass storage has been defined out of the stingray (Xoom) kernel. It's not even in the default kernel.
To get mass storage support, be prepared to build your own kernel and reflash the device (once that's done, the am command above or the enabler app will work properly).
I've founded a working(ish) solution. This Xoom forum post details an approach that permits transfer of video/music/etc to the Xoom via Linux.
Couple of caveats:
1. The gnomad2 application is very unstable. Crashes frequently.
2. It appears to be write-only: I have not been able to delete files from the Xoom using this interface.
Thanks for the instructions to connect to a xoom tablet via Linux! However, I'm using Opensuse 11.3 and 11.4 on two different systems. I did install the mtp-tools with no issues, however, there is NO file by the name of mtpfs. A search on the net does not reveal it either. Where do I get this, or what package is it part of? Thanks again. If I can't get this tablet to connect to my linux box, I will have to take it back, since I do NOT use winbloze or Mac. Pretty short sited of Motorola IMHO.
Personally, I've given up on MTP + Linux Combo. I just use a straigt FTP transfer over wifi ( FTP Server on tablet ). It's about the same speeds.
any headway on this...
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
stlsaint said:
i am getting the: Transport endpoint is not connected error still and i have no real experience with FUSE so im stuck to using windows for any transferring.
Click to expand...
Click to collapse
try following the directions in this thread:
http://forum.xda-developers.com/showthread.php?t=981774
They are basically a superset of what I posted. If you still have trouble after that post in either thread (this one or that one) and I will try and help as best I can.
followed the thread up unto the fstab part as i dont wan to edit my fstab without confirmation that it will work. But i get the exact same error with the endpoint text. I am trying this on Crunchbang linux which is based off debain the same way ubuntu is. I am probably going wrong with FUSE somehow but i have never messed with it so i dont know how to troubleshoot it.
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
mikeew83 said:
I am still having same issue with adb and linux not recognizing my epic I have posted in regards to this and had no responses there all so many devs that work with epic and yet not one has commented to offer a fix i have tried adding 99-samsung.rules with proper edits and changed the 51 rules to match i have reloaded those rules I have added the edited adb i have restarded linux i have changed cables phones usb ports and it picks up my friend og droid no prob but neither me nor my fiances epic will be recognized. any help please.
Click to expand...
Click to collapse
This is the way its done. Sorry up front for quoting myself but I have responded to this issue in the past:
Download the file from this post
http://forum.xda-developers.com/showpost.php?p=8752645&postcount=5
Follow the steps with this post
http://forum.xda-developers.com/showpost.php?p=14199959&postcount=11
Profit!
Holy run on sentence Batman.
Sounds like a drivers issue, or that you don't have USB debugging enabled on the phone.
Open the Dalvik Debugging Monitor Service (DDMS) that came with the Android SDK.
Does it recognize the phone at all in DDMS?
If yes, then does it say "online"? If yes, then you have something blocking adb from talking to your phone from your computer. (firewall?)
If no, then you have a driver or USB connectivity issue. (bad driver installation, usb debugging not enabled on phone, bad usb cable, plugged usb cable into a port not directly on the motherboard)
EDIT: Looks like the post above me could understand the run on sentence more than I could.
You can also run the command lsusb and it should tell you if your system is seeing the device.
What Linux distro your running?
Sent from an Epic with 4G
ok to recap
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
tried your directions again
I have tried them again and they do not work.
Try the usb cable for the droid x. Its a really good one.
if that were an option
I have an incredible cord i can try that is about the only one but i dont see how it has anything to do with the usb cable when lsusb recognizes the device plugged in just adb will not list it on devices so that i dont think is the answer but thank you for the suggestion.
mikeew83 said:
I have followed your prior threads does not work. I have usb debugging on as explaiend i have tried everything means I have searched for hours on end and come with nothing. I have replaced the ADB and created 99-android.rules and edited that as well as editing the 15-android.rules files I have run lsusb and it does show samsung device.
Click to expand...
Click to collapse
You should only have 1 rules file, my suggestion, delete the 15 one and keep the 99.
Make sure the permissions are configured correctly, the biggest issue to run this type of operations in linux is the permissions and the ownership on the config files
Sent from an Epic with 4G
thanks
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
mikeew83 said:
could you possibly explain this a bit more in detail as im still very new to this im a quick learner and great at researching.
Click to expand...
Click to collapse
Let me go over what to do:
After downloading the rules file on the above post, for example I have the SDK (adb) installed on my PC on the following path: ~/android/tools/, so go to your SDK folder (where adb is located) and run the chmod a+rwx adb command.
After this, take the rules file you downloaded from the above post and moved it to the /etc/udev/rules.d/ folder (logged as root, NOT SUDO). After doing this, run the following commands:
make sure that 51-android.rules file has the following permissions -rw-r--r (read and write for owner, group + others read only)
su [then placed the password] (Once again DO NOT USE SUDO)
chown root:root 51-android.rules
Once done, restart the PC and it should be working 100%. Before connecting the phone, make sure USB Debugging is active, and restart your phone.
Connect your phone via USB and run the lsusb command to confirm the connection of the device and then run ./adb devices and check for the positive return!
Note: if you have never had a password on su, run the following command: sudo passwd and change the password and try running the series of command above.
Note2: add your user to the plugdev group on your computer
Note3: sometimes while performing the ./adb devices command will return a response stating that a device by the name ?????????????? is connected, this is OK, you can connect via ./adb shell and you will see your device file structure, if you request SU permissions you will have to authorize it on the phone via the SUPERUSER app that gets installed when rooting the device.
IMPORTANT: The password for ROOT (su) user is not the same as the password you enter for the SUDO command (your user) unless you make them the same!
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
SweetBearCub said:
I'm not sure what exact problem you are having, but I was having a similar problem until this morning (of ADB not recognizing the phone) until I did this:
A) Open the phone dialer.
B) Enter "##8778#".
C) Set both options to "PDA".
D) Make sure sure "USB Debugging" is enabled under "Settings", "Applications", "Development".
I have no idea if this fully applies to your issue, but if it helps, great. If not, no harm done.
Click to expand...
Click to collapse
Though this is good info (thanks for pointing it out), I would highly suggest to leave UART as Modem, and just change USB to PDA.
Sometimes you may have issues with Tethering if you set the UART to PDA.
I have been a bit busy I appreciate the run down and will try it here tomorrow or its 2am so later today I also checked the 8778 and my usb is already set to what was specified.
Sent from my SPH-D700 using Tapatalk
Hello,
(First sorry for my very bad english. It's not my natural language but I do my best for sharing with you!)
04/13 - UPDATE: Now 3G works for ICS with some ROMs like Megatron.
Revolver will be based on TF101G ICS ROM soon.
09/17 - UPDATE:Roach2010 and gnufabio have developped an apk that enable Mobile Network settings (for 3G dongle).
Their APK change the bootloader. (Read more and download)
So maybe this thread has no purpose except for issues and for the list of compatible dongles. If you have a dongle which work and which is not in the list.....
11/08 - UPDATE: 3G dongle works too with Extension-Kit/TFUSB1 Asus P/N 90-XB2UOKEX00020
You can find it here: http://shop.asus.fr/shop/fr/fr-FR/Home/1-Produits/1500-Collection-ASUS/1936-Accessoires-Eee-Pad/1937-Accessoires-Transformer-Prime-TF201/90-XB2UOKEX00070-Adaptateur-USB-externe-pour-ASUS-Eee-Pad.aspx (Thanks to ValenteL for information)
************************************************************
Bellow you can find the first post
Thank you,
Regards.
FIRST POST:
There is probably other ways to make the 3G Dongle working on TF101 but here you can find how we have done.
The follow lines work to have Prime v1.5 installed on your Transformer (works with any version!)
Then you could upgrade to Revolver 2.1.
Otherwise you can directly nvflash your TF101 with the Revolver 2.5 NVFlashed version of cuckoopt.
You just have to follow instructions on this post.
Don't forget to thank him if it works for you
Note: SetCpu doesn't seem to work. I don't know if the issue is coming from Revolver or HC. By re-installing SetCpu, it works one time then crashes.
A. Prime V1.5 Installation:
1. You have to backup all your data/apk from your Internal SD Card because we will make a clean install. So use your backup software.
Becareful. if you project to use Titanium Backup, his backup files are on the internal SD Card so afterwards, you have to move it to your MicroSD (from /mnt/sdcard/Titatium Backup to /data/Removable/MicroSD)
2. Download NVFlash: http://www.filefactory.com/file/ccda97c/n/nvflash.zip then the NVFlash version of Prime v1.5: http://www.sdx-downloads.com/devs/roach2010/flash_roms/prime_v1.5_nvflash.tar.bz2
Updated note: I am not able to activate the Mobile Network option with version 1.6 (even Zip version for ClockWorkMod nor NVFlash version).
But some people have succesfully activated it by flashing NetFinder 1.5 just after the fresh Install of Prime v1.6 and before rebooting the system ; it means in the same CWM
3. unpack NVFlash and Prime v1.5 in the same directory. The image files of Prime v1.5 should be unpacked into the NVFLashTF folder.
4. Connect your TF101 to your PC via USB. Then hold the volume UP and Power button until a NEW device named "APX" appears in the Device Manager. Note that the screen of the Transformer stays black.
5. Click on the APX to install drivers from directory USBPCDriver (included in NVFlash.zip)
info: I used Windows XP 32 bits.
6. Then run Download.bat if you are on Windows, download.sh for Linux users
7. When NVFlash is ended, reboot your TF101.
During boot, there is a setup wizard. Choose connection with "3G and Wifi", not "only Wifi"!!
At this step, you must have the Mobile Network option in Parameters.
8. Download Maxh2003 Script: http://android.modaco.com/index.php?act=attach&type=post&id=73836 (you need to be a register user on Modaco You could find another link some posts after!)
Download the Patch files for ACER A500 tab: http://forum.xda-developers.com/attachment.php?attachmentid=638588&d=1309189189
9. Unzip the script and the Patch file in the same directory.
If you want to upgrade to Revolver 2.1 version (HoneyComb 3.2), you must stop here and go to step B (chapter B).
Otherwise continue chapter A.
10. Connect your TF101 and run install-TF101.bat
11. Mobile Network option is here.
B. REVOLVER 2.1 Installation
1. Do a fresh install of Prime v1.5 NVFlsh version.
If it's not the case go back to the begin of this post and execute steps A.1 to A.9. then go back to B.2
2. Download this file
3. If you read this, Prime v1.5 NVFlash version is installed and you are in CWM Recovery screen.
Install the Recovery 2.1 version (Full). DON'T WIPE DATA
4. At the end, just reboot your system and verify that Mobile Network option is still here.
5. Then we have to install drivers for your dongle (see the list below for compatible dongles).
Let your TF101 on, connect it to your PC via USB cable and run install-TF101.bat via cmd.exe from Windows (tested under Windows XP x86 and Windows 7 x64)
C. List of COMPATIBLE DONGLES
Note: if your dongle is not in this list, but works with TF101, please tell me. It will be added to the list.
* ZTE MF 639 (might need roaming enabled to get data working)
* Alcatel X225L (thx to urko95)
* Vodafone K3765-H
* Vodafone K3715
* Vodafone K3565 / Huawei E160
* Huawei E156G (thx to sh337 for testing)
* Huawei E160G (thx to htc-hd2. His post)
* Huawei E161 (thx to zumbik. His post)
* Huawei E169
* Huawai E170
* Huawai E171
* Huawei E173 (ATTENTION: E173 EVO version NOT COMPATIBLE - thx to sronweb for his tests - Read more)
* Huawei E180 (thx to ValenteL. His post)
* Huawei E220 (thx to eyz. Connexion seems to be not stable. Read more)
* Huawei E270 (thx to eyz. His post)
* Huawei E1550
* Huawei E1552
* Huawei E1692
* Huawei E1750
* Huawei E1752
* Huawei E1762 (thx to bennyyen. His post)
* Huawei E1820
* Huawei E1823 (Thx to bswpt. His post)
* Huawei E2010 (Thx to madangryscientis. His post)
* HUAWEI K3520
* HUAWEI K3565 -Rev 2
Click to expand...
Click to collapse
D. About LED on HUAWEI 3G Dongle:[/B]
The LED indicator displays the current connection status of your Orange E1752 dongle, with each colour representing a different status:
When the LED displays green and is blinking twice every three seconds, this means that the dongle is powered on.
When the LED displays green and is blinking once every three seconds, this means that the dongle is attempting to register onto a 2G network.
When the LED displays blue and is blinking once every three seconds, this means that the dongle is attempting to register onto a 3G network.
When the LED displays solid green, this means that the dongle is connected onto a 2G network.
When the LED displays solid blue, this means that the dongle is connected onto a 3G network.
When the LED displays solid cyan, this means that the dongle is connected onto a 3G+ network
When the LED displays no colour, this means that the dongle is removed.
Click to expand...
Click to collapse
And dont forget to turn off the composite device of the 3G dongle.
Here how to do (thanks to Matchstick from Modaco who wrote these lines):
You can test this by plugging the stick into a PC and seeing if it detects the modem as a CD or Memory stick device as well as a modem.
If it does then the method I used to turn off the composite device (on Windows 7) was:
1) Install the software and drivers for the modem under windows and make sure that the connection software sees the modem correctly.
2) Go to Settings/Control Panel/Device Manager and if you expand the Modems section you should see your USB modem listed there
3) Double click on the entry for the modem to get the properties panel up and selected the Modem tab
4) You should see a line at the very top of the tab that says something like Port: COM11 - This is the virtual serial port that the PC uses to talk to the modem which we're going to use to send the command to turn off all the stuff we don't want.
5) Next we want to install a serial console application. PuTTY is perfect for this. If you don't have a copy you can get if from here,
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
6) Run putty, select Serial under Connection Typem and enter the port we found in step 4 (eg COM11) into the box marked Serial Line and press the Open button
7) An empty window should pop up, which if things are working correctly is connected to the Modem
8) Type "ATI" into the window (without the quotes) and press return. The ATI command asks the modem for basic information and it should respond with something like
Manufacturer: huawei
Model: E1752
Revision: 11.126.03.01.314
IMEI: 123456789012345
+GCAP: +CGSM,+DS,+ES
OK
9) If you see this then you are connected correctly, if you don't see a response try physicaly unplugging and reconnecting the modem into a different USB port and start again from step 2 after windows has loaded the drivers for the modem.
10) Assuming everything is OK, the we can send the command to turn off the stuff we don't want. To do this simply type "AT^U2DIAG=0" (again without quotes) into the putty window. you should see the response OK.
11) If you do then the composite device features should now be turned off and you are ready to try the modem in your transformer.
Click to expand...
Click to collapse
Remerciements/Thanks to AndroidRoot.mobi for NVFlash, Paul for Prime!, Maxh2003 for his script and help, Matchstick for his help, Dexter_nlb for his A500 patch and, of course, all our developers and users who help us.
Not sure why I've flashed several roms in APX from w7 64 bit just fine.
It seems that these drivers don't work for win7 64 and works for Vista 64.
Perhaps they are unsigned.... didn't know. I don't make more tests.
Regards.
Looking good. Now to get a 3G plan and dongle...
Anyone get this working?
to kasimodo
Could you upload Maxh2003's scrift file here. I can't download it from your link.
Thanks
nsec said:
to kasimodo
Could you upload Maxh2003's scrift file here. I can't download it from your link.
Thanks
Click to expand...
Click to collapse
Here the file.
Regards
insmod is having no luck with these kernel modules, none are loaded, and I get nothing??? what's the deal? has anyone got this working including the OP or is this just a theoretical WIP
dan-htc-touch said:
insmod is having no luck with these kernel modules, none are loaded, and I get nothing??? what's the deal? has anyone got this working including the OP or is this just a theoretical WIP
Click to expand...
Click to collapse
Hello it's not a theoretical WIP.
Look here
Can you give more details please?
Regards,
oh... I guess insmod won't work on the modules without a compatible modem plugged in then?
many thanks! got it to work on my E1750
although you might want to put the instruction steps to remove the storage on the modem (only works after I did it):
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
dan-htc-touch said:
oh... I guess insmod won't work on the modules without a compatible modem plugged in then?
Click to expand...
Click to collapse
Probably. is you 3G Dongle in the "compatibility list".
If yes, you have to turn off the composite device of the 3G dongle.
Here how to do (thanks to Matchstick from Modaco):
Code:
You can test this by plugging the stick into a PC and seeing if it detects the modem as a CD or Memory stick device as well as a modem.
If it does then the method I used to turn off the composite device (on Windows 7) was:
1) Install the software and drivers for the modem under windows and make sure that the connection software sees the modem correctly.
2) Go to Settings/Control Panel/Device Manager and if you expand the Modems section you should see your USB modem listed there
3) Double click on the entry for the modem to get the properties panel up and selected the Modem tab
4) You should see a line at the very top of the tab that says something like Port: COM11 - This is the virtual serial port that the PC uses to talk to the modem which we're going to use to send the command to turn off all the stuff we don't want.
5) Next we want to install a serial console application. PuTTY is perfect for this. If you don't have a copy you can get if from here,
http://www.chiark.greenend.org.uk/~sgtatha...y/download.html
6) Run putty, select Serial under Connection Typem and enter the port we found in step 4 (eg COM11) into the box marked Serial Line and press the Open button
7) An empty window should pop up, which if things are working correctly is connected to the Modem
8) Type "ATI" into the window (without the quotes) and press return. The ATI command asks the modem for basic information and it should respond with something like
Manufacturer: huawei
Model: E1752
Revision: 11.126.03.01.314
IMEI: 123456789012345
+GCAP: +CGSM,+DS,+ES
OK
9) If you see this then you are connected correctly, if you don't see a response try physicaly unplugging and reconnecting the modem into a different USB port and start again from step 2 after windows has loaded the drivers for the modem.
10) Assuming everything is OK, the we can send the command to turn off the stuff we don't want. To do this simply type "AT^U2DIAG=0" (again without quotes) into the putty window. you should see the response OK.
11) If you do then the composite device features should now be turned off and you are ready to try the modem in your transformer.
Regards
brensim said:
many thanks! got it to work on my E1750
although you might want to put the instruction steps to remove the storage on the modem (only works after I did it):
Insert modem into pc and wait for driver to install
check in device manager which com port is assignated to your modem
download putty
here the.earth.li/~sgtatham/putty/latest/x86/putty.exe
close every program related to modem
run putty
click serial below port number and then change port number to one previously founded
click open
write atz and press enter, modem should answer ok
write ati and press enter, modem should give name, type, etc
write AT^U2DIAG=0 and press enter, zero cd is now disabled
Click to expand...
Click to collapse
What kind of OTG adapter are you using for this?
Hi all,
will this work with the Huawei E173u2 , the second version adapted for (pseudo)"4G" networks
I am with stock 3.1 + root.
Does it work or I need to install PRIME anyway?
At the moment, everyone who has got this to work has had to install Prime 1.5 (and several of us had to install the NVFlash specific version of Prime)
acid12 said:
Hi all,
will this work with the Huawei E173u2 , the second version adapted for (pseudo)"4G" networks
Click to expand...
Click to collapse
Is this similar to the huawei E367 ? As I'm looking at the E367 at the moment.
One easy(ish) way to check is to follow Steps 1-8 from post 12, then enter the command "AT^GETPORTMODE" (without the quotes)
If you get a response like
"^getportmode:type:WCDMA:Qualcomm,MDM:0,NDIS:1,DIAG:2,PCUI:3,CDROM:4"
then the E173u2 is using the new interface like the E367 and at the moment I can't get it to work.
It may be that the drivers aren't compatible (I'm not seeing ttyUSB0-ttyUSB2 devices appearing in /dev/) or it may just be that I haven't got the correct interfaces enabled.
There's information on the AT commands for the new-style Huawei modems here
http://www.dd-wrt.com/phpBB2/viewtopic.php?p=618504
Matchstick said:
At the moment, everyone who has got this to work has had to install Prime 1.5 (and several of us had to install the NVFlash specific version of Prime)
Click to expand...
Click to collapse
So i think that it is not only root needed but also something that in PRIME is present and that we can not add to stock rom.....
thanks
chrispazz said:
I am with stock 3.1 + root.
Does it work or I need to install PRIME anyway?
Click to expand...
Click to collapse
you can try by using Settings/Privacy then Reset to factory
Then restart and hen wizard ask you to choose for "3g and wifi" or "wifi only" choose 3g and wifi
Afterward you must see mobile network in settings.
tell us and don't forget to backup your data
Kasimodo said:
you can try by using Settings/Privacy then Reset to factory
Then restart and hen wizard ask you to choose for "3g and wifi" or "wifi only" choose 3g and wifi
Afterward you must see mobile network in settings.
tell us and don't forget to backup your data
Click to expand...
Click to collapse
Ok. I have to wait for my docking to come back from ASUS (RMA) and then I will try.
TY
After reading around, I've learnt that MinimalTouch 1.1beta5 is a reliable way to root my new Nook Simple Touch. Since I intend selecting the package version in the beta5 folder, I must choose between the "START" zips: beta5-2 XUFullTouch-PART-1-START and beta5-2 XWFullTouch-PART-1-START. I gather the first zip is ADB over USB, and the second, ADB over WiFi, but have found little documentation on either, except that ADB is a method to connect your home computer to your Nook.
The above link states that all W zips install ADB wireless Uramdisk, and all U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need. Am I right that ADB over USB is the best choice because both USB and WiFi are available after rooting? If so, would anyone select the ADB over WiFi option?
Can someone please explain how and why one chooses between the two options when rooting the Nook?
On startup the ADB daemon, adbd looks at the property service.adb.tcp.port
If it is set it uses that value as the port number over TCP (presumably over WiFi) to listen for connections.
If it is not set it tries to connect over USB.
I'm not sure how these applications that switch mode work.
They probably kill the daemon and restart it.
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Renate NST said:
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Click to expand...
Click to collapse
Thanks for your help. I've taken a while to make sense of your post since all this is new to me - I rarely use a mobile phone.
I've just looked at contents of both the "START" zip files and noticed they're the same, except that the file uRamdisk in the folder boot of the WiFi option is marginally bigger. You have shown me the difference lies in the property service.adb.tcp.port in the Java source code, and that property determines whether the rooted Nook tries to connect by WiFi or USB. In other words, the two zips are identical except for ADB connection.
But my opening post, in ignorance, attempted to ask a more trivial question. I know whenever I wish to access any laptop computer from my desktop computer under Windows XP, I can connect the two using a network cable from the laptop to my wireless router/modem or, more simply, by activating WiFi on the laptop. Similarly, I am assuming I can connect the rooted Nook to my desktop either by cabling the Nook microUSB port to a USB port on my desktop, or by activating WiFi on the Nook. I expect to connect every few days. Since the USB "START" zip of MinimalTouch 1.1beta5 provides an ADB widget to enable wireless adb at need, what is the point - for the end user - of a separate WiFi only "START" zip file?
In other words, in routinely connecting my rooted Nook to the desktop computer every few days, why on earth would I or anyone benefit from having had the two "START" zip options available in MinimalTouch 1.1beta5?
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
desimunda42 said:
Code:
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Click to expand...
Click to collapse
That seems suspicious. Was this taken while the phone was connected to your mac?
Here's my phone's dump while NOT connected to a computer
Code:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Here it is when connected to computer
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
[COLOR="red"] mConnected: true
mConfigured: true
[/COLOR] mUsbDataUnlocked: false
mCurrentAccessory: null
[COLOR="red"] Kernel state: CONFIGURED
[/COLOR] Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
[COLOR="Red"] Last key received: blahblahblahblah (not null)
User keys: blahblahblahblah (no exception)
[/COLOR] System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
adotkdotjh said:
That seems suspicious. Was this taken while the phone was connected to your mac?
Are you on a custom rom? Do you get an authorization prompt if you call "adb device" after doing "Revoke USB debugging authorizations" from Develop options?
Click to expand...
Click to collapse
I wasn't connected to my Mac at the time I pulled the report (I confirmed by repeating it just now and still get that 'FileNotFoundException" in the logs for USB device. I don't have a custom rom, I have the standard OEM from the Google Store and didn't do anything else with it.
Also, I did revoke the USB debugging auth multiple times and inspite of that I never get any prompt when I connect.
I also got the report while connected to the Mac and am still seeing the same exception:
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
desimunda42 said:
Hi everyone,
I have a Nexus 6P which simply refuses to connect via USB on my Mac (i.e. it doesn't show up as a valid device under adb devices or via Android File Transfer). I believe it was working at some point but it seems to have stopped now. Might be worth noting, I did try connecting it to my car's charger a few months ago but had the worst time with it, it would charge and disconnect every few seconds (may or may not be relevant in this case as it pertains to the USB). I tried a different charger and it works fine with it though.
I have tried a lot of different things (which I'll list below) but have had no luck getting my Nexus 6P being recognized as a device when I connect it to my Mac (or any other). I do have the Developer settings enabled and I am able to switch to MTP but I never get the prompt to change USB mode. Anytime I connect my device, adb devices doesn't list it at all. I tried ADB File transfer as well and that also says "Please connect your device".
Here are some of the things I have tried so far:
1. Used different cables - no luck
2. Used a different mac - no luck
3. Tried a different Nexus 6P with my cable, it works fine (so it is not a cable issue)
4. Tried a different Nexus 6P with my mac, it works fine (so my Mac seems to be OK too)
5. Restarted in recovery mode - no luck
6. Tried removing a bunch of apps in case there was something conflicting - no luck so far
7. Chatted up Google support - They couldn't tell me much outside of the last option - Factory Reset - I have been holding off on that since I want to be able to transfer my files out first but I really want to avoid having to try that before exhausting all other options. They did offer to replace with a refurb'ed device but I had to decline that.
I did create a bug report dump using the device to see if anything interesting showed up and the only thing noticeable there is an exception related to USB. I am putting that info here in case it is useful in helping with this.
Code:
DUMP OF SERVICE usb:
USB Manager State:
USB Device State:
mCurrentFunctions: mtp,adb
mCurrentFunctionsApplied: true
mConnected: false
mConfigured: false
mUsbDataUnlocked: false
mCurrentAccessory: null
Kernel state: DISCONNECTED
Kernel function list: mtp,ffs
USB Debugging State:
Connected to adbd: true
Last key received: null
User keys:
IOException: java.io.FileNotFoundException: /data/misc/adb/adb_keys: open failed: ENOENT (No such file or directory)
System keys:
IOException: java.io.FileNotFoundException: /adb_keys: open failed: ENOENT (No such file or directory)
USB Host State:
USB Port State:
otg_default: port=UsbPort{id=otg_default, supportedModes=dual}, status=UsbPortStatus{connected=true, currentMode=ufp, currentPowerRole=sink, currentDataRole=device, supportedRoleCombinations=[source:host, sink:device]}, canChangeMode=true, canChangePowerRole=false, canChangeDataRole=false
USB Audio Devices:
USB MIDI Devices:
Settings for user 0:
Device permissions:
Accessory permissions:
Device preferences:
Accessory preferences:
Any help here is really appreciated! Thanks
Click to expand...
Click to collapse
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
If you havent done any of this yet the thats the problem. If everything I just typed seems confusing then you can try this which explains everything you need to do to set up adb a whole lot better than my attempt above lol buts its going to take some time to accomplish https://seo-michael.co.uk/how-to-setup-adb-on-os-x/
or
You can also install and configure adb a whole lot easier by issuing the following commands from within your mac terminal.... (This will install Brew on your Mac, if you arent familiar with what it is, Its a software distrobution platform. Sort of like git hub and linux software repos. When in doubt, do a little reading first. It'll solve all your problems....
-Install Brew - Copy and paste this command into a mac terminal and follow the prompts that show up.
/usr/bin/ruby -e "$(curl -fsSL https://raw.githubusercontent.com/Homebrew/install/master/install)"
-Once that finishes, next use this command
brew update && brew cask install java
-Once that is complete enter this last command
brew install android-platform-tools
Those 3 commands will do 99 percent of the work. When its done just find the platform tools folder and go from there. Hope this helps.
Sass86oh said:
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac. Youll have to pull up your terminal and and direct it to the folder containing adb and fastboot. Its usually ina a folder called "platform-tools" Which can be found in the dictory in whch you installed the Android SDK or SDK Tools packages... Now that I think about it, you have to download adb from the SDK package I just mentioned. After doing so, youll find the platform tools folder and it should contain what you need. As long as java is correctly installed on your mac then everything should work once you issue the "adb devices" command in a terminal session thats points at the "platform-tools" folder. YOU ALSO HAVE TO HAVE JDK INSTALLED in order for it to work with your device. I just looked at what you posted and it looks like youred missing JDK"...
Click to expand...
Click to collapse
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
adotkdotjh said:
He says he already tried adb devices which didn't list anything. That tells me adb is configured correctly. Otherwise it should've given errors. Plus, he also said another Nexus 6P worked on the same mac.
Click to expand...
Click to collapse
Yep
Sass86oh said:
I usually only get the key prompt for ADB authorzation when I connect my device and type "adb devices"..... If worse comes to worse, You can restore your phone to factory settings without wiping your sd card. Then you could test that option with compromising your data. Just flash each image from the archive yourself when restoring the firmware as opposed to using the flash-all scipt, or resetting the phone from settings... DO NOT flash the "userdata.img" included in the factory firmware archive or issue the command "fastboot format userdata" during the restore process and all of your files will be fine. This may be an option as long as fastboot is still functional on your device. Ive come across so many different devices in so many different conditions over the years, as long as the device could power on and the usb port was functional, fasboot has worked time and time again.
PS adb on Mac can be a bit tricky especially if this is the first time youre attempting to o install and use it. Unless you set the correct enviornment variables during the install process, you will oly be able to access adb from inside the folder that its stored in on your mac.
Click to expand...
Click to collapse
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
desimunda42 said:
Yep
Thanks for the detailed steps but like adotkdotjh mentioned, I already have a working adb (and it worked fine with a different Nexus 6P on the same mac). How would 'fastboot' work if the computer does not even see my device under list of devices? I've never done any image flashing before so that would be quite an unfamiliar territory but I'd be willing to explore. Where would I get these image files and how do I issue the command to the device while it is not being recognized? Thanks
Click to expand...
Click to collapse
Fastboot (also refered to as "download mode") is a tool used to essentially reprogram your device in the event that you are unable to enter into recovery mode in oreder to fix whatever issue your device is having. Android devices have 3 working modes, normal function, recovery mode, and fastboot. Number one is obvious, recovery allows you to completely reset your device without using a computer if every other measure youve tried hasn't worked. When you use this feature everything on your device is erased and your phone is completely restored to factory settings. Its convienet becuase not everyone is computer savvy and its to the point. But say you were updating (system update) your phone and accidently dropped it causing the battery to fall out and the device to shut off in the middle of the update process. What will most likely happen is the system partition will become corrupt, causing the phone to stick at the initial boot screen. Usually if that happens you can still access recovery mode and just reset but if for some reason that didnt work you would go to the manufacturers website and download the latest firmware for your device. You put the phone into fastboot mode by holding volume down and then pressing and holding the power button at the same time (while the phone is off).The process varies bydevice, If done correctly you will see on your screen a bunch of info along with Andy (the Android) chillin with his hatch open. You connect your phone to your computer and as long as your computer is set up correctly with adb and fastboot, you now have the abailty to reprogram (flash) your device using a series of commands that are issued from either the command line (windows) or terminal (linux/mac).
YOUR BOOTLOADER NEEDS TO BE UNLOCKED BEFORE CONTINUING. IF YOU DONT SEE A LITTLE LOCK AT THE BOTTOM OF YOUR DEVICE UNDER THE GOOGLE LOGO WHEN YOU FIRST TURN IT ON THEN YOU NEED TO GO TO SETTINGS, ABOUT DEVICE, FIND BUILD NUMBER AND TAP IT RAPIDLY UNTIL YOU SEE A MESSAGE POP UP SAYING YOU UNLOCKED DEVELOPER OPTIONS. GO BACK TO THE SETTINGS MENU AND SELEC DEVELOPER OPTIONS WHICH SHOULD NOW BE THERE AND INSIDE THERES AN OPTION CALLED "ALLOW OEM UNLOCKING" TURN IT ON. AND CONTINUE
Eextract the firmware archive you downloaded which will produce a folder containing 2 ".img files" files, another ".tar" archive, and some script files that you can use to make the process pretty much automated.
There are two of them, one for Windows (flash-all.bat) and one for Linux and Mac (flash-all.sh)....
Open the folder that was extracted from the firmware archive... Hold shift then right click a blank area in the folder. Select "open command prompt here" (Windows)
or
Type in terminal : cd ~/downloads/xxx where "xxx" is the name of the folder that was extracted but make sure that folder is moved to your "downloads" directory first
Then type the following commands:
IF YOU HAVENT UNLOCkED YOUR BOOTLOADER BEFORE THEN THIS IS WHERE YOU WILL NEED TO:
For Mac/Linux type: ./fastboot flashing unlock **Make sure you use the ./ or the command wont be recognized**
For Windows type: fastboot flashing unlock
Select yes on the phone when it asks if youre sure..... BAM, unlocked bootloader.
Your phone is completely free of restrections if you want to install custom firmware now. If not you can relock it after flashing the stock firmare by enterning fastboot mode again and typing
fastboot flashing lock or ./fastboot flashing lock (mac/linux).....
Now we can proceed with flashing the device...
For Windows: flash-all.bat and hit enter. The computer will do the rest.
Linux/Mac: ./flash-all.sh Make sure you use the ./ or the command wont be recognized.
If youre feeling brave you can do the entire process yourself by extracting the files in that second archive that was produced and flash each of them individually using a series of command in a specific order.
The 2nd extracted archive will give you a folder with five .img files
boot.img
cache.img
system.img
recovery.img
userdata.img ***** DO NOT FLASH THIS IMAGE. FORGET ITS EVEN THERE****
Take all five and move them to the original folder that was extracted. There are 2 other .img files that were extracted from the first archive also like I mentioned above, one that says "BOOTLOADER.xxx.xx.img" and one that says "RADIO.xxx.xxx.img"... Rename RADIO.xxx.xxx.img to | radio.img |and the other to| bootloader.img |ALL LOWER CASE keep them in that folder along with the other five. Now you should have 7 total image files in one folder. (Its smart to use the folder that your command prompt or terminal was opened in, if you decide to use a different folder then you have to direct each fastboot command to the folder where the .img file is located.
from the command line you flash each img individually with the following commands.....
(Mac/Linux need to include ./ before every fastboot command begins like this: ./fastboot or it wont work.
fastboot flash bootloader bootloader.img
fastboot reboot-bootloader (phone will reboot then go back into fastboot mode, dont worry should only take seconds)
fastboot flash radio radio.img
fastboot reboot-bootloader (reboots again)
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata (this command takes place of the "userdata.img" file I told you to forget about)
fastboot reboot
As long as you see action on the screen and a "complete" after every command then youre in business. If you get an error check your spelling. THE COMMAND LINE IS CASE SENSETIVE. You might type the correct words but if one letter is capital the command wont work. If theres an extra space between words then the command wont work so check everything. Safe rule: Everything should be in lower case letters with 1 space after every word.... THIS S*** MATTERS
Its not as hard as it seems if you arent familiar with the process, but its also not something to mess with unless youve done your homework. Read up on it, there are so many good posts and people in here so you'll be able to find everything you need without any issue.
Fastboot can also be used to install a custom recovery like TWRP which would then allow you to install custom firmware (roms) on your device as long as theres support for it. Nexus devices are built for that very reason! They tend to have a huge selection of development within the Android community. They come with Android as Google intended it to be! No extra BS.... And its wicked easy to unlock the bootloader. That is why they are, in my opinion, the best Android devices available. But someone who doesnt really care much for things like modding and installing custom firmware might see the Nexus as plain device which lacks the bells and whistles included in other devices. Which is ok! I personally love the simplicity of pure Android and the whole philosophy behind the Nexus Program. To each is own! If you need anything else send me a message!
Have not read it all on here lol install this on your Mac https://www.android.com/filetransfer/ and see if it sees you 6p make sure you plug in them change from charging to file transfer on the phone then exit out of the app and reboot that will tell you if your Mac sees your phone