Hello everyone!
I want to root my phone, but have some question before starting the process, because something maybe will not work as expected.
1. The main propose of my root is to install Cerberus as system app, wich will protect the app from a hard reset;
2. I want to remove some useless apps, like lens, google files, and others (I have found some posts with is safe to disable/remove);
3. I want to integrate the app's updates the phone receives after setting an account. I have used Link2SD on previous phones;
4. MAYBE I will install Butterfly For Daisy (the multitasking is annoying!!), so, maybe I'll install Kernel Auditior as system app.
5. I'll NOT use custom ROM, I'll keep Android One experience for now.
So, as far I read, to complete the root process, I have to disable encryption on phone. The problem is: i use 4 accounts on my phone, one of them is a Google App one, wich means when I configure it, it will ask to encrypt my phone. Google Apps accounts ALWAYS use encryption on my organization, is mandatory. So...
A. Can I root without disable encryption?
B. Can I just boot TWRP to root, without permanently install it?
C. I'll have phone updates problems with questions 1, 2, 3 and 4 above?
D. Will a Google App account work on a rooted phone with Magisk for Mi A2 Lite?
E. Magisk Manager will be installed as system app or user app? Because Cerberus will use root. If I reset the phone, I'll lose Magisk Manager if it is installed as user, so Cerberus will not get root permissions and will not work properly.
Thank you in advice, and sorry for tons of questions.
romulocarlos said:
A. Can I root without disable encryption?
B. Can I just boot TWRP to root, without permanently install it?
C. I'll have phone updates problems with questions 1, 2, 3 and 4 above?
D. Will a Google App account work on a rooted phone with Magisk for Mi A2 Lite?
E. Magisk Manager will be installed as system app or user app? Because Cerberus will use root. If I reset the phone, I'll lose Magisk Manager if it is installed as user, so Cerberus will not get root permissions and will not work properly.
Click to expand...
Click to collapse
A. Magisk/root works fine with encryption.
B. Don't use TWRP to root. But you can boot it without installing (fastboot boot image.img)
C. Follow the process in the Magisk guide thread to install OTAs.
D. No idea
E. User app. It gives itself root via Magisk.
If you modify the system image you'll have a much harder time doing OTAs. You must have unmodified partitions to install OTAs. I do this to get a dark bootanim, but for install/remove system apps you'd be much better off to use Magisk modules. There's modules for both systemizing apps and hiding system apps.
a1291762 said:
A. Magisk/root works fine with encryption.
B. Don't use TWRP to root. But you can boot it without installing (fastboot boot image.img)
C. Follow the process in the Magisk guide thread to install OTAs.
D. No idea
E. User app. It gives itself root via Magisk.
If you modify the system image you'll have a much harder time doing OTAs. You must have unmodified partitions to install OTAs. I do this to get a dark bootanim, but for install/remove system apps you'd be much better off to use Magisk modules. There's modules for both systemizing apps and hiding system apps.
Click to expand...
Click to collapse
Thank you.
A. OK, I'll try soon
B. Ok, I'll use it to take a full backup before start the process
C. You mean your guide or BubuXP's? In fact, BubuXP's seems easier to do!
D. Let's cross fingers...
E. Can I convert it to system? Like I sayed, Cerberus will need root after a reset. Without Manager, I'll not see the warning to grant root access, don't?
I'll search for these modules. Thank you.
romulocarlos said:
C. You mean your guide or BubuXP's?
E. Can I convert it to system? Like I sayed, Cerberus will need root after a reset. Without Manager, I'll not see the warning to grant root access, don't?
Click to expand...
Click to collapse
C. If you just have Magisk, use bubuxps guide. My guide is if you have magisk and twrp and want to do otas. It's mostly the same, with extra steps.
E. Magisk Manager does not need to be a system app. It won't help you if it lives on /system and Magisk gets removed.
Factory reset doesn't touch boot so I guess if you intend to do factory reset often it might be useful to put apps on system. But by doing so, you'll make it much harder to take OTAs.
To take an OTA you'll need to flash the original system, apply the ota then apply your system changes again. If you're upgrading to a release without fastboot images you'll want to take a backup of system before you modify it.
It might even be worthwhile only upgrading to fastboot releases because you'll have the backup and can modify the images before you flash them, avoiding booting without your customizations.
a1291762 said:
C. If you just have Magisk, use bubuxps guide. My guide is if you have magisk and twrp and want to do otas. It's mostly the same, with extra steps.
E. Magisk Manager does not need to be a system app. It won't help you if it lives on /system and Magisk gets removed.
Factory reset doesn't touch boot so I guess if you intend to do factory reset often it might be useful to put apps on system. But by doing so, you'll make it much harder to take OTAs.
To take an OTA you'll need to flash the original system, apply the ota then apply your system changes again. If you're upgrading to a release without fastboot images you'll want to take a backup of system before you modify it.
It might even be worthwhile only upgrading to fastboot releases because you'll have the backup and can modify the images before you flash them, avoiding booting without your customizations.
Click to expand...
Click to collapse
Thank you again. But...
C. I used BubuXP's guide. Works well. I just need an updated "Disable-Force-Encryption-Treble.zip", because it install an older version of Magisk, and I need encryption disabled to make backups, as TWRP can't make backup on /data.
E. Well, Magisk itself won't be removed after a reset, but if Magisk Manager is removed, how an app will get root permissions? The warning about the permissions comes from Magisk Manager, not from Magisk itself (the one on boot), don't?
And, yes, I want some apps on /system, as Cerberus, for example. I'll put the updates on /system, also. It makes easier to handle the phone after a reset. I don't mind too much to OTAs, as we can download the whole ROM and flash it as I need.
EDIT: don't need an updated "disable-force-encription". Just installed lastest Magisk version in TWRP after disable-force-encription.
Related
I've spent quite a bit of time setting up everything on my phone as I like it, as I'm sure many have. I'd like to use Android Pay, and research has shown me that the only way to do so as of now is to use a systemless root. Is there anyway to switch to using systemless root without doing a complete wipe on my phone? I'd really rather not have to set everything up again just for android pay. Thanks in advance for any help.
I'm assuming you have already traditional root in place. If not, give more information on your setup.
Reflash stock system and boot partition for your current build from factory image then flash latest SuperSU 2.66 (and additional packages you previously had to flash). Wipe dalvik and reboot. Use Heisenbergs guide for unlock/root/flash for details.
You shouldn't lose anything but make a nandroid backup just in case.
Just read you're on pure nexus..
IamFuzzles said:
I've spent quite a bit of time setting up everything on my phone as I like it, as I'm sure many have. I'd like to use Android Pay, and research has shown me that the only way to do so as of now is to use a systemless root. Is there anyway to switch to using systemless root without doing a complete wipe on my phone? I'd really rather not have to set everything up again just for android pay. Thanks in advance for any help.
Click to expand...
Click to collapse
You should be able to flash the unsu.zip posted and then flash the system less root zip. Just don't let twrp install root on first boot. This is what I did with cataclysm, I was all set up, rooted with standard methods. I don't use pay so I can't say anything about that.
Make a back up first, and give it a shot.
I recall that installing SuperSU on the HTC10 was originally a special case. Due to the encryption it used, originally flashing SuperSU onto the HTC10 would break the cellular radio, eventually SuperSU was updated to fix this.
I want to know if Magisk is in the same boat, or it could break your radio too like SuperSU used to, or if the way it works does not cause this issue on the HTC10.
And if so, can it be installed in place of SuperSU without having to wipe/reset your data?
I haven't used Magisk so I can't speak from experience.
However:
1) I know in the ICE Rom thread, that users have recently asked for an aroma option not to have SU installed (or PHH SU installed rather than SuperSU) so they can more easily get Magisk working.
2) Secondly, the original developer of Magisk has a HTC 10.
It's a pretty safe bet to say Magisk works if you follow the instructions...
Nearly all the instructions recommend wiping your data though, and that's not an option for me.
the Dev from Magisk has a HTC10 as main device ^^
so Magisk works flawless (except maybe sprint/verizon).
Super Su is not recommended anyway, as you can read on post Nr 2.
i've been using phh's SU for a while now and havent had a single issue.
AFAIK you dont have to wipe data but restore Stock System (Image) and kernel.
stock boot.img is important to wipe the Ramdisk.
I am already on the stock rom, all I originally did was unlock the bootloader then flash SuperSU, I never flashed a custom rom.
Works fine for me!
Works great for me on Leedroid.
1) Full unroot with SuperSU (don't restore anything)
2) Flash Magisk
3) Flash PHH root
4) Install Magisk Manager
5) Install PHH SuperUser
How is Magisk better than systemless SuperSU ?
CroCop18 said:
How is Magisk better than systemless SuperSU ?
Click to expand...
Click to collapse
Its not to say one is better than the either.....
To put it in VERY simple terms (There is much more to it)
Magisk is a utility for rooted related mounts and SElinux permissive status. It allows all mods to be truly systemless. It also allows rooted users to still have the ability to utilize Android Pay. You can read MUCH more at http://forum.xda-developers.com/android/software/mod-magisk-v1-universal-systemless-t3432382
To use Magisk effectively at this point, you need PHH SuperSU.
Magisk, systemless xposed, phh supersu are all under the same umbrella and are designed to be used together.
It works perfect for me on the HTC 10 with the multiple ROMS, including stock, that I have tested. I have used SUPERSU for as long as I remember, but in this case, the modified chainfire supersu did not work smoothly for me in the systemless magisk envionrment. Gotta give thanks to both topjohnwu, PHH and chainfire alike!
Does anyone know if you use magisk will that allow you to take ota updates from HTC or will the ota updates not work using magisk either ? Another question if anyone knows I have an Unlocked HTC 10 but may get the new Marlin due out being made by Htc so I am also wondering if magisk will work and you still get your updates from Google using magisk. I just thought maybe someone one here might know rather than try to go through tons of pages on that thread itself. I am hoping so as that would rock if you could still get your ota updates and have root too using magisk.
By the way, why did you say I might have problems if I am on Sprint?
Cyber Akuma said:
Nearly all the instructions recommend wiping your data though, and that's not an option for me.
Click to expand...
Click to collapse
they say it's recommended.
this is my experience ce seting up Magisk on a LG g4 (h811) running Resurrection Remix, and super su. I have an unlocked bootloader.
my main concern was maintaining viper4android (originally installed with arise (I don't remember the version))
I downloaded all the files for magisk plus the rom (resurrection remix official, just in case I needed to start clean)
I booted into twrp, made a complete backup (system would have been enough, but safety first)
I then rebooted into Android and backed up viper4android from /system/priv-app/. removed the following, super su binary, super su app, busybox/app, Viper driver then the app, and a few other root apps installed to system (I simply deleted the apk from /system/app and /system/priv-app)
now I rebooted back into Android, once booted I rebooted into recovery
and installed all Magisk requirements, and then Magisk viper4android mod.
and finally wiped cache and dalvik/art
now I shut down for about 30 minutes (phone got too hot) stupid snapdragon 808
booted back into Android, opened play and installed the Super user needed for Magisk.
now I open kernel adiutor and allow su access (need to turn off cpus 3-6)
Now I open play and install Google pay and safetynet playground.
now I open Magisk manager, and disable root.
Open play I add my cards fine.
I exit play, and open safetynet playground and check, it passes.
now I enable root again.
I install the Viper I backed up earlier as a user app, and try and use it. Nope it's trying to Install the driver. I cancel and remove it and install the official Viper.
it works fine (remember I already installed the Viper Magisk mod earlier)
Now I'm golden.
Now I never cleared my data, but I did clear dalvik/art and cache.
the only part of arise that I changed was the Viper version, I removed arise version of viper from /system/priv-app and installed the official Viper as a user app)
in all I'm just saying make a backup and try without wiping data.
I chose to wipe dalvik/art and cache because of the major change on the device.
This may or may not work for hboot lock devices. (I'm using a LG g4 (h811))
the release thread does say you need an unlocked bootloader
I have been trying to Google this but am a little confused on all the steps I need to (and don't need to) take at this point, especially since I am a little behind. So I wanted to ask for help on forums, if anyone is willing to give some advice on this.
First of all, I have a Sprint version of the HTC 10. I don't know if that matters or not (I recall back when I was trying to figure out the original Magisk, someone mentioned that a Sprint model HTC 10 could be an issue, but I am not sure why).
Also, so far all I have done in terms of rooting it is:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Ummm, anyone?
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Its all there in the op of the magisk thread.
I read that thread, as I said, I still don't understand some parts.
Cyber Akuma said:
Ummm, anyone?
Click to expand...
Click to collapse
Have you tried posting in the dedicated Magisk thread?
Try installing leedroid nightly latest it has magisk available when you install rom
i did not try it, till now. I read something a few weeks ago.
But in the magisk thread the op said something that SuperSu is not the supported SU method? only phh superuser?!
I would ask the question in magisk thread.
Firstly: You ask a lot of semi-related questions, a lot of these are already answered, out there, in the appropriate threads.
Let me systematically try to answer your questions
What you have done:
- Use the HTC Bootloader unlock
- Install TWRP Touch Recovery with the option of not modifying the system partition (From what I understand, this would cause it to be a temporary install that would go away after a reboot, but it seems to have stayed installed)
- Perform backups with TWRP
- Flash the SuperSU zip with TWRP
Click to expand...
Click to collapse
When you install the TWRP recovery, you actually install it to the recovery partition of your device.
the option the "not modify system" has nothing to do with installing TWRP, but with installing other mods/roms
It's there so you can make a backup without modifying the system partition, that way you can go back to a working isntall if you do happen to mess something up.
And... that's it, still on stock ROM and everything, didn't install anything else that depends on root like Xposed or whatever (That wasn't automatically installed by TWRP or SuperSU or something was it?). I am pretty sure root access is working because two of my apps (Titanium Backup and Chase) tried to request it, and I can see those requests in SuperSU, but other apps don't seem to act like I am rooted. Namely, Google Pay.
From what I understand, Google Pay is not supposed to work if you have root due to that SafetyNet API. However, when I start Google Pay, I see no error message or anything, it seems to work. Granted, I haven't added a credit card to it yet, does the error only happen when you try to make a payment or try to add a card or something? Or should I see it on starting the app? Did I somehow inadvertently setup my phone in a way where root is not being detected?
Click to expand...
Click to collapse
SuperSu *should* break safetney and thus should break android pay, as Chainfire says in the following thread: http://forum.xda-developers.com/apps/supersu/supersu-safetynet-android-pay-t3298115
"In case any SuperSU-rooted device passes SafetyNet, that is a bug in SafetyNet, not a feature of SuperSU."
I also seem to be getting conflicting information on how I should install everything. The guide I followed for rooting my phone said to install SuperSU by flashing the zip, not through the app store.... but the guide for Magisk seems to claim to uninstall SuperSU and install phh's Superuser from the app store. Is there a reason I should do this one way, or another?
Click to expand...
Click to collapse
Installing SuperSu trough TWRP installs the dependencies (the actual root) and the application (which just manages the root access), the magisk guide tells you to first flash the preferred root (SuperSu or SuperUser phh's) trough recovery and then install the correct manager app trough the playstore.
This is probably so John doesn't have to keep on updating his zips everytime the makers of the manager apps update their apps, users can just download the latest version.
Also, all the guides for Magisk say that it is heavily recommended that I reset my phone to stock system, and I really can't reset the data on my phone. Can it be done without erasing anything? I am unclear what resetting to "stock system" would do exactly.
Click to expand...
Click to collapse
Resetting to stock is important for 2 reasons:
1. it cleans out all "old" root apps and methods
2. it cleans up a patched boot.img (kernel)
Then again, if you haven't flashed any other mods, you would probably be safe to install magisk on your rom.
One important thing everyone will always tell you: make a backup! (make a nandroid)
To do this, boot to TWRP and choose "backup" make sure to select: Boot, System and Data
It sounds a little too simple: Uninstall SuperSU and install Superuser (though the method I should do it through is not clear), flash Magisk through TWRP, and then flash AutoMagisk through TWRP. I feel like I am definitely forgetting steps. That, and if somehow I am getting past SafetyNet with Android Pay I don't want to mess with something that might break however I managed to pull it off.
Click to expand...
Click to collapse
The proper steps would be:
0. Make a nandroid backup in TWRP!!
1. Open SuperSU and choose to completly unroot (somewhere near the bottom of the settings menu)
2. Boot to TWRP and flash Magisk
3. Flash the phhh superuser zip file (from the magisk thread)
4. boot android and install the superuser app from the playstore
5. boot twrp and install AutoMagisk
That's it!
Another worry is breaking my cellular radio. I remember that SuperSU for a while did something (or rather, didn't do something with encryption that the HTC 10 needed which resulted in the cellular radio not working once it was flashed, and that for a while there was a special fork of SuperSU for HTC 10 phones to fix this until the main SuperSU app implemented it. I have no idea if Superuser or Magisk also could cause this issue. Does anyone have any idea?
Click to expand...
Click to collapse
Radio shouldn't be broken unless you flash very old zips, don't worry about it
Oh, and finally, my phone is complaining that an update is available, has been complaining for a while, update 1.80.651.6. Can I safely install this OTA update while rooted? Will it remove or break root if I do? And would it be recommended to install it now before I mess with Superuser and Magisk, or after?
Click to expand...
Click to collapse
I allmost enver use official OTA's so I can't say for certain buttttt as you used SuperSU, the root should be systemless so it should accept OTA updates..
What I would do:
1. make a nandroid
2. install OTA
3. See if everything works as expected
4. restore backup if something doesnt work properly =D
I would install the OTA before trying Magisk
Thank you, that was very helpful. I did try Googling all this, but couldn't find clear answers, which is why I am asking here.
And yes, I am definitely going to make a backup before messing with it. Is there any reason to make a Titanium backup too, or will the nandroid one be enough?
As for removing SuperSU, what would that system/boot stock reset delete? Would it delete any installed applications or application settings? Or undo updates to pre-installed system apps? Or reinstall apps that came with the phone that I uninstalled?
Got it working, thanks. (Though, AutoMagisk seems to only be available as an APK, not as a zip that can be installed from TWRP).
Seems like a few configuration settings got wiped due to the system partition being reset, but other than that most of my data seems perfectly intact.
Hi guys,
I bought a HTC One M9 from my friend but I discovered that it's rooted. That's not a big issue but I can't use Snapchat because the device has been rooted. I only know it's rooted with SuperSU.
I don't know anything about roots and ROMs so can anyone help me with this problem? I red some other threads but they didn't work out... The apps hidemyroot and Root Cloaker also didn't help me.
Thanks a lot!
You'd be best off either unrooting or flashing a fresh rom without any root, and using something like Titanium Backup to backup Snapchat, and whenever you re-root, restore from that backup. You won't have to login again. (Correct me if I'm wrong, as this process had worked in the past, however I am unsure if this is the case now.)
Andranoxi said:
You'd be best off either unrooting or flashing a fresh rom without any root, and using something like Titanium Backup to backup Snapchat, and whenever you re-root, restore from that backup. You won't have to login again. (Correct me if I'm wrong, as this process had worked in the past, however I am unsure if this is the case now.)
Click to expand...
Click to collapse
Thanks for your answer! I just don't know how you do everything with roots etc. Is it possible to get the root away? Would be the best solution for me because I never use it. Is there already a good thread which tells you how to unroot your HTC? My phone is S-On so they told me it was not possible...
If you desperately need snapchat that much then you'll have to flash the phone back to its stock state. There is a thread, by flippy, in the general section stickies that explains how to do that.
Beamed in by telepathy.
Don't listen to these guys, you can download a few things and be on your merry Snapchat. What you'll need (all can be found on XDA):
UnSU-signed.zip
SuperSU 2.79 SR3 zip
suhide zip
RootSwitch 1.3.3.2
xposed framework [optional] (I recommend version 86.2 by topjohnwu)
First reboot to recovery, flash UnSU zip, then reboot to system. Download SafetyNet Helper Test and check if you pass just without root, if it's green we're good to proceed. If it doesn't pass, blue or red, you'll want to flash a ROM and start fresh.
Reboot to recovery again, flash SuperSU zip, it should install as systemless automatically. After that you can install the suhide zip and if you want xposed, then wipe Dalvik and cache and reboot.
Once you're rebooted back in the system you'll want to install the RootSwitch apk and suhide GUI from the playstore. Once they are installed, open RootSwitch and select the options for Disable USB debugging and Stop all su daemons (I also have notification showing so I always know whether it's enabled or not). Open suhide GUI and make sure these items are checked off: Android Pay, Pokemon Go, SnapChat and SystemUI. Once those options are checked, go back to RootSwitch and hit Disable Root. Open SN Helper and test again; it should be green.
You now have a device with systemless root and xposed that can be disabled at any time without a reboot and used as a stock device, working with Android Pay and other apps that block rooted phones, including SnapChat. ?
Of course, if you don't want any of this and just want a stock HTC M9, I recommend downloading the RUU for your model direct from HTC and doing a full restore on it.
Hope this helps.
HI everyone I need your help. i installed Adaway using F-Droid without first installing and activating the systemless hosts modules -- which I thought was optional.
Supposedly, failing to activate "systemless hosts" triggers a warning to do so during install, but not in my case. My Mi Max 3 (Global Edition, Post ARB) is stuck on bootloop to OrangeFox.
Uninstalling Adaway from OrangeFox did not fix the bootloop.
I'd be okay with losing all data and reverting to unrooted stock but I don't know how to revert to unrooted stock in OrangeFox when OrangeFox isn't finding any backup images.
Might manually editing the hosts file perhaps fix this?
Should I go into Wipe and wipe everything? Or simply delete Magisk? Theoretically, should this result in a system reboot back to stock?
If I can't see any img files are they still hidden in the phone somewhere (stock images) to reboot to? Because I moved since I rooted and cannot find the backup drive with my images on them.
My OS is still stock Android and Miui. These are the modules installed in Magisk Version 20.3:
optimizedgpsconf
quickstepswitcher
riru-core
riru-edxposed
terminal_debloater
Please, any suggestions -- I am sorry for being so clueless despite being in this forum for five years but although I am good at following instructions this stuff remains basically "magic" to me.
Best wishes!
Anybody ever lose all recovery, including stock, after flashing?
Hi again, I'm the one that bootlooped following adaway install. Stopped mucking around, wiped my data and used Orangefox to flash the OTA, which fixed the bootloop but the phone was encrypted (I really did wipe everything and check all the right boxes in the Miui menu). No big deal. I booted back into Orange Fox and did another data wipe and was able to boot to system.
Unfortunately, not only did I lose root, I lost recovery -- no TWRP, no OrangeFox, no stock recovery. I can only boot into the system.
And yet oddly, I can still browse the root files using a root browser and some play apps for root users still detect Magisk. (but Magisk Mgr isn't one of them).
I'm guessing the wise thing to do at this point is to use ADB and start over from scratch, reinstalling TWRP, Orangefox, Magisk and the rom?
Again, if anyone has encountered this error or has any inkling of a quicker way to fix it, please jump in. Thanks!
I