MotoXPlay on Android 6.0.1 after ionstall superSu 2.46 - X Play Q&A, Help & Troubleshooting

Hello,
i have a problem with my phone.
i follow this thread : https://forum.xda-developers.com/moto-x-play/general/untested-how-to-root-moto-x-play-t3211941
can't start recovery mode with button power + volume down .
so i use fastboot to boot on TWRP : twrp-lux-3.0.2-r5.img
i install SuperSu 2.46 and my phone never boot on android 6.0.1.
i have do this echo SYSTEMLESS=true>>/data/.supersu
but no succes :/
what can i do ?

because you use too old supersu version. try this v2.79-SR3:
Code:
https://my.pcloud.com/publink/show?code=XZFdHdZn1hituupJ4pG1bF70SLeXB2SRiT7

Related

[HELP] G900F is not rooting

Heya
I got a Samsung Galaxy S5-G900F and I can't root it
I tried to flash cf auto root with odin but each time it ended with "recovery is not seandroid enforcing" and forcing me to remove the battery and turn on the phone normally.
I tried to flash a custom recovery (like twrp and philz) but it ended with "recovery is not seandroid enforcing" too...
Can someone help me please ?
My phone informations :
Product Name : kltexx
Bootloader Version : G900FXXU1BOJ1
PDA Version : G900FXXU1BOJ1
CSC Version : G900FROM1BOJ1
Baseband Version : G900FXXU1BOJ1
Build Number : LRX21T.G900FXXU1BOJ1
Can you boot into the recovery in the first place? The "Recovery is not seandroid enforcing" message is normal
Frost009 said:
Can you boot into the recovery in the first place? The "Recovery is not seandroid enforcing" message is normal
Click to expand...
Click to collapse
Yup I can but it's the original recovery (Android system recovery <3e> LRX21T.G900FXXU1BOJ1)
I have these options :
_reboot system now
_apply update from ADB
_apply update from external storage
_apply update from cache
_wipe data/factory reset
_wipe cache partition
_reboot to bootloader
_power down
_view logs
and that's all
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'
2) boot into download mode
3) flash TWRP 2.8.7.0 specifically this version.
4) DO NOT allow phone to boot, instead..
5) boot directly into recovery
6) flash SuperSU zip
7) boot device as normal
TWRP 2.8.7.0
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip
http://forum.xda-developers.com/showthread.php?t=1538053
Hope this helps.
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'
2) boot into download mode
3) flash TWRP 2.8.7.0 specifically this version.
4) DO NOT allow phone to boot, instead..
5) boot directly into recovery
6) flash SuperSU zip
7) boot device as normal
TWRP 2.8.7.0
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip
http://forum.xda-developers.com/showthread.php?t=1538053
Hope this helps.
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Okay I'll try that, but how do I don't allow the phone to boot after flashing with Odin?
Because last time I tried (with reboot option on Odin unchecked) I ended with "Recovery is not seandroid enforced".
We agree that to boot in new custom recovery, it's Volume up + home button + power button?
BlueStream said:
Okay I'll try that, but how do I don't allow the phone to boot after flashing with Odin?
Because last time I tried (with reboot option on Odin unchecked) I ended with "Recovery is not seandroid enforced".
We agree that to boot in new custom recovery, it's Volume up + home button + power button?
Click to expand...
Click to collapse
Pull the battery after flashing, then put it back in and Vol Up, Home, Power to boot to recovery
Make sure you have SuperSU.zip on MicroSD in the phone already
Thank you all !!! My s5 is actually rooted !
Now does anyone know how to install Xposed for the S5 on Lollipop (stock rom) ?
Don't think it works too well on stock TW ROMs, heard of boot loops and such but not tried it myself
Yeah....it works well on KitKat firmwares, but not on Lollipop firmwares (that is one of the reasons I've not upgraded to LP)
It *can* be used with LP, but it's WAY more complicated than normal just to get xposed installer to work.....and that's without trying to figure out which modules are waiting to be updated......
http://i.imgur.com/rVnFwJM.jpg

root SM-G900H with Android 5.0

Hi, There is root for:
MODEL: SM-G900H
ANDROID: 5.0
BASE BAND:G900HXXU1BOCA
I try to root using this thread (http://forum.xda-developers.com/showthread.php?t=2696537&page=123) but I don´t have success.
Att.
Ricardo Cunha
Flash this with ODIN
http://download.chainfire.eu/402/CF-Root/CF-Auto-Root/CF-Auto-Root-k3g-k3gxx-smg900h.zip
Or flash TWRP for H variant by PlayfulGod with ODIN, and then SuperSU from TWRP recovery
If you get seandroid is not...... error, then choose "Do not reboot" after the flash - pull the battery, replace the battery, enter recovery with Vol Up, Home, Power, and then flash SuperSU.zip
EDITED TWRP version
Try this......
1) deactivate 'Reactivation Lock'.
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP.
5) DO NOT allow phone to boot, (remove the battery as soon as the TWRP flash has completed if necessary) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
TWRP for H variant by PlayfulGod
http://forum.xda-developers.com/showthread.php?t=2725939
Both this method and CF Root WILL trip knox.....which will void your warranty.
http://i.imgur.com/rVnFwJM.jpg

No TWRP, Bootloop after installing EdXposed Module

I am running the latest OOS 10.0.1 Stable on my OP6T
I installed the Riru-Core module from magisk manager, rebooted perfectly fine. Afterwards installed the EdXposed module. Now I am stuck in a bootloop. Is there a way to uninstall the module without having TWRP? or factory resetting.
edit: I am unable to boot into fastboot or recovery
Please help me out
Thank you
Press volume up + power button to force reboot then press volume down + power to get into stock recovery. Then you can boot to fastboot through stock recovery...
2 Options ,
1. Try flashing stock boot.img on fastboot to remove Root so EdExposed won't work. (Recommended)
Then you'll have the option to remove EdExposed modules.
2. msmdownloadtool , But it will REMOVE all your data and will put your phone on Android 9.

Magisk 21.4 causing bootloop on LG G5(H850)

Hi all,
So I was triying to update my Magisk through the recommended direct update method. I got a bootloop. Never had any issues with this update method, Magisk always did a splendid job.
Now my only options are:
1. Flash a custom rom (I don't have any stock Telekom roms)
2. Update Android OS to 8.0 with LG Bridge (my goal is to have a stock rooted android os, that's why I'm doing this)
3. adb reboot, flash the latest twrp recovery (at least that's working)
4. flash the latest Magisks without reboot option, just power off and then turn on. And this is stage where I get a bootloop.
I only have v19.3 saved on my HDD. Flashing that is working just fine, not causing any bootloop. However Fake GPS and Pokémon Go are not working with this version anymore. :/ So I'm kinda chess-mated here because of this Magisk bootloop.
Anyone can help me how can we fix this?
I have bootloops with all Magisk 21.x versions, so I'm stuck with 20.4. Can't you download Magisk 20.4 and install it from TWRP? I don't need SafetyNet, so I have no idea if Magisk 20.4 can still pass the check, but at least it would be newer than Magisk 19.3.
I downloaded the previous 21.0 versions from here https://droidfeats.com/download-magisk-zip/ flashed it and it's working. I also tested the previous versions. Seems like only 21.4 version is affected only, which is the latest stable.
I had the same problem: I had Magisk 21.4 and withing Magisk Manager I tried to update to v. 22.0 because I got an update prompt that asked me to do so. Trusting everything was fine I updated but I got a bootloop. I managed to recover from bootloop and get the latest version of Magisk working in my Huawei Y5 MYA-L13 (Android 6.0). For these steps, it is assumed Magisk v21.4 and Magisk v22.0 ZIP files are stored in your storage. This is the way I did it:
Manage to get into stock recovery mode.
This step was more time-consuming than it should have been... This Huawei model with the bootloader unlocked states at boot: "Press volume key up to 3 seconds to enter recovery to restore your device". It didn't... With Vol+ just restarted the device (no TWRP or stock recovery or download mode...) and pressing Vol- it loaded into the bootloop. It took me some time to guess the right way:
Plug the turned-off device into a USB cable plugged into the computer.
Wait for the device to start into "charging mode" (I made up this... I mean wait until the charging percentage appears).
Turn on the device using the Power Button.
Immediately, press and hold Vol+.
The device will reboot. Press and hold Vol -.
The device will get into the stock recovery mode (EMUI Huawei eRecovery).
Try again if this fails... After a few attempts, you'll get it.
Now the device will be visible to ADB. Verify this in a command prompt with adb devices. Mine was listed as 0123456789ABCDEF recovery.
Use the command adb reboot recovery to get into the real recovery mode. I mean TWRP. (It's still there even if it seemed to be it wasn't).
Flash the version that caused the problem. In my case, I had Magisk v21.4 initially, so I installed this same version ZIP I got from the official Magisk GitHub releases section.
Once finished the installation, if it was successful Reboot. The device should boot normally this time, having installed this version of Magisk and not the new one, of course.
Now proceed to uninstall Magisk 21.4 completely using the ZIP file provided in the above URL (step 4) with TWRP.
Follow the official installation guide in the Custom Recovery section to install Magisk 22.0 (that is: having renamed Magisk-v22.0.apk to Magisk-v22.0.zip previously, use TWRP to install it). Reboot.
Your device should boot normally. You'll find a Magisk app where you'll be able to verify latest Magisk 22.0 was successfully installed!!! DONE.
I hope my guide is useful to someone. If so, please like my post to be aware it was useful. Greetings!
TL;DR
adb reboot recovery
Install Magisk-v21-4.zip. This solves bootloop problem!
Uninstall Magisk using Magisk-uninstaller-20210117.zip
Rename Magisk-v22.0.apk to Magisk-v22.0.zip. Install it using TWRP.
Reboot. You have the latest Magisk version v22.0 installed with no bootloop!!!
I've upgraded from v20.4 to v22 yesterday using the new Magisk app, it all went smoothly.

Samsung tab S5e LTE - bootloader unlocked / twrp installed , rooted with magisk

Dear sir ,
I have unlocked bootloader, tried to root with magisk / install twrp . I have unlocked bootloader in download mode. Download mode - power button + volume up & down . Once you are in download mode , long press volume up button till screen shows that bootloader unloced . Then I have followed the steps that are described in LOS official page , i am able to install Lineage OS vbmeta.tar followed by LOS recovery .tar file. Successful installed Lineage OS . After that boot into download mode by using Odin , I am able to flash twrp.tar file into AP . once flashed then reboot to recovery . TWRP will be installed permanently. No problem so far .

Categories

Resources