Hi, I have a problem, I keep receiving subscription ads requests, it seems that it is from my cellphone company, since you can see the sim image in there but I am not sure. This are some examples:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Background info: (running Android 6.01, 26.3.B.0.131)
So I used to be on a cell phone company which had this subcription ads request (Movistar), but I changed to another one which they say they do not have any of that (Tuenti), with the same number, and they are both owned by the same company (Otecel), so maybe some settings from the old operator were kept in the new ones, I have talk and talk and talk with them, and i just keep receiving this ads.
Is Root the solution?
Maybe if root my device, I can disable the sim services app, or I do not know something else, and I would not receive this ads again, or what do you guys recommend me.
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Pixelado said:
Hello, have you tried to 'adb hide' or 'adb disable' the STK apk? No root required AFAIK
Click to expand...
Click to collapse
No, I have not tried not, because I do not know how to do it, could you please teach me , please noob steps
Sorry for being so late haha.
I'll assume you're using Windows 7 or newer.
Steps:
- Get ADB and proper drivers for your devices (Flashtool ships with all of this)
- Enable dev settings on your phone
- Enable USB debugging. Disregard all warnings
- Connect your Xperia to your PC via USB cable
- Wait for drivers to install
- Open a terminal/command prompt on your PC, point it to a directory where you have an ADB executable (adb.exe) (you can do this by opening the flashtool libs folder, eg: c:\flashtool\x10flasherlib, and right-clicking anywhere on the window while keeping the SHIFT key pressed)
- Issue the following command:
-- adb devices
Your phone should ask for authorization now. Grant it
- Issue the following command(s):
-- adb shell (this gives you access to your device's terminal from your PC)
-- pm disable com.android.stk
If the above command fails, try:
-- pm hide com.android.stk
- You're done
You can avoid using a PC by using a terminal emulator on your device AFAIK. I might be wrong though.
Related
Hello everybody,
want to ask your advice in re: following issue
I am going to use nextbook NX868QW8G tablet as an embedded advertisement solution ie it should start when external power gets plugged in. I can find a normal tech desc of this model in the internet even on the official site.
It have almost the same look&hardware as NX785QC8G availabe at wallmart but have slightly another cpu mtk8382 and embedded 3g modem which was the decisive factor since we need tablets to be updated remotely.
Here are system settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have done the following:
1) rooted device via cydia impactor - root check apps from gplay are saying its rooted now + it has auto instaled chainfire SU to the tablet. For some reasons cydia impactor thinks its HTC ONE X. I have installed a PdaNetA4150 and it also considers it as HTC phone. I have tried to install drivers for nextbook8 I have found in internet but window doesnt recognize them as appropriate. At the moment device is recognized as unknown MT65XX Android phone
2) run adb reboot-bootloader
3) run fastboot oem unlock
4) run fastboot oem off-mode-charge 0
I have tried doing it manually and through cydia impactor but in both cases the command thread for #3 and #4 seems to be in an infinite sleep - just displays "..." in command line shell and cydia impactor simply gets frozen for a couple of minutes then throws timeout exception.
I think its waiting my input after #3 however the screen remains black and it does nothing when I press on vol up/down/power buttons. Fastboot prints "OK [X sec]" when I call fastboot reboot from another shell window.
In regards to the adb drivers and etc - device is visible through both 'adb devices' and 'fastboot devices' commands. For some reasons
Please advice in which direction to seach and digg.
Any help will be highly appreciated,
Max
Hi,
my Pixel 4 got stuck booting on the G logo. I tried rebooting from recovery, but no luck.
I sidloaded Android 11 hoping that would fix it, but no luck.
So my option I guess it's to factory reset. But in order to avoid losing data, can anyone give me pointers to backup the phone?
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Any help is appreciated
andreadoli96 said:
The bootloader is unlocked, but not rooted. Developer settings were enabled and usb debugging should on by default.
From recovery adb devices sees an unknown device I cannot successful run backup commands on as the device is unauthorized.
Click to expand...
Click to collapse
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
jwoegerbauer said:
You can't establish a valid ADB connection because on phone the ADB RSA keys didn't get confirmed
That's what the "unauthorized" ADB-message means.
FYI: When you click to always allow, Android appends the public key from ADB on the computer into a specific file ( /data/misc/adb/adb_keys ) on the phone.
Click to expand...
Click to collapse
So considering that I can't turn the phone on to confirm that is there a workaround?
@andreadoli96
Don't know whether this will work or not
Code:
adb devices
adb push %USERPROFILE%\.android\adbkey.pub /data/misc/adb/adb_keys
adb reboot
adb devices
Good luck.
BTW:
Take note that if your Android version has encryption enabled out of the box ( there’s no way to remove encryption !!! ) then trying to backup the user-data ( will say pulling them out by means of ADB ) may work, but is senseless because you can't decrypt them.
Since the last MIUI update I am experiencing an issue with notification. When using a video player (like Plex, VLC, YouTube Vanced), I usually see a notification icon when using background playback. This is now gone. Also, and this is the main issue actually, when I close the app I still see it in the notification center and when I swipe it away it still occupies the same space. The notifications below it won't move up. And when I put the phone in stand-by and then open it again, the multimedia notification is there again. The only way to get rid of it is to force close the app.
Is anybody else experiencing this ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i have the exact same issue after 12.5 update
Yes is a known bug of this release.
The only solution is by ADB
Open developer tools, connect by USB, and by ADB shell type the following command:
adb shell settings put secure qs_media_resumption 0
That's all
adb shell settings put secure qs_media_resumption 0
thank you, fixed the issue
rello1976 said:
Yes is a known bug of this release.
The only solution is by ADB
Open developer tools, connect by USB, and by ADB shell type the following command:
adb shell settings put secure qs_media_resumption 0
That's all
Click to expand...
Click to collapse
Thanks for this. I'm trying to get this to work, but I don't have much experience using adb. Could you perhaps tell me why it's not working for me ?
adb shell
* daemon not running; starting now at tcp:5037
* daemon started successfully
renoir:/ $ settings put secure qs_media_resumption 0 Exception occurred while executing 'put': java.lang.SecurityException: Permission denial: writing to settings requires:android.permission.WRITE_SECURE_SETTINGS at com.android.providers.settings.SettingsProvider.enforceWritePermission(SettingsProvider.java:2105) at com.android.providers.settings.SettingsProvider.mutateSecureSetting(SettingsProvider.java:1615) at com.android.providers.settings.SettingsProvider.insertSecureSetting(SettingsProvider.java:1566) at com.android.providers.settings.SettingsProvider.call(SettingsProvider.java:408) at android.content.ContentProvider.call(ContentProvider.java:2486) at android.content.ContentProvider$Transport.call(ContentProvider.java:522) at com.android.providers.settings.SettingsService$MyShellCommand.putForUser(SettingsService.java:375) at com.android.providers.settings.SettingsService$MyShellCommand.onCommand(SettingsService.java:277) at android.os.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:98) at android.os.ShellCommand.exec(ShellCommand.java:44) at com.android.providers.settings.SettingsService.onShellCommand(SettingsService.java:49) at android.os.Binder.shellCommand(Binder.java:932) at android.os.Binder.onTransact(Binder.java:816) at android.os.Binder.execTransactInternal(Binder.java:1162) at android.os.Binder.execTransact(Binder.java:1126)
UPDATE: nvm, I figured it out. I had to also enable the debugging feature that allows secure access. (and log into my Mi account, blegh).
Thanks again
Thank you, the above fixed the issue
Here is a simpler way to fix that, you just need to update MIUI Notifications built-in app to a newer version.
I have attached the apk file, just install it on top of the existing version.
Gonna try it now. Thanks!
Hi, I did the adb process adb shell settings put secure qs_media_resumption 0 but now i'm having issues when the phone connects to the car bluetooth as the song names aren't being updated. How can I revert this, which is the default value for it? I would like to try and see if fixes the issue with the car system and then try to update the notif apk.
thanks!
anyone?
Rase to wake not working.
Phone waking up even Rase to wake in off position
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
It may be a bug. You can try to upgrade the system
红豆生南瓜 said:
It may be a bug. You can try to upgrade the system
Click to expand...
Click to collapse
Hi
It is up to date
Fixed.
Follow these steps:
1- Activate developers options on your phone.
For this you have to open Settings>About phone and tap on MIUI Version for about 7-10 time.
Now you go back to settings>adittional settings > Developer Options. Make sure you have USB Debugging and
USB Debugging(Security settings) are activated. For this last one i think you have to be logged in your MI account.
2- Install ADB(Android Debug Bridge) on your computer.
If you are on Windows, install ADB Universal drivers first.
Then download the ADB files.
3- Excecute commands.
Open a Command prompt (or shell) on the directory where you have the adb files.
Connect your phone with a USB cable. Change the USB mode to “file transfer".
In the Command Prompt window, enter the following command to launch the ADB daemon: adb devices.
You should get a prompt on your phone to allow (or deny) USB Debugging. Allow it and re enter on command prompt the "adb devices" command.
Now you should see your phone serial number. And you just have to enter the mentioned commands.
adb shell
settings put secure wake_gesture_enabled 0
exit (to exit adb shell)
And that`s all.
Screen turning on by itself.
When moving the redmi Note 9 the screen turns on by itself. I have disabled the "lift to activate" option, but the screen keeps turning on when moving. Someone can help me please? When the winds of change blow, some build walls, others build...
forum.xda-developers.com
Hello everyone!
This is my first post here so I hope everything I try to explain is according to the rules as far as I read it.
I need to root my Doogee S88 pro mobile since I need test and develop some AR stuff. The standard apps are not accesible by the playstore so I need to bypass that. For doing that I need to root my phone (this is what I read at least).
So... I installed the doggee usb drivers from their website for my phone, usb debugging is activated and OEM is activated as well. I downloaded the most recen platform tools and the usb-cable should be fine since I find the phone with
Code:
adb devices
I execute the following commands:
Code:
adb devices
adb reboot bootloader
fastboot devices
I get the small Fastboot text in the lower left corner. Then if I try to execute
Code:
fastboot flashing unlock
or
fastboot flashing unlock-critical
I only get back <waiting for device>
As said I installed the usb drivers provided by doogee. But: In the device manager I can see the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also I periodically (every 10 seconds) hear the sound as if a usb-device is disconnected. Afterwards the device manager refreshes the list.
So... it is a driver issue? I tried updating the drivers but picking manually the folder where driver files are located leads to no result. Automatic search as well. If it is a driver issue - where can I get the appropriate driver files? Thank you for any hint.
Get the Google USB Driver | Android Studio | Android Developers
The Google USB Driver is required to perform adb debugging on Windows with Google devices.
developer.android.com
Unfortunately that didnt help either. Dunno... What I did was: I switched to my Lnux OS and over there it worked out of the box (only needed to install adb and fastboot from repositories).