Database Users

Root Issues after installing Cataclysm

Hey guys,
I unlocked the bootloader and rooted my phone using the toolkit and all was well. I installed the Cataclysm ROM and everything was too. However, one day randomly I checked and Super SU and BusyBox was missing and Root checker said my device isn't rooted. However, my phone does boot into recovery (TWRP) and it IS running Cataclysm ROM. I downloaded Super SU from Playstore and it says "There is no SU binary installed and Super SU cannot install it". Some forums for other devices say just flash the latest version of Super SU but the marshmallow pages say go back to stock or something, I don't get it since I'm a Noob. If someone could tell me what I need to do to fix this the right way I would be really grateful. Thanks in advance. :angel:

holydevil27 said:
Hey guys,
I unlocked the bootloader and rooted my phone using the toolkit and all was well. I installed the Cataclysm ROM and everything was too. However, one day randomly I checked and Super SU and BusyBox was missing and Root checker said my device isn't rooted. However, my phone does boot into recovery (TWRP) and it IS running Cataclysm ROM. I downloaded Super SU from Playstore and it says "There is no SU binary installed and Super SU cannot install it". Some forums for other devices say just flash the latest version of Super SU but the marshmallow pages say go back to stock or something, I don't get it since I'm a Noob. If someone could tell me what I need to do to fix this the right way I would be really grateful. Thanks in advance. :angel:
Click to expand...
Click to collapse
It really depends on what you're trying to do. If you flash the older beta 2.52 super su, for the 'old style' system root, you should be able to flash the zip and be well on your way. You need to go back to the stock and follow the flash instructions if you're going to use the newer / experimental systemless root. If you don't know what you're doing exactly, I'd recommend the old system root, but flashing super su 2.52.

It sounds pretty messed up for Super SU just to disappear and root access to just be gone. Although like teh roxxorz said it depends on what type of root you are doing. I think system root is much easier and cleaner personally. If I was you I would probably flash back to stock, flash TWRP, install SuperSU 2.65. Then flash back which ever ROM you want. Since you are having issues with root I would not restore your ROM from a back up either, just start fresh.

teh roxxorz said:
It really depends on what you're trying to do. If you flash the older beta 2.52 super su, for the 'old style' system root, you should be able to flash the zip and be well on your way. You need to go back to the stock and follow the flash instructions if you're going to use the newer / experimental systemless root. If you don't know what you're doing exactly, I'd recommend the old system root, but flashing super su 2.52.
Click to expand...
Click to collapse
If I want to do the old system root, do I just download Super SU and flash it with TWRP? Or do I format my phone and do it? Or do I have to flash stock firmware first?

AndroidPurity said:
It sounds pretty messed up for Super SU just to disappear and root access to just be gone. Although like teh roxxorz said it depends on what type of root you are doing. I think system root is much easier and cleaner personally. If I was you I would probably flash back to stock, flash TWRP, install SuperSU 2.65. Then flash back which ever ROM you want. Since you are having issues with root I would not restore your ROM from a back up either, just start fresh.
Click to expand...
Click to collapse
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD

holydevil27 said:
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
Click to expand...
Click to collapse
No worries man. Even tough I been rooting phones and playing around for over a year I still have lots to learn myself. What helped me the most when I wanted to know how to do something was watching a you tube tutorial on it. Here is a good detailed tutorial how to flash back to stock right here.
Once you do that, to do a systemless root, you can watch this short little video tutorial right here. The newest SuperSU 2.65 you can find on Chainfire's thread at the bottom of this page right here.
If you have any questions going through either of those 2 video tutorials feel free to ask.

holydevil27 said:
Can you guide me as to how to flash back to stock? A link would be great, and I apologize for the lack of knowledge, the last rooted Android phone I had was Samsung s3! Things have really changed since then xD
Click to expand...
Click to collapse
No need to be sorry; we all have to start somewhere..
AndroidPurity said:
No worries man. Even tough I been rooting phones and playing around for over a year I still have lots to learn myself. What helped me the most when I wanted to know how to do something was watching a you tube tutorial on it. Here is a good detailed tutorial how to flash back to stock right here.
Once you do that, to do a systemless root, you can watch this short little video tutorial right here. The newest SuperSU 2.65 you can find on Chainfire's thread at the bottom of this page right here.
If you have any questions going through either of those 2 video tutorials feel free to ask.
Click to expand...
Click to collapse
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
holydevil27 said:
If I want to do the old system root, do I just download Super SU and flash it with TWRP? Or do I format my phone and do it? Or do I have to flash stock firmware first?
Click to expand...
Click to collapse
Correct, you would just download the zip and flash in TWRP; I linked it in an above post.

teh roxxorz said:
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
Click to expand...
Click to collapse
Thanks! Just curious, what are a couple of the most known/popular root apps that don't work with system less root? I haven't found a thread yet on that. Also on the other hand Android pay don't work with the 'old' system root method right? And I think wallet no longer works with it too, correct?

AndroidPurity said:
Thanks! Just curious, what are a couple of the most known/popular root apps that don't work with system less root? I haven't found a thread yet on that. Also on the other hand Android pay don't work with the 'old' system root method right? And I think wallet no longer works with it too, correct?
Click to expand...
Click to collapse
No problem. And the one I know that comes to mind that doesn't work with systemless root is Es File Explorer - though any root app where it is hardcoded tot he path for supersu won't work, additionally, apparently some kernels won't work with systemless root, though I haven't seen it on our end.
Wallet still works with the system root, but as you said, Android Pay does not - though the Chroma ROM apparently has it working, but I've yet to use the ROM, as it isn't a deal breaker for me.

teh roxxorz said:
No need to be sorry; we all have to start somewhere..
Good look. Though I still think the system root might be a good pace, and it's 100% working; still some quirks with certain root apps on systemless root. SuperSu 2.52
---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------
Correct, you would just download the zip and flash in TWRP; I linked it in an above post.
Click to expand...
Click to collapse
Thanks guys,
I just went into TWRP and flashed 2.64 Super SU (since that's the one I got with the tool kit and what I had installed before) and Root came back! I hope it stays! Thanks again folks!

[Q] SuHide by Chainfire, Anybody got working for Android Pay yet?

Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message

TheATHEiST said:
Has anybody managed to get Android Pay working yet on our device with custom rom?
Tried the new SuHide by Chainfire but still get the unable to verify device is Android compatible message
Click to expand...
Click to collapse
requirements :
- SuperSU installed in systemless mode
So does not work on our device

xander33 said:
requirements :
- SuperSU installed in systemless mode
So does not work on our device
Click to expand...
Click to collapse
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?

TheATHEiST said:
Can you clarify why not with our device?
When you install supersu it lists in output that it's being installed as systemless?
Click to expand...
Click to collapse
As i know the method for root our phone is system mode, the systemless zip not work
Here the procedure that i followed for rooting my phone and is system mode
What you need:
Unlocked bootloader (see chapter 2).
TWRP installed (see chapter 7).
1.Zip .
2.Zip .
How:
Put 1.zip and 2.zip into your sd card/internal storage.
Boot into TWRP.
Ignore the message from TWRP.
Choose the "install" button.
Locate 1.zip (if on sd card go "up a level" and then "external sdcard" there you should find it).
Install it.
Reboot your phone.
Boot into TWRP again.
Locate 2.zip .
Install it.
Reboot

That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.

TheATHEiST said:
That's just the initial bootloader unlock and root method.
I used same method but later flashed custom rom witch also comes rooted. I have also unrooted and then rerooted systemless mode with SuperSU zip.
Click to expand...
Click to collapse
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app

Fedroid said:
You need to use Magisk.
It works for me.
Have a look here...
http://pecholite.blogspot.co.ke/2016/08/magisk-la-interfaz-systemless.html?m=1
http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
Greetings
Sent from my ALE-L21 using XDA-Developers mobile app
Click to expand...
Click to collapse
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.

TheATHEiST said:
Doesn't seem to work for me. Just keep getting the unable to verify device message in Android Pay app.
Click to expand...
Click to collapse
3 months since your last contact....
Things have changed a lot and android pay is working hard for avoid us pay with rooted phones.
Nowadays magisk is on v9 version and facing v10.
Want a clue?
If your mobile is compatible with multirom go this way. One rom rooted and modified as you want and another stock for doing payments.
Luck!

can't update to marshmallow

Hello friends
My phone is HTC One m8w
There isn't "update" in
Setting
About
Android version,
5.0.1
Software number
1.0.0.m8w
Build number
4.19.1402.15 CL458284 release-keys
Please help me for this problem
How can I update my phone?
Thanks a lot

Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps

Ta3miyyasandwich said:
Hello, I experienced something similar- complete absence of system update! A little digging revealed that any modifications to the system partition would render the device un-updateable, so naturally I downloaded the complete marshmallow package update for my device, booted into standard recovery, and updated from sd card
Hope this helps
Click to expand...
Click to collapse
There isn't any update for my build number
Sent from my HTC_M9pw using Tapatalk

if you are willing to, just root your phone and flash the marshmallow rom on to your phone and use titanium backup to backup everything before you do so.

you can root your phone,flash twrp recovery,flash Marshmallow rom.

lmentor said:
you can root your phone,flash twrp recovery,flash Marshmallow rom.
Click to expand...
Click to collapse
That's exactly what I just said

justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom on to your phone
Click to expand...
Click to collapse
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.

redpoint73 said:
You don't need root to install TWRP, nor to install a custom ROM.
Exception is Verizon, where you need root to s-off, and then unlock bootloader; as bootloader unlock by HTCDev.com is not supported for that version alone.
Click to expand...
Click to collapse
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone. Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.

justinchao740 said:
If you get bootloader unlocked, you basically rooted your device cause now you are allowed to modify the system data and make modification that can result in unusable phone .
Click to expand...
Click to collapse
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
justinchao740 said:
Plus if you are willing to take the risk of unlocking your bootloader, why don't you just root anyways, its just a matter of flashing super su zip.
Click to expand...
Click to collapse
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.

redpoint73 said:
No, you didn't. Root is a very specific thing. You either have root (SU) priviledge, or you don't. Unlocked bootloader does not give you root privilege. It only allows you to flash unsigned zips to certain partitions.
Because it would be a wasted step (completely unnecessary), if you are going to flash a custom ROM.
Click to expand...
Click to collapse
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access

justinchao740 said:
Think of it this way. If you flashed a cm ROM without root in the first place, you would get root. I'm not saying unlocking bootloader immediately give you root access but it allows almost anything that you flash to have root access
Click to expand...
Click to collapse
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.

redpoint73 said:
Some folks keep incorrectly stating that you need root to flash custom recovery on this device (on some devices, you do - but not this one). I'm just trying to make sure that misinformation doesn't keep getting conveyed (the post after yours said it, too).
Stating the process precisely, is the best way to do that.
Click to expand...
Click to collapse
Agreed plus my post never stated anything about rooting.

justinchao740 said:
Agreed plus my post never stated anything about rooting.
Click to expand...
Click to collapse
While my intent is not to be the guy that always has the last word; I also can't let you state a complete falsehood.
justinchao740 said:
if you are willing to, just root your phone and flash the marshmallow rom
Click to expand...
Click to collapse

Anyone tried Magisk HD8 7th Gen?

Hi, just got around to rooting my Kindle. Currently using SuperSu, curious if anyone has used Magisk with this tablet? Any reason not to do so?.
Thanks in advance.

I've debated doing this as well, as I don't like having to default grant everything root access.
As far as I understand though, none of your root apps/su requests can modify the system partition, so I haven't tried it yet.
@diplomatic is this true for the bootless root method without dm-verity?

No, you can modify /system if there's no dm-verity, @Kctucka

diplomatic said:
No, you can modify /system if there's no dm-verity, @Kctucka
Click to expand...
Click to collapse
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.

Kctucka said:
Oh wow that's pretty awesome.
Sounds like there's no downside to Magisk on the 2017 HD 8 then.
Click to expand...
Click to collapse
Thanks, guys!

SuperSU access workaround
Kctucka said:
I've debated doing this as well, as I don't like having to default grant everything root access.
.....
Click to expand...
Click to collapse
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?

Dan_firehd said:
There is a SuperSU access workaround without having to default grant everything root access:
https://forum.xda-developers.com/hd8-hd10/general/supersu-access-workaround-fire-devices-t3738269
Maybe I am mistaken, but how does one install Magisk on 2017 HD8 without TWRP ?
Click to expand...
Click to collapse
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.

Kctucka said:
Yeah I've seen that method, but didn't wanna redo it for every root app I add.
And this is the Bootless Root Magisk method:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
I think I'm gonna try this method when I get some free time.
Click to expand...
Click to collapse
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.

koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Yeah will do! I'll probably try it tomorrow or the day after.

koop1955 said:
@Kctucka would you let me know if that method works for you? I tried grabbing the stock boot image and modifying it with the latest version of Magisk, Could not get that to work either via ADB or Flashify because of the locked bootloader - stupid of me not to realize that from the start. I let my excitement get the best of me.
I am out of time today, but it seems like a modified BIN file might be an option.
Click to expand...
Click to collapse
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
So far, all of my root apps detect root, except for titanium backup. I've messed around with it for a bit but haven't been able to figure it out. I'm guessing it has something to do with the location of the su binaries.
Also of note, FlashFire did not work at first. I realized that this is because the timebomb method we used along with the older app version, was from before Magisk existed. I grabbed the latest version of FlashFire from apk mirror, and it started without issues. I haven't tested by flashing anything yet though.
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
All in all, this is a pretty solid root method, but obviously non ideal due to the locked bootloader.
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!

Kctucka said:
Ok so I successfully have Magisk working, and have been playing around with it for a bit now. I am running the latest version of Magisk Manager. To get it up and running, I chose the option in SuperSu to clean up binaries for different su method.
Click to expand...
Click to collapse
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into this after so long I feel like a n00b again.

koop1955 said:
Was that all that you did? That option and then install? And how did you change the time in your Kindle to get Flashify to work or just the latest APK?
And thanks for everything! Getting back into thhis after so long I feel like a n00b again.
Click to expand...
Click to collapse
That option was all I did to remove SuperSu. Then I followed the instructions here:
https://forum.xda-developers.com/showpost.php?p=79626434&postcount=135
Didn't take long to get it working.
And the time change was to get the version of FlashFire working that was compatible with the version of SuperSu we could run. See this post for more info if you're curious:
https://forum.xda-developers.com/hd8-hd10/general/hd-10-2017-xposed-t3722252
But with this new method, the most recent version of FlashFire works, as it's compatible with Magisk. The older version of FlashFire I had is not.
Also, I'm a noob myself. That's why I tagged diplomatic again, to correct the dumb things I might have said

Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.

koop1955 said:
Well, I am busy adding to your "Thanks" quotient, something seems to have fallen by the wayside today. Glad t have you around.
I think ultimately we are going to end up with a custom BIN file with Magisk and Xposed integrated.
Cheers.
Click to expand...
Click to collapse
That's awesome! Would that pass signature verification? Or would it be through hacked fastboot?
Also, that'd make it much easier to set up the device after a softbrick. FlashFire would be good to flash backups right away.

Kctucka said:
.....
Lastly, the one minor inconvenience is that my kernel tweaks I enable at boot, do not work, as there is no root at boot. So I have to manually add zram every reboot. Perhaps there's a better way to do this.
.....
Click to expand...
Click to collapse
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.

Dan_firehd said:
Would you please let us know how did you do your "kernel tweaks" to add zram for a rooted 2017 HD8?
Thanks.
Click to expand...
Click to collapse
My kernel tweaks were done with KA Mod Reborn, using the "apply on boot" setting:
https://forum.xda-developers.com/android/apps-games/approot4-0-ka-mod-reborn-v18-t3714105
I added 260 MB ZRAM with a swapiness of 10. You can also tweak low memory killer, laptop mode, and a whole bunch of other dials that I don't mess with as I don't fully understand what they do.
Kernel changes could also be done with a number of different apps that do similar things.
Unfortunately, the bootless root method doesn't give root on boot, so it and also most Magisk modules won't work. Can't think of a workaround currently.

Kctucka said:
I've also not tested how easy it is to switch back to SuperSu if desired, but I assume it's as simple as disabling the start up script, and updating su binaries in SuperSu.
@diplomatic is this the case? Or would you also need to delete the created files in the data partition? Thanks again for the awesome method!
Click to expand...
Click to collapse
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....

diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
That's super beneficial then, you can swap back and forth easily depending on what you need.

diplomatic said:
Yeah, pretty much. The activation of root depends only the init.d app running the script. The su binaries don't really exist in storage. You can delete all the stuff under /data/adb if you want to wipe everything Magisk. In theory, it should be possible to install Magisk on the system partition. It probably doesn't support that method officially anymore. But if the bootless method works, then a similar script can be added to /system....
Click to expand...
Click to collapse
How about just swapping the install-recovery.sh script for suboot.sh on devices that don't have dm-verity?
I think that's pretty much what SuperSU does as well.
That would give root much earlier during boot and not depend on the extra App.
Probably doesn't even need to run mtk-su each boot then either.

Yeah, that's on the right track, @k4y0z. What you can probably use is a modified SU_MINISCRIPT section of suboot.sh, at least as a starting point. That is the code that needs to be run as root. What should be changed is the path to the magiskinit & magisk binaries. Those could be placed somewhere on /system. You would only need mtk-su if selinux needs to be permissive. But I suspect it does for the 'magiskpolicy --live' call. (But then how does SuperSU handle it with enforcing?)

TWRP without ROOT MODE ?

Hello,
I have an S5 (kccat6).
After installing TWRP with ODIN, do I also need to install superSU to fully use TWRP? Or can I do without the root mode without problems?
Thanks for your advice.

HIPOKAMPing said:
Hello,
I have an S5 (kccat6).
After installing TWRP with ODIN, do I also need to install superSU to fully use TWRP? Or can I do without the root mode without problems?
Thanks for your advice.
Click to expand...
Click to collapse
No.
TWRP just replaces stock recovery to be used instead.
SU or nowadays Magisk gives root privileges but they need TWRP to flash them.

bmwdroid said:
No.
TWRP just replaces stock recovery to be used instead.
SU or nowadays Magisk gives root privileges but they need TWRP to flash them.
Click to expand...
Click to collapse
So I can make a full backup of my unrooted android system with TWRP, and restore it as well without any problem ?
Rooting is not mandatory for that ?

HIPOKAMPing said:
So I can make a full backup of my unrooted android system with TWRP, and restore it as well without any problem ?
Click to expand...
Click to collapse
Backup yes, restoring can't be guaranteed although I never had a problem with that.
HIPOKAMPing said:
Rooting is not mandatory for that ?
Click to expand...
Click to collapse
No. TWRP doesn't care

bmwdroid said:
Backup yes, restoring can't be guaranteed although I never had a problem with that.
No. TWRP doesn't care
Click to expand...
Click to collapse
Great, I prefer to keep it unrooted.
Especially since I hardly do anything with it. Just a ghost system for security and that's it.
Thanks a lot for your help, bmwdroid. ;-)

bmwdroid said:
Backup yes, restoring can't be guaranteed although I never had a problem with that.
No. TWRP doesn't care
Click to expand...
Click to collapse
It works, restoration included. Without rooting. I apparently have no problem.
Thanks, I'll see the next step to install LineageOS maybe.
Have a nice weekend.