hey guys n gals, iv been reg'd a few days now n thought id make my first post a worth while one
Alot of the credit though must go to Christian Buchner for his initial guide of getting a ZTE usb modem working with vodafone over in Germany.
NOTE: BASED ON ZT-180 SLATE 0929 FIRMWARE (rooted)
To get your ZTE modem working you must be able to use adb confidently!
ok first things first, as Christian pointed out in his guide, if the Flash drive side of the modem is enabled, your slate wont recognise it, so our first job is to disable it.
*Nix Users - Im assuming you have a good knowledge of AT commands already and how to use them so just run
Code:
AT+ZCDRUN=8
Windows Users See Here hxxp://3g-modem.wetpaint.com/page/executing+AT-commands+under+Windows
and execute the above AT command
Right, so now our slate recognises our Modem, now lets get this rocking and get connected.
You will need to Pull the following files from your slate
note: some files may not exist so you will have to create them
/system/etc/ppp/peers/cdma
/system/etc/ppp/peers/cdma_h
/system/etc/ppp/peers/cdma~
/system/etc/ppp/options-3g
/system/etc/ppp/chat-3g-connect
/system/etc/ppp/chat-3g-disconnect
/system/etc/ppp/pap-secrets
/system/etc/ppp/chap-secrets
Now heres what goes in them...
/system/etc/ppp/peers/cdma
Code:
file /system/etc/ppp/options-3g
connect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-connect'
disconnect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-disconnect'
user three
/system/etc/ppp/peers/cdma_h
Code:
file /system/etc/ppp/options-3g
connect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-connect'
disconnect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-disconnect'
user three
/system/etc/ppp/peers/cdma~
Code:
file /system/etc/ppp/options-3g
connect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-connect'
disconnect '/system/xbin/chat -v -f /system/etc/ppp/chat-3g-disconnect'
user three
/system/etc/ppp/options-3g
Code:
/dev/ttyUSB3
921600
nolock
crtscts
modem
passive
novj
defaultroute
noipdefault
usepeerdns
noauth
hide-password
debug
nodetach
ipcp-accept-local
ipcp-accept-remote
/system/etc/ppp/chat-3g-connect
Code:
ABORT "BUSY"
ABORT "NO CARRIER"
ABORT "VOICE"
ABORT "NO DIALTONE"
ABORT "NO DIAL TONE"
ABORT "NO ANSWER"
ABORT "DELAYED"
ABORT "ERROR"
REPORT CONNECT
TIMEOUT 10
"" AT
OK AT+CGDCONT=1,"IP","3internet"
OK ATDT*99#
TIMEOUT 20
CONNECT ""
/system/etc/ppp/chat-3g-disconnect
Code:
ABORT "BUSY"
ABORT "ERROR"
ABORT "NO DIALTONE"
SAY "\nSending break to the modem\n"
"" "\K"
"" "\K"
"" "\K"
"" "\d\d+++\d\dATH"
SAY "\nPDP context detached\n"
/system/etc/ppp/pap-secrets
Code:
# client server secret IP addresses
three * three
/system/etc/ppp/chap-secrets
Code:
# client server secret IP addresses
three * three
Now Push all the files back into your slate and reboot.
Once you plug your modem in you will notice it show signal strength, however sometimes it requires you to set an APN up manually, but try a hard reset first if that fails, this is how to do it...
Settings > Wireless & Networks > Mobile Networks > Access Point Names
Name : Anything
APN : 3internet
Username : three
Password : three
Authentication Type : PAP or CHAP
and thats really all there is to it!
nitr0genics said:
hey guys n gals, iv been reg'd a few days now n thought id make my first post a worth while one
Hello !!! I received 180 ZT 1030 and have upgraded the firmware. Now I want to use ZTE 3G modem mf100 follow your instructions but still not on the internet. I live in Russia and the Beeline network using WCDMA. Looking forward to your help. Excuse my English . Thanks !!!
Click to expand...
Click to collapse
Hi nitr0genics,
I tried this with Frojo and it works perfect . Thank you for this also to all other experts.
(google translate, hope you understand )
Hi people
I read the surfstick from german provider 1und1 (ZTE MF110) to run in the ZT-180. Do any of you can experience the driver has to extract? i will use the stick in my gome flytouch2
thx
working on android
hello, does anyone know if this means that we can use the MF110 on any android device with froyo??
thanks
”You will need to Pull the following files from your slate
note: some files may not exist so you will have to create them
/system/etc/ppp/peers/cdma
/system/etc/ppp/peers/cdma_h
/system/etc/ppp/peers/cdma~
/system/etc/ppp/options-3g
/system/etc/ppp/chat-3g-connect
/system/etc/ppp/chat-3g-disconnect
/system/etc/ppp/pap-secrets
/system/etc/ppp/chap-secrets”
How can i make these files, because if iuse notepad those are no more executabiles ?
So on my tablet, there is no option in "Application Settings" to turn on USB debug.
I have root and su access and a terminal.
Is there a command in terminal I can issue to turn USB debug on?
On my phone its saved at
/data/property/persist.service.adb.enable
Maybe its the same on your tablet?
Edit: If its in the same place this command should work.(not tested - use at own risk! - worst case scenario...wipe data).
echo 1 > /data/property/persist.service.adb.enable
Sent from my HTC Desire using XDA App
Bingo! That got me going.
Ran that command as 'su'
It didn't come back with any errors, so I assumed it worked.
Plugged into the computer, said recognize device. Listd it as a <NULL><NULL> USB Device.
Go to my My Computer, and it shows an E: drive, but cannot open it. I select to Mount my USB in the notification area and now I can see my SD card.
The code
mercianary said:
On my phone its saved at
/data/property/persist.service.adb.enable
Maybe its the same on your tablet?
Edit: If its in the same place this command should work.(not tested - use at own risk! - worst case scenario...wipe data).
echo 1 > /data/property/persist.service.adb.enable
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
_______________________________________________________________________________________________________________________
Where did you find where that is saved?
Wow! mines located there too and I can change to 1/0 by editing it through text editor program
just so you guys know. what seemed to work for me was to
go to about phone or tablet under settings
scroll to bottom where it shows build number
tap build number 7 times
developer window now shows. This works in android 4.2
This works from a terminal emulator (with root permissions) and from TWRP or any other terminal supporting recovery:
WARNING
Only use this method if you are sure the property files are located under /data/property/...
Enable adb functions:
Code:
echo 1 > /data/property/persist.service.adb.enable
echo 1 > /data/property/persist.service.debuggable
echo adb > /data/property/persist.sys.usb.config
Disable adb function:
Code:
echo 0 > /data/property/persist.service.adb.enable
echo 0 > /data/property/persist.service.debuggable
echo mass_storage > /data/property/persist.sys.usb.config
If it worked for you, a thank you is always appreciated!
Hello everyone,
I have an issue on my research. I rooted my samsung galaxy s2 using CWM method.
now i notice that my device is running only on one core(cpu0). I need help how to enable second core(cpu1) active always.
i used the commands,
adb shell
su
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
cat /sys/devices/system/cpu/cpu1/online
0
how to solve this issue. can anyone help me to find a way to make the second core active.
Thanks in advance,
--Ravi
ravipgm said:
Hello everyone,
I have an issue on my research. I rooted my samsung galaxy s2 using CWM method.
now i notice that my device is running only on one core(cpu0). I need help how to enable second core(cpu1) active always.
i used the commands,
adb shell
su
chmod 666 /sys/devices/system/cpu/cpu1/online
echo 1 > /sys/devices/system/cpu/cpu1/online
cat /sys/devices/system/cpu/cpu1/online
0
how to solve this issue. can anyone help me to find a way to make the second core active.
Thanks in advance,
--Ravi
Click to expand...
Click to collapse
Multi core devices turn unused cores off until they are needed (I believe) to save on battery life, the core will be there when its needed, so unless yyour getting some crazzy lag and the cores never active then all should be working normaly
Hello everyone, i'm new to this forum, so i'm not sure if i should ask for help here, but anyway.
I'm trying to do a data call using adb shell (also i view logs using logcat), but i can't find the modem file. I've read this article http://forum.xda-developers.com/showthread.php?t=1471241 but i didn't help me.
When i execute cat /proc/tty/drivers i get the following:
Code:
/dev/tty /dev/tty 5 0 system:/dev/tty
/dev/console /dev/console 5 1 system:console
/dev/ptmx /dev/ptmx 5 2 system
/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
rfcomm /dev/rfcomm 216 0-255 serial
g_serial /dev/ttyGS 237 0-3 serial
serial /dev/ttyS 4 64-67 serial
pty_slave /dev/pts 136 0-1048575 pty:slave
pty_master /dev/ptm 128 0-1048575 pty:master
unknown /dev/tty 4 1-63 console
Looks like i shoud send commands to /dev/ttyGS0, but it doesn't reply. I've tried the following commands:
Code:
echo "AT\r" > /dev/ttyGS0
echo "ATD12345678900;\r" > /dev/ttyGS0
but nothing happens. Actually, i'm not sure that i have to send commands to this file, but others don't reply too. So, i'm asking for help to do a data call, thanks in advance.
Also i have huawei P1 XL (u9200) and LG P765, which are based on similar chipsets, but for some reason i can't make data call with huawei, but can do it with LG. All devices are rooted. If u have any suggestions please let me know=)
Hey there.
I'd love to enable the diagnostic mode in my Nexus 5 so that I can trace the radio interface with software such as QXDM, X-CAL, etc... but I've had no luck so far.
basically I'm trying to change the variable sys.usb.config to [diag,adb] as shown in this post for the Nexus 4. I'm doing:
> su -c 'setprop sys.usb.config diag,adb'
(if you run getprop you see that the correct order is sys.usb, not usb.sys as shown in that post)
However, when I enter this command the phone automatically reboots... and the value is reverted back to [mtp,adb].
Any ideas? Do you know of any 'friendlier' way to enable diag mode on the Nexus 5? For example, in the Galaxy S4 you can just dial *#0808# to get into the USB config menu, which easily allows you choose the DM mode... but I can't find a similar menu on the Nexus 5.
Seems a bit absurd to me that a developer-oriented phone is the hardest one to put in diag mode... :/
Note: I'm rooted.
my phone is the same situation
prometheusZ said:
my phone is the same situation
Click to expand...
Click to collapse
I'm seeing the same thing.
Code:
[email protected]:/ $ su -c 'setprop sys.usb.config diag,adb'
[email protected]:/ $ getprop sys.usb.config
mtp,adb
Was this a change in AOSP? Might have to dig through the sources to see what changed.
---------- Post added at 04:56 PM ---------- Previous post was at 04:52 PM ----------
For what it's worth I can get that to change in recovery, but it doesn't enable anything else.
Code:
setprop sys.usb.config diag,adb
~ # getprop sys.usb.config
diag,adb
satadru said:
I'm seeing the same thing.
Code:
[email protected]:/ $ su -c 'setprop sys.usb.config diag,adb'
[email protected]:/ $ getprop sys.usb.config
mtp,adb
Was this a change in AOSP? Might have to dig through the sources to see what changed.
---------- Post added at 04:56 PM ---------- Previous post was at 04:52 PM ----------
For what it's worth I can get that to change in recovery, but it doesn't enable anything else.
Code:
setprop sys.usb.config diag,adb
~ # getprop sys.usb.config
diag,adb
Click to expand...
Click to collapse
i have done this with cm11, but the result was the same
prometheusZ said:
i have done this with cm11, but the result was the same
Click to expand...
Click to collapse
I'm definitely seeing that this works on d2 devices with cm11. I wonder if it works on the LG G2, since that is similar inside.
The problem is that this needs to be run as root, with SELinux disabled.
You can set SELinux to permissive with this tool: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
As per here:http://forum.xda-developers.com/showpost.php?p=39686712&postcount=3 the usb init script for hammerhead should tell us the steps for diag mode.
That hammerhead init script is here: https://android.googlesource.com/device/lge/hammerhead/+/kitkat-release/init.hammerhead.usb.rc
Here's the essence, if you want to run it from your own script:
Code:
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 61F1 > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo smd > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
setprop sys.usb.state diag,adb
Here's what you need to do from a shell, either via adb shell or a shell from a console app:
Code:
su
setprop sys.usb.config diag,adb
The device immediately disconnects you.
When I do a
Code:
getprop sys.usb.config
from a console on the device it does show diag,adb mode but I'm not seeing a device showing up when I connect the adb cable.
dmesg on the device (needs to be run as su) shows this error:
Code:
adb release
dwc3 f920000.dw3: request ed50b780 was not queued to ep0out
mtp_release
adb_open
android_usb_gadget: unable to get diag usb channel
diag: Cannot open channel 'diag'
android_bind_enabled_functions: diag failed
andoird_enable:usb_add_config failed: err: -19
adb_open
mtp_release
satadru said:
The problem is that this needs to be run as root, with SELinux disabled.
You can set SELinux to permissive with this tool: https://play.google.com/store/apps/details?id=com.mrbimc.selinux
As per here:http://forum.xda-developers.com/showpost.php?p=39686712&postcount=3 the usb init script for hammerhead should tell us the steps for diag mode.
That hammerhead init script is here: https://android.googlesource.com/device/lge/hammerhead/+/kitkat-release/init.hammerhead.usb.rc
Here's the essence, if you want to run it from your own script:
Code:
stop adbd
echo 0 > /sys/class/android_usb/android0/enable
echo 1004 > /sys/class/android_usb/android0/idVendor
echo 61F1 > /sys/class/android_usb/android0/idProduct
echo 239 > /sys/class/android_usb/android0/bDeviceClass
echo 2 > /sys/class/android_usb/android0/bDeviceSubClass
echo 1 > /sys/class/android_usb/android0/bDeviceProtocol
echo smd > /sys/class/android_usb/android0/f_acm/acm_transports
echo diag > /sys/class/android_usb/android0/f_diag/clients
echo acm,diag,mtp,adb > /sys/class/android_usb/android0/functions
echo 1 > /sys/class/android_usb/android0/enable
start adbd
setprop sys.usb.state diag,adb
Here's what you need to do from a shell, either via adb shell or a shell from a console app:
Code:
su
setprop sys.usb.config diag,adb
The device immediately disconnects you.
When I do a
Code:
getprop sys.usb.config
from a console on the device it does show diag,adb mode but I'm not seeing a device showing up when I connect the adb cable.
dmesg on the device (needs to be run as su) shows this error:
Code:
adb release
dwc3 f920000.dw3: request ed50b780 was not queued to ep0out
mtp_release
adb_open
android_usb_gadget: unable to get diag usb channel
diag: Cannot open channel 'diag'
android_bind_enabled_functions: diag failed
andoird_enable:usb_add_config failed: err: -19
adb_open
mtp_release
Click to expand...
Click to collapse
yes i got these messages too. does they mean google disable the diag channel on hardware level?
I suspect a software and not a hardware issue. Maybe compare kernel sources with that on the LG G2 and also that for the Nexus 4...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:23 AM ---------- Previous post was at 10:23 AM ----------
Or maybe a kernel module in the source just isn't getting built.
Sent from my SCH-I535 using XDA Premium 4 mobile app
satadru said:
I suspect a software and not a hardware issue. Maybe compare kernel sources with that on the LG G2 and also that for the Nexus 4...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:23 AM ---------- Previous post was at 10:23 AM ----------
Or maybe a kernel module in the source just isn't getting built.
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
"unable to get diag usb channel" maybe is the key of this problem, i guess
I think so. But it seems silly to disable a diag channel in hardware in case there's a problem...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
We might also be able to check the diag functionality by looking at other devices that also have a Qualcomm MDM9x25 chipset, which is only in newer devices...
Sent from my SCH-I535 using XDA Premium 4 mobile app
could you locate the source code witch throws this err?
Sent from my Nexus 5 using xda app-developers app
satadru said:
I think so. But it seems silly to disable a diag channel in hardware in case there's a problem...
Sent from my SCH-I535 using XDA Premium 4 mobile app
---------- Post added at 10:38 AM ---------- Previous post was at 10:35 AM ----------
We might also be able to check the diag functionality by looking at other devices that also have a Qualcomm MDM9x25 chipset, which is only in newer devices...
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
found this err in /kernel/msm / android-msm-flo-3.4-kitkat-mr0 / drivers / usb / gadget / f_diag.c
int diag_function_add(struct usb_configuration *c, const char *name,
int (*update_pid)(uint32_t, const char *))
{
struct diag_context *dev;
struct usb_diag_ch *_ch;
int found = 0, ret;
DBG(c->cdev, "diag_function_add\n");
list_for_each_entry(_ch, &usb_diag_ch_list, list) {
if (!strcmp(name, _ch->name)) {
found = 1;
break;
}
}
if (!found) {
ERROR(c->cdev, "unable to get diag usb channel\n");
return -ENODEV;
}
......
......
}
prometheusZ said:
found this err in /kernel/msm / android-msm-flo-3.4-kitkat-mr0 / drivers / usb / gadget / f_diag.c
Click to expand...
Click to collapse
Does the Galaxy S4 also use the same chipset? The kitkat kernel sources for that (at least the google edition model) just got released too.
We might be able to do a diff on the usb trees inside the kernel source and see if there's a difference. Probably also makes sense to compare the the source out there for the LG G2 model too, since that's going to be very close to our model.
Also have you seen the work they're trying to do with the LG G2 with qpst here: http://forum.xda-developers.com/showthread.php?t=2493659?
We might want to combine our efforts.
satadru said:
Does the Galaxy S4 also use the same chipset? The kitkat kernel sources for that (at least the google edition model) just got released too.
We might be able to do a diff on the usb trees inside the kernel source and see if there's a difference. Probably also makes sense to compare the the source out there for the LG G2 model too, since that's going to be very close to our model.
Also have you seen the work they're trying to do with the LG G2 with qpst here: http://forum.xda-developers.com/showthread.php?t=2493659?
We might want to combine our efforts.
Click to expand...
Click to collapse
my friends and i recompile the kernel with choosing "usb qualcomn diagnostic bridge driver" option, and made a boot.img. after flash the boot.img, the diag mode still can not open and the error messages are the same
prometheusZ said:
my friends and i recompile the kernel with choosing "usb qualcomn diagnostic bridge driver" option, and made a boot.img. after flash the boot.img, the diag mode still can not open and the error messages are the same
Click to expand...
Click to collapse
Is the qualcomm bridge driver loaded in the LG G2 kernel?
If it isn't enabled in the N5 kernel, it's possible that they didn't bother updating the code for it. Will the LG G2 kernel load on our device? They're definitely able to get diag mode on their device.
satadru said:
Is the qualcomm bridge driver loaded in the LG G2 kernel?
If it isn't enabled in the N5 kernel, it's possible that they didn't bother updating the code for it. Will the LG G2 kernel load on our device? They're definitely able to get diag mode on their device.
Click to expand...
Click to collapse
wo tried and succeed. finally the diag mode is opened. you can try recompile the kernel by choosing these options
Awesome. Can somebody upload the modified kernel image with the diag kernel?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Yippeee!!!
satadru said:
Awesome. Can somebody upload the modified kernel image with the diag kernel?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yup...eagerly waiting for the modified kernel and exact command to get it working.
:good:
enable diag mode : Boot_with_diag.img
- bbs.gfan.com/android-6953114-1-1.html
- pan.baidu.com/s/1sxMe1
satadru said:
Awesome. Can somebody upload the modified kernel image with the diag kernel?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
use fastboot command to flash this image