GT-N8000 "No driver found" - using ZTE USB Modem FFF1
Hi,
first off all, big and huge respect Josh that you run this forum alone! *thumb up*
I am using:
Samsung Galaxy Note 10.1 (android 4.0.4) + USB Connector
ppp Widget 1.15
ZTE USB Modem FFF1
If I connect my USB Modem with my Galaxy note, ppp Widget shows me "No driver found". I know that it recognize this USB Modem because the light of this Modem is blinking till this message appears "No driver found"
So, now I unchecked "Automatic device detection" and touched the widget icon. It shows me now
"1519:0020 (Comneon)".
So, if i now connect my Modem with my device and click then on the widget Icon, it shows me another option
"19d2:fff1 (ZTE, Incorporated)". After i chose this, it says again "not driver found"
Please help me. I am sure i need a configuration file, right? If not, is there any solution? I can remember on Ubuntu I had a configuration file and edit something. I cant remember any more, sorry. But i think it put a line equal to "0" and after that again equal to "1" and then it worked....
btw. I am not that newbie like the way i wrote :-)
first off all, big and huge respect Josh that you run this forum alone! *thumb up*
I am using:
Samsung Galaxy Note 10.1 (android 4.0.4) + USB Connector
ppp Widget 1.15
ZTE USB Modem FFF1
If I connect my USB Modem with my Galaxy note, ppp Widget shows me "No driver found". I know that it recognize this USB Modem because the light of this Modem is blinking till this message appears "No driver found"
So, now I unchecked "Automatic device detection" and touched the widget icon. It shows me now
"1519:0020 (Comneon)".
So, if i now connect my Modem with my device and click then on the widget Icon, it shows me another option
"19d2:fff1 (ZTE, Incorporated)". After i chose this, it says again "not driver found"
Please help me. I am sure i need a configuration file, right? If not, is there any solution? I can remember on Ubuntu I had a configuration file and edit something. I cant remember any more, sorry. But i think it put a line equal to "0" and after that again equal to "1" and then it worked....
btw. I am not that newbie like the way i wrote :-)
Last edited by dahood on 02 Jan 2013, 03:07, edited 1 time in total.
Re: "No driver found" - using ZTE USB Modem FFF1
The message "No driver found" means exactly that.
Any USB device needs a driver. The Linux kernel provides loads of them, but on Android kernels usually only few of them are available. It mainly depends on the device maker how he adapts the kernel for his device-specific OS version.
To make most wireless modems work, a USB driver is needed which supports serial (TTY) interfaces. There are two possible modules, "option" and "usbserial" (the latter as a fallback).
If these modules are not present on the device (and also not built into the kernel), there is nothing that PPP Widget can do.
You can try to find the modules in the file system of your device. Maybe they are in unusual folders?
Look for "option.ko" and "usbserial.ko".
Any USB device needs a driver. The Linux kernel provides loads of them, but on Android kernels usually only few of them are available. It mainly depends on the device maker how he adapts the kernel for his device-specific OS version.
To make most wireless modems work, a USB driver is needed which supports serial (TTY) interfaces. There are two possible modules, "option" and "usbserial" (the latter as a fallback).
If these modules are not present on the device (and also not built into the kernel), there is nothing that PPP Widget can do.
You can try to find the modules in the file system of your device. Maybe they are in unusual folders?
Look for "option.ko" and "usbserial.ko".
Re: "No driver found" - using ZTE USB Modem FFF1
Aww this doesnt sound good for me and I also wasnt able to find these 2 files on my tablet "option.ko" and "usbserial.ko". I guess to download it somewhere and copy it to my tablet wouldnt make much sense.
What would you now suggest to me? I live in Iraq and we dnt have many options to go online and it would be great if I could use my 3g dongle or 3g modem or option, I dnt know which one is the correct word.
What would you now suggest to me? I live in Iraq and we dnt have many options to go online and it would be great if I could use my 3g dongle or 3g modem or option, I dnt know which one is the correct word.
Re: "No driver found" - using ZTE USB Modem FFF1
You can copy those modules onto your device - provided they were compiled for your exact kernel version. Maybe someone has done that already ...
Newer versions of the "option" driver are split to two files so you would need the "usb_wwan" module in addition.
But before searching for modules (or even compile them on your own), check if they are not already built into the kernel. Look for the path "/sys/bus/usb-serial/drivers/option1"; if you can see this, the driver is active and the trouble with PPP Widget lies somewhere else.
Newer versions of the "option" driver are split to two files so you would need the "usb_wwan" module in addition.
But before searching for modules (or even compile them on your own), check if they are not already built into the kernel. Look for the path "/sys/bus/usb-serial/drivers/option1"; if you can see this, the driver is active and the trouble with PPP Widget lies somewhere else.
Re: "No driver found" - using ZTE USB Modem FFF1
Remember when i said "I am not that newbie like the way i wrote"? Well I think i was wrong, sorry!
So, i looked for this path "/sys/bus/usb-serial/drivers/option1" but after drivers, there is no "option1". Instead there is "pl2303" and if i click on this folder i get this this files: "bind", "new_id", "uevent" and "unbind"
I am not sure if its the fault of my Samsung Galaxy Note 10.1, because its a new device or is it the fault of Android 4.0.4. Maybe if I am gonna install another ROM, for example Cyanogonmod 10, would it work maybe? Maybe someone has done this with success...
However, all i can do now is to search in internet for the file "option.ko" and "usbserial.ko" and "usb_wwan". Lets assume they were compiled for my exact kernel version, where should I copy them?
Just for the records:
My Device's Kernel Version:
3.0.15-982379-user
dpi@DELL164#1
SMP PREEMPT Wed Aug 1 11:36:04 KST 2012
I did also a screenshot with more information about my Device, maybe someone else had the same problem.
So, i looked for this path "/sys/bus/usb-serial/drivers/option1" but after drivers, there is no "option1". Instead there is "pl2303" and if i click on this folder i get this this files: "bind", "new_id", "uevent" and "unbind"
I am not sure if its the fault of my Samsung Galaxy Note 10.1, because its a new device or is it the fault of Android 4.0.4. Maybe if I am gonna install another ROM, for example Cyanogonmod 10, would it work maybe? Maybe someone has done this with success...
However, all i can do now is to search in internet for the file "option.ko" and "usbserial.ko" and "usb_wwan". Lets assume they were compiled for my exact kernel version, where should I copy them?
Just for the records:
My Device's Kernel Version:
3.0.15-982379-user
dpi@DELL164#1
SMP PREEMPT Wed Aug 1 11:36:04 KST 2012
I did also a screenshot with more information about my Device, maybe someone else had the same problem.
- Attachments
-
- About my device
- about Device.jpg (52.85 KiB) Viewed 16640 times
Re: "No driver found" - using ZTE USB Modem FFF1
PPP Widget will look for modules in these folders:
/system/lib/modules
/lib/modules
/sdcard/pppwidget/lib
To avoid messing with the system folders, I suggest putting custom modules in the sdcard folder.
/system/lib/modules
/lib/modules
/sdcard/pppwidget/lib
To avoid messing with the system folders, I suggest putting custom modules in the sdcard folder.
Re: "No driver found" - using ZTE USB Modem FFF1
I have provided the additional modules for a selection of Samsung devices.
See the new sticky thread on top of this forum.
See the new sticky thread on top of this forum.
Re: "No driver found" - using ZTE USB Modem FFF1
Hi Josh
First of all, BIG thanks to you for not giving up this device "Samsung Galaxy Note 10.1"
Since Galaxy note 10.1 got so popular, maybe I am gonna be able to solve this problem now and other user can make benefit of this post.
I download the Attachment for my module "GT-N8000_modules.zip [221.98 KiB]" and it still doesn't work.
Meanwhile I updated my device to Jellybean, see picture.
I also added the "USB_ModeSwitch log" file.
I also copied and pasted my terminal, when I typed dmesg, into a text file and uploaded it because it is so long.
Can you see the problem? I hope it is not because of my dongle 3g modem
Just for the records, i dont have this folder "modules" in "/system/lib/" or "/lib/"
I have root access and I already looked for /system/lib/modules or /lib/modules. I just mention it because i noticed that you often ask the user to look inside these folder for files
First of all, BIG thanks to you for not giving up this device "Samsung Galaxy Note 10.1"
Since Galaxy note 10.1 got so popular, maybe I am gonna be able to solve this problem now and other user can make benefit of this post.
I download the Attachment for my module "GT-N8000_modules.zip [221.98 KiB]" and it still doesn't work.
Meanwhile I updated my device to Jellybean, see picture.
I also added the "USB_ModeSwitch log" file.
I also copied and pasted my terminal, when I typed dmesg, into a text file and uploaded it because it is so long.
Can you see the problem? I hope it is not because of my dongle 3g modem
Just for the records, i dont have this folder "modules" in "/system/lib/" or "/lib/"
I have root access and I already looked for /system/lib/modules or /lib/modules. I just mention it because i noticed that you often ask the user to look inside these folder for files
- Attachments
-
- About my device
- AboutDevice.png (6.82 KiB) Viewed 15994 times
-
- dmesg.txt
- "dmesg"
- (130.54 KiB) Downloaded 542 times
-
- USB_ModeSwitch log .txt
- USB_ModeSwitch log
- (3.7 KiB) Downloaded 515 times
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
At the moment, there is a problem with Samsung's JB kernels. The ICS kernels are accepting additional modules with few problems, the newer kernels don't.
You may need to be patient for a while ...
You may need to be patient for a while ...
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
I have enough patience if that day comes, just infrom us, thank you in advance
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
Thank you for waiting ... we apologize for any inconvenience ...
I have found a way to check and match module versions properly. The new N8000 module package has a good chance of being actually useable. Get it at the "Driver Module" post.
I have found a way to check and match module versions properly. The new N8000 module package has a good chance of being actually useable. Get it at the "Driver Module" post.
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
Hey Josh,
Sorry for my late answer. I tried at the first day when i read your post, but it didnt work. But unfortunately i had final exams, so i decided to wait till Jelly Bean is out. now i tried it again with jelly bean. still not working.
But now i am there again and will daily check this page for the reason if you need confirmations with my GT-N8000. So please let me know what i can do, to help you. Its my honor to help.
Edit: I forgot the USB Log
USB_ModeSwitch log from Mon Feb 18 21:23:41 AST 2013
Raw args from udev: 2-1/2-1:1.0
Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 6 -v 19d2 -p fff5 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 002/006 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /sdcard/pppwidget/lib/ppp_async.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/ppp_async.ko' failed (Exec format error)
Loading support module /sdcard/pppwidget/lib/usb_wwan.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/usb_wwan.ko' failed (Exec format error)
Loading main driver module "option"
Error: insmod: init_module '/sdcard/pppwidget/lib/option.ko' failed (Exec format error)
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting
Sorry for my late answer. I tried at the first day when i read your post, but it didnt work. But unfortunately i had final exams, so i decided to wait till Jelly Bean is out. now i tried it again with jelly bean. still not working.
But now i am there again and will daily check this page for the reason if you need confirmations with my GT-N8000. So please let me know what i can do, to help you. Its my honor to help.
Edit: I forgot the USB Log
USB_ModeSwitch log from Mon Feb 18 21:23:41 AST 2013
Raw args from udev: 2-1/2-1:1.0
Using top device dir /sys/bus/usb/devices/2-1
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
devList 1:
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 2 -g 6 -v 19d2 -p fff5 -f $cB
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 002/006 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Could not reset endpoint (probably harmless): -34
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -6
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
Mode switch has completed
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Device class of first interface is ff
Now checking for bound driver ...
No driver has bound to interface 0 yet
Module loader is /system/bin/insmod
Trying to find and install main driver module "option"
Trying to find module "option"
Loading support module /sdcard/pppwidget/lib/ppp_async.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/ppp_async.ko' failed (Exec format error)
Loading support module /sdcard/pppwidget/lib/usb_wwan.ko
Error: insmod: init_module '/sdcard/pppwidget/lib/usb_wwan.ko' failed (Exec format error)
Loading main driver module "option"
Error: insmod: init_module '/sdcard/pppwidget/lib/option.ko' failed (Exec format error)
Falling back to "usbserial"
Module "usb_serial" not found, can't do more here
Driver binding did not work for this device
All done, exiting
- Attachments
-
- KernelVersion_small.png (6.74 KiB) Viewed 15563 times
-
- usb_modeswitch.log
- usb modeswitch log
- (3.83 KiB) Downloaded 459 times
-
- dmesg.txt
- demesg
- (128.4 KiB) Downloaded 469 times
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
Well, for the new kernel I would need one of the existing kernel modules from your device.
The most convenient one is "/lib/modules/scsi_wait_scan.ko". You can just attach it to your reply.
The most convenient one is "/lib/modules/scsi_wait_scan.ko". You can just attach it to your reply.
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
You can also look into /system/lib/modules.
It's important to catch a module (any module) which came with the device.
It's important to catch a module (any module) which came with the device.
Re: GT-N8000 "No driver found" - using ZTE USB Modem FFF1
Here you are!
Edit: Sorry i deleted my previous comment, because i found it. internet is so slow, i didnt see that you already replied it
Edit: Sorry i deleted my previous comment, because i found it. internet is so slow, i didnt see that you already replied it
- Attachments
-
- scsi_wait_scan.ko
- scsi_wait_scan
- (2.14 KiB) Downloaded 543 times