Sorry for some very basic questions about Device Id.
My assumption
My simple understanding is that your device id is a unique identifier that is generated based on your device and your Google account id.
This id is then used when for instance connection to the market and is required for you to download/install apps from it.
I know you can run an application like "Device Id" on the market to derive it.
Questions:
When will I ever need to use it?
If I flash a custom ROM - does that transfer over a new device Id and I will have to change the device id post-flash back to what it used to be in order for my device to access the market correctly - or is this something I need to do when/if I go back to stock?
Interested to see what the 'need'/use for this device id is.
Regardless I did make a note of mine...should I ever...need it
The identifiers for the device are in the build.prop and can be modded with root, to change system parameters and what apps are available in the market.
http://www.xda-developers.com/andro...-market-compatibility-and-performance-tweaks/
Related
I just loaded a custom ROM on the nexus 7 2013. In the fast boot screen there is information pertaining to the device such as
product name, Variant, Bootloader Ver, etc. There is a serial number also listed. The device is wifi only. I am curious if the serial number would have any merit in locating the device in the event it were lost or stolen and someone were to log into their Google account, create a new Google account, and access the internet. Would there be a way or a service that could find out the ip of the people who stole/found this device via the serial number? Or what is a recommended way of protecting the device and relocating it?
jake0125 said:
I just loaded a custom ROM on the nexus 7 2013. In the fast boot screen there is information pertaining to the device such as
product name, Variant, Bootloader Ver, etc. There is a serial number also listed. The device is wifi only. I am curious if the serial number would have any merit in locating the device in the event it were lost or stolen and someone were to log into their Google account, create a new Google account, and access the internet. Would there be a way or a service that could find out the ip of the people who stole/found this device via the serial number? Or what is a recommended way of protecting the device and relocating it?
Click to expand...
Click to collapse
Search for Android Device Manager on the Play Store. It might be what you are looking for.
I have root via Magisk and want to know how to change device id for a specific app as Oreo does that now instead of in the past making device id across the phone one id that was easily changeable via apps. Any ideas?
Would anyone know if the Galaxy S9 natively supports user profiles so that multiple users can login and use the same phone with their unique settings and apps? If not would anyone be able to recommend an application that could accomplish this?
The functionality has been disabled for stock Samsung ROMs long time ago (if it was ever enabled). There were some discusions in the past regarding this and what I remember is that you need root for this to work. You have to edit build.prop and include the lines:
fw.show_multiuserui=1
fw.max_users=n (where "n" is a number indicating the max users on device - should be at least 2)
Alternative is to flash an AOSP based ROM that has the function enabled.
Rapier said:
The functionality has been disabled for stock Samsung ROMs long time ago (if it was ever enabled). There were some discusions in the past regarding this and what I remember is that you need root for this to work. You have to edit build.prop and include the lines:
fw.show_multiuserui=1
fw.max_users=n (where "n" is a number indicating the max users on device - should be at least 2)
Alternative is to flash an AOSP based ROM that has the function enabled.
Click to expand...
Click to collapse
I unfortunately cannot root the device as it will be provisioned for company use :/ is there a launcher that could help to accomplish this?
Sorry, none I know. The functionality is deep embeded in the OS, a launcher would not be enough to accomplish that
You could however use dual accounts for certain apps or mail and also use Secure Folder to lock out personal/private data. This way you will have some sort of multi user since the secure folder keeps data in separate encrypted form
Sent from nowhere over the air...
Hello,
I'm hoping that someone here will be able to help to do one or more of the following things:
1) Complete data recovery of Samsung Galaxy S9 snapdragon
2) Bypass pattern lock
A partner against whom I have a restraining order purchased this phone for me and I have since become aware that there is software installed on it which I cannot access which is recording my location, communications, etc.
All I installed is Mxplorer, OS Monitor, and Logcat, all of which were recommended by users on these forums and which were Google Play verified. When I started going through what I could access and recording the logs, my phone went crazy and a bunch of root files began to delete themselves. Now it is locked by a pattern and I never set a pattern.
Is it possible for me to bypass this pattern without deleting all the data on the phone, or to backup all the data on the phone including root files even if I cannot download the phone itself?
Alternatively, is anyone aware of any organization that would help me to examine the phone, as I do not feel that I have the technological ability to do so myself?
Also, I understand that the best thing to do for my own security is to use a different phone and to reset the passwords for all the accts that were saved on that phone from a different device and I am already doing that but it is very important to me to identify and preserve the spyware that was installed on this phone in order to 1) ensure the continuation of the restraining order 2) know what information he has had access to and 3) share the information that I find with organizations that are involved in combatting the development/sale/use of this kind of stalkerware.
Thank you.
PS C:\Users\Genevieve\Desktop\platform-tools_r30.0.5-windows (1)\platform-tools> .\adb shell
starqlteue:/ $ cd /data/data/com.android.providers.settings/databases
/system/bin/sh: cd: /data/data/com.android.providers.settings/databases: Permission denied
2|starqlteue:/ $
2|starqlteue:/ $
This is what I'm coming up against when I try to bypass the screen lock using adb, just for reference.
Permission denied on that path is not unusual, some devices simply don't support accessing that path over ADB. To delete that path, USB debugging needs to have already been enabled in the device's developer options so you can delete the gesture.key file and regain access. I've had a similar fight with an older Android device, trying to retrieve photos from a phone with an unlock pattern the owner had forgotten.
In the end I managed to gain access to the filesystem, but I had to do it through recovery mode by flashing an alternative recovery image to the device which bricked it for normal use.
I'd be surprised if this other person managed to install commercial spyware/malware without rooting the device, which would also give you access to that path.
That sort of 0day vuln is either darknet for $$$ (at which point, just wipe the cache partition, reflash the stock firmware and start from scratch) or nation state actor complexity.
I published a script that can automatically resign GrapheneOS OTAs with your own keys, and also optionally apply a few modifications like enabling ADB root (without turning on ro.debuggable), ignoring allowbackup and changing the update URL.
You can use it if you like GrapheneOS (I think it's the Android OS with the best engineering, security and privacy), but would also like to have full control of your device, by controlling the verified boot keys of your device and applying modifications that make the OS do what you want regardless of what upstream OS developers, app developers, or anyone else might want.
Note that, on the other hand, GrapheneOS follows the Google Android security model which says that the OS will not perform an action you want it to perform if it may result in something that "application developers, content producers, service providers, and employers" do not consent to (which means not letting you have root, or ignore app wishes regarding backups and other settings, or send arbitrary responses to app requests, etc.), while this script will let you do what you want with your own device regardless of whether it's in anyone else's interest or not, including things that this script does not itself support since you control the verified boot keys of the device and can thus sign anything; all this while still taking advantage of all the security and privacy features in GrapheneOS, including verified boot.
You can find it at https://github.com/chriswoope/resign-android-image
Currently it's intended for people with good technical knowledge, although once you set it up (if you run Qubes a lot of steps are automated) it should continue working with no or minimal intervention.