Help with buildprop edit not saving - Google Pixel XL Questions & Answers

I bootloader unlocked and rooted my pixel xl that was on android version 10 using these instructions https://forum.xda-developers.com/pixel-xl/how-to/guide-pixel-xl-android-10-0-q-t3964112
Bootloader shows to be unlocked. Root checking app shows to be rooted (Superuser App: Installed, Superuser Binary Files: Not installed, Root User Account: Success). Magisk manager is installed and shows to be up to date.
Used a buildprop editor to try to get hotspot enabled. When I save the file it says error saving and doesn't save changes. Can anyone help me fix what is wrong?? TIA

https://forum.xda-developers.com/apps/magisk/magisk-tethering-enabler-t3937427

Related

SuperSU & Framaroot - Need help!

First of all, I have no idea where should this be posted as I am a total noobie to this forum and there is way too many categories.
I have a big problem. I installed Framaroot, used the first option (Boromir?) and have rooted my phone successfully. I tried to use *#*#supersu#*#* but nothing came up, the digits just disappeared, so I installed SuperSU from the market. I didn't do much on it, just changed the theme and hid it from my apps. I were rooted and happy for about a month, then however I got angered by SuperSU because I had to restart Hex Editor every time to get the root permissions (I were editing Terraria save files). The anger made me want to uninstall SuperSU, hoping it would just grant all the perms to the editor. First of all I disabled SuperSU, and when I realised it actually disabled the whole root, I enabled it again (unsure if it worked), I assumed everything is working, but I still wanted to get rid of the permission thing, so I pressed something like 'clean up to switch to a different superuser', and restarted my phone. I come back, and I have no root, so I went into Framaroot and used all the options, each returning that SuperSU and superuser binaries were installed. I restarted my phone, grabbed SuperSU from the Play store, just to find out that 'SuperSU binaries were not installed and SuperSU cannot install them, this is a problem!'. I then went on Framaroot, uninstalled root with all 3 options, restarted, then installed all, restarded, and the problem is still occuring. I am running Android Jelly Bean on Alcatel 4030X.
I have completely no PC access, so any USB roots or things like that are a no go. Please help!
Hi
since no-one has replied it may be because you have no paragraphs so it shows a disorganised mind....giggles
#########
Since you claim you used framaroot to install we now try to get root again
system settings security enable unknown sources
install framaroot ....if you lost it....to sdcard
install it
run it
choose first root exploit as you say that worked
if success you must reboot
###########
What you need to do if you have chainfire's superuser installed next time
go to app drawer
click on the red and yellow su icon
click on settings
change the default from .....ask each time to grant
reboot phone to test permission for apps is now auto granted. Especially test Hex Editor
###########
Altho you don't ask....there are 2 ways of updating chainfire's app
playstore ....click on update for app
open it
it will give you a dialog box to update
choose normal............it attempts to autoupdate
b) install a custom recovery and choose TWRP or CWM or CTR etc and try to update thru custom recovery
good luck

Root issue with superSU in some android applications

I have rooted my Mi Max with original MI OS and most of the applications can run with root access but my important application that can change the font was not passed the root permission and as well as adblock application.
I did run with root checker application and it shows that my phone has proper root access but when I applied the font changer application and got error that no root access. I have used latest superSU and busybox, I have no idea to fix up and I have tried to google it but can not find it.
Please let me know if you got experience with that, thanks in advance.

How to Enable Viper with Stock Rooted Android 7

Various links in Google world. Some worked. Others had issues. To keep this simple I am going to attach two files to use. This is based on the use of Magisk for rooting your setup. It does NOT work if you are only using SuperUser. The mods that stated how to do this with SU did NOT work for me, so I will not include anything with regards to that. Again, this is working for me with latest just posted Android 7 firmware for my SM-G925T and rooted with Magisk and TWRP recovery installed. Please don't ask if you are not rooted or no TWRP or whatever. They ARE required and Magisk is required too. Plus go to Playstore and make sure BusyBox is installed. I would also uninstall any prior versions of Viper prior to doing this. Or use Titanium BU to delete so as NOT to have competing files. After the above, take the attached file audio_effects.conf and replace the one located in your system\etc folder. The file is zipped simply to allow uploading. This is NOT installable from recovery. Simply unzip to use the conf file. Disregard the backup file in this zipped upload. The .bak is not needed. You will need an app like root explorer to do this. Make sure you set the file permissions the same as the app you are replacing. This is important. Permissions must be the correct same as the original file. Finally...take the attached v4afx_v1.4 zip and install from TWRP recovery. Reboot and should be good to go. If done correctly the left menu in viper that shows driver status will show everything processing, enabled, and working when Viper is ON and music is playing
Added webcam shot showing driver status. A screen shot would remove that window showing driver status.
Do you randomly lose root after this install?

3a XL - lost root / can't root - any fix?

So this phone is used by my close relative and I usually update their phone for them. It worked great, no complaints.
Just today I wanted to do something in Magisk, but I didn't have the bottom options like I didn't have root.
Interesting. I thought something broke it, so I decided to update to latest OS and then try again.
Since the phone was running a few months old update, I thought I'd update + root to make sure everything works.
I used flash-all.bat to update, it flashed fine, the phone loaded fine, it shows September security update.
so I went ahead and tried to root like I always did.
got the latest image, updated via flash-all.bat (without -w switch), then copied over the boot.IMG, patched it on phone, copied back to my PC from /sdcard/Downloads, then used "fastboot boot magisk...img" to boot the patched img.
now, this is how I rooted my 9R and this 3a XL a dozen times. but not now.
I open Magisk once it boots up and it just shows me the same Install option.
It same as nothing happened.
like root just doesn't exist. wtf?
did Google mess remotely with Pixels? or what's going on?
ps.: I even tried to "flash" the img into the active slot, both slots, nothing.
like the .img itself is not getting patched.
using Magisk stable, 23.0.
update 1: Interestingly enough, Root Checker says I have root. But Magisk only has Patch File option, no Direct Install. Tried Canary too, nothing. Reinstalled Magisk app, nothing. So weird... like Magisk lost root access? But why? How do I fix that? So weird...
You can open a terminal app and type 'su' to see if it prompts you for root access. If not you can try uninstalling magisk, then rename the magisk.apk to .zip and sideload from recovery.
SOLVED!
Sorry for not updating my thread, it was pretty late when I cracked this.
Here is how I fixed it. (I'll format it a bit later.)
I went Termux, root with su.
went into /data/adb/ and there is a magisk.db file.
I copied that to /sdcard/ and then to PC (you can do this on phone too using SQLite editor apps but whatever. On PC it's easier, more screen estate, etc.)
I used SQLite Browser (free) to open the file, then Browse Data and Policies
here I saw all the apps that had root granted...
So I added a new line.
I used adb shell on PC to find out the data I needed.
first, pm list packages | grep magisk to find magisk's name (it's "com.topjohnwu.magisk")
then, dumpsys package com.topjohnwu.magisk | grep userId to find out the user ID (uid) for it.
I added these into the database, it looked like this in the end:
uid package_name policy until logging notification
10386 com.topjohnwu.magisk 2 0 1 1
(^ your userId will NOT be the same!
and the first line is the column names)
saved the file, copied it back to my phone in Windows, then used Termux to copy the file from /sdcard/magisk.db to /data/adb/magisk.db
then I shut down the phone, used "fastboot boot magisk_.. patched.img" so I'd have a rooted boot image loaded up.
and boom, Magisk app works again.....
how to tell if Magisk app loses root?
well, for me the screen went dark briefly for like 2 times when I opened the app on clean boot.
and of course, Direct Install was missing.
to verify root in this case - you can only use apps that are present in the .db file.
ie.: apps that you granted beforehand.
so I'd really recommend opening Termux then doing a "su" at least after a root.
Why does it happen?!?!
I THINK this happens when you repackage Magisk. So I'd recommend changing it back before doing a system update. Because after the system update, you most often need to reinstall the .APK and then its under the original package + app name. Thus, it's not in the Policy file -> ie.: the Magisk app will not have root.

Unable to edit root directory files.

I recently rooted my moto g5s with magisk i wanted to change a few system files and the boot animation but i found myself unable to edit any root directory file. I thought that the problem was the root and that i did it wrong, but after installing root checker it said it was fine. I was able to use some aplications that need root like fluid ng but i am not able to use ones that create/delete/edit files. I have no clue whats the problem please help.
OBS: my magisk version is 23.0 and im using android oreo 8.1.0

Categories

Resources