Is there way to enter /data/system/users/0/settings_ssaid.xml without root ?
beacuse this app must need same ssaid in other devices i need to enter /data/system/users/0/settings_ssaid.xml see ssaid without root pls help me
Android ID can be changed with the help of ADB through the following command
Code:
adb shell "settings secure put android_id [my_new_android_id]"
where ROOT isn't required.
xXx yYy said:
Android ID can be changed with the help of ADB through the following command
Code:
adb shell "settings secure put android_id [my_new_android_id]"
where ROOT isn't required.
Click to expand...
Click to collapse
no i want see ssaid first without root after that i will change with other device rooted
OMG
Then simply revise the command as follows
Code:
adb shell "settings get secure android_id"
Hint: Become familiar with Android's system ( LINUX ) commands.
I need app developer help will give you enough money have a problem that I want to solve
This app can be accessed from another device only once a month.
It uses a value called ssaid, which is different for each device.
What I want is to bypass this ssaid value
It seems that this value is stored on the server
Related
Hi,
I know this topic has been beaten into the ground but I have been looking around and have found no solutions for this issue relating to my position.
Why do I need to a solution to?
I work in a business which deals with a lot of phones which are mostly faulty/cracked screen/need data retrieved while they have a lock screen;
I see mainly Samsung phones come in with these issues;
Factory reset is not always an option for data recovery reasons, etc etc.
The situation?
Rooting the devices is not an option.
Touch screen may not work or lock code may have been forgotten.
USB debugging probably isn't enabled.
What do I need to know?
How do I enable USB debugging from without going to settings; and
How can I remove the lock without inputting the code?
What I have tried:
adb shell
cd /data/data/com.android.providers.settings/databases
sqlite3 settings.db
update system set value=0 where name='lock_pattern_autolock';
update system set value=0 where name='lockscreen.lockedoutpermanently';
.quit
Click to expand...
Click to collapse
Why it didn't work?
sqlite3: not found
adb shell rm /data/system/gesture.key
Click to expand...
Click to collapse
Why it didn't work?
Permission denied
And all the other threads I found pretty much all lead to the same two results.
Any help that leads to a solution for me would be greatly appreciated!!
You can't use sqlite3 or rm if the adb doesn't have root access.
It has to show a # instead of a $ sign. So just root the device and unroot it later if you want
And some phones give root access on adb even if you don't root them. So on adb shell type "su". If it showed a # sign then everything will work fine.
If it gave an error that su wasn't found then you need to root it.
Or you can try using adb pull commands to pull files from sdcard
You cannot enable USB debugging without going to settings. But there are some custom recoveries that gives full adb access. So just flash a custom recovery.
Sent from my One X+ using XDA Premium 4 mobile app
i want to know what is sudo location?
Because i have a rooted android and when i checked it by using root checker it shows its rooted but no sudo location...
amey.patil said:
i want to know what is sudo location?
Because i have a rooted android and when i checked it by using root checker it shows its rooted but no sudo location...
Click to expand...
Click to collapse
If I open terminal emulator and want to get root access, I'm just type "su" and get the root access..
lietsen said:
If I open terminal emulator and want to get root access, I'm just type "su" and get the root access..
Click to expand...
Click to collapse
what is the difference between sudo and su?
amey.patil said:
what is the difference between sudo and su?
Click to expand...
Click to collapse
I'm not a linux/android expert, but as long as I know, 'su' forces you to share your root password to other users whereas 'sudo' makes it possible to execute system commands without root password. When we're login into linux system and not a root, with sudo we can execute some program without using root password, as long as the user is in sudoers file conf.
Ex: I want execute "mysqld start" in linux, and I'm not root, but my username was registered in sudoers file, we can simply type "sudo mysqld start", and then system will ask the current user password. Another example is, we type "su". If the root has a password, then we must type the root password before we can executed another command, after that we'll become root.
I don't know in android if root has password or not, but till now where I want to executed some root program in terminal, I only type 'su' and no password.
*sorry for my bad english and explanation, i'm just nood*
SUDO vs. SU
The SUDO command stands for "superuser do". It prompts you for your personal password and confirms your request to execute a command by checking a file, called sudoers, which the system administrator configures. Using the sudoers file, system administrators can give certain users or groups access to some or all commands without those users having to know the root password. It also logs all commands and arguments so there is a record of who used it for what, and when. The SU command on the other hand stands for "switch user", and allows you to become another user. Using su creates security hazards, is potentially dangerous, and requires more administrative maintenance. It's not good practice to have numerous people knowing and using the root password because when logged in as root, you can do anything to the system. This could provide too much power for inexperienced users, who could unintentionally damage the system.
Source
Is it possible to enable root debugging from the command line. The rom that I'm using is missing the setting in developers options. When trying adb root I get the
Code:
ADB Root access is disabled by system setting - enable in Settings -> System -> Developer options
I don't believe it's totally disabled because I don't get the "adb root is not allowed in production builds". I think it's there but no switch to toggle. Haven't found anything searching for setting name and would need correct value and table if it can be set. Anybody know how to toggle it on from shell ?
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
jwoegerbauer said:
Command adb root works in development builds only ( i.e. eng and userdebug which have ro.debuggable=1 by default ). So to enable the adb root command on your otherwise rooted device just add the ro.debuggable=1 line to /system/build.prop file.
If you want adb shell to start as root by default - then add ro.secure=0 as well.
Click to expand...
Click to collapse
Thanks, actually looking into it, I don't know what to think about it. It is a user build of crdroid. I can not and absolutely do not understand the point of building a user build to post on XDA. The fact that someone is installing a custom rom kinda throws a user build out the window AFAIFC. It didn't even dawn on me to check if it was userdebug or not, in my mind, of course it is. That's what I get for thinking I guess. I like CrDroid so syncing source now, time to sync and build I should have an eng build in about 3 hours.
Take note that if adbd in your phone's firmware is build without ALLOW_ADBD_ROOT then you're wasting your time.
On GitHub: https://github.com/KDVB/BlueStacks-ADB-root-accessDisclaimerFor informational purposes only. The author does not call for further actions. Created to warn users who use this product
BackgroundADB (Android Debug Brigde) - is a versatile command-line tool that lets you communicate with a device. The adb command facilitates a variety of device actions, such as installing and debugging apps. adb provides access to a Unix shell that you can use to run a variety of commands on a device.
Research WalkthroughFor default, in Bluestacks, ADB port is open, but we can't to use shell command (output "error: closed")
Searching for information in the emulator files found the following file ".adbcmd" in Root.vnhd image. Path to file "dataFS\downloads". In this file we can see adb commands that we can run without connection to shell
For example, "getprop" command, that gives us information about android propetries
As we can see, interaction with android shell is working. So, I think "if I can interact with unix shell, maybe tryed to use pipe operators" and pwn i can interact with file system, but with shell-user privilage.
As a result i continue my search to find su command to get root access. SU file is in "/boot/android/android/system/xbin/bstk/su". I tryed pipe operator to get root access, but get error and shell didn't open(
After that i tryed list terminator ";" and it works. I get root shell
ResultBluestacks have this vulnerability and people involved in its development know about it and are engaged in its elimination.
The real test is to see if you can actually do anything. Sure, you've ID'd as root, but will it actually let you change anything?
V0latyle said:
The real test is to see if you can actually do anything. Sure, you've ID'd as root, but will it actually let you change anything?
Click to expand...
Click to collapse
Thanks for your reply. Actually you can change in current session, but when emulator reboot, all changes remove. If we speak about system folders. In sdcard folders changes save. Sorry, I didn't mention it in the post.
When i searched information on the virtual disk, i found some scripts that build a system. That takes information from .conf files, but that works only for local work. For example, when you using OpenVPN Connect that port still open and you can interact with it.
I'm using Huawei Nova Y90. My problem is that in developer options there's no OEM Unlock option.
I can't unlock the bootloader.
I checked these two:
getprop ro.oem_unlock_supported is 1
getprop sys.oem_unlock_allowed is 0
So, basically oem unlock is turned off and it is hidden from developer options. Is it possible to set it to 1 in another way?
Or is there a way to root the phone without unlocking the bootloader? I tried all no-pc apps, they don't work.
If phone's Android got rooted you in system file build.prop can set the entry sys.oem_unlock_allowed to 1.
BTW: To root Android it's never required to unlock phone's bootloader: this is a nurse's tale.
FYI: If phone's Android build is of type userdebug and USB-Debug in phone's Developer options is turned on then you simply run
Code:
adb devices
adb root
adb shell
<YOUR SHELL COMMANDS GO HERE>
exit
to gain root access and run shell commands that require elevated rights.