Just bought a XT1575. I followed this link to get it unlocked, installed latest stock rom (6.0 MPH24.49-18-4 from here), and I installed latest TWRP recovery.
Then I tried to install root and Xposed framework. I tried several methods from this link :
Install superSU 2.62-3, my device goes bootloop. I have to recover from my TWRP backup.
Install SuperSU 2.78 with "echo SYSTEMLESS=true>>/data/.supersu" before install. bootloop again.
Please help me on this, thank you so much!
Try this for forced systemless root: http://forum.xda-developers.com/moto-x-style/help/wifi-wont-root-t3463656/post68764815
Then flash Systemless Xposed by topjohnwu, attachment named "xposed-v86.2-sdk23-topjohnwu.zip": http://forum.xda-developers.com/showpost.php?p=67074428&postcount=2
Or romracer's version named "xposed-v86.1-sdk23-arm64-systemless-by-romracer-20160928.zip" in sdk23 > arm64: http://forum.xda-developers.com/xposed/super-alpha-posted-permission-xposed-t3072979
The systemless method you noted is correct. Did you boot fully on the 6.0 ROM first, before trying to flash SuperSU? If you did, verify in the TWRP terminal 'cat /data/.supersu' contains only the SYSTEMLESS=true string, and when you flash SuperSU the log says something about systemless installation.
@acejavelin I did checked there's only SYSTEMLESS=true before install. Very weird.
@pshadoww I know it works... I literally did it this morning to test the lastest 2.78-SR1. It will bootloop twice, then boot after a very long wait that seems scarily long.
@Spasticdroid Greate resources. I tried the systemless root installer you mentioned and it works.
That might be it, I guess I waited for too long and think it's not working. Anyways I used the forced systemless root installer and it works now. Thank you!
Related
I'm on a B09, bootloader unlocked and rooted with SuperSU 2.65 A2017G.
Except from the 2.65 version, is there another one working for the A2017G?
I want to get Xposed and if I do understand I need SuperSU 2.75 or above to get Xposed to work in systemless.
If there isn't another version could you guys help to get Xposed working on my phone?
That would be much appreciated.
EDIT: Well I'm dumb, I assumed Oki's guide only worked on the A2017U variant. Sorry guys :/
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Yeah I figured it out with the help of Oki's guide.
Thanks for the answer!
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
nuserame said:
I'm having a problem where many apps do not get root unless I manually open SuperSU, which means that most root apps are not working properly because they can't work automatically. Is there another version of SuperSU or TWRP that I can flash to solve this problem?
I'm on A2017U B29 stock, SuperSU 2.79 flashed from TWRP 3.0.2-2
Click to expand...
Click to collapse
Did you make sure to disable system write protection? Boot into TWRP, open up the terminal emulator, and issue the command: reboot disemmcwp
I'm having a similar problem while flashing superuser. The error happens after the "patching sepolicy" line runs. The error prevents SuperSU from being installed at all. Any suggestions?
You need to flash twrp 3.0.3 or above and flash SuperSU 2.79
Latest SuperSU Causes Endless Loops on the Axon 7
Literally, every time I install the latest version of SuperSU on my axon I get an endless bootloop. These are SuperSU files I get directly from chainfire's website. There must be something im missing, or maybe im downloading the wrong version? Im not sure i was hoping to get some help. I just tried installing: SR3-SuperSU-v2.79-SR3-20170114223742.
>> Can anyone point me in the right direction of the latest SuperSU that works with the Axon 7 that doesnt bootloop it.
I remember that the Pixel phones had SuperSUs that were made for it. I am wondering does the same thing apply here?
I have installed everything right on my phone to the T. Everything was brand new stock.
Kinanizer said:
If you have the official version of TWRP you should be able to install the latest version of SuperSU.
Click to expand...
Click to collapse
so i recently got the pixel, had the moto x for about a year and decided to see what was going on with the rooting scene with this device. turns out that someone came along and created a simple solution to rooting and installing twrp for this device. I was happy. TWRP works just fine. But upon flashing SuperSU and rebooting from that i'm now stuck on the M logo permanently it seems. Yes i can reboot back into recovery and fastboot mode. But i can't seem to get past the M logo and all i've done was flash TWRP and SuperSU any idea about what's going on?
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Spasticdroid said:
You need to flash as systemless root. Recent versions of SuperSU installs it as system root by default on this phone for some reason.
The SuperSU zip from my thread does it: https://forum.xda-developers.com/mo...t/rom-marshmallow-6-0-september-2016-t3536120
Click to expand...
Click to collapse
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
silvernirvash said:
awesome thanks!!!! <3 now i just need to find a rom to play around with :3
Click to expand...
Click to collapse
No offense, but why are you bothering to root if you are just going to flash a ROM?
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
acejavelin said:
Also, there is nothing wrong with the latest version of SuperSU, you just need to do a manual systemless flash by creating the file /data/.supersu with the contents "SYSTEMLESS=true" and it will work perfectly.
Click to expand...
Click to collapse
That's exactly what my zip does. I've only put it together to make the process much simpler, and I love automating stuff when it's possible.
SuperSU inside is unmodified. Updater-script copies a file named "systemless" from the zip which has "SYSTEMLESS=true" in it to /data, renames it to ".supersu", then proceeds flashing SuperSU.
Hello all,
I need some help!I have a Moto X Pure Edition XT 1575 I just unlocked bootloader and then intalled TWRP 3.1.1 and then installed SuperSU 2.79 and now no Sim is detected. What did I do wrong?
Thanks!
Unroot & clean with supersu app. It should restore boot image.
/You can also restore boot, system, wipe data in twrp/
Reboot & check.
If ok try rooting with supersu 2.82 or magisk 14. @kaleend101
This is my installation process [last post is OK]
https://forum.xda-developers.com/galaxy-s5/help/wifi-problem-flashed-lineageos-t3576865
Below are screens from CATLOG [not full tho]
If I try to update binaries in TWRP it stops [nothing in TWRP logs about SU], restarts and stops during Lineage loading screen forever.
So I flash ROM again, and SuperSU from TWRP to fix it.
I was reading that after flashing SuperSU - during first restart it should ask me something like "DO you want to keep root" - it doesn't happen.
SuperSU has no apps listed with root access, but root is OK. TitaniumBackup works, but I'm afraid some of the apps doesn't work properly
Now I'm using
lineage-14.1-20170329-nightly-klte-signed.zip
addonsu-ARM-signed_14.1
SM-G900F
Is there a way to have it done?
I remember like trough a fod that once I was setting permissions in Terminal for some files before updating SU? AM I correct?
Thanks for reding
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Saber said:
Hi,
With LineageOS, you must only use one root method otherwise problems will occur. The addonSU zip and SuperSU are not the same thing.
The provided root SU zip from Lineage should be enough to give root permissions for apps. If you want to use SuperSU instead of the SU provided by the Lineage team, you must not flash the addonSU zip.
Click to expand...
Click to collapse
I have tried to flash everything and indeed only addonsu-ARM-signed_14.1 is working from TWRP level. Although SuperSU from APK is working OK [latest SR4].
So root seems to be fine for browsing into root or TB! is not complaining about root, but I can not update SU binary - I have also updated Lineage to today's nightly - same thing.
I've used an S4 with lineage and flashing supersu doesn't work. ONE app in particular will not work because the su part of lineage (and old cyanogenmod) doesn't cooperate; it needs supersu for some reason. I was originally on Cyanogenmod from about a year ago, and tried flashing supersu and had this very problem, which is why I tried lineage, but lineage doesn't work and I cannot flash supersu either. I can install from the play store, but it won't update the binary; flashing in recovery fails (in both older cyanogenmod and lineage os) at the boot image patcher step.
supersu 2.79 said:
Finding boot image
Boot image: /dev/block/mmcblk0p20
Extracting ramdisk
Decompressing ramdisk
Failure, aborting
Click to expand...
Click to collapse
The only reason I'm having to resort to this is because Samsung has a problem with their s7 screens failing and won't do a recall...so I'm having to use an older phone and trying to setup my rooted apps, all of which work with the standard Cyanogenmod root or lineage+su addon, except for one app.
EDIT:
Ah-ha, system mode may be the solution, but I'm still trying to get it to boot without getting stuck! I haven't tinkered with supersu in well over a year, and I didn't even know there were two methods for it now.
https://forum.xda-developers.com/apps/supersu/v2-64-2-66-supersu-mode-t3286120
Does anybody know if it's possible to change Superuser without having to flash stock ROM?
I'm on stock 7.0 and when I tried to install SuperSU I've got a bootloop (wrong version of SuperSU, there wasn't the wright version available yet) so I found a guide to root my device using another supersu (phh superuser) and it's working perfectly.
I wonder if there is a way to change from Phh superuser to SuperSU (now there's a compatible version with 7.0 available) without having to flash stock ROM again and lose all the data.
(Sorry if there's a thread already talking about that but, if there is, I didn't find it)
There's a screenshot of the superuser app
Supersu installation using twrp
To install supersu you need twrp. You have to use systemless mode to install supersu. For systemless mode goto twrp then advanced>terminal
Type:
echo "SYSTEMLESS=true" > /data/.supersu
Then install Supersu.zip.
For latest supersu visit official supersu download page.
Dex5er said:
Does anybody know if it's possible to change Superuser without having to flash stock ROM?
I'm on stock 7.0 and when I tried to install SuperSU I've got a bootloop (wrong version of SuperSU, there wasn't the wright version available yet) so I found a guide to root my device using another supersu (phh superuser) and it's working perfectly.
I wonder if there is a way to change from Phh superuser to SuperSU (now there's a compatible version with 7.0 available) without having to flash stock ROM again and lose all the data.
(Sorry if there's a thread already talking about that but, if there is, I didn't find it)
There's a screenshot of the superuser app
Click to expand...
Click to collapse
@Dex5er You Need To Flash Elementalx Kernel Before You
Try To Flash SuperSU And SuperSU Version Doesn't Matters Its Universal For All Devices
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
For Users who want to remain Encrypted:
1. Boot into TWRP Recovery and allow system modifications.
2. Swipe right and enable modifications.
3. Select your preferred Language, Tap “Never show this screen on boot again,” and Swipe allow modification.
4. Navigate to Install and select Magisk Or SuperSU to root OnePlus 5.
5. Swipe to confirm the flash
6. Reboot System
Click to expand...
Click to collapse
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
.........
-Calling user ramdisk patch script
---Failure, aborting
-Unmounting /system and /vender
-Done
Click to expand...
Click to collapse
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
netsonic said:
Oneplus 5, Official ROM, H2OS, Android 7.1
1. First time, I followed https://forum.xda-developers.com/oneplus-5/how-to/oneplus-5-unlock-bootloader-flash-twrp-t3624877 and successfully install TWRP and root using Supersu. I can goes into TWRP recovery without any problem. I notice that the supersu I installed in a systemless one, some apps can't get root access, like AD Away, Titanium Backup. But most apps can work with it. I used the one of the two root method in that tutorial as follows:
2. After several months I want to upgrade the original H2OS to new version, so I unroot in Supersu first, when it ask me if I want to recover Boot Image, I say "Yes", and say "NO" when ask me if I want to recover Recovery Image. Then I upgrade to the new H2OS v13 (Android 7.1) using the Full package through TWRP, after that I reinstall TWRP 3.2.1, it was successful. But it doesn't ask me to allow it to make modification. I tried to install Supersu 2.82 and 2.82 SR5 using the same method as in tutorial, at the end of "Booting Image patcher" it shows
Then I reboot to recovery, it return to official REC, not TWRP, and system says there is no root.
Click to expand...
Click to collapse
Just use the latest universal codeworks recovery and flash it via fastboot.
For root i suggest use of Magisk over Su, the latest 15.3 works fine for me.
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
netsonic said:
What is the codeworks recovery? Is it "twrp-3.2.1-0-cheeseburger.img" on https://twrp.me/oneplus/oneplus5.html?
Click to expand...
Click to collapse
No, it's the -universal- one from here https://forum.xda-developers.com/on...overy-twrp-3-2-1-0-oreo-oxygenos-5-0-t3725723
I can flash universal TWRP and Magisk 15.3. But Magisk show "SafetyNet API Error"? How to fix it?