Database Users

Unable to install SuperSU, on MM stuck on boot.

Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Edit: Solution is just using the SuperSU in this thread: http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792
Thanks.

Did you select install SuperSU when twrp asked ? After flashing newest supersu?
Sent from my XT1575 using Tapatalk

Settler11 said:
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Thanks.
Click to expand...
Click to collapse
Which SuperSU version are you using?

Settler11 said:
Hello there,
I thought that there were more people with this problem, but I've this problem: first off, I got stock MM installed on my Style xt1572. Unlocked bootloader and the latest TWRP. But when I try to install SuperSU via TWRP, it just get stuck before the reboot animation. Any idea's what I could try perhaps?
Thanks.
Click to expand...
Click to collapse
Men i have the same problem and i dont know what to do :/

@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.

Depending on the version of SuperSU that you are using there are 2 different rooting methods.
My suggestion would be to use the systemless root option here: http://forum.xda-developers.com/showpost.php?p=64161125&postcount=3
v2.65 is what you want. When you flash this in twrp it will automatically patch the boot image on your device (whilst also creating a backup of the original). It sounds as though you are both trying to use a version of SuperSU that implements the standard rooting method, this would mean that you must manually flash a modified boot image in order to bypass Android 6.0's internal system modification checks!

Flash the stock boot.img. Then see if it boots. Then ^^^ this^^^

Settler11 said:
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Click to expand...
Click to collapse
Do not allow twrp to attempt to install superSU
IMPORTANT!!!!
Because you have already allowed twrp to do this, you will need to reflash your system partition to ensure that all traces of that version of SuperSU are removed before you flash the newer version.
I hope this helps you guys.

patt2k said:
...
reflash your system partition
....
Click to expand...
Click to collapse
What do you mean with that? We've to reflash a rom, kernel? What?

Settler11 said:
@patt yes.
@Doktaphex The one TWRP asked me to install and the latest beta. 2.49. Same problem.
Click to expand...
Click to collapse
You are not suppose to click install superSU when twrp asks for it.
Sent from my XT1575 using Tapatalk

patt2k said:
You are not suppose to click install superSU when twrp asks for it.
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
Yes.. But as you can see, I've done that already. But I got a restore without it. But even if I install that latest beta, the problem still presumes.

Settler11 said:
What do you mean with that? We've to reflash a rom, kernel? What?
Click to expand...
Click to collapse
Sorry, I should have been more clear in my instructions. I would go ahead and reflash the rom that you want to use and then flash superSU v2.65.
Reboot and if twrp asks if you want it to install superSU choose the option for it NOT to do so.

Settler11 said:
Yes.. But as you can see, I've done that already. But I got a restore without it. But even if I install that latest beta, the problem still presumes.
Click to expand...
Click to collapse
I had this issue but I had backup of my stock rooted rom. I'd suggest maybe go back to stock with restore tool?
Sent from my XT1575 using Tapatalk

patt2k said:
I had this issue but I had backup of my stock rooted rom. I'd suggest maybe go back to stock with restore tool?
Sent from my XT1575 using Tapatalk
Click to expand...
Click to collapse
I'M on stock! And that restore tool is for Pure, not Style! And I don't want to install a custom rom. Stock rom is still fine for me.

Settler11 said:
I'M on stock! And that restore tool is for Pure, not Style! And I don't want to install a custom rom. Stock rom is still fine for me.
Click to expand...
Click to collapse
Idk then sorry I have pure
Sent from my XT1575 using Tapatalk

Also tried Kingo root funny enough, but no go.

Edit: Wow, okay. Installing some kind of version of SuperSU does the trick apparently. It's in here:
http://forum.xda-developers.com/moto-x-style/general/xt1572-mm-twrp-root-xposed-t3276792

How to keep permanent root?

So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help

adriel161 said:
So I have converted my Note for to developer and have an unlocked bootloader and installed TWRP through Odin. I have tried a few times to gain root by installing SuperSU through TWRP, but it just manages to keep looping my phone after it installs. Is there a way to install SuperSU without doing it through TWRP as I think that's the problem?
Also I wouldn't be able to install a ROM until I gain root correct?
Thank you for all of your help
Click to expand...
Click to collapse
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app

Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524

elliwigy said:
install a prerooted rom of your choice through twrp recocery.. they will come pre rooted..
if not i have a feeling youre not using the correct supersu zip to root the device..
have you flashed cf auto root?
Sent from my SM-G925V using XDA-Developers mobile app
Click to expand...
Click to collapse
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?

refusedchaos said:
Flash a prerooted rom or flash the Emotion-TW-5.1.1-nightly-r21 kernal + BETA-SuperSU-v2.71-20160331103524
Click to expand...
Click to collapse
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.

shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Settings-/developer options/ enable root
Sent from my SM-N920F using XDA-Developers mobile app

adriel161 said:
Cool, thanks got it to work!
Now my only issue is that once I was rooted and everything I wanted to flash CM13.
I shut down my phone and went into TWRP, I restored and the tried to install CM13+Gapps and it just went into a black screen and started over. I rebooted, but now I'm in a boot loop.
So I am going to start over and regain root, but do you know if I did something incorrectly? How would I go about it? Thank you.
Click to expand...
Click to collapse
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?

refusedchaos said:
Hmm im not sure (i'm running stock + Emotion kernel). But if you want to go CM13, you dont need to flash the Emotion kernel.
EDIT: you did a full factory reset (via recovery) before you flashed CM13 right?
Click to expand...
Click to collapse
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.

[/COLOR]
shusuke028 said:
So yea.I don't mean to hijack this thread or anything, but I'm having thebsane issue. I've converted to Dev edition, installed TWRP, and am currently running CM 13. However, whenever I try to use an app that requires root, it says that I don't have root.
I've tried flashing the latest Super SU in recovery, downloading Super SU from the play store, and I've tried flashing the Emotion kernel (when i try to flash that, my screen goes black and I'm returned to my recovery home)
What pre rooted ROMs are out?
And are my issues rooting because I flashed a 6.0,1 ROM before getting permanent root?
Click to expand...
Click to collapse
Cm13 is pre-rooted, root is embedded in the rom, superSu isn't needed, you can turn it on in developer settings.

adriel161 said:
Yes I did, but I had the Emotion Kernal installed. That's probably why, I'm going to attempt right now to flash SuperSu then CM13.
Click to expand...
Click to collapse
Yea, try with stock kernal. I don't think you need to flash SS when flashing CM13 though

For me, when I try to flash CM13 through TWRP it'll get to saying "MTP Enabled" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do

Orange Offizier said:
For me, when I try to flash CM13 through TWRP it'll get to saying "MTP" in the terminal window, then black screens for a few seconds, and reboots to TWRP. It also doesn't flash CM13, and I'm at a loss for what to do
Click to expand...
Click to collapse
Which version of TWRP do you have? And did you make sure it was a vzw build?

Reminon said:
Which version of TWRP do you have? And did you make sure it was a vzw build?
Click to expand...
Click to collapse
I have TWRP 3.0.2, and it is a vzw build

TWRP wipes after flashing AOSP 9 Pie

Hello everyone I have recently flashed AOSP pie 9 ROM but after that my TWRP recovery gets wipe and stock recovery gets installed and after reflashing TWRP I can't flash magisk and get root access.
Edit: Issue solved. The solution with Magisk not appearing even after clean flashed on AOSP 9:
Step1: Flash TWRP with Tissot manager: https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637 "Download" Note: You can leave Treble stuff and just flash TWRP
Step2: Goto Advanced and select Tissot Manager "Run"
After that flash magisk.
Note: It will also work on temporary TWRP but the with the @CosmicDan TWRP, it will get installed to both slot kernels so you don't need to hassle on selecting/changing slot.
Thank You!

Athakuri700 said:
Hello everyone I have recently flashed AOSP pie 9 ROM but after that my TWRP recovery gets wipe and stock recovery gets installed and because of that I can't flash magisk and get root access.
Click to expand...
Click to collapse
Ask in the AOSP 9 Thread!!! Don't create one?
And just flash TWRP again. Not hard to think of.

justboryata said:
Ask in the AOSP 9 Thread!!! Don't create one?
And just flash TWRP again. Not hard to think of.
Click to expand...
Click to collapse
Mistake, thanks

Solti le purai Naya banai dexa qn sodhna lai?

5anzay said:
Solti le purai Naya banai dexa qn sodhna lai?
Click to expand...
Click to collapse
More experienced than you. ? Junior. I have mentioned earlier it was a mistake and it got posted in both thread. Now if you know or not about deleting?????

Athakuri700 said:
More experienced than you. ? Junior. I have mentioned earlier it was a mistake and it got posted in both thread. Now if you know or not about deleting?????
Click to expand...
Click to collapse
Have you flashed the TWRP installer after the ROM, like on every other ROM for our A/B device with no dedicated recovery partition?

Haxomen said:
Have you flashed the TWRP installer after the ROM, like on every other ROM for our A/B device with no dedicated recovery partition?
Click to expand...
Click to collapse
The issue has been fixed ? I just forgot to switch A/B partition. Feeling fool on myself ? anyway thanks.

Athakuri700 said:
The issue has been fixed ? I just forgot to switch A/B partition. Feeling fool on myself ? anyway thanks.
Click to expand...
Click to collapse
You dont need to switch partitions, you just need to flash the twrp installer after the ROM

Haxomen said:
You dont need to switch partitions, you just need to flash the twrp installer after the ROM
Click to expand...
Click to collapse
I had no issue on installing TWRP, I was stuck on Magisk as it was not appearing even after neat flash.

Athakuri700 said:
I had no issue on installing TWRP, I was stuck on Magisk as it was not appearing even after neat flash.
Click to expand...
Click to collapse
Me too, just installed the magisk manager apk

Storage mounting issues after flashing TWRP

Just unlocked and flashed TWRP. No matter what I try, I can't get it to recognise my storage to install SuperSU.
What can I do to fix this?
I am on stock OOS 5.1.5
Thanks
EDIT - Worked it out. I formatted the data and it then let me install SuperSU.
EDIT 2 - After installing SuperSU zip file, the phone wasn't rooted when rebooting and also, TWRP won't recognise my data once I rebooted into it again.
Any ideas?

gman88667733 said:
Just unlocked and flashed TWRP. No matter what I try, I can't get it to recognise my storage to install SuperSU.
What can I do to fix this?
I am on stock OOS 5.1.5
Thanks
EDIT - Worked it out. I formatted the data and it then let me install SuperSU.
EDIT 2 - After installing SuperSU zip file, the phone wasn't rooted when rebooting and also, TWRP won't recognise my data once I rebooted into it again.
Any ideas?
Click to expand...
Click to collapse
After twrp installation and before the first system reboot you need to flash magisk so twrp will be stick in place.
I really don't know if it works with supersu. Do you want to stay encrypted(internal storage)? Which twrp(file name) did you flash?

Preferably encrypted. I flashed twrp 3.1.1 cheeseburger.
I am trying to install Franco Kernel. So I unlocked the bootloader, flashed TWRP 3.1.1 and then tried to flash Super SU or Magisk and neither worked. It came up with an issue with file mounting.

gman88667733 said:
Preferably encrypted. I flashed twrp 3.1.1 cheeseburger.
I am trying to install Franco Kernel. So I unlocked the bootloader, flashed TWRP 3.1.1 and then tried to flash Super SU or Magisk and neither worked. It came up with an issue with file mounting.
Click to expand...
Click to collapse
It seems to me you did not use latest blu spark or codeworkx recovery instead you used official twrp.
It's recommended to not use official twrp. Please change the twrp and test again.

strongst said:
It seems to me you did not use latest blu spark or codeworkx recovery instead you used official twrp.
It's recommended to not use official twrp. Please change the twrp and test again.
Click to expand...
Click to collapse
You are correct. I did not use the blu spark TWRP.
Can I use TWRP 3.1.1 BLU spark version, or shall I use 3.2.1 blu spark?
Thanks.

gman88667733 said:
You are correct. I did not use the blu spark TWRP.
Can I use TWRP 3.1.1 BLU spark version, or shall I use 3.2.1 blu spark?
Thanks.
Click to expand...
Click to collapse
Just use latest blu spark twrp with treble in file name from here https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933

strongst said:
Just use latest blu spark twrp with treble in file name from here https://forum.xda-developers.com/oneplus-5/development/kernel-t3651933
Click to expand...
Click to collapse
All done! I now have another issue. I originally tried to flash Super SU and it did not work. I have tried to flash Magisk today after flashing franco kernel and get an error says that there is an unsupported boot image program or something.
I am on stock OOS, with franco kernel and no root. How can I get it so that I am on stock OOS with franco kernel and Magisk?
Thanks.

gman88667733 said:
All done! I now have another issue. I originally tried to flash Super SU and it did not work. I have tried to flash Magisk today after flashing franco kernel and get an error says that there is an unsupported boot image program or something.
I am on stock OOS, with franco kernel and no root. How can I get it so that I am on stock OOS with franco kernel and Magisk?
Thanks.
Click to expand...
Click to collapse
Did you uninstall supersu according to instructions or just dirty flashed magisk(bad idea)?

strongst said:
Did you uninstall supersu according to instructions or just dirty flashed magisk(bad idea)?
Click to expand...
Click to collapse
I attempted to dirty flash Magisk (however it did not install)
So what do I need to do to uninstall SuperSU?
The main issue is, after installing supersu, my phone still wasn't rooted!

gman88667733 said:
I attempted to dirty flash Magisk (however it did not install)
So what do I need to do to uninstall SuperSU?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459

strongst said:
https://forum.xda-developers.com/showpost.php?p=63615067&postcount=2459
Click to expand...
Click to collapse
Thanks. Will I need to flash a stock boot.img too? If so, where would I find this given I am on stock OOS.

gman88667733 said:
Thanks. Will I need to flash a stock boot.img too? If so, where would I find this given I am on stock OOS.
Click to expand...
Click to collapse
Normally not, but if needed: every rom zip comes along with a boot.img inside the zip. Just extract it from this rom zip and you have the kernel of this rom :good:

strongst said:
Normally not, but if needed: every rom zip comes along with a boot.img inside the zip. Just extract it from this rom zip and you have the kernel of this rom :good:
Click to expand...
Click to collapse
How do I get the ROM zip for OOS stock?

strongst said:
Normally not, but if needed: every rom zip comes along with a boot.img inside the zip. Just extract it from this rom zip and you have the kernel of this rom :good:
Click to expand...
Click to collapse
Interestingly, I just flashed the unSU zip, wiped cache and then tried Magisk. It says I need to flash a stock boot.img
What is the process of doing this?
Thanks

gman88667733 said:
Interestingly, I just flashed the unSU zip, wiped cache and then tried Magisk. It says I need to flash a stock boot.img
What is the process of doing this?
Thanks
Click to expand...
Click to collapse
Flash the boot.img through twrp

strongst said:
Flash the boot.img through twrp
Click to expand...
Click to collapse
Do I need to wipe or anything? Or do I just flash the boot.img, wipe cache and then flash Magisk? Or shall I boot fully into the OS, then back into TWRP to flash it?
Still not sure where I get the correct boot.img from!
Edit - can I dirty flash the whole firmware? I would like to do this so I can do a clean backup with the stock kernel before I then flash Magisk and Franco. Would this work?

gman88667733 said:
Do I need to wipe or anything? Or do I just flash the boot.img, wipe cache and then flash Magisk? Or shall I boot fully into the OS, then back into TWRP to flash it?
Still not sure where I get the correct boot.img from!
Edit - can I dirty flash the whole firmware? I would like to do this so I can do a clean backup with the stock kernel before I then flash Magisk and Franco. Would this work?
Click to expand...
Click to collapse
You can also flash the complete rom with kernel.
But just look inside the downloaded rom zip file, there's the boot.img you're looking for. You don't need to wipe anything or boot into OS for flashing just the kernel!

strongst said:
You can also flash the complete rom with kernel.
But just look inside the downloaded rom zip file, there's the boot.img you're looking for. You don't need to wipe anything or boot into OS for flashing just the kernel!
Click to expand...
Click to collapse
Thanks for that, all up and running now.
Do you know where I can find the Franco governor profiles? I've had a good look around but can't find them again!
Thanks

gman88667733 said:
Thanks for that, all up and running now.
Do you know where I can find the Franco governor profiles? I've had a good look around but can't find them again!
Thanks
Click to expand...
Click to collapse
The profiles are inside the app manager imo https://forum.xda-developers.com/on...francokernel-r1-8th-aug-t3653500/post73328473

strongst said:
The profiles are inside the app manager imo https://forum.xda-developers.com/on...francokernel-r1-8th-aug-t3653500/post73328473
Click to expand...
Click to collapse
I have the app manager. However there is only 'Ravi' profile under the governor profile options.

TWRP-Flashable stock ROM? [Lavender Global]

Hello,
I'm interested in going back to stock after having some issues with xiaomi.eu ROMs. However, the one time I tried it, I had an error mid-flash (with MiFlashTool) and the phone got wiped. Thankfully I was able to re-flash TWRP and flash Xiaomi.eu ROM from there. But I want to return to stock now. However, I don't want to have to use MiFlashTool as last time I did that, the phone almost got bricked. Xiaomi's tools are horrible anyway.
Is there a way to get the latest stable Global ROM for Lavender in a .ZIP file that I'd be able to flash from TWRP?
Any help is appreciated.

rottensong said:
Hello,
I'm interested in going back to stock after having some issues with xiaomi.eu ROMs. However, the one time I tried it, I had an error mid-flash (with MiFlashTool) and the phone got wiped. Thankfully I was able to re-flash TWRP and flash Xiaomi.eu ROM from there. But I want to return to stock now. However, I don't want to have to use MiFlashTool as last time I did that, the phone almost got bricked. Xiaomi's tools are horrible anyway.
Is there a way to get the latest stable Global ROM for Lavender in a .ZIP file that I'd be able to flash from TWRP?
Any help is appreciated.
Click to expand...
Click to collapse
Every zip from the official MIUI download page are flashable via TWRP. Remember to make a full backup with TWRP and also backup your internal sdcard as the global rom will reset the official recovery and encrypt your data again (that's what happened in my case).

thunderteaser said:
Every zip from the official MIUI download page are flashable via TWRP. Remember to make a full backup with TWRP and also backup your internal sdcard as the global rom will reset the official recovery and encrypt your data again (that's what happened in my case).
Click to expand...
Click to collapse
Thank you so much! I really don't care much about the data, the phone is new, I just want it to work.
I'll get on this ASAP. Thanks again!

thunderteaser said:
Every zip from the official MIUI download page are flashable via TWRP. Remember to make a full backup with TWRP and also backup your internal sdcard as the global rom will reset the official recovery and encrypt your data again (that's what happened in my case).
Click to expand...
Click to collapse
I get a "zip treble" compatibility error with the stock .zip

rottensong said:
I get a "zip treble" compatibility error with the stock .zip
Click to expand...
Click to collapse
Which TWRP version are you using?

thunderteaser said:
Which TWRP version are you using?
Click to expand...
Click to collapse
V. 3.3.0-0

thunderteaser said:
Which TWRP version are you using?
Click to expand...
Click to collapse
Just in case, I flashed https://forum.xda-developers.com/re...very-unofficial-twrp-touch-recovery-t3921637/ and got the same result.

It did not happen in my case as I was already on global. Maybe you should look for a guide to switch from Xiaomi.eu to global

thunderteaser said:
It did not happen in my case as I was already on global. Maybe you should look for a guide to switch from Xiaomi.eu to global
Click to expand...
Click to collapse
All guides point to using Fastboot flash and that's what almost killed my phone last time.
I've flashed xiaomi.eu Stable now, and did a /data format and full wipe. Let's see if this isn't better. I honestly just want stuff to work at this point.
Thank you for your help.

It took me hours to fix it as ADB wouldnt work with me for some reason...
BUT there is allways an indian guy who does tutorials:
https://www.youtube.com/watch?v=kr3kUJF6d0Y
WORKED FLAWLESS!
Hope i can help some ppl in the future that googled like me