Hi,
My essential is already rooted and i have tried the below commands:
mata:/ # setprop sys.usb.config diag,adb
mata:/ # getprop sys.usb.config
diag,adb
However still nothing in device manager in terms of a diagnostics port being recognized.
Any help is appreciated, Thanks.
have you solved it?im the same question.
involves installing software on pc but check this out https://www.youtube.com/watch?v=W1KZi5Jubqc
The_Automator said:
involves installing software on pc but check this out
Click to expand...
Click to collapse
im sure no use
Found it, just run:
Code:
setprop sys.usb.config diag,serial_cdev,rmnet,adb
As root.
Worked for me with latest (2018.10.) ROM after the phone is rooted.
jackzhu said:
im sure no use
Click to expand...
Click to collapse
i cant find this in the last AndroidTools version
ARDV said:
i cant find this in the last AndroidTools version
Click to expand...
Click to collapse
If you have a rooted phone, use the "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command as root in a terminal emulator.
ktmom said:
If you have a rooted phone, use the "setprop sys.usb.config diag,serial_cdev,rmnet,adb" command as root in a terminal emulator.
Click to expand...
Click to collapse
I'm using crdroid with rooted lg g2 d800. After writing that command nothing changes in pc.
I slso tried this with samsung s5 with havoc rom and nothing changes after that command.
ARDV said:
I'm using crdroid with rooted lg g2 d800. After writing that command nothing changes in pc.
I slso tried this with samsung s5 with havoc rom and nothing changes after that command.
Click to expand...
Click to collapse
You do realize this is a thread specific to the essential PH-1, right?
Related
I have troubles with developer mode on my phone.
Enable usb debug option is checked, but adb (running under gentoo linux, ubuntu, windows 7) doesn't show any devices.
But when recovery (CWM) is loaded, everything works well.
When I'm trying to start adbd with
Code:
#adbd start
I get message "cannot bind tcp:5037"
I thought it appears because adbd is already running but
Code:
ps aux | grep adb
gives nothing
Any ideas what to do? Does anyone have problems with adb even if Usb debug is turned on?
I use Debian and my command is adb start-server.
Give it a try.
Fr0zen1977 said:
I use Debian and my command is adb start-server.
Give it a try.
Click to expand...
Click to collapse
It doesn't help
Shtsh said:
...But when recovery (CWM) is loaded, everything works well...
Click to expand...
Click to collapse
Looks like ROM problem. Did you tried another one??
Yes. I'm tried several stock ROMs (2.3.6, 2.3.5), cranium, broodROM. Factory reset doesn't help.
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
feered said:
Has anyone gotten this to work? When I type ADB devices, I get:
Code:
????????? no permissions
I rebooted into fastboot with no luck either. Except now ADB doesn't even pick up any devices. And yes, I enabled USB debug mode and unauthorized sources.
Thanks!
Click to expand...
Click to collapse
Which OS are you using (Windows, Mac, Linux)?
Elrondolio said:
I'd guess you are using an older version of the toolkit. Try downloading the latest SDK and using it to see if that helps (it'll also update to the latest drivers). Good luck.
Click to expand...
Click to collapse
It's the latest SDK.
bsara said:
Which OS are you using (Windows, Mac, Linux)?
Click to expand...
Click to collapse
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Hope this helps someone. Cheers!
feered said:
Linux - Ubuntu to be more specific.
So I figured out the issue. I rebooted into the bootloader (unplug NP, plug it back in, immediately hold the button located on the bottom of the player until the light flashes), typed fastboot devices and it finally recognized the device. ADB still however did not recognize the device while in the bootloader until I powered it back on. Very strange... Not sure if the order I did things made a difference but I'm able to connect to the interface now.
Click to expand...
Click to collapse
I had the same issue on Ubuntu. You need to run ADB with sudo...why? I have no idea...but I found a post suggesting it on StackOverflow and it worked...so I'm not questioning it.
Before doing anything below, have you installed adb via apt-get? If so, remove it and just put a link to your SDK manager adb and fastboot in a folder included in your PATH or add the directory to the path, then start a new shell before proceeding. The adb and fastboot provided by apt-get are old.
Do the following:
Have your device plugged in and fully booted and with USB debugging enabled
run this command: "sudo adb kill-server && adb start-server"
You should be prompted on the device to authorize the access of your computer via adb
run "adb devices" to make sure that it all worked correctly
Hello, I have att model of G2 which doesnt natively support 800 frequency,here in my country i cant get lte signal because of that.can it somehow be added to supported ones? thanks for your attention
Im in the exact same situation as you. This is what I have found:
Apparently, devices as the G2 with Qualcomm CPU's can unlock bands, and to do so you need to follow this:
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
BUT, the funny thing is that i cant get the G2 into "DIAG mode". And thats what is stoping me from doing it.
If you find the way to enter into DIAG MODE, tell me
Eminemiero said:
Im in the exact same situation as you. This is what I have found:
Apparently, devices as the G2 with Qualcomm CPU's can unlock bands, and to do so you need to follow this:
http://forum.xda-developers.com/cro...ad-progress-please-leave-im-updating-t2871269
BUT, the funny thing is that i cant get the G2 into "DIAG mode". And thats what is stoping me from doing it.
If you find the way to enter into DIAG MODE, tell me
Click to expand...
Click to collapse
Code:
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
tide and wave said:
Code:
adb shell
su
echo 1 > /sys/devices/platform/lg_diag_cmd/diag_enable
setprop sys.usb.config acm,diag,mtp,adb
Click to expand...
Click to collapse
didnt work
Hi all,
After unlocking/recovery/rooting via Heisenberg's guide, I then tried to connect to my Amazon FireTV via Terminal Emulator, but when I try any adb command from it, it says:
/system/bin/sh: adb: not found
What am I missing or forgetting to do? Thanks.
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
zephiK said:
adb is computer -> phone connection. Adb cannot be used in terminal emulator.
Click to expand...
Click to collapse
I've been using the same ADB commands in Terminal Emulator on my Android phones for years...
Anyone?
Anyone? Would really like to be able to connect to all my Android devices...
Can anyone help me with this? I can't find anything online and surprised no one else is asking about the issue...
Same issue was posted here on reddit FYI: https://www.reddit.com/r/AndroidQue.../adb_tool_no_longer_available_on_marshmallow/
How can we connect to other Android devices via Android 6.0 devices if this no longer works?
Yesterday I re-installed all the Drivers (Intel Drivers, iSOC drivers and PC Link) and wrote IMEI (IMEI was 0049 then), it wrote successfully but just after writing it, the phone stopped showing in computer. I checked Device Manager and it is showing there, ADB commands are working even, in this state. When I connect my phone, it shows the phone just for 1 sec and then the icon disappears but is still connected coz I can do everything except copy-paste. Please help.
P.S.: I also tried to uninstall the drivers and install again, no luck. Actually, here's the log of Instel USB drivers:
Code:
x64 os
Windows version: 7
Installing drivers, please wait
drvinstall.exe intc_usbcomp.inf returned 0
drvinstall.exe intc_cdcserial.inf returned 0
drvinstall.exe intc_rndis.inf returned 0
drvinstall.exe intc_mtp.inf returned 0
drvinstall.exe intc_adb.inf returned 0
drvinstall.exe intc_dvctrace.inf returned 0
Thanks in advance! :good::highfive:
You got imei problem again bro?
adb shell "su -c rm /data/property/persist.system.at-proxy.mode"
adb reboot
paktepu said:
You got imei problem again bro?
adb shell "su -c rm /data/property/persist.system.at-proxy.mode"
adb reboot
Click to expand...
Click to collapse
No Bro, everything is working fine except that I can't copy to and from my phone via PC. Would this command do this (I mean show my phone in PC)?
cy56 said:
No Bro, everything is working fine except that I can't copy to and from my phone via PC. Would this command do this (I mean show my phone in PC)?
Click to expand...
Click to collapse
this cmd will make your phone into SoC mode, writting IMEI
adb shell "su -c rm /data/property/persist.system.at-proxy.mode"
and this cmd will make phone to normal mode
adb shell "su -c setprop persist.system.at-proxy.mode 2"
Sent from my ASUS_T00F using XDA-Developers mobile app
paktepu said:
this cmd will make your phone into SoC mode, writting IMEI
adb shell "su -c rm /data/property/persist.system.at-proxy.mode"
and this cmd will make phone to normal mode
adb shell "su -c setprop persist.system.at-proxy.mode 2"
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
So, if the IMEI is working absolutely fine, should I only use the second command? Or still I have to use both commands?
cy56 said:
So, if the IMEI is working absolutely fine, should I only use the second command? Or still I have to use both commands?
Click to expand...
Click to collapse
look at writting imei thread.
first cmd to writting imei, here your phone only detect as SoC.
If we missing run second cmd, the phone will never detect as normally. Look at device manager, is it show SoC?
Sent from my ASUS_T00F using XDA-Developers mobile app
paktepu said:
look at writting imei thread.
first cmd to writting imei, here your phone only detect as SoC.
If we missing run second cmd, the phone will never detect as normally. Look at device manager, is it show SoC?
Sent from my ASUS_T00F using XDA-Developers mobile app
Click to expand...
Click to collapse
Whoa!! Miracle!!!!! Phone got scared now showing in PC without working on commands!!! Everytime!! Thanks bro!
I had same problems too, laptop didn't see the phone whenever i connect it to laptop. And imei showing null. Pressing vol up+power button showing nothing, i had to press vol up+power then when it vibrate unhold vol up and hold vol down to access the sleeping robot with no command. The only way to show the menu is by press and hold the same button trick.
My question is do i have to use the command above (both of them?) Or just flash downgrade firmware to get the imei back?
Sorry but this will be my first flashing zenfone since i'm used to flash samsung. Thank you very much.