Develop Bugs

Best way to currently install marshmallow after failed attempts

Hi, after trying to use philz recovery to flash a ROM on to my device I got what I think was called a soft brick where I had to download and flash the stock ROM.
My device (GT-N7100) is now not rooted again and back to square one. Any problems I come across occur from using old tutorials with dead links so if someone could recommend a tutorial to install a custom rom like 5.1 I would be very grateful. Thanks
EDIT. I found this guide on youtube http://mytechtube.in/samsung-galaxy-note2-rooting.html + http://mytechtube.in/samsung-galaxy-note2-6-0-1.html . Does it look like it will work?

Flash twrp using Odin, then flash a custom rom via twrp.

Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk

Root is not required to flash TWRP. TWRP can be flashed directly to the phone using Odin.

1life2love4 said:
Root your phone first. Flash recovery like twrp and install custom rom like Resurrection remix the ROM is stable most of the things works and good as daily driver.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
audit13 said:
Flash twrp using Odin, then flash a custom rom via twrp.
Click to expand...
Click to collapse
Should I just use the latest version of TWRP direct from their website https://twrp.me/devices/samsunggalaxynote2n7100.html ?
I think my phone code name is t03g how can i confirm?
Thanks
EDIT. Just installed TWRP :good: now on to picking a good ROM. will have a look at the ressurection one too.
To install apps that require root should O root it now or do some ROMS root it for me?
Sorry for the amount of questions

The easiest way to install twrp would be to flash the tar version using Odin.

audit13 said:
The easiest way to install twrp would be to flash the tar version using Odin.
Click to expand...
Click to collapse
Just did as you suggested thanks. To install apps that require root should I root it now or do some ROMS root it for me?

Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.

audit13 said:
Most custom Roms come prerooted. If the rom is not rooted, you can flash supersu.zip from recovery.
Root can be enabled on cm13 under developer options in settings.
Click to expand...
Click to collapse
Thanks for the info. I've watched some videos of cm13 and I so far thats what im going with. Will look for a youtube video to help with installing it.

To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.

audit13 said:
To install, download cm13 to an sad card, wipe cache, wipe system, wipe data, install cm13 zip from ad card, reboot.
Cm13 does not come with Google apps (gapps) so you'll have to decide which version you want.
Click to expand...
Click to collapse
I didnt realise that before. Could I for example install any of the GAPPS from this link https://devs-lab.com/android-gapps-download.html " full google apps" or pico google apps ?
From whatI gather GAPPS are installed straight after rom install before root though is this the same in cm13?

Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/

audit13 said:
Flash CM13, flash Gapps, reboot.
I like open gapps frome here: http://opengapps.org/
Click to expand...
Click to collapse
Perfect Im going to try that in the next hour. I like the look of aroma. For platform would I select ARM and android 6.0?
EDIT. Found the answer it was ARM.

Arm as I believe your phone has a Qualcomm processor.

audit13 said:
Arm as I believe your phone has a Qualcomm processor.
Click to expand...
Click to collapse
Yeah was ARM as I just installed CM13. Thank you seriously headig your way.

Hopefully, everything works.
Now that you have twrp on your phone, you can use it to create a backup of everything in your phone, including time efs folder. Save the efs folder in a safe place in case you need to restore it to the phone at a later date.
After making a backup, you can flash other Roms and you can return to cm13 by restoring your backup.

Just getting familiar with it. Thanks for the help.
Do you know if there's settings to turn screen on during during calls because it works with the front sensor and that sensor is broke on my phone?
Sent from my GT-N7100 using Tapatalk

You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.

Got it sorted using an app from the play store.
Sent from my GT-N7100 using Tapatalk

audit13 said:
You could try disabling the proximity sensor in the phone so the phone screen doesn't blank out during a call.
Click to expand...
Click to collapse
Hi, phones been running great until yesterday when it started telling me the disk space was nearly full(via es filee xplorer). It then turned off a few times and i turned it on again. The phone would shut off if I tried to do anything like launch the camera app. It now bootloops when i try to turn it on.
I have tried wiping dalvic cache, factory reset, recover from a recovery point i made when i installed the rom and reinstalling the custom rom like I did the first time.
The phone did once go into a boot animation of the old boot screen(02 animation), another time it started the miui boot logo but went back to the normal samsung galaxy note 2 boot loop.
Any suggestions on how i could get it running again? Thanks!

Still confused about how to install Magisk/Automagisk on my HTC 10

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.

re-flash stock firmware

Hi there!
I'm using stock rooted phone on latest stock firmware. I would like to know how I can reflash stock firmware again using TWRP (Wich I have installed already) without loosing data or recovery if possible. Thanks a lot people!

marcomir said:
Hi there!
I'm using stock rooted phone on latest stock firmware. I would like to know how I can reflash stock firmware again using TWRP (Wich I have installed already) without loosing data or recovery if possible. Thanks a lot people!
Click to expand...
Click to collapse
Yes you can reinstall it using fastboot without losing data. You might have to install twrp again and SuperSU if you want root. If you use the flashall method take off the -w.

Tulsadiver said:
Yes you can reinstall it using fastboot without losing data. You might have to install twrp again and SuperSU if you want root. If you use the flashall method take off the -w.
Click to expand...
Click to collapse
Thanks! But I think you can do it right from TWRP. I think it was just wiping SYSTEM and one of the caches, leaving data and internal storage alone, then reinstalling it. I was following a guide once that did this, but can't seem to find it anywhere again. But I think I might go with the method you told me. Thanks for your reply!

marcomir said:
Thanks! But I think you can do it right from TWRP. I think it was just wiping SYSTEM and one of the caches, leaving data and internal storage alone, then reinstalling it. I was following a guide once that did this, but can't seem to find it anywhere again. But I think I might go with the method you told me. Thanks for your reply!
Click to expand...
Click to collapse
You can sideload an ota update thru twrp. Maybe that is what you were thinking about.

Unpack Factory Image and manually flash each .img in TWRP. Just switch from .zip flash to image flash mode in Install section.

ROM new Lineage 14.1 Unofficial WhenICanlies d2tmo 4-10-18

I have been working on the sister models also. I saw no one was building these anymore so here it is I hope it can be enjoyed by all. Spread the word. provide feedback so other fans of this ROM may obtain it and work out any bugs if there are any. I will update once or twice a week depending on time and demand. I'm compiling for three different variants. Hit the thanks button and Enjoy. Dirty flash the updates not the initial flash of this rom but the updates to it. Initial install = Factory reset, wipe data and cache, install rom zip, install gapps zip, install su zip, reboot system. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
4-10-18
https://www.androidfilehost.com/?fid=890129502657597436
4-13-18
https://www.androidfilehost.com/?fid=818070582850507491
4-17-18
https://www.androidfilehost.com/?fid=818070582850508419
4-24-18
https://www.androidfilehost.com/?fid=673956719939836620 If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app
5-4-18
https://www.androidfilehost.com/?fid=818222786056028546
Root is not baked in. Flash and root your preferable way.
5-20-18
https://www.androidfilehost.com/?fid=674106145207488021
5-31-18
https://www.androidfilehost.com/?fid=674106145207490572
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060741
9-3-18
https://www.androidfilehost.com/?fid=1322778262903996744
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022369
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868411
12-16-18
https://www.androidfilehost.com/?fid=11410963190603876081
2-25-19
https://www.androidfilehost.com/?fid=1395089523397901582
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924752
5-6-19
http://download1589.mediafire.com/7...q5/lineage-14.1-20190507-UNOFFICIAL-d2tmo.zip
10-13-19
https://www.androidfilehost.com/?fid=1899786940962607809
i recommend clean flash as i built with different computer
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.

thanks bro... but is it rooted rom or use any method to root it ?

hasan.sy said:
thanks bro... but is it rooted rom or use any method to root it ?
Click to expand...
Click to collapse
I use SuperSU zip

the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it

hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
I appreciate the feedback and no worries mate I'm still trying to get the no sim bug worked out in the att variant no luck so far sprint variant is doing good also

Update posted 4-17-18

It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.

Sammay_Boiii said:
It won't boot up for me. I installed the ROM after wiping my entire system through TWRP, flashed Gapps, and installed SuperSU provided by TWRP. When it boots up it says system isn't responding.
Click to expand...
Click to collapse
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding

Joker1716 said:
Wipe system, cache, and dalvik install rom zip install nougat Gapps and SuperSU all at the same time meaning do not reboot until you have flashed all three if it didn't work the first time try it again just make sure you wipe system, cache and dalvik and install the Gapps at the same time it sounds like it's booting up but conflicting with other elements otherwise it would be bootloop and not system isn't responding
Click to expand...
Click to collapse
Thank you for your rapid response! I will try that as soon as I get to my house and I'll let you know what happens

After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?

Sammay_Boiii said:
After doing what you said, it still says "process system isn't responding" I will try a few more times. Also, I'm flashing off nothing. There is no OS, no personal data, just TWRP. Does this have to be flashed on CM12 or something?
Click to expand...
Click to collapse
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
This should help
https://forum.xda-developers.com/showthread.php?t=1949687

Joker1716 said:
You need to Odin flash the latest stock firmware then root then flash recovery then flash the rom
Click to expand...
Click to collapse
I will do that. Your rom needs to be flashed over stock rom?

Sammay_Boiii said:
I will do that. Your rom needs to be flashed over stock rom?
Click to expand...
Click to collapse
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?

Joker1716 said:
No this is lineage os 14.1 it's not mine I just build it because they have stopped doing it officially for this variant of the s3 but there's more to a phone than just the system and you have nothing but a recovery? There's bootloader modem, Efs etc. You wouldn't be able to even flash CM12. in TWRP are you going into advanced wipe or are you just swiping the slider?
Click to expand...
Click to collapse
What you said makes a lot of sense actually. Im used to just flashing back ups of other roms that I forgot how to flash fresh ones. I'm not used to this haha but I got it now. Stock rom 4.3 has been flashed via odin and the root method is currently on my screen.

hasan.sy said:
the rom is smooth and stable and i havent faced any probleme ..thank you for you effort and hope you can make oreo rom when the developers fix the problems on it
Click to expand...
Click to collapse
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3

Sammay_Boiii said:
What was your system status before flashing the rom? What software? I'm having trouble flashing it on my S3
Click to expand...
Click to collapse
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher

hasan.sy said:
t999uvuenc2 firmware and bootloader 4.3 using twrp recovery 3.2.1-0..... you must update to latest official firmware t999uvuenc2 to flash any rom 5.1.1 lollipop and higher
Click to expand...
Click to collapse
Thank you. Ive been flashing this rom repeatedly and always received a "Process system not responding" then it falls into a boot loop

Update posted

Joker1716 said:
Update posted
Click to expand...
Click to collapse
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)

hasan.sy said:
Does it need wipe data and cash before flash or we can do dirty flash without any thing?(update from 13-4-2018 to this rooted update)
Click to expand...
Click to collapse
If it's an update then dirty flash it if you already had SuperSU installed you will need to reflash the SuperSU zip if you are installing for the first time you just need to install the SuperSU app

HELP PLEASE: Bootlooped Mi Max 3 after botched Adaway Install

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