My speaker begins to crackle more than ever, even after a clean install of the official dev global rom. I have no tools nor knowledge about this repair, so Where can I buy a speaker in Europe and where can I find a video showing the repair?
I changed the speaker for a brand new speaker and the cracking is still here. so the problem is with the board.
blue whale said:
I changed the speaker for a brand new speaker and the cracking is still here. so the problem is with the board.
Click to expand...
Click to collapse
Try flashing global stable with fastboot.
I installed several fastboot roms and the crackling is here.
I am trying this
type this on terminal/command prompt:
adb shell setprop audio.offload.disable 0
adb shell setprop tunnel.decode true
adb shell setprop tunnel.audiovideo.decode true
adb shell setprop audio.offload.pcm.enable false
adb shell setprop tunnel.audio.encode true
adb shell setprop av.offload.enable true
adb shell setprop audio.offload.gapless.enable true
adb shell setprop persist.speaker.prot.enable true
adb shell setprop persist.audio.dirac.speaker false
from http://en.miui.com/forum.php?mod=viewthread&tid=368219
it reduces a bit the duration but there is still buzzing
the phones now buzzes like it always does. whatever I attempt, it goes back to buzzing.
Related
I found I can use these ADB commands to turn on and of the WiFi of a rooted phone:
Code:
adb shell su -c 'svc wifi enable'
adb shell su -c 'svc wifi disable'
However, I'm interested in doing it without having to root the phone for an automatic testing I'm doing. Do you guys know if this is possible?
I found this project which allows me to connect to a WiFi through ADB commands not being a root user. I was wondering if anyone knows how to disconnect also from ADB and not being a root user.
UPDATE:
I've been recently trying:
Code:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date. killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
and
Code:
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
I also found doing this type of command:
Code:
adb shell input keyevent 20 & adb shell input keyevent 23
I can navigate and click. The problem seems to be that I always finish in a different state so the next time I input the command
Code:
adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
I start in a different place and start clicking elsewhere. I've tried returning home, but that doesn't fix the issue. Is there any way to start always from the same point inside the WiFi settings?
Thanks!
natiya said:
I found I can use these ADB commands to turn on and of the WiFi of a rooted phone:
Code:
adb shell su -c 'svc wifi enable'
adb shell su -c 'svc wifi disable'
However, I'm interested in doing it without having to root the phone for an automatic testing I'm doing. Do you guys know if this is possible?
Click to expand...
Click to collapse
Turn WiFi off
Code:
adb shell settings put global airplane_mode_on 1
adb shell settings put global wifi_on 0
adb shell settings put global wifi_scan_always_enabled 0
Afterwards you've to re-boot the device.
Turn WiFi on
Code:
adb shell settings put global airplane_mode 0
adb shell settings put global wifi_on 1
adb shell settings put global wifi_scan_always_enabled 1
jwoegerbauer said:
Turn WiFi off
Code:
adb shell settings put global airplane_mode_on 1
adb shell settings put global wifi_on 0
adb shell settings put global wifi_scan_always_enabled 0
Afterwards you've to re-boot the device.
Turn WiFi on
Code:
adb shell settings put global airplane_mode 0
adb shell settings put global wifi_on 1
adb shell settings put global wifi_scan_always_enabled 1
Click to expand...
Click to collapse
Thank you, but those don't produce any change on my device. Actually, if I put the first two commands without doing "adb kill-server" in between, I get this message:
error: more than one device/emulator
Click to expand...
Click to collapse
But the output when they work is:
adb server is out of date. killing...
* daemon started successfully *
Click to expand...
Click to collapse
and nothing happens.
I've been recently trying:
Code:
C:\adb>adb shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
adb server is out of date. killing...
* daemon started successfully *
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
and
Code:
C:\adb>adb -s serial_number shell am start -a android.intent.action.MAIN -n com.android.settings/.wifi.WifiSettings
Starting: Intent { act=android.intent.action.MAIN cmp=com.android.settings/.wifi.WifiSettings }
Warning: Activity not started, its current task has been brought to the front
This opens the screen where you can turn on and off the WiFi but it doesn't do it...not sure if I'm missing something!
Just to be shure, make shure your using the latest version of ADB offered by google here:
https://developer.android.com/studio/releases/platform-tools
You could use adb wifi
After activating when using usb it and connecting through the same wifi:
svc wifi enable
works without root
I'm a little late to this thread, but if it still helps the OP, non-rooted Android 10 and below allowed wireless adb connections AFTER a USB connection was first established (adb start-server && adb tcpip 5555 && adb connect [IP]:5555), but that changed (for the better) in Android 11 and above with the new new Developer options Wireless debugging random port assignments (adb connect [IP]:[PORT] or adb pair [IP]:[PORT] [PIN]) such that the adb wireless connection never needs USB cable ever again.
Given Android 11 allows Developer options Wireless debugging via a random port, and Android 12 new Developer options Wireless debugging allows that to be accessed even easier with a new Developer options Wireless debugging tile, the only thing missing is a way to turn the non-rooted Android Wi-Fi on or off via adb (which was the OP's original question after all).
Maybe this will work if we can figure out how to tap the buttons?
adb shell "am start -a android.settings.WIFI_SETTINGS"
Click to expand...
Click to collapse
For swiping on the phone from adb this works...
C:\> adb shell input swipe 500 1000 500 100
This will instantly swipe from center to the top of the screen.
You can add a time period, e.g., take 3 seconds to swipe that.
C:\> adb shell input swipe 500 1000 500 100 3000
Click to expand...
Click to collapse
But you want to tap the buttons, right?
If we can figure out the positions, maybe this would work?
C:\> adb shell am start -n com.google.android.gms/.ads.settings.AdsSettingsActivity
That should pop up an Android "Reset Advertising ID" settings page.
C:\> adb shell input tap 500 400
If run after the command above, that will tap the button to
asking to "Opt out of Ads Personalization" in that Activity
if that button is like mine, at the X=500 & Y=400 location.
On my phone, this is the "Reset advertising ID" button location:
adb shell input tap 500 200
On my phone, this is the "OK" button on that GUI above.
adb shell input tap 700 1000
C:\> adb shell am force-stop com.google.android.gms
If run after bringing up the advertising-id reset Activity,
it will close the activity without doing anything else.
Click to expand...
Click to collapse
Here is a somewhat related post...
[adb,scrcpy,vysor] What ports does Android 12 randomly set when Wi-Fi connecting via Wireless debugging adb "pair" or "connect" commands?
Type adb tcpip 5555 in the command line or Terminal and press Enter.
Find your phone's IP address in Settings > About Phone > Status > IP Address.
Back in the command line or Terminal, type adb connect [your Android's IP address].
Finally, press Enter again.
Regards,
J Wick
Hi,
I read some information from users who do not have 5G available and Volte on calls.
Is this a problem that phone operators can fix or will a OnePlus fix be needed?
Thanks
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Pouic said:
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Click to expand...
Click to collapse
Any idea when it is going to happen?
Pouic said:
5G compatibility with missing carriers/ISP can only be fixed by OTA from OnePlus
VoLTE + WifiCalling can be fixed by OTA too or once we gain root in the future and we can modify radio system files ourselves
Click to expand...
Click to collapse
Is there a way to fix this now?
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
I have volte calls enabled by default but still doesnt work. Probably you also need support from your carrier and one plus will never exist for my carrier.
My Nord 2 isnt using VOLTE or VOWIFI with Sunrise. Is there a way to enable it like with older models?
*#800# does not work
No, we still need to wait for future OTA to resolve this
skyzonemc said:
My Nord 2 isnt using VOLTE or VOWIFI with Sunrise. Is there a way to enable it like with older models?
Click to expand...
Click to collapse
Hey,
If you go on the digitec website and search for your phone, you get a disclairmer about 5G and Sunrise. This isn't strictly related to your issue, but I was wondering if you were able to use the Swiss 5G network with your phone. Maybe you can try calling sunrise directly ?
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Worked! Thank you
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Do you know how to enable 5g? my phone doesn't seem to connect to any 5g network. 5g is not shown as an option in sim settings.
Sorry, I don’t know.
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Thanks for the info. Do you know how to enable voWifi (WiFi Calling) for Vodafone UK?
aathi1 said:
Do you know how to enable 5g? my phone doesn't seem to connect to any 5g network. 5g is not shown as an option in sim settings.
Click to expand...
Click to collapse
Hi, I had the same problem. Usually you can do this with *#*#4636#*#* to access the phone info but those codes don't work on this phone.
I installed an app called "5G switch" (not sponsored by any means), then you can access the menu, and selected NR/LTE/TDSCDMA/GSM/WCDMA, which makes 5G appear in the settings, and works with Yallo (Sunrise) as a carrier. Hope it helps!
DerSandmann said:
Hi, I had the same problem. Usually you can do this with *#*#4636#*#* to access the phone info but those codes don't work on this phone.
I installed an app called "5G switch" (not sponsored by any means), then you can access the menu, and selected NR/LTE/TDSCDMA/GSM/WCDMA, which makes 5G appear in the settings, and works with Yallo (Sunrise) as a carrier. Hope it helps!
Click to expand...
Click to collapse
I have tried that but it does not work for me. Even though I selected the NR/LTE.. it still hooks onto 4g. are you aware of any methods to modify the radio files.. Thnx.
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Hi,
This method didn't work for me (although I have to mention that the VoLTE toggle was present in the SIM settings since first use).
I'm currently on a Dutch provider called hollandsenieuwe which operates on Vodafone NL network.
The strange thing is that VoWiFi just works fine since first use.
I checked all the settings for VoLTE (even the one for the icon to appear in the top bar which is disabled by default but nothing).
Asked support to the provider but they just say that the issue is with the device.
I tested with the previous model Oneplus Nord 5G and VoLTE and VoWIFI both work fine, with Oneplus Nord 2 only VoWiFI is working.
Any suggestion?
Up.
Up.
No solution for now, we need to wait for oneplus to add the missing 5g/volte profiles in a next OTA... it could take a while or simply never arrive .
What commands should be entered instead of these to
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
everything as it was? I think the reason they lost wifi and bluetooth. They don't turn on at all...
A.15 update finally did it, since this morning I have 5G and VolTE working on my phone on swiss networks!
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Hi master, greetings from Chile. Sorry for my ignorance. I don't understand step 2. Would you please explain to me. I'm a dumb. Sorry
cerfaaa said:
VoLTE activation procedure on OnePlus Nord 2 5G:
If NoRoot:
1. Get ready to use the adb command
2. adb reboot recovery And reboot to recovery
3. When the language selection screen appears, you will be able to connect to adb, so wait until the driver setup is completed.
* If ⚠ is displayed in the device manager, the driver cannot be loaded, so right-click and see Update Driver → Computer. Search for the driver → Available on your computer ~ → Android Device → Load the Android Composite ADB Interface.
If that doesn't work, try plugging and unplugging the cable or using the USB 2.0 port.
4. Execute the following command line by line
adb root
adb shell setprop persist.dbg.ims_volte_enable 1
adb shell setprop persist.dbg.volte_avail_ovr 1
adb shell setprop persist.dbg.vt_avail_ovr 1
adb shell setprop persist.radio.VT_ENABLE 1
adb reboot
After restarting, "VoLTE call" will appear in the SIM settings, so turn it on.
If Rooted:
1. Install Termux from GP
2. Enter "su"
3.
setprop persist.dbg.ims_volte_enable 1
setprop persist.dbg.volte_avail_ovr 1
setprop persist.dbg.vt_avail_ovr 1
setprop persist.radio.VT_ENABLE 1
setprop persist.dbg.wfc_avail_ovr 1
reboot
Click to expand...
Click to collapse
Has there been any recent updates that could have broken step 3? Tested on both Windows and Linux but whenever it reboots into recovery mode, ADB never reconnects. Is there something else I'm missing?
McGinsky said:
Has there been any recent updates that could have broken step 3? Tested on both Windows and Linux but whenever it reboots into recovery mode, ADB never reconnects. Is there something else I'm missing?
Click to expand...
Click to collapse
Since A14 or A15 update, ADB is not available in recovery mode...
Some of build.prop adb commands, some of them have no real visible effects, but worth the try.
Perquisite:
1)Rooted
2) PC with ADB and fastboot
3)ADB debug enabled in phone
4) patience
Run in cmd , each line at a time.
adb shell su -c setprop persist.dbg.volte_avail_ovr 1
adb shell su -c setprop persist.dbg.vt_avail_ovr 1
adb shell su -c setprop persist.dbg.wfc_avail_ovr 1
adb shell su -c setprop persist.dbg.ims_volte_enable 1
adb shell su -c setprop persist.dbg.radio.rat_on 1
adb shell su -c setprop persist.radio.rat_on combine
adb shell su -c setprop persist.dbg.radio.data_ltd_sys_ind 1
adb shell su -c setprop persist.dbg.radio.data_con_rprt 1
adb shell su -c setprop persist.dbg.radio.calls.on.ims 1
adb shell su -c setprop persist.dbg.audio.fluence.voicerec 1
adb shell su -c setprop persist.dbg.audio.offload.passthrough 1
adb shell su -c setprop persist.dbg.audio.feature.anc_headset.enable 1
adb shell su -c setprop persist.dbg.audio.feature.hifi_audio.enable 1
adb shell su -c setprop persist.dbg.audio.feature.maxx_audio.enable 1
adb shell su -c setprop persist.dbg.audio.feature.wsa.enable 1
adb shell su -c setprop persist.dbg.audio.feature.audiozoom.enable 1
adb shell su -c setprop persist.dbg.surface_flinger.use_content_detection_for_refresh_rate 1
adb shell su -c setprop persist.dbg.audio.dolby.ds2.enabled 1
adb shell su -c setprop persist.dbg.audio.dolby.ds2.hardbypass 1
adb shell su -c setprop persist.dbg.audio.offload.multiple.enabled 1
adb shell su -c setprop persist.dbg.audio.offload.passthrough 1
adb shell su -c setprop persist.dbg.audio.safx.pbe.enabled 1
adb shell su -c setprop persist.dbg.audio.feature.ext_hw_plugin.enable 1
adb shell su -c setprop persist.dbg.audio.feature.record_play_concurency.enable 1
adb shell su -c setprop persist.dbg.enable_async_powermode 1
adb shell su -c setprop persist.dbg.display.use_smooth_motion 1
I have some idea about unlocking the bootloader OEM unlock menu but i don't know if we are able to.
The new system shell exploit allows us to set properties, if we can set read only system properties by using an ARM binary compiled with the ndk we might be able to unlock the oem unlock menu.
Does anyone know if we can execute a self built executable as a system user? can't find any way to execute the binary via adb it might be able via an app.... haven't been in android development for a while so don't know if this is possible.
If we are able to execute this tool we can do a lot on samsung maybe, the tool is available on https://github.com/liwugang/android_properties (as we can set system properties via the system user we might be able to set ro properties)
DaanNL said:
Does anyone know if we can execute a self built executable as a system user?
Click to expand...
Click to collapse
Hello and good morning, @DaanNL
Prior to your next posting please read the guidances that are stuck on top of every forum like
[Read Before Posting]QUESTIONS DO NOT BELONG IN GENERAL
Hello Everybody, In order to attempt to keep this forum neat and tidy the moderation team is asking you to post your questions into the Questions and Answers (Q&A) forum and not into the General section. You can find the Q&A forum by clicking...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
DaanNL said:
I have some idea about unlocking the bootloader OEM unlock menu but i don't know if we are able to.
The new system shell exploit allows us to set properties, if we can set read only system properties by using an ARM binary compiled with the ndk we might be able to unlock the oem unlock menu.
Does anyone know if we can execute a self built executable as a system user? can't find any way to execute the binary via adb it might be able via an app.... haven't been in android development for a while so don't know if this is possible.
If we are able to execute this tool we can do a lot on samsung maybe, the tool is available on https://github.com/liwugang/android_properties (as we can set system properties via the system user we might be able to set ro properties)
Click to expand...
Click to collapse
You do realize OEM toggle is absolutely useless for US Samsung devices. It's more of an eye sore and a big HA HA if you get it to spring to life, which is not easy to do. But i can say i haven't seen that repo ever. I'll ask the pro's what they think. Don't hold your breath though. The closest I've got to ever seeing it....is here. (See pic attached).
Ok, thanks for clearing that up....
This tool on github seems just to be an alternative to setprop and getprop even worse if you can't set props without root.
"Set operation need root first, and can set all the properties(include prefixed with 'ro').", can i ask you how that screenshot was been made? because for that option to appear ro properties need to be set.... and if we can set ro properties we might be able to do some fancy stuff.
I also don't understand why everybody is so focussed on unlocking bootloader, if we get root permissions we could just flash magisk onto the raw filesystem right?
DaanNL said:
Ok, thanks for clearing that up....
This tool on github seems just to be an alternative to setprop and getprop even worse if you can't set props without root.
"Set operation need root first, and can set all the properties(include prefixed with 'ro').", can i ask you how that screenshot was been made? because for that option to appear ro properties need to be set.... and if we can set ro properties we might be able to do some fancy stuff.
I also don't understand why everybody is so focussed on unlocking bootloader, if we get root permissions we could just flash magisk onto the raw filesystem right?
Click to expand...
Click to collapse
setprop persist.sys.adbroot
setprop sys.factory.runningFtClient true
setprop persist.sys.fflag.override.binary.type eng
setprop sys.factory.facm_mode 1
setprop persist.sys.recovery_update 1
setprop persist.sys.dm.verity.state disabled
setprop persist.sys.logkit.ctrl 0x7
setprop persist.sys.adb.secure 0
setprop persist.sys.root_access 3
setprop persist.sys.verity.log 1
setprop persist.sys.usb.ffs.ready 1
setprop persist.sys.enable_op_logs 1
setprop persist.sys.usb.ffs.ready 1
setprop persist.sys.debug.enable 1
setprop persist.sys.silent 1
setprop persist.nfc.debug_enabled ""
setprop persist.service.usb.hubport 1
setprop persist.sys.adoptable force_on
setprop persist.sys.virtual_disk true
setprop persist.service.adb.root 1
setprop service.adb.root 1
setprop persist.sys.usb.sport 2
setprop dev.silentlog.bootup On
setprop persist.sys.ssr.enable_ramdumps 1
setprop sys.mdlogproperty On
setprop sys.hidden.otatest 1
setprop sys.hiddenmenu.enable 1
setprop persist.sys.knox.sdp_cryptod false
setprop debug.atrace.tags.enableflags 1
setprop ril.preconfig.enable true
setprop ril.region_props TMB.XAA
setprop mdc.sys.carrierid_etcpath /prism/etc/carriers/XAA
setprop mdc.system.nw_path2 /optics/configs/carriers/XAA/conf/system
setprop mdc.vendor.nw_path2 /optics/configs/carriers/XAA/conf/system
setprop persist.sys.carrierid_etcpath /prism/etc/carriers/XAA
setprop persist.sys.omcnw_path2 /optics/configs/carriers/XAA/conf
setprop persist.sys.prev_salescode XAA
setprop persist.sys.prev_omcnwcode2 XAA
setprop persist.sys.fflag.override.settings_fuse true
setprop persist.sys.max_users 15
setprop persist.sys.show_multiuserui 1
setprop ro.build.official.developer true
setprop persist.sys.oem.otg_support true
setprop persist.ril.preconfig 1
setprop sys.dexopt.ctrl true
setprop security.perf_harden 0
setprop persist.sys.fflag.override.settings_dynamic_system true
setprop debug.atrace.tags.enableflags 1
setprop persist.sys.knox.device_owner false
setprop logd.logpersistd.enable true
setprop logd.ready true
setprop debug.slsi_platform 1
setprop persist.sys.fuse.passthrough.enable true
setprop sys.keep_app_1 com.samsung.SMT
setprop sys.keep_app_2 moe.shizuku.privileged.api
setprop service.adb.tcp.port 9995
setprop persist.sys.usb.qxdm.debug 1
setprop sys.usb.qxdm.debug 1
setprop presist.service.adb.enable 1
setprop persist.sys.usb.qxdm.debug 1
setprop sys.usb.qxdm.debug 1
setprop persist.security.perf_hardening 0
setprop persist.service.adb.enable 1
setprop service.adb.enable 1
setprop persist.rollback.is_test true
setprop persist.sys.get_unlock_ability 1
setprop sys.get_unlock_ability 1
setprop persist.sys.get_unlock_ability 1
setprop sys.oem_unlock_allowed 1
setprop persist.sys.oem_unlock_allowed 1
setprop debug.performance.tuning ""
setprop debug.qc.hardware ""
setprop debug.qctwa.preservebuf 1
setprop debug.qctwa.statusbar 1
setprop debug.egl.profiler 0
setprop ril.preconfig 1
setprop persist.sys.ui.hw 1
setprop debug.egl.force_msaa 1
setprop debug.sf.hw 1
setprop debug.egl.hw 1
setprop debug.sf.nobootanimation 1
setprop video.accelerate.hw 1
setprop debug.enable true
setprop debug.assert 1
setprop libc.debug.hooks.enable 1
setprop dumpstate.unroot false
device_config put exo is_exo_dogfood true
device_config put exo is_exo_eng true
device_config put privacy location_indicators_enabled true
device_config put privacy safety_center_is_enabled true
device_config put device_personalization_services Captions__enable_zero_day true
device_config put device_personalization_services Captions__enable_setting_page true
device_config put device_personalization_services Captions__enable true
device_config put privacy permissions_hub_enabled true
device_config put launcher ENABLE_SMARTSPACE_ENHANCED true
setprop persist.sys.debug.enable 1
setprop persist.sys.enable_op_logs 1
setprop persist.sys.usb.ffs.ready 1
setprop persist.sys.logkit.ctrl 0x7
setprop knox.kg.state kg_debug
setprop persist.sys.recovery_update 1
setprop persist.sys.dm.verity.state disabled
setprop persist.sys.logkit.ctrl 0x7
setprop persist.sys.adb.secure 0
setprop persist.sys.root_access 3
setprop persist.sys.verity.log 1
setprop persist.sys.usb.ffs.ready 1
setprop persist.sys.enable_op_logs 1
setprop persist.sys.usb.ffs.ready 1
setprop persist.sys.debug.enable 1
setprop persist.sys.oem_unlock_allowed 1
setprop persist.sys.fflag.override.binary.type eng
KILL OTA
settings put global ota_disable_automatic_update 1
settings put global galaxy_system_update_block -1
settings put global galaxy_system_update -1
WARNING
setprop persist.sys.boot.reason kernel_panic (KERNEL PANIC)
setprop persist.sys.max_users 15 <<can be any number other then 1 or two
setprop persist.sys.show_multiuserui 1
All these commands at one point were set with a system shell. Some props are still good and some are not. And to be very honest, i have absolutely no idea what combination of setprops i did, that allowed me to see what i saw. But the list is here. And this is the first time I have ever posted this on a public forum (only privately). But have at it and see what you can come up with.
*FAIR WARNING TO THOSE WONDERING EYES. DONT ASK ME ABOUT ANY OF THIS UNLESS YOU SOMEHOW FIND A PERFECT COMBO OF SETPROPS THAT TAKES YOU TO A HIGHER LEVEL KF PRIVILEGE*
Thanks for your reply....
Maybe it's still usefull
i think it was the setprop persist.sys.oem_unlock_allowed 1 which did the trick in old firmwares.... this showed the option but there where more requirements to be met... if i look at the code now they changed the properties.... i still think that if we would have root access we could enable all the required props to unlock the bootloader.... also found some file something like samsungmembers.dat which allowed downgrading oneui i think in beta..... the stupid thing is that i used my s7 for a long time and just bought this s10 as nothing has really changed in phone world.... i was just running all the updates but it had stock firmware but i'm sure we'll figure something out when an android kernel root exploit becomes available
DaanNL said:
Thanks for your reply....
Maybe it's still usefull
i think it was the setprop persist.sys.oem_unlock_allowed 1 which did the trick in old firmwares.... this showed the option but there where more requirements to be met... if i look at the code now they changed the properties.... i still think that if we would have root access we could enable all the required props to unlock the bootloader.... also found some file something like samsungmembers.dat which allowed downgrading oneui i think in beta..... the stupid thing is that i used my s7 for a long time and just bought this s10 as nothing has really changed in phone world.... i was just running all the updates but it had stock firmware but i'm sure we'll figure something out when an android kernel root exploit becomes available
Click to expand...
Click to collapse
Are you familiar with something called magic.bin? Also...
cp -R /data/log /sdcard
You'll thank me later....
wr3cckl3ss1 said:
Are you familiar with something called magic.bin? Also...
cp -R /data/log /sdcard
You'll thank me later....
Click to expand...
Click to collapse
You mean the script which probes for magic's at a binary file so you can extract usable content? or part of the bootloader....
Ahhh /data/log looks interesting.... i was into rom building and stuff with the galaxy s4 and made some android wear rom for the asus zenwatch.... long time ago
Think i found what you mean in the efs folder, but can't find any relation in the logs....
Check something called "recovery.log", you'll find info on /efs.
magic.bin for S22 Ultra but dead for S23 Ultra.
Yes i found that magic.bin before, but it's unknown to me what you can do with it...
wr3cckl3ss1 said:
Check something called "recovery.log", you'll find info on /efs.
magic.bin for S22 Ultra but dead for S23 Ultra.
View attachment 5882731View attachment 5882739View attachment 5882741
Click to expand...
Click to collapse
Yes i found that magic.bin before, but it's unknown to me what you can do with it...
Another step closer....