i want to enter diagnostic mode in LOS14.1, i use command:
setprop sys.usb.config diag,adb
but it didn't work, pls help me,thk
kirtikhurana said:
Use this
Click to expand...
Click to collapse
i have try,but nothing change
kirtikhurana said:
you should be rooted unless it won't work.
Click to expand...
Click to collapse
i rooted,but these command work for lenovo offical rom,such as 048,062,232,244,251,not on los,any suggestion?
kirtikhurana said:
before that command i told. write the two.
adb shell
su
then diag commands.
during these commands your phone will prompt to grant permissions. Tap OK/Yes on phone
*remember to check Android bebugging Is ON in developer settings.
Even if you're unsuccessful you're probably doing wrong.
Click to expand...
Click to collapse
bro,setprop should be root,i know it,i use successful in lenovo offical rom, i told you,my question is: why not work for los,can you check it?
Related
I have my Evo rooted with DC 3.1.1 and I also have Nand Unlock via Toasts Way. But I did all of this using Windows. I already installed Android SDK for Mac. But every time I try to execute a command after I do the cd /android-sdk/tools. It just says -bash: adb: command not found. Can anyone give me a hand?
same issue for me
nitty917 said:
same issue for me
Click to expand...
Click to collapse
If you need help. PM Me.
Use ./adb instead of adb
BearCavalry said:
Use ./adb instead of adb
Click to expand...
Click to collapse
That wont help at all.
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Cakeor314 said:
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Click to expand...
Click to collapse
Use *#*#3424#*#*
purple patch said:
Use *#*#3424#*#*
Click to expand...
Click to collapse
Tried it. This gives you the functions test, not USB diagnostics.
Cakeor314 said:
Tried it. This gives you the functions test, not USB diagnostics.
Click to expand...
Click to collapse
Oh cool, that was just in memory lol. Can you use an app for diagnostic, not sure what you want to test. The only other one is *#*#4636#*#* I think.
purple patch said:
Oh cool, that was just in memory lol. Can you use an app for diagnostic, not sure what you want to test. The only other one is *#*#4636#*#* I think.
Click to expand...
Click to collapse
I don't think an app will work, thanks though. I'm trying to unlock the Canadian LTE bands. I just need to put the phone in USB diagnostics mode so I can use the modem tools on it.
Cakeor314 said:
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Click to expand...
Click to collapse
dude, i have the same question as you. i wanna enable the band 12 on my htc 10 unlocked version since i convert it to verizon RUU and sometimes wanna switch between my verizon and Tmobile sim cards. if i flash verizon RUU i cannot get band 12 but if i flash unlocked ruu i cannot get CDMA!!
---------- Post added at 09:21 AM ---------- Previous post was at 09:16 AM ----------
i am not sure whether this rom flash will work on that band problem but it says all carrier support
http://forum.xda-developers.com/htc-10/development/rom-21-02-viper10-1-0-0-tweaks-hub-t3379151
Has anyone figured out how to enable DM mode on the US Unlocked model? On Sprint and Verizon ##3424# works just fine.
Cakeor314 said:
Has anyone been able to access the USB diagnostics on the 10? Usually it's ##3424## but it either changed or it's blocked. I tried multiple ROMs with same results.
Click to expand...
Click to collapse
any luck on enabling diag mode on HTC 10?
i've tried the command bellow but its no luck.
Code:
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
kenter said:
any luck on enabling diag mode on HTC 10?
i've tried the command bellow but its no luck.
Code:
adb shell
su
echo 1 > /sys/devices/virtual/android_usb/android0/f_diag/func_en
Click to expand...
Click to collapse
adb shell "su -c 'setprop sys.usb.config rndis,diag,modem'"
or
adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
b8engl said:
adb shell "su -c 'setprop sys.usb.config rndis,diag,modem'" or adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
Click to expand...
Click to collapse
thanks mate. but already move from HTC 10. i do appreciate that
b8engl said:
adb shell "su -c 'setprop sys.usb.config rndis,diag,modem'"
or
adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
Click to expand...
Click to collapse
that worked for my htc 10 being recognized by nvr tools
but how do i revert this command? or better say, how do i turn off diag mode, magisk seems to crash at viewing my logs because of this
cigarpill said:
that worked for my htc 10 being recognized by nvr tools
but how do i revert this command? or better say, how do i turn off diag mode, magisk seems to crash at viewing my logs because of this
Click to expand...
Click to collapse
just replace the last entries...
adb shell "su -c 'setprop sys.usb.config adb,diag,acm'"
adb shell "su -c 'setprop sys.usb.config mtp,adb'"
I hope someone can help me here. I am looking to disable the annoying ugly heads up notifications that come on my phone.
I am rooted with magisk using OB4 8.1 Oreo. I also tried this on OB3 and it didn't work but I thought OB4 might work.
I have tried the terminal bmehtod and the dB method but both don't work for me. Is there a reason why or does anyone know a way to disable heads up. Thanks
Gravitybox allows you to disable them on a per-app basis or as a global setting.
Enable gaming mode
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
Code:
adb shell settings put global heads_up_notifications_enabled 0
hassan_1000 said:
I hope someone can help me here. I am looking to disable the annoying ugly heads up notifications that come on my phone.
I am rooted with magisk using OB4 8.1 Oreo. I also tried this on OB3 and it didn't work but I thought OB4 might work.
I have tried the terminal bmehtod and the dB method but both don't work for me. Is there a reason why or does anyone know a way to disable heads up. Thanks
Click to expand...
Click to collapse
Need to do su command twice, so "su"-> enter then again "su" - enter.
lockmunk said:
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
Code:
adb shell settings put global heads_up_notifications_enabled 0
Click to expand...
Click to collapse
i i want enable again what is the command
MsuatafaKhatab said:
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
i i want enable again what is the command
Click to expand...
Click to collapse
Change 0 to 1
vkass said:
Need to do su command twice, so "su"-> enter then again "su" - enter.
Click to expand...
Click to collapse
This worked for me. Thanks so much!
lockmunk said:
i use the same command as yours in adb, it works on OB4.
just add "adb shell" before the command.
Code:
adb shell settings put global heads_up_notifications_enabled 0
Click to expand...
Click to collapse
it does not work with Terminal Emulator. I tried with Terminal Emulator and can see the result as sh: adb: not found.
I haven't tried it with my PC.
I found an alternative methods to do this.
Application Method:
2- HeadsOff app method [FREE]
a) Install "HeadsOff - TickerOn" - https://play.google.com/store/apps/d...oheadsup&hl=en
b) Open the application.
c) Disable the Heads-Up notifications clicking on Settings.
d) Select "Start the App" button.
e) If a "Notification access" screen appears, allow the app to control your notifications by ticking it.
f) Reboot your phone.
g) Done!
Terminal Emulator Method:
3- Terminal method (directly from your phone) [FREE]
a) Install "Terminal Emulator for Android" - https://play.google.com/store/apps/d...roidterm&hl=en
b) Open the application. Use the following command:
Code:
su
c) The indicator should change from "$" to "#". Do the following command now:
Code:
settings put global heads_up_notifications_enabled 0
d) Reboot your phone.
e) Done!
Thanks to @1edson
Posting link: https://forum.xda-developers.com/android/general/howto-4-to-disable-heads-notifications-t3197660
Made a new thread as seems this is demanded option. Some people already checked this and looks like this works. I can't check right now but if you want, please check and post if it works for you.
Restriction is phone number country code based, can be bypassed. Also looks like its developers left setting to disable country checks at all. To do that, you just need to change android setting 'pixel.oslo.allowed_override' to '1' or 'true'.
Connect Pixel 4 with developer mode and execute command in adb shell:
Code:
adb shell setprop pixel.oslo.allowed_override true
or
Code:
adb shell "setprop persist.pixel.oslo.allowed_override true; setprop ctl.restart zygote"
or edit system/build.prop with some app (eg. MagiskHide Props Config)
You need root to do this.
Also there is Xposed Module in xposed manager to do this automatically called "EnableSoliOnPixel4", here's thread about it https://forum.xda-developers.com/pixel-4-xl/themes/success-enable-soli-china-t3994917
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Monazite said:
Do I need root permission to execute this command via adb? Thanks
Sent from my Google Pixel 2 using XDA Labs
Click to expand...
Click to collapse
Yes, without root you can’t edit system props
Eugnis said:
Yes, without root you can’t edit system props
Click to expand...
Click to collapse
getting failed to set property reply. any idea what i'm doing wrong?
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
omar5099 said:
getting failed to set property reply. any idea what i'm doing wrong?
Click to expand...
Click to collapse
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Kris Chen said:
Does it mean that I still can use soli in any country even that country doesn't support for it ?
For example, If I traveled to Japan one day, I still can use soli after enable soli by this xposed module ?
Kris
Click to expand...
Click to collapse
Yes, this setting just disable country check at all. So Soli will work worldwide
Eugnis said:
Looks like ADB not received root rights on phone. To check this use
Code:
adb shell su
if you receive response ' su: not found ' then you should enable root access for adb on phone (with supersu or similar)
Also you can set this prop with MagiskHide Props Config from phone if you used Magisk to root it
Click to expand...
Click to collapse
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Now I gotta root my phone and lose automatic updates just to be able to use it normally. Thanks a lot, Google!! _l_
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Bogega said:
I've obtained root for ADB shell via this command, however none of those 2 original adb lines are working. I'm still getting the failed to set property reply.
Any help appreciated...
Click to expand...
Click to collapse
yes same here, any1 got this to work ? thanks
Pixeling said:
You will still get automatic updates, you can root your phone, set the persistent property, and remove the root. Should persist across updates.
Click to expand...
Click to collapse
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
That's what I suspect since the property lives in /data which is not changed/erased after OTA. I've not tried it myself however that's probably what I will do when I get the phone.
aco.falc said:
So if I set the property and then unroot, it will persist even after OTA updates? No need to root again and set it again after every OTA?
Click to expand...
Click to collapse
Performing some more reading on the subject, there is a possibility that unlocking the bootloader by itself trips safetynet which in turn prevents OTA. I can't know whether this is true for sure, but in this case keeping Magisk root shall hide that and let you download the OTA.
Before applying the OTA you should use magisk to restore the boot.img, let the OTA install, and then let Magisk install itself to the other inactive flash slot where the OTA is. That will make sure that root is kept intact post update and keep hiding that the bootloader is unlocked. Can anyone confirm?
WORKED
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
sta3b said:
hello, i can confirm its working, steps to follow :
when u flash the magisk_patched image the phone wont boot at first, so u have to flash the boot.img then reflash the magisk_patched.
then the phone will boot normally.
after that, download terminal from play store, and type in it : SU , this will ask u for root permissions
then u need to type these 3 commands within the terminal :
setprop pixel.oslo.allowed_override true
setprop persist.pixel.oslo.allowed_override true
setprop ctl.restart zygote
then motion sense will turn on.
enjoy!
if u need detailed steps about the whole thing let me know
Click to expand...
Click to collapse
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Bogega said:
Can confirm that typing these commands in terminal did the trick. Used 'Terminal Emulator for Android' app from playstore.
And I skipped first steps (flashing boot.img etc) as I'm already rooted.
Thanks!
Click to expand...
Click to collapse
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
chris111111 said:
It works for me! Thank you!
Do I need to do this all over again when I reboot my phone?
Click to expand...
Click to collapse
Soli doesn't survive reboots if you're using this method.
There's a magisk module (non Xposed) which solves this though (https://forum.xda-developers.com/pixel-4-xl/themes/enable-soli-contries-magisk-module-t3997035)
wolfgangam31 said:
It seems that when rebooting the phone the soli is disabled again, can someone confirm?
Also I read here something about unrooting? can I really root and unroot everytime I want and retain OTA updates?
Click to expand...
Click to collapse
correct, rebooting the phone will cause SOLI to get disabled, you need to re-enter the commands in the terminal to get it to work again
Hello,
can someone name me the adb command for the DeveloperOptions?
Jens21 said:
Hello,
can someone name me the adb command for the DeveloperOptions?
Click to expand...
Click to collapse
Sorry, maybe i am missing something. What are you trying to do ? The only options in developer options are ADB and install unknown sources.
Michajin said:
Sorry, maybe i am missing something. What are you trying to do ? The only options in developer options are ADB and install unknown sources.
Click to expand...
Click to collapse
I only know the command "adb shell am start com.amazon.ssm/com.amazon.ssm.ControlPanel" but this opened the Developer Options. I search for the command to open directly the audio/video information. (it is the second option in Developer Options menu)