Bootloop due to DPI change - Xiaomi Mi Note 3 Questions & Answers

Hi,
After changing the DPI to 992 the phone stucked at boot. I found that I can use "adb shell wm density reset" command. But when I tried I get the following (when I try "adb device" command I have access to my phone)
~$ adb shell wm density reset
Security exception: Must hold permission android.permission.WRITE_SECURE_SETTINGS
java.lang.SecurityException: Must hold permission android.permission.WRITE_SECURE_SETTINGS
at com.android.server.wm.WindowManagerService.clearForcedDisplayDensityForUser(WindowManagerService.java:5737)
at com.android.server.wm.WindowManagerShellCommand.runDisplayDensity(WindowManagerShellCommand.java:168)
at com.android.server.wm.WindowManagerShellCommand.onCommand(WindowManagerShellCommand.java:68)
at android.os.ShellCommand.exec(ShellCommand.java:110)
at com.android.server.wm.WindowManagerService.onShellCommand(WindowManagerService.java:1055)
at android.os.Binder.shellCommand(Binder.java:629)
at android.os.Binder.onTransact(Binder.java:527)
at android.view.IWindowManager$Stub.onTransact(IWindowManager.java:1140)
at com.android.server.wm.WindowManagerService.onTransact(WindowManagerService.java:1265)
at android.os.Binder.execTransact(Binder.java:726)
So I can't change it. Since I don't have root permission I can't also edit the "build.prop" file.
I just want to get my files. Is there any solution that I can root or change dpi setting without loosing the data? (miui 12 with MI recovery 3.0 )

Related

adb root: Permission denied but OK in recovery mode.

Dear Sirs,
I have HTC Desire Z with CM 7.0.3 (superuser installed) and s-off. Posting here since the issue seems relevant to android in general rather than specific hardware...
I have already seen the following threads before opening this one but they do not help since I cannot issue any of the commands that they mention:
:http://forum.xda-developers.com/showthread.php?t=1364521
:http://forum.xda-developers.com/showthread.php?t=1087350
:http://forum.xda-developers.com/showthread.php?t=837102 (it says to use mount command but thats exactly where I get the permission denied)
When I boot the phone normally and "adb shell", I can get a root prompt (id command shows root user, "cd" shows "/"). But ANY command I run brings permission denied (even ls, chmod, mount). I literally can't do anything. Same whether I boot with/without S D card. I CAN however issue commands such as "adb pull /init.rc" if I exit and go back to DOS.
If I open a terminal session (with Superuser full permissions), I can SU as root, but again cannot issue any commands without getting "permission denied"/
However if I boot into clockworkmod recovery and mount /data and /system, and then open an adb shell via USB, I can connect as root and browse everything, everything is fine and all commands work OK. /etc/fstab shows all partitions would be mounted as rw.
So it looks like some application during boot, is resetting the permission for /system to be ro, and also removing root's privileges.
Please could you let us know if there is a method to determine what app is doing this during boot. I cannot see anywhere in init.rc where I can catch this application that is doing this and prevent it from making /system inaccessible after boot.
Preferably if someone could point me to the complete log of the boot process that shows each command that is run, I might have a clue as to where in the boot up process, the /system partition suddenly becomes ro and root loses all permissions.
The problem prevents busybox updating and other root apps that need to write to /system.
This was not a problem for months after installing and rooting CM 703, only recently it has become an issue, perhaps following some hidden Google update???
Thanks

[Q] Bootloop after resolution change ADB fix possible?

Hello,
I used Resolution Changer Pro App (Nexter) on my Samsung Galaxy Note 1 GT-N700 for change resolution HDMI output (with accessory USB OTG/HDMI 1080p default resolution output). Actually, i have a bootloop on Samsung logo but no problem for use recovery mode and ADB.
Information :
Rom official Android 4.1.2
Root
PhilZ Touch 4 CWM v6.0.3.1
I used ADB with this command :
Code:
adb devices
: my android phone in recovery mode appears
Code:
adb remount
: remount succeeded message (before this mount data/system folder with Philz touch 4 interface)
Code:
adb shell am display-size reset
Code:
adb shell am display-density reset
no message/error after this command and no change after reboot why?
I tried
Code:
adb root
Code:
adb shell
Code:
su
no result
I pull build.prop file but i find only dpi information.
An idea for fix this problem without need wipe?
thanks for help
Bootloop solved after dpi change in build.prop file.
Not perfect (low resolution) but it's ok for save.

Samsung health error

Guys I need some help !!
I have official firmware in my phone S7 edge ( Android 7.0 G935F ) but once i tried to root it and it was stuck in boot logo so i went to a store for a suppose unroot ,but know e cant use Samsung health app because gives me an error. I already searched this error and just have to change the tima value to 0 in build.prop
My real question is can I edit build.prop to fix this error without root or do i have to root my device again to fix this error ??
Please help
thanksssss, waiting 4 answers
Your phone KNOX is ticked 0X1 that's why not working, you must root your phone and edit built prob, edit line TIMA=0 and will work
so i have to root it again ?? i have some problems (fear) doing it again because i don't know how to do it right
Or othe way to make it work. But need to be Root. Delete v5 restar install v4. Loging abd update. Done
I would recommend you the recovery mode if you don't want root the phone again. You have full access to system files in recovery mode, but only if it is mounted.*
Many stock recoveries don't have option to mount system partition or don't have adb access for commands. You might want a custom recovery for this. And no, you don't need root for custom recovery. So now all you need to do is, boot into recovery (custom preferred), mount system and then using adb, pull the build.prop file:
adb pull /system/build.prop <path to save file>
Now edit the file you just extracted and save it*
Push it back to your phone via adb
adb push <path to your file> /system/build.prop
You're not done yet. You need to set permissions too. So open she'll via terminal
adb shell
Now from shell, set the right permissions
chmod 644 /system/build.prop
And you're done
Reboot your phone and see the changes

ADB change bluetooth_name not working

Hello,
I am working on a script to provision many android tablets using adb via usb.
The devices all have root access and android 8.1.0.
Some settings I need can be changed using the settings stored in /data/system/users/0/settings_global.xml
i.e.
Code:
adb shell settings put global bluetooth_on 1
However changing the "device name" which is the bluetooth_name stored in /data/system/users/0/settings_secure.xml does not work.
This is the line:
<setting id="218" name="bluetooth_name" value="tablet-99" package="android" defaultValue="tablet-99" defaultSysSet="true" />
Code:
adb shell settings put secure bluetooth_name "tablet-77"
--> this just changes the value and not the defaultValue (how to do this?) ... both settings are reset after reboot
--> changing the file manually via sed/vi is reset after boot
In this thread Cloning Pre-configured Android 8.1 Device / ROM changing settings_secure.xml settings seems to work without problems.
Where else could the setting be stored?
thanks and peace.

How to enter /data/system/users/0/settings_ssaid.xml without root?

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

Categories

Resources