Database Develop

Xposed Installer destroyed my Toshiba AT300SE rooted

I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.

Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
i'll try this

kingvortex said:
Restore the backup that you should have made before installing the Xposed framework, or flash the Xposed disabler zip from recovery. Or read the FAQ.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Seems that disabler zip did not work.
Any other brilliant ideas................

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk

kingvortex said:
Yes, plenty, but your sarcasm precludes me from sharing them with you.
Read the FAQ and/or other pinned threads in this section.
I won't reply in this thread again. Have a good day.
Sent from my C6603 using Tapatalk
Click to expand...
Click to collapse
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.

Rooks said:
Well it's nice to share something.
.
.
.
.
.
.
.
If it's helpful for someone.
Click to expand...
Click to collapse
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.

Rooks said:
Seems that disabler zip did not work.
Any other brilliant ideas................
Click to expand...
Click to collapse
Only brilliant idea here was flashing something before backing up your rom.
Sent from my Nexus 5 using Tapatalk

GermainZ said:
Sadly, not many people around here possess a crystal ball to determine what may be helpful to you on advance. If it didn't help you, just say so politely.
If the Xposed disabler zip didn't work, you probably want to make sure it flashed correctly. You can also use adb to disable the Xposed framework if that still doesn't work out for you.
Click to expand...
Click to collapse
I did not mean to be rude or ANY disrespect.
So guys, PLEASE point me to right direction so that i can bring back my device.

rovo89 said:
In case you get into a boot loop:
First, try using the safemode by pressing any hardware key repeatedly. You can find a short explanation how it works here.
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053

rovo89 said:
http://forum.xda-developers.com/xposed/xposed-installer-versions-changelog-t2714053
Click to expand...
Click to collapse
Where can i find disabler zip file?
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.

Rooks said:
Where can i find disabler zip file?
Click to expand...
Click to collapse
From the linked post:
If that doesn't work, you can flash the attached Xposed-Disabler-Recovery.zip by Tungstwenty. It will be copied to your (external) SD card when you install Xposed as well. The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse
Rooks said:
I downloaded some files from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
The only thing it does is copying /system/bin/app_process.orig back to /system/bin/app_process, which you can also do yourself (e.g. with adb shell in recovery mode).
Click to expand...
Click to collapse

GermainZ said:
From the linked post:
Assuming it doesn't work for one reason or the other, you can do this (also from the linked post):
Click to expand...
Click to collapse
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.

Rooks said:
Yes i've tried three different files, all failed to install.
Guess i've no choice left except adb.
Click to expand...
Click to collapse
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.

Rooks said:
Yes i've tried three different files, all failed to install.
Click to expand...
Click to collapse
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?

Rooks said:
Where can i find disabler zip file?
I downloaded some file from web (all around 1.2kb in size) and all these have only one folder "meta-inf", nothing else.
Click to expand...
Click to collapse
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.

GermainZ said:
You may also want to grab a logcat of the boot loop (also using adb), BTW. That way, the issue might actually be identified and possibly resolved in the future.
Click to expand...
Click to collapse
I'll try to get logcat for this issue.
rovo89 said:
You should mainly try the one attached to the other thread... But it will only work on a custom recovery (CWM/TWRP). Not sure, but yours looks more like a stock recovery.
Also, did you try pressing a key many times as written in my quote?
Click to expand...
Click to collapse
Yes, it's the stock recovery and i've tried several times with hardware keys but safe mode did not work in my scenario.
esgie said:
Uninstaller performs only one move operation (or a copy operation plus delete operation) which is being performed on the files which already exist in the device. No need of involving external files, so the only dir in the zip is the one containg updater-binary file ie. META-INF. binary can be a simple, single-liner shell script which triggers basic shell command performing required, trivial operation. As most custom recoveries accept unsigned zips so signing it is not really required, resulting flashable woulď be a zip file containing singłe no more than 100bytes long file placed in a an empty subdir.
12kb size of such a zip shall be considered as a nothing that you should worry about then.
Probably u are running stock recovery which cąnnot flash zips signeď by anyone except a producer. It is also possible that the screenshots come from the older custom recovery, afair primer builds of cwm-based recoveries looked very similiar to stock ones. In thąt case the only reason of failure that I may think of is the fact that earlier versions of cwm did not neccessary provide a possibility to flash unsigned zips; didn't check but maybe uninstaller zip created by the installer is not signed (which I didnt check so I might be wrong; modern recoveries are flashing zips with no signature without any problems by default but less popular devices might be forced to use a version compiled by someone once ąnd never maintained = the only available). You may want to check if there is any option in your CWM that will enablę flashing such a zips and if it isnt possible, sign the zips on your own using any key, even a test one included to signapk.jar.
Click to expand...
Click to collapse
I've tried three different file with different sizes (143kb, 121kb and 145kb), all these files include the same script ("updater-script" file) by Tungswenty.
ui_print("");
ui_print("");
ui_print("------------------------");
ui_print(" Xposed disabler tool ");
ui_print(" by Tungswenty ");
ui_print("------------------------");
ui_print("");
ui_print("Mounting system partition");
ifelse(!is_mounted("/system"),
run_program("/sbin/busybox", "mount", "/system"));
assert(is_mounted("/system"));
ifelse(run_program("/system/bin/sh", "-c", "test -f /system/bin/app_process.orig") == 0,
(
ui_print("Restoring the original app_process file");
assert(run_program("/sbin/busybox", "cp", "-a", "/system/bin/app_process.orig", "/system/bin/app_process"));
set_perm(0, 2000, 0755, "/system/bin/app_process");
ui_print("Restore complete.");
ui_print("You should now be able to boot normally and remove all traces of Xposed from within the Installer app.");
),
(
ui_print("No backup found for app_process, nothing to be performed!");
));
ui_print("");
ui_print("Done.");
ui_print("");
Click to expand...
Click to collapse

Rooks said:
Yes, it's the stock recovery
Click to expand...
Click to collapse
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).

rovo89 said:
Then you can stop trying any flashable zips, they won't work on stock recovery.
If you can install a custom recovery, that should help. Or flashing only the /system partition of your ROM again. Or check if you can execute "adb shell id" and post the result (should show whether you get root access in recovery to perform the steps manually).
Click to expand...
Click to collapse
I've stock rom and recovery, there is no custom rom or recovery available for my device (Toshiba Excite 10 SE aka AT300SE).
So with stock rom and recovery it won't accept any zips and i can't format system partition with stock recovery. And about adb, i don't know where to start. In recovery there is an option to push a file through adb but when i connect my device while this option, my pc does not recognize the device, neither i can update the adb drivers.

Rooks said:
I installed Xposed Installer (v2.6.1) on my rooted Toshiba AT300SE (Excite 10 SE) with AOSP JB on it.
After installation device rebooted and now stuck on boot loop.
Any suggestion to get out of this.
Click to expand...
Click to collapse
HOW YOU ROOT...???!!!
PLEASE TELL ME
I CANT FIND IN WEB....
Give me a links if you can ....
THANKS

[Solution] Getting Android Pay working on Pure Nexus , Chroma, or OMNI

Special thanks to @funkyboy1281, @lentm, @macboy3000 for helping getting this work. As far as I can tell, this is the easiest and most straight forward instruction set for getting Android Pay to work on the latest version of Pure Nexus, Chroma, or OMNI Rom
Clean Flashing
Download the appropriate Rom.
Pure Nexus Discussion​Chroma Discussion​OMNI (no link available, sorry)​
Download Pure Nexus Dynamic Gapps 2-3-16 (Very important, you cannot use 15-3-16 or later). Yes, even if you use Chroma or OMNI, these Gapps should work for you. Link
Download the unSU script for completely unrooting before installing systemless root. Link
Download SuperSU 2.68 (or higher) Link || Discussion
Advance wipe in recovery all but internal storage
Install the ROM, gapps, and unSU
Optional: Install custom kernel
In TWRP, under advanced, go to terminal and type the following:
Code:
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu
Note: You may also do this using ADB in recovery (adb shell, and then enter the same commands. This is much easier in my opinion, and is the method I used.
Flash 2.68 beta in TWRP
Fully reboot, go through initial device setup
Verify in SuperSU that you cannot install SU to the system. This will verify that we are using the systemless root option
Download SafetyNet Helper and make sure it passes
Install Android Pay and profit!
Dirty Flashing
Verify that SafetyNet still passes in Android.
Verify in Android that /data/.supersu is still present and contains the appropriate options (see clean flashing). You may also verify in recovery by going to terminal commands and entering in:
Code:
cat /data/.supersu
Install the updated ROM (do not reinstall gapps unless your ROM builder specifically tells you to do so. Pure nexus does not require a reflash)
Optional: Install unSU. This was not necessary on PureNexus, but I cannot be sure for other roms. It shouldn't hurt anything to flash.
Optional: Install custom kernel
Install SuperSu 2.68 (or higher)
Check SafetyNet Helper and make sure it still passes
FAQ
Q. Can I still install and use AdAway?
A. Yes. You must first install something in recovery before installing AdAway. See the discussion Thread. You should be installing v3.1 of the app after you install the recovery zip.
Q. Can I still use V4A?
A. Yes. I do not use this however, but it has been reported that nothing special needs to be done.
Q. Can I change the screen density?
A. We have not found a way to do this without tripping Safety Net

..

@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.

MrBrady said:
@skaforey thanks for this thread! Might want to note in the OP that Wiping Data erases the internal storage. Some people may not know that.
Click to expand...
Click to collapse
Noted, thank you! Still hoping some of the lucky folks that have it working can help us out here.

Has anyone found a way to adjust the screen density while keeping Android Pay functional?

MrBrady said:
Has anyone found a way to adjust the screen density while keeping Android Pay functional?
Click to expand...
Click to collapse
You (should) be able to change the density through adb using
Code:
adb shell wm density DPI
with dpi being what you want, or if you have root you can do that from a terminal emulator, just remove the adb shell part.

I tried the 2nd method without formating data in different combos to no avail, still hesitant to wipe my internal sdcard, it shouldn't be that hard man, will follow this thread
anyone know other aosp ROMs that have AP working outside of pure nexus?
Sent from my Nexus 6 using Tapatalk

Following the steps in the top most instructions in the OP...
1) Pure Nexus 3/8 does not have root out of the box, so the Unroot step was not needed.
2) TWRP did not show any files/folders in the /su directory, so the Terminal command didn't work. I booted up the device and did it through the Terminal there instead and then rebooted.
After that, loaded up Android Pay and it says "Android Pay can't be used".
Running SafetyNet reports....
SafteyNet request: success
Response validation: success
CTS profile match: false

Tried different methods, not working for me.
1. Download Pure Nexus 1/03/16 or newer (Layers), the latest PN GApps, UnSU, the latest SuperSU.
2. Backup any important data.
3. Boot into TWRP and wipe everything including internal storage
4. Format data.
5. reboot TWRP with USB-OTG that has fines necessary.
6. Flash Pure Nexus.
7. Flash GApps.
8. Flash UnSU.
9. In terminal I saw I still had a folder /supersu so I deleted that.
reboot. Setup phone with google account. Did not have it restore apps, but did have it restore basic setup from google.
Install Safetynet helper
Still fail CTS Profile Match
Don't know what the people are doing different, but not working for me.
Are you using the PN-Gapps or others?
The updated-unsu is what date?
Thanks!

The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.

What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.

@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk

sgloki77 said:
@macboy3000 what kernel and what version of SuperSU did you use, ? I tried your method, ROM booted fine but safetynet test failed...
this is how I did it
unzip ROM
edit code out
delete supersu folder
zip ROM
advance wipe everything but internal
flash ROM
flash pn gapps
flash elemental kernel
flash supersu
boot into android, delete xbin_bind
reboot system
permissions on bin folder were already 751, so didn't need to change
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.

macboy3000 said:
Weird...I'm using SuperSU 2.67 and I'm also using Elemental kernel.
Click to expand...
Click to collapse
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk

sgloki77 said:
Did you format data? I'll give it a shot with 2.67, I used 2.68
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I formatted everything except internal storage before installing.

macboy3000 said:
What I did to get AP to work was removing these lines from updater-script located in META-INF > com > google > android
Code:
ui_print("Flashing SuperSU..");
package_extract_dir("supersu", "/tmp/supersu");
run_program("/sbin/busybox", "unzip", "/tmp/supersu/supersu.zip", "META-INF/com/google/android/*", "-d", "/tmp/supersu");
run_program("/sbin/busybox", "sh", "/tmp/supersu/META-INF/com/google/android/update-binary", "dummy", "1", "/tmp/supersu/supersu.zip");
ui_print(" ");
and removed the supersu folder inside the zip file. I then installed my custom kernel and systemless supersu. After that, I set the permissions for bin folder inside su to 751 using a root explorer and deleted xbin_bind.
Click to expand...
Click to collapse
Well I tried this and still no luck
I even tried flashing the modified ROM, gapps, and never flashing SuperSU at all (so my rom wasn't rooted at all), and SafetyNet still gives me a red screen. I really wish I knew what was triggering this for some and how others can make it work.

I tried again using 2.57 SuperSU and Elemental X and still fails. Would someone that got it working be able to post a more detailed log of exactly what steps you're using and exactly what files you're flashing.

MrBrady said:
The only way I have gotten AP to work is from a stock image based ROM. It doesn't seem to work with AOSP ROMs like Pure Nexus.
For example, I am currently running Tupac's debloated stock ROM with Cataclysm MOD, Viper4Android and AdAway ad blocking. Android Pay works fine, as long as you follow the SU steps listed in the OP of this thread.
Click to expand...
Click to collapse
This has been my experience as well !

jcrompton said:
This has been my experience as well !
Click to expand...
Click to collapse
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?

lentm said:
Got Android Pay working with Tupac's debloated stock ROM too! Thanks!
Is it possible to change DPI and keep Android Pay working?
Click to expand...
Click to collapse
Not that I have found, unfortunately. Even via just ADB commands.

[ROOT][6.0][XT1097] Systemless root for Moto X 2014

Hello, everyone!
TL;DR: You're about to perform a systemless root installation on your phone so make sure you have uninstalled Xposed Framework, uninstalled root, the device's bootloader is unlocked and your phone's boot image is in its untouched stock state. Then boot into TWRP and install SuperSU-v.279-SR3 or newer.
UPDATE 2017-01-19:
- Provided missing bootloader information regarding root. Thanks, @Charlita for the heads-up!
- Moved TL;DR section to the top.
UPDATE 2017-01-15:
- SuperSU-v.279-SR3 learned how to use systemless mode as default flashing method for Motos. This is great news as the installation process now is just a matter of flashing the SuperSU installer. The segmentation fault had been fixed on SR2 and this version also includes that fix.
- Included a TL;DR section.
UPDATE 2016-12-25:
- SuperSU-v.279-SR1 contains a regression bug regarding the "segmentation fault". Skip this version for now. I've already contacted Chainfire.
- suhide: as the Chainfire himself stated, the tool is a losing game so I'm not putting any further effort here.
UPDATE 2016-11-03:
- As of SuperSU-v2.78-SR3 boot image patching works out-of-the-box. Just install it and you're done!
- TWRP version 3.x works as expected.
- Unfortunately, SafetyNet checking fails as Google constantly updates the server-side code.
- WIP: Check if Chainfire's suhide are able to help here.
UPDATE 2016-08-08:
- Added a backup reminder.
- Added flashable zip systemless_root_enabler_by_glauberlima.zip.
After a few days playing with it, I finally managed to perform a systemless root install for our beloved Moto X 2014
Benefits:
- Install OTA updates when they arrive;
- SafetyNet checking will pass so Android Pay can be used (not available in Brazil yet).
Requirements (links below) :
- Android 6 Marshmallow
- Bootloader must be unlocked otherwise you won't be able to root your phone;
- Boot partition must be in its original untouched stock state otherwise, SuperSU installer won't be able to patch it;
- System partition must be untouched as well but a simple uninstall of applications that have changed it should be enough. This step is not mandatory but if your system partition remains changed SafetyNet checking will fail;
- Your device must be unrooted. SuperSU has the option "Completly remove root". Use it;
- If you have Xposed Framework installed, uninstall it;
- You'll need ADB and Fastboot in order to flash stock boot.img if applicable;
- TWRP. Version 3.0.2-2 works just fine. If you prefer 2x series, I highly recommend version 2.8.7.1;
- SuperSU-v2.79-SR3 zip installer (or a newer version). DO NOT TRY AN OLDER VERSION. WILL NOT WORK;
Install guide:
- Make a Nandroid backup first using TWRP;
- Uninstall Xposed Framework if applicable;
- Uninstall SuperSU;
- Connect your device to your computer via USB;
- Reboot into bootloader:
Code:
adb reboot-bootloader
- Restore stock boot partition (you can skip this step if you already been on stock boot):
Code:
fastboot flash boot xt1097_boot_stock_with_may_2016_update.img
VERY IMPORTANT: The binary file boot xt1097_boot_stock_with_may_2016_update.img is device dependent. I have extracted stock boot.img from victara May 2016 update full ROM package and put it here. If you are trying on the other variants, make sure you will use the right image.
- Reboot into Recovery (TWRP);
- Flash the attached zip file systemless_root_enabler_by_glauberlima.zip. This will set both variables SYSTEMLESS=true and BINDSYSTEMXBIN=false. Without these variables set, SuperSU will fail to systemless root the device. Feel free if you want to manually enter the commands in the Command Prompt:
Code:
adb shell "echo SYSTEMLESS=true>/data/.supersu"
adb shell "echo BINDSYSTEMXBIN=false>>/data/.supersu"
- Install SuperSU and reboot system. If the first boot fails, just wait - the second will work I promise you!
- As soon as Android UI shows up you should be systemless rooted;
- Confirm SuperSU is installed by recognizing the green icon on your app drawer;
- Open up any root app you have. The world-famous Superuser permission request dialog should pop-up;
- Install SafetyNet Helper, in order to attest your Android, is passing Google's SafetyNet checking: https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Now you should be good. Congrats!
Go ahead and get some systemless apps:
- Systemless Xposed Framework
- Systemless Adaway
This procedure should work for the other variants too - all you need is the original boot.img
If you need any help feel free to ask.
Attached you can find the screenshots taken from my XT1097 after the procedure
Related links:
SuperSU-v2.79-SR3:
https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip
Latest stable SuperSU:
http://download.chainfire.eu/supersu-stable
Systemless Xposed Framework:
http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Systemless AdAway:
http://forum.xda-developers.com/showthread.php?t=2190753
Material Design Xposed Installer:
http://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758
Minimal ADB and Fastboot:
http://forum.xda-developers.com/showthread.php?t=2317790
TWRP for Moto X 2014:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-0-0-touch-recovery-t2911523
Thanks:
@Chainfire

Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk

rtrotsky said:
Even if I am on stock I have to flash boot*.img?
Sent from my XT1097 using Tapatalk
Click to expand...
Click to collapse
Since your device already has the untouched stock boot you don't need to flash anything.

I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?

jbaumert said:
I seem to be having trouble installing the "Systemless Xposed". It errors out with - ! Failed: Unable to extract zip file!
I have verified "systemless root - ver 2.76" and tried re-downloading the zip. Any thoughts?
Click to expand...
Click to collapse
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.

glauberlima said:
Could you provide your recovery.log from TWRP?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip[code]
This will copy contents to the clipboard. Paste it in notepad then save and attach here.[/QUOTE]
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse

vpxf said:
This is pretty neat. Given what I read as the requirements am I correct this only works with stock ROM? (and test will only pass on stock).
Click to expand...
Click to collapse
Hi @vpxf
The unmodified boot.img is a requirement for SuperSU as it tries to patch the boot image on-the-fly during the install process (by the time you flash it using TWRP). If the image is not in its original state, SuperSU will fail to install in systemless mode.
Regarding your question about custom ROMs compatibility I don't know if the SafetyNet checking will pass/fail. That's a good test to perform.

glauberlima said:
Could you provide your recovery.log from TWRP so we can see the detailed logging information?
You can pull it from your device by running the following command in command prompt:
Code:
adb shell cat /tmp/recovery.log | clip
This will copy recovery.log contents to the clipboard. Paste it into notepad then save and attach here.
Click to expand...
Click to collapse
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.

As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.

bertolehm said:
As glauberlima found out in the other thread, you need to re-zip the xposed installer with 7-zip (that's what i used at least) and the install will work.
Click to expand...
Click to collapse
jbaumert said:
I've attached the log. I did notice "unzip: zip flags 1 and 8 are not supported".
NOTE: I was able to flash the 85.7 version found in the second post of the "Systemless Xposed" thread. The newest 86.2 is the one giving me troubles.
Click to expand...
Click to collapse
As stated by @bertolehm I've discussed in the other posts the exactly same issue with the zip installer you have reported @jbaumert. Take a look at them:
http://forum.xda-developers.com/showpost.php?p=67792193&postcount=1193
http://forum.xda-developers.com/showpost.php?p=67805517&postcount=1233
Regarding your device being systemless rooted check with SafetyNet Helper Sample app. If everything turns green you are good

** Duplicated **

Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little

oyoyl said:
Thanks for the tutorial.
The first boot fails, ok ; but how long is the second boot ?
I wait a long time (around 15 minutes) blocked at the first screent (static moto logo) and I stop it, reboot and reinstall my backup. I panic a little
Click to expand...
Click to collapse
Which variant is your X?

glauberlima said:
Which variant is your X?
Click to expand...
Click to collapse
XT1092

oyoyl said:
XT1092
Click to expand...
Click to collapse
15 minutes... That's definitely too much.
I'm about to update this guide with my new findings so If you don't mind I'd like to suggest you this:
Repeat the steps but this time skip the update to latest version. After the reboot access SuperSU. It should display a message regarding your su needs update. Accept it.
Make sure your nandroid backup is up to date.

Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks

Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss

Hi! Hey, I followed the steps and my MotoX got stuck when rebooting after flashing. I'm trying to enter fastboot with power+Volume down but no luck so far, any idea? I hope you can help me!

oyoyl said:
Same thing, but it's possible that my boot image is not up to date and I have no other boot backup to test.
I have only a complete backup (boot + system without root), perahps I'll try later with complete restore ...
Thanks
Click to expand...
Click to collapse
OK. Just leave a reply by the time you have the result of your test.

guilhermoaraujo said:
Something went wrong, the root works fine, but when I run the SafetyNet test, I got "CTS profile match: false", I just want to keep the OTA upgrades working, if I did something wrong, is there any way to unroot and do the systemless root again?? Thankss
Click to expand...
Click to collapse
One of your installed apps modified system partition. Did you test on a completly stock image?

[Guide] Oneplus 3 Magisk Install (Android pay W/ Root and Xposed)

Okay so basically. topjohnwu has released another marvelous mod that allows you to use android pay with xposed and root by unmounting root.
ALL CREDITS GO TO HIM : http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382 (buy him a beer)
I'm making this guide just for oneplus 3 users, some people might be scared of breaking there device or maybe couldn't understand the instructions too clearly. As I don't want to be held accountable, I am not responsible for anything that happens to you while following this guide.
EDIT: You can find your boot.img just by extracting your rom or opening it with some type of archiving program such as Winrar or 7-zip
IF YOU ARE ON V3 or lower please use the uninstaller first before upgrading. LINK HERE IF YOU NEED IT
(Then follow the same steps)
Update : Topjohnwu has updated most of the API ( I will post a tasker script when I test it a bit more) . Also Magisk is now a seperate apk signed by him.
Requirements :
100% stock system + boot (This is recommended, I simply just flashed boot.img and uninstalled supersu and xposed). I am on 3.2.2
Remove supersu and xposed (If you're not going to be completely go stock.
Downloads : (Things you're going to need)
Magisk v6 : Link Please go to the original thread and make sure it's the latest one
Magisk Compatible phh's SuperUser v17: Link
V1.2 Magisk ManagerNeeded for toggling
You're also going to have to download the manager for it : (Here)
These are the steps I took thus me creating the guide
Steps :
Step 1 : If you aren't completely stock go ahead and flash boot.img. Here's the link to the boot img from OOS 3.2.2 (Click)
-So to flash a boot img all you have to do is use adb and run the command
Code:
fastboot flash boot boot.img
then
Code:
fastboot reboot
Step 2 : When you flash the boot.img, you're going to have to flash TWRP after that as it'll be gone.
Step 3 : Flash the Magisk zip
Step 4 : Flash phh's SuperUser Zip (reboot the phone and make sure everything is still working) and then download the root manager from the playstore. You can test by opening up Magisk and toggle "Root Mount Toggle" and try to add a card in android pay
Step 5 : Install Systemless xposed (I'll give a step by step underneath here)
Download and install Material Design Xposed Installer (Here)
You can open up Material Design Xposed Installer then click "Systemless" tab and click install/update (make sure it says sdk23), This didn't work for me so if it does not work download the latest one :HERE
Profit!?
If you guys want any explanation or help, post here and i'll help you out . You can also donate to me here CLICK HERE (Hint : It's not my donation link)
Also mods, if this is somehow against the rules, feel free to delete this. I just want to help out some fellow users.

Wonderful guide. Got Android Pay working this way.
At the time of writing this, I think the reason step 5.2 doesn't work on Material Design Xposed Installer was partly because xposed 86.2 was the highest version available for me. In order for Magisk to work, you'll need xposed 86.3 which is provided by the OP.
Well done!

First off, great guide. I'd like some information if that is okay.
So according to the original thread this doesn't enable the option to use CM 13 and still have Android Pay, no custom roms. Is that correct? If so, what is the actual use? Because Android Pay works on stock, so why root if you can't change a rom?

Just one information: on phh' site there are 3 different superuser zips :
[ ] superuser-r170.zip 2016-01-31 22:25 3.7M
[ ] superuser-r197.zip 2016-04-12 13:29 3.6M
[ ] superuser.zip 2016-01-31 22:25 3.7M
Which one i have to flash? I thought the latest one (197) should be fine.
Thank you in advance.

Pengod said:
First off, great guide. I'd like some information if that is okay.
So according to the original thread this doesn't enable the option to use CM 13 and still have Android Pay, no custom roms. Is that correct? If so, what is the actual use? Because Android Pay works on stock, so why root if you can't change a rom?
Click to expand...
Click to collapse
Okay, this is a hard question to answer but it should work on an official release of cm 13. Not a nightly, as those aren't CTS run. I will try and get it running on my Oneplus one. The only thing though is if you do decide to go for it. CM comes pre-rooted so you might have to find a way to delete it from the system.
However, you can still flash this and test it, if it doesn't work then just report back and i'll try and come up with something should it be in my power . Always make a backup though through TWRP .

wolfrules said:
Just one information: on phh' site there are 3 different superuser zips :
[ ] superuser-r170.zip 2016-01-31 22:25 3.7M
[ ] superuser-r197.zip 2016-04-12 13:29 3.6M
[ ] superuser.zip 2016-01-31 22:25 3.7M
Which one i have to flash? I thought the latest one (197) should be fine.
Thank you in advance.
Click to expand...
Click to collapse
Download the one from the link I put in my post. It has a couple of changes in it. It also includes
Code:
"# phh's open source root for Magisk
# by topjohnwu
#"
In it's update-binary.

katsumex said:
Download the one from the link I put in my post. It has a couple of changes in it. It also includes
Code:
"# phh's open source root for Magisk
# by topjohnwu
#"
In it's update-binary.
Click to expand...
Click to collapse
Thank you very much,great work.

Will this mod help you pass the safetynet test?
And by flashing the boot.img will you wipe your apps/data?

SysAdmNj said:
Will this mod help you pass the safetynet test?
And by flashing the boot.img will you wipe your apps/data?
Click to expand...
Click to collapse
Yes , it'll unmount the whole root and pass the safetynet till you remount it.
No it will not wipe all your data. It'll only wipe your recovery and possible your root.

Question.. does root mount need to be toggled to ON for adaway to work? if so, with that being ON will you be able to use android pay at stores (understood that credit card will be added after toggling root to off).. I guess I am asking what to do after you successfully add a card to android pay. Can the toggle be changed to mount root and still have android pay work in stores?

Wonder if there is a way to control this via Tasker?

androidbuff123 said:
Question.. does root mount need to be toggled to ON for adaway to work? if so, with that being ON will you be able to use android pay at stores (understood that credit card will be added after toggling root to off).. I guess I am asking what to do after you successfully add a card to android pay. Can the toggle be changed to mount root and still have android pay work in stores?
Click to expand...
Click to collapse
Whenever you want to use it, you have to toggle it.

dustintinsley said:
Wonder if there is a way to control this via Tasker?
Click to expand...
Click to collapse
Not yet. I made a request so let's see if he'll add some functionality

I had mount root set to on and I was able to withdraw cash from a bank of America ATM. One possible reason why that worked could be because for ATM use all it takes from android pay is the card information. You do have to input the pin after.
Sent from my ONEPLUS A3000 using Tapatalk

androidbuff123 said:
I had mount root set to on and I was able to withdraw cash from a bank of America ATM. One possible reason why that worked could be because for ATM use all it takes from android pay is the card information. You do have to input the pin after.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
Very interesting, maybe it'll work for one boot cycle. I restarted my phone and had to toggle it to bypass pay again.

Works perfectly! Now I can use my banking app in New Zealand (ASB)

What about custom kernel user ?

otonieru said:
What about custom kernel user ?
Click to expand...
Click to collapse
It works with everything. It's just you won't get Android Pay on non-stock phone.
I personally use this on RR with ElementalX 'cause I don't care for Pay at all.

Personal tested Android Pay with 2 purchase and all work.
Unlike chainfire systemless root method, systemless phh's SuperUser work without disabling Xposed.. Plus, no reboot is required.. Using Oneplus 3 stock rom.

ThomasC1970 said:
Personal tested Android Pay with 2 purchase and all work.
Unlike chainfire systemless root method, systemless phh's SuperUser work without disabling Xposed.. Plus, no reboot is required.. Using Oneplus 3 stock rom.
Click to expand...
Click to collapse
How does Magisk compare to SuperSU? Is everything the same "on the outside" (user experience, etc).

Magisk module unzip error

I rooted my Motorola One Macro yesterday, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
Pasting uzipped energized folder to /data/adb/modules makes it appear in module section in Magisk, but still it don't work. Material Terminal says acces denied after typing in energized - m command. Reinstallation of Magisk didnt helped. I dont really want to factory reset my phone, is there anything that i can do?

_lama195 said:
I rooted my Motorola One Macro yesterday, I unlocked bootloader and installed Magisk. I don't have custom recovery beacuse i had problem with installing it. Root Checker says root is properly installed on my device, but I have somme issues with getting things to work. I downloaded Magic Mask Repo, and tried installing Energized module. It downloaded suscessfully, but installation doesn't seem to do anything even after reboot. I also tried installing it manually with Magisk, but I got this in console:
- Copying zip to temp directory
! Unzip error
Pasting uzipped energized folder to /data/adb/modules makes it appear in module section in Magisk, but still it don't work. Material Terminal says acces denied after typing in energized - m command. Reinstallation of Magisk didnt helped. I dont really want to factory reset my phone, is there anything that i can do?
Click to expand...
Click to collapse
this is an easy one....
that error *usually* implies youve downloaded a master zip of a github repo, and not a zip file from the releases section
if you went to
GitHub - Magisk-Modules-Repo/energizedprotection: Energized Protection Magisk Module.
Energized Protection Magisk Module. Contribute to Magisk-Modules-Repo/energizedprotection development by creating an account on GitHub.
github.com
and then downloaded the zip it will NOT work, and they dont have a release
so heres the easy fix, and why it fails
1) unzip the file, you'll get a folder (energizedprotection-master)
Note this is why magisk wont install it, it expects to find files (especially crucial files to tell it how to install the module) and folders in the root directory, not a single folder with nested files and folders under it...
2) go into energizedprotection-master folder
3) select all files/folders
4) zip the selected contents into a new zip file (ideally with 7zip - WinRAR can create dud zips)
5) move that zip to device and flash
Ideally you'll install Fox's Magisk Module Manager and use that for most modules - energized may not be on it - download the .apk
Release Release v2.0.2 · Fox2Code/FoxMagiskModuleManager
Please read the full changelog. It contains very important information on the future of this app and caveats when updating. Release notes: https://www.androidacy.com/magisk-module-download-simplifi...
github.com
the old magisk repo was decommisioned....

It works now, I greatly appreciate it, thanks!

73sydney said:
this is an easy one....
that error *usually* implies youve downloaded a master zip of a github repo, and not a zip file from the releases section
if you went to
GitHub - Magisk-Modules-Repo/energizedprotection: Energized Protection Magisk Module.
Energized Protection Magisk Module. Contribute to Magisk-Modules-Repo/energizedprotection development by creating an account on GitHub.
github.com
and then downloaded the zip it will NOT work, and they dont have a release
so heres the easy fix, and why it fails
1) unzip the file, you'll get a folder (energizedprotection-master)
Note this is why magisk wont install it, it expects to find files (especially crucial files to tell it how to install the module) and folders in the root directory, not a single folder with nested files and folders under it...
2) go into energizedprotection-master folder
3) select all files/folders
4) zip the selected contents into a new zip file (ideally with 7zip - WinRAR can create dud zips)
5) move that zip to device and flash
Ideally you'll install Fox's Magisk Module Manager and use that for most modules - energized may not be on it - download the .apk
Release Release v2.0.2 · Fox2Code/FoxMagiskModuleManager
Please read the full changelog. It contains very important information on the future of this app and caveats when updating. Release notes: https://www.androidacy.com/magisk-module-download-simplifi...
github.com
the old magisk repo was decommisioned....
Click to expand...
Click to collapse
Hey I am trying to install BCR - Module module from github " https://github.com/chenxiaolong/BCR " but I am unable to install it in magisk. It is throwing the same error . Can you help me with that ? Thanks in advance

Arnavsingh7075 said:
Hey I am trying to install BCR - Module module from github " https://github.com/chenxiaolong/BCR " but I am unable to install it in magisk. It is throwing the same error . Can you help me with that ? Thanks in advance
Click to expand...
Click to collapse
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....

73sydney said:
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
Click to expand...
Click to collapse
You are an absolute hero, thank you so so much for this

73sydney said:
go to the Releases section on the right of the page with Version 1.29 and green latest to the right of it, scroll down to assets and click on BCR-1.29-release.zip to download the module...this WILL flash, or your money back...
....like my earlier post says, youre probably downloading the master or source code which wont work unless you unpack and repack it (and then sometimes not, if they havent actually compiled the apk if theres an apk component), if there is a Release section with active Releases, use that....
Click to expand...
Click to collapse
Bro what abt this it's having same issue is there any other way rather unzip and zip it again https://github.com/rithvikvibhu/nh-magisk-wifi-firmware