Does anyone know if the Essential phone has a dial code, application, or method that will allow me to turn on Qualcomm Diagnositic Mode with RMNET and ADB?
I have RF testing software for my PC that interfaces with phones but I cannot get the Essential phone to be discovered because I cannot find those settings. I know on many other devices either the 0808 or 7284 dial codes worked.
I've already worked with the software developer, they support the chipset, but getting the phone to be recognized by the software is on me.
Any help would be appreciated.
abs0lutezer0 said:
Does anyone know if the Essential phone has a dial code, application, or method that will allow me to turn on Qualcomm Diagnositic Mode with RMNET and ADB?
I have RF testing software for my PC that interfaces with phones but I cannot get the Essential phone to be discovered because I cannot find those settings. I know on many other devices either the 0808 or 7284 dial codes worked.
I've already worked with the software developer, they support the chipset, but getting the phone to be recognized by the software is on me.
Any help would be appreciated.
Click to expand...
Click to collapse
Hi, where you able to solve this? I'm having the exact same problem
Hey! I was able to find the solution for this.
First you will need to root the phone with Android 7.1.1 Nougat (you can find the procedure in the forum or in youtube).
After phone is rooted, run the following ADB commands:
su
setprop persist.sys.usb.config diag,serial_cdev,rmnet,adb
setprop sys.usb.state diag,serial_cdev,rmnet,adb
setprop sys.usb.config diag,serial_cdev,rmnet,adb
Please note after entering "su" (super user) you'll need to grant superuser permissions (prompt shown on the phone).
After doing this, TEMS Investigation can detect and activate the phone, as you'll can see here. I assume other software (Nemo, XCAL, etc) should work as well.
Hope this helps!!
Related
Hi Folks,
I'm trying to send AT command and retrieve it's output via adb shell or an app.
I tried several stuff I already found here, like service ATFwdCmd but it didn't exist in MTK device.
I found with getprop that the "baseband" device must be on /dev/ttyC0 but on my device it didn't exist.
output of getprop
[rild.libargs]: [-d /dev/ttyC0]
[rild.libpath]: [/system/lib/mtk-ril.so]
So I started reversing the mtk-ril.so and found that there is a "property_get("mux.debuglog.enable")", and I tried to set this property with setpropex but it's not working too.
I tried using atinout tool at sourceforge with echo 'at+cops?' | atinout - /dev/ttyGS0 -. I also tried the MTK Engineering App and tried to enable full modem log, without luck again.
I'm stuck at here now, if anyone has an idea, i will be very happy to speak with him
PS: sorry for my bad english
Cheers,
Jon
hi, did you solved this ?
I also need to send AT commands on a MTK device, but I have no luck .
Using "cat /dev/pts/4 &" & "echo -e 'ATI\r' > /dev/pts/4" approach gives me no predictive response (the output is sent to logcat and ...partially to the above background process (even when calling "stop ril-daemon", i suspect this is doing nothing, the mtkrild process is still running, killing the mtkrild ..is no solution, the connectivity is lost).
Is there any reliable way we can use mtkrild directly to send AT Commands "
I'm trying to follow this guide to enable extra LTE band on my g2 d800.
Through hidden menu 3845#*800# I have set port settings -> Diag Setting -> USB
Also I've enabled Hardware key mode (all three back button on powering on -> Mode on)
However, QPST is unable to see my phone. I have to disable Show serial and USB /QC diagnostic port only to see the phone modem port. Also even after doing that and adding it, qpst doesn't detect phone
Any ideas of what might be causing it ? I'm using Windows 7 64-Bit as OS and Cloudy 3.3 w/ dorimanx 4.6 kernel and USB mode set to MTP
Mafioso said:
I'm trying to follow this guide to enable extra LTE band on my g2 d800.
Through hidden menu 3845#*800# I have set port settings -> Diag Setting -> USB
Also I've enabled Hardware key mode (all three back button on powering on -> Mode on)
However, QPST is unable to see my phone. I have to disable Show serial and USB /QC diagnostic port only to see the phone modem port. Also even after doing that and adding it, qpst doesn't detect phone
Any ideas of what might be causing it ? I'm using Windows 7 64-Bit as OS and Cloudy 3.3 w/ dorimanx 4.6 kernel and USB mode set to MTP
Click to expand...
Click to collapse
Dont bother. The bands have to be programmed into the radio antenna. Even if you do set the files to allow those bands without it being programmed into the antenna it wont do any good and you run a good chance of messing something up
zelendel said:
Dont bother. The bands have to be programmed into the radio antenna. Even if you do set the files to allow those bands without it being programmed into the antenna it wont do any good and you run a good chance of messing something up
Click to expand...
Click to collapse
Ok thanks As i found out also, it doesn't work on G2 but didn't know the reason...
BTW if anyone is stuck with same problem i.e. QPST not detecting port do below commands via adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Mafioso said:
Ok thanks As i found out also, it doesn't work on G2 but didn't know the reason...
BTW if anyone is stuck with same problem i.e. QPST not detecting port do below commands via adb shell
su
setprop persist.usb.eng 1
setprop usb.rndis.enable 1
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Click to expand...
Click to collapse
thank you
that makes the software detect my phone, but now i cant connect with it with mtp
i lost my imei after flash and i'm using qpst to recover it, when i click backup it tells me:
Memory Backup Failed
Disk Error while writing to file.
i need help please
i'm following this guide:
https://www.**********.com/how-to-backup-and-restore-lost-imei-on-lg-g2/
I am wondering around the internet to learn any method to disable MTP/PTP/all usb stuff except charging.
So, why i want this?
Because i want my device to be secure.
I don't anyone to sneak around and try to go into bootloader or recovery/connection to a pc etc to set my device to make a fresh start/copying data and end my privacy up.
So is there a way to disable those functions?
And if it is possible then what? Will it be secured?
And the big question is that can i enable it through recovery (from adb or moving mobile files) as you know if one has a messed up rom then he/she should have those functions workable.
.
@LGaljo?
@nik60?
@MAXSIMUS96?
@adityaupreti?
@Ciro?
@Renix63?
@sev3n1985?
delete mtpApplication.apk in syste/priv-app and in dev options..deflag debug usb
anyway ...not tried because i don't use pin in LS--but in S6 when phone is locked with pin is not recognized with PC
So will it disable the mobile to connect to a pc through bootloader?
I found this on a web:
.
The most device-compatible way to disable everything is to run this command at startup or set this in your build.prop:
Code:
setprop persist.sys.usb.config none
which is equivalent to charge-only on all Android devices.
That also disables adb. If you use adb regularly, then:
Code:
setprop persist.sys.usb.config adb
will allow adb when developer options are turned on/checked. If you don't use ADB often, I would not recommend it, because setting adb causes my S5 to still recognize in device manager, even when it is locked.
To restore original functionality,
Code:
setprop persist.sys.usb.config mtp,ptp,adb
allows all USB protocols.
I have a OnePlus 5 and I'm trying to get ADB to work in my Mac OS high Sierra. I have tried multiple threads and I still cannot get it to work. Whenever I enter ./adb devices it doesn't show my device under the listed devices and was wondering if anyone can help me
You don't need the ./
Just type adb devices
Also make sure you have USB debugging enabled in developer options
rickysidhu_ said:
You don't need the ./
Just type adb devices
Also make sure you have USB debugging enabled in developer options
Click to expand...
Click to collapse
thank you but I had figured out what happened. I was getting an error code so I used these adb & fastboot files in this link and it worked. https://dl.google.com/android/repository/platform-tools_r26.0.1-darwin.zip. it supposedly has a fix some people were working on. now everything works fine
Is adb not able to connect over even see these Joying FYT Airmont units with Oreo on it?
The head unit has a switch to allow debug over usb but when I connect a usb to my laptop I don't get the dialogue screen on the head unit asking if I want to connect to this device and the laptop cannot see the unit at all.
I figured maybe it needed device specific drivers in Windows so figuring Joying hasn't made any I found universal usb drivers for it. Nothing.
I got an app called Naptime or something that's supposed to be able to put the unit in full doze. It's designed to work on rooted devices but also says that can be worked around by using adb to give certain permissions. I can't do that if I can't even connect adb to the damn thing.
Also, is rooting these using that Magisk method result in the same type of full root the normal way on other devices? It isn't limited compared to the normal way is it?
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
rooted = rooted.
It doesn't make a difference in functionality whether the boot.img is rooted (called systemless rooting) or /system.
You always need an apk to "hand out" root rights, be it SuperSU, Superuser, Magisk or another.
In general the current systemless boot.img rooting is preferred. One of the big advantages is that it allows for OTA updates. But... we know that our units do not support that.
If you want to know more, just google for "systemless root" (sometimes "system-less root").
And I don't consider myself a guru. I read a lot and I have a good memory
Click to expand...
Click to collapse
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
rigattoni said:
If the USB connection does not work for any reason, you could try the following:
Some units (as mine SC9853i) ADB can be used by WiFi, if you first run some commands on the unit.
You need a shell app and run these commands:
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
reboot
After that you can connect via ADB from your laptop if both are in the same network.
Unfortunately that doesn´t work with all units.
Click to expand...
Click to collapse
These commands require root
surfer63 said:
You can't use adb over tcpip on these units.
You can use adb over usb. You have to enable the developer options (tapping it 7 times). Go out, go in, and you have the adb over usb (OTG) option which does require an OTG cable.
@rigattoni posted in one of the SC9853i threads a step-by-step approach if my one-liner doesn't give you enough info.
Click to expand...
Click to collapse
Maybe I'm doing something wrong then. The developer options are enabled and I have it set for unlocked bootloader but my laptop can't see it whether I'm connected through the OTG usb port or the standard one and the HU doesn't give the popup dialogue asking if I want to allow the connection like my tablet and phone did. Maybe they changed something with these particular units with the new UI?
I did notice on another thread someone that had a FYT Joying Airmont with 8.1 and they said something about the 3 dot menu on the top right for "USB Connection" that brings up two options both in Chinese an his only worked on the lower option. I did try that too but still nothing. IDK. Maybe I had something else set wrong when I tried that lower option that made it not work in all my effort yesterday to get adb to see it and connect.