I have an Android music player that’s wanting to update the firmware. It’s an Astell and Kern SP1000 running Android 6.0.1 Marshmallow, API 23, build MMB29T.
There is no disable updates in the settings. The update is for the players firmware. I don’t believe it’s updating the whole Android OS. I could be wrong.
After firmware 1.16 I am no longer able to install apps Astell and Kern haven’t authorized. So I wouldn’t be able to install a file explorer or other streaming apps I persanly like using. If I knew they were planing on controlling the app so much I’d still be useing a phone with a DAC.
I currently have root by using the King root. I’m able to edit system files. I edited the host file blocking the update server. Yet the player has already downloaded an update and I can’t locate the file to delete it.
I’m constantly receiving the update notice about 10 times a day. The notification isn’t a normal notification. It’s a full screen overlay.
1. I would like to disable updates by altering some system file.
2. Also disable the notification.
3. Locate the FW file and delete it.
Thank you for the help.
Related
Im willing to pay through PayPal. I have a jp 5 s tablet from a prison it can receive bluetooth but installation of apps from unknown sources is blocked. In settings the check box to allow this has been disabled. It runs 4.2.2 Jellybean so my only hope is an image music file or video that could some how run a script to allow it or install a file manager. That's my ultimate goal. Thanks for any help.
Hi ,
I was trying to install certain application, but I couldn't because of my android version, so then I rooted my device and I edited configuration file (system/build.prop) with system variables such as API version, android version, name of device etc. First I changed only my android version from 4.3 to 5.1 and I rebooted my tablet and my system was fine, but my application still doesn't open. Then I thought that API version could cause the program to start, so I changed it from 18 to 24, I rebooted tablet and every Google Service was crashing with message "Unfortunately, Google XXX services has stopped"
I was trying to open configuration file again, but it's impossible, because of error messages.
I did force restore android system, but it doesn't restore system configuration files
And I installed app with gives access for editing system files again (i got apk file by usb), but I can't open it.
My tablet: Huawei Mediapad t1 8.0
Thank you for help
Dear all,
Though I'm kind of a beginner, I have made much progress backing up and decrypting Whatsapp messages from my old Android phone. However, there seems to have been an even older installment of Whatsapp running from an SD-card on the same device. There are Whatsapp-database files there, but I cannot find the decryption key.
I have tried many ways of going about it:
1. Exploring the root of the SD Card does not lead anywhere.
2. When I use Whatsapp-Key-DB-extractor by Tripcode, it only extracts from the phone's main drive.
3. When I transfer the older databases from the SD-card into their corresponding folder on the phone (either alongside, or replacing them), and then run the Extractor, again no success.
4. In the Apps menu of my phone Configurations, when I go to Whatsapp, the button "Move to SD-card" is unavailable. I figured this may be because only older versions of Whatsapp were able to move to an SD-card and run from there.
5. I downloaded and tried to install older versions of Whatsapp through APK-mirror (with the objective to consequently see if I can move it to the SD-card), but all of them ended in "unable to install"... And anyway, the oldest version available on apkmirror is not as old as the databases we're talking about (which are from June-July 2014).
6. Finally, I noticed that part of the Whatsapp-extractor's procedure is to revert to an older version (2.11.431) and back, so I tried interrupting the process before it sets the new version back. To no avail.
Can anyone come up with a workaround? Those messages are quite precious diaries of those days. My phone is an Experia Z (Model D5503, Android 5.1.1), but it has been stuck in a BootLoop since a very long time. I finally found the time and energy to sit down and see if I can learn how to get the most valuable information out of it after all, and after many, many hours and lots of patience and steady-handedness (the rebooting seems to occur with movement), I decrypted the database from the phone itself. Now I really cannot accept defeat in front of an even older treasure
Oh and post-edit: The databases from 2014 are crypt7. The ones that I DID extract succesfully are crypt12.
Best,
Publo
I came across this android app from voguemaster which will download a zip and the extract the zip to update the android kodi files, essentially installing a new 'build'.
Now I understand that a lot of the addons etc from the build it currently downloads are probably not supported and I'm not interested in that anyway. I wanted to change it to update my own build (without unsupported addons) for my friends, so when I make an update they can update as well without me having to pop over their house with my USB stick.
Unfortunately, although I worked out what to change in the app via Android Suite to link to my 'build', i wasn't able to sign and pack the apk because the gradle was out of date - and then I had some warnings about some code being out of date as well. I guess that's to be expected from an apk that's had little or no support since 2015.
My question is, would anyone be interested/able to fork this apk so it will work? I had a go myself but I really don't have a clue what I'm doing beyond the very basics!
https://github.com/voguemaster/SettingsDeployer
This device is a network radio/smartphone built in to a UHF transceiver. My question only pertains to the Android aspect of the device.
Here's the issue: I updated the Sophos AV app to the newest version today via the Play store. The app is now called 'Intercept X' and it boasts a revamped interface. After updating, I ran a scan of the device's file system and the results identified the presence of 1 threat. The previous version of the app always rendered clean scan results. The threat identified was shown to be contained in a system app called com.example.gui.myapplication but it gave no file system location and provided no options to remove it. I thus installed Malwarebytes for Android and ran a system scan. Malwarebytes also hit on the threat and pointed to the following file: /system/priv-app/remotekill/remotekill.apk
When I tapped on the 'Remove' option in Malwarebytes, it generated a dialog that instructed me to disable the file and displayed a statement that the file would be ignored during subsequent scans. I disabled the file as instructed. The next MB scan reported clean results. Btw, the original MB scan log result entry (containing the hit) shows "Threats removed: 0 of 1" in red font.
This device is not rooted. As such, I'm not sure that I can remove the file. And I'm not even sure that doing so is necessary or would be advisable. MB shows it as a trojan called Android/Trojan.Agent.nr but I can't seem to find much about how to deal with it. I'm wondering whether this is a false positive? Is that at all possible even with the hits from both MB and Sophos Intercept X? Could the remotekill.apk be a legitimate Google remote kill file? Is leaving the file disabled an acceptable practice? Those are some of my questions.
If anyone has thoughts on this please let me know.
Thanks