Attempting To Install Xposed to 7.1.2 - Google Pixel Questions & Answers

I can't get Xposed to install to stock 7.1.2. I looked into the error code and the xposed installer checks for /system/build.prop. Since that file doesn't exist the installer aborts... But when I boot into the OS and navigate to /system/ build.prop exists. I'm not sure what to do. Any ideas?

Related

[Q] Root apps not working

Hi,
I rooted my phone and installed a factory image of 5.0.1(default kernel, stock rom). Now my rooted apps(like super SU, greenify and Xposed installer) are not working. For greenify I am getting message "Failed to put **** into hibernation", for Super SU no binary is installed, and in case of Xposed framework "The latest version of Xposed is currently not active". Any help on this would be immensely appreciated.
1. You need to flash latest SuperSU beta zip from custom.recovery for root.
2. Xposed won't work on lollipop at all. It only works with dalvik not ART and lollipop only has ART
rootSU said:
1. You need to flash latest SuperSU beta zip from custom.recovery for root.
2. Xposed won't work on lollipop at all. It only works with dalvik not ART and lollipop only has ART
Click to expand...
Click to collapse
Thanks!!! Flashing to latest super su zip file helped!!!

Systemless root info

There seems to be a lot of issues regarding the systemless root method. Here is some help/basic info.
Prerequisite:
1. Bootloader must be unlocked
2. Must have TWRP recovery installed
How to systemless root:
1. Download SuperSU v2.61 or SuperSU v2.62-3. Both work, I use the v2.62-3.
2. Flash either in TWRP recovery. Reboot to system. You now have systemless root.
Problems/Fixes:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
2. One of your favorite root apps doesn't see that your rooted? Do THIS.
I update super su from the playstore without issues.
kadopt said:
I update super su from the playstore without issues.
Click to expand...
Click to collapse
Could you explain your process? I tried updating from the 2.61 and had issues.
gokart2 said:
Could you explain your process? I tried updating from the 2.61 and had issues.
Click to expand...
Click to collapse
Well, to get root (systemless) you flash super su 2.62-3 with twrp, then go to playstore and update super su app, open Super su and a pop up will indicate that your binaries need updating, press OK and wait until it's complete, then just reboot your device.
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
gokart2 said:
1. Don't update SuperSU via the Play Store. I didn't have any luck updating this way (nothing but problems). If you want to update SuperSU/binaries, just download the current version SuperSU v2.71 and flash it in TWRP. As long as you previously flashed one of the SuperSU's listed in "How to systemless root", it will boot without issue.
Click to expand...
Click to collapse
Where can one find this magical "How to systemless root" list of safe-to-flash systemless SuperSU?
And I assume only the BETA versions are systemless? I have tried flashing the latest STABLE v2.76 and it just stuck on boot.
The SuperSU v2.62-3 that you mentioned does work but just want to find the latest version to flash.
jason2678 said:
Good post. I see nothing but problems in here from people trying to flash some of the newer supersu zips and not booting due to it installing to /system.
I'd just like to add that you can start with whatever version supersu you want (as long as it is new enough to support systemless install - don't dig out 2.47 and expect it to work). You don't have to start with 2.62, but 2.62 is a good choice since it only installed systemless.
On unrooted, unmodified stock you just have to add a preference file to force supersu to install systemless. I find its easiest to do via adb in TWRP, but TWRP's built-in terminal would work too. It is one extra step before rooting, but if you're on unmodified stock then you probably just fastboot flashed TWRP so the PC and USB cable are already handy. Just enter:
Code:
echo "SYSTEMLESS=true" >> /data/.supersu
Once that's done you should be able to flash newer supersu zips. No need to start from 2.62. :good:
Click to expand...
Click to collapse
Adding the single line text file to /data worked for me to root stock 1575 18-4 with the latest Supersu 2.76 stable.
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
The systemless file contains the following:
SYSTEMLESS=true
BINDSYSTEMXBIN=false
Click to expand...
Click to collapse
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
Click to expand...
Click to collapse
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
csrow said:
Thanks for the script. It should make it easier for someone to apply systemless root. FYI, supersu 2.76 defaults the /su/bin to 751 permission.
Click to expand...
Click to collapse
Yeah I'm hoping this will make it easier for those who are flashing SuperSU and ending up with an un-bootable phone due to the installer defaulting to system root in newer versions.
I've removed the permission script since I had no idea 2.76 now applies it. Thanks for the heads up!
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
Click to expand...
Click to collapse
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Edvin73 said:
Flashed your script but SU wasn't installed. After that, I flashed SU 2.76 in TWRP and everything is as it should be. Android Pay also working.:good:
Click to expand...
Click to collapse
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Spasticdroid said:
Found the issue. The installer couldn't find the zip as I pointed it to a different file that wasn't there
("supersu-v2.76-20160630161323.zip" instead of "UPDATE-SuperSU-v2.76-20160630161323.zip". Thanks!
Click to expand...
Click to collapse
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Ijspegel said:
Do you have changed this in the zip file? So if i download the zip it will Flash super user or do i have to Flash super su separate?
Sent from my XT1572 using XDA-Developers mobile app
Click to expand...
Click to collapse
Yes, I have updated the zip to fix this and it will now find and flash it.
Spasticdroid said:
Yes, I have updated the zip to fix this and it will now find and flash it.
Click to expand...
Click to collapse
Thank you for your work on this one, it is very helpfull!?
Sent from my XT1572 using XDA-Developers mobile app
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
Thanks man, your script was the only thing that worked for me, but now wifi isn't working. what can I do?
Spasticdroid said:
Making it very easy for everyone, here's my simple flash zip which force-installs any version of SuperSU (2.62 or newer) as systemless.
What the installer does:
1. Copies the "systemless" file to the /data partition.
2. Renames the "systemless" file in /data to ".supersu" (as required in SuperSU's guide to overriding.)
3. Installs SuperSU as systemless, as the "systemless/.supersu" file forces it to.
The installer includes SuperSU 2.76. Read updater-script in the ZIP if Chainfire releases a new update and you want to update the zip with a newer version of SuperSU.
EDIT: Updated the installer to apply permission fixes to /su/bin for Android Pay compatibility after installation.
EDIT 2: Removed the /su/bin permission script since SuperSU 2.76 now applies it itself.
EDIT 3: Fixed the installer to look for the correct filename of SuperSU. Everything is perfect now.
Click to expand...
Click to collapse
OMG THANK YOU
I had accidentally installed the wrong SU and i thought I would have to wipe my entire device after hours of trying different methods. Yours was the only one that worked and my phone booted back on. Thank you so much.
Taking a risk of sounding stupid, will your SystemLess Root work for Android 7.0 Nougat?
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
phillyguy /northeast said:
Need help guys i flash super su v2.46 now on bootloop i have twrp install how do i get the newer supersu to flash to my phone . How and where would i downloqd it .
Click to expand...
Click to collapse
Didn't we fix this in another thread?!?!

Help!!!!

Hi,i updated my Htc A9 device from Marshmallow stock rom to Nougat official rom.
My Device Info:
***UNLOCKED***
S-OFF
CID BS_US001
MID 2PQ912000
Os 2.18.617.10​​I decided to root my device but i have problem on that!!!
Step 1- installed twrp 3.1.1-0 by fastboot mode
Step 2-installed Magisk Manager and download magisk v 12.0 zip file from magisk manager.
Step 3-Reboot to twrp recovery and select (Swipe To Allow Modifictions),then i flashed Magisk v 12.zip file from install menu and after that reboot device.(recovery log)
Step 4-Run Magisk Manager and see this Status:
installed magisk ver 12.0 --->Iatest version magisk installed and Properly rooted--->8:MAGISKSU
(tpjohnwu)Pic 1.
Superuser show on Magisk manager menu(Pic 2) and apps send request for permission to #superuser(Pic 3).
On the surface everything is OK but i have problem,for example i installed Link2SD app to use that for uninstall system apps and freez apps but does not work properly & show error msg(Pic 4).
I would be honored if you tell me what is my problem,thanks...
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
eavandijk83 said:
Hi, did you install busybox? I'm not familiar with Magisk nor Link2SD, but I can imagine there's an option to "ignore systemless root" so you'll be able to make changes to the system partition.
Do other root apps have problems as well?
Click to expand...
Click to collapse
I can't install busy box,when o clicked on install button,busy box closed!!!!
cowboy_ea said:
I can't install busy box,when o clicked on install button,busy box closed!!!!
Click to expand...
Click to collapse
I think you'll be better off if you install the latest LOS ROM (20170530) and flash SuperSU. I don't know about Magisk, but I've never experienced problems with SuperSU. Once rooted, install busybox from the playstore and install into "system/xbin/"
In SuperSU make sure you override LOS root settings since it's set to off by default. By the way, you can turn on LOS root settings manualy. That way you don't need Magisk or SuperSU at all. Settings can be unlocked by tapping the build number several times in settings-->Device status. A menu will be unlocked called Developers options. Within that menu you'll find the root settings.
Good luck

Stuck In Bootloop?? Here is Rescue System [Guide]

I assume here you have custom recovery like twrp and Magisk (Required only in Method 2) Installed in your device, I have made it simple, crsipy and concise so that noob can get rescued from bootloop
Note : This guide is helpful only of bootloop is caused by Xposed modules, Magisk modules, System or User App.
[emoji637]?*?**?*?*?*?*?*?***
1)Reboot to Recovery
2)Go to Recovery File Manager and Browse to /data/app/
3)Find there package name of xposed module,user app causing bootloop like package name of famous xposed module Xposed Edge is "com. Jozien.xposededge"(just remind app name and you will get it) and swipe to deleter that folder
4)You are done, just reboot your device
*[emoji638]?*?***?*?*?*?*?*?**
(Recommend For Xposed Users and Systemless Mods)
1)Download Magisk Manager For Recovery by @VR25 From Magisk Respo.
2)Flash via Magisk or Recovery (works even after you are stuck in bootloop)
3) Now Go to Recovery Terminal
4)Type the fallowing Command
"/data/media/mm" without quotes
5)Type "a" without quotes to enable or disable magisk module)
6)Now type keyword (first two, three letters matching with magisk module and enter to disable it
7)Enter Again to Complete Procedure
Suppose An xposed module is causing bootloop (Assuming you have Ed Xposed Framework Installed)
Just type Ed or Xposed keyword to disable This module and other module similarly and you are done
Uraniam9 said:
I assume here you have custom recovery like twrp and Magisk (Required only in Method 2) Installed in your device, I have made it simple, crsipy and concise so that noob can get rescued from bootloop
Note : This guide is helpful only of bootloop is caused by Xposed modules, Magisk modules, System or User App.
Here are the steps to get out from a Bootloop
*METHOD 1*
1)Reboot to Recovery
2)Go to Recovery File Manager and Broswe to /data/app/
3)Find there package name of xposed module,user app causing bootloop like package name of famous xposed module Xposed Edge is "com. Jozien.xposededge"(just remind app name and you will get it) and swipe to deleter that folder
4)You are done, just reboot your device
* METHOD 2*
Recommend For Xposed Users
1)Download Magisk Manager For Recovery by @VR25 From Magisk Respo.
2)Flash via Magisk or Recovery (works even after you are stuck in bootloop)
3) Now Go to Recovery Terminal
4)Type the fallowing Command
"/data/media/mm" without quotes
5)Type "a" without quotes to enable or disable magisk module)
6)Now type keyword (first two, three letters matching with magisk module and enter to disable it
Suppose An xposed module is causing bootloop (Assuming you have Ed Xposed Framework Installed)
Just type Ed or Xposed keyword to disable This module and other module similarly and you are done
Click to expand...
Click to collapse
You may add that you need to enter twice = to do what Ctrl+C as said in the app. In the last step
Added
Thanks. I just included this thread in my signature
Thank you so very much, Mr. uraniam9. You just saved me a hell lot of work restoring my phone. God bless you.
I just can't make Edxposed work, system hangs on the Samsung animated logo. Device is SM-J730G/DS running stock official with Magisk 20.3 and latest TWRP for my device. I'm getting this problem flashing both sandhook or that other one I forgot it's name.

J327p safetynet pass

I have an sm-j327p with xposed and supersu and I want to play pokémon go. Any way I can pass safetynet? If not, can someone please make an xposed module for me to do so? It's possible to make such an xposed module according to my dad who said that it's impossible to stop a hacker. My baseband version is j327pvpu4arj2.
download magisk 18 zip - http://www.mediafire.com/file/4rmzovup0xz0ben/Magisk-v18.0%2818000%29.zip/file.
uninstall xposed completely.
unroot in supersu.
MAKE SURE YOU SELECT 'RESTORE STOCK BOOT IMAGE'.
then flash magisk zip.
then reflash the samsung xposed and then enable in xposed 'No Device Check'.
then delete any busybox app.
Now you should pass SafetyNet.
Prob is pokemon go detects the xposed installer and the magisk manager, activate in magisk 'Repackage Magisk Manager with random package name.'
Then you have to try renaming the xposed installer apk with apk editor or something else.

Categories

Resources