Related
HI, I am a complete stranger to rooting but I wanted to improve my phone without buying a new phone.
I have read the "effen manual" and downgraded the ROM.
I then installed 'cfx_ace-4.2-SR5.zip' and after a long time and a couple of forced reboots the phone came to life. I then had no access to download apps (the gapps zip was not included or mentioned on the site, I think).
I wiped the phone clean and then installed 'cm-JellyTime_42_R2.zip' and still had the same issue. Basically, after the initial HTC screen nothing happens after the ROM has been installed and I have rebooted the phone. It takes a lot of re-installing, removing battery, re-installing before I finally get the phone to work. Finally everything works, I also install 'gapps-jb-20121212-signed.zip' to get access to Google playstore but a new problem arises. I am not able to access the internet.
I am in Australia and use Lycamobile (I have added the APN settings ‘manually' but still no luck, I have rebooted my machine many times, spoken with the customer support but still no luck. Strangely enough the same sim card works fine in an unrooted phone.
I have now wiped the phone clean again and am in the process of installing 'ViperSaga_OTA_1.1.0.zip' but am stuck on a blank screen for the past half hour in desperation. (http://forum.xda-developers.com/showthread.php?t=1983604).
The instructions say
1. Download the ROM – Done (but does not say which one so I have downloaded the Ota one)
2. Flash the ROM (AROMA Installer will pop up) – It did and once it was done, it said reboot
3. Choose Fullwipe (important)- from where??
4. Choose the mods you want – from where??
5. Reboot
6. The Rosie (HTC Sense launcher) needs about 5-10 minutes to get the best speed, so it needs some time of playing until you have the best speed
7. Battery life is the best after 3 charginig cycles so give the ROM a chance
My question(s) for which I am seeking your advice is
a) What am I doing wrong in installing the ROM's why does my phone take so long to come to life?
b) What do I need to do to fix my internet issue (Wifi works fine). My radio version is 26.10.04.03_M
Many thanks and apologies for the long post and showing my ignorance…
How long a time approximately? All ROMs take a bit of time on first boot. This is when they're populating the dalvik-cache with optimized data for each app on the phone. So it's normal to see a black screen or continuous bootanimation for some time on first boot. So once you flash a ROM, just let your phone be idle till it turns on fully. Don't pull battery or do anything in between. The next time you reboot your phone, you'll see that it boots much faster because the dalvik-cache is already built.
Coming to the topic of the ROM you're trying to flash, ViperSaga is a ROM for the HTC Desire S, not the Desire HD. You shouldn't be flashing it. Even if it was a ROM for the DHD, you need to flash the ROM zip first and *then* flash the OTA. OTA = Over The Air. OTA zip files are meant for small updates to an already existing ROM. They are not the full ROM, so you need to flash the full ROM first and then flash the OTA package to update it. These OTAs can also be downloaded in Settings->About->System software updates.
In the 4th post in the ViperSaga thread, a list of ROM downloads is provided. The actual ROM file is ViperSAGA v1.0.0 (dev-host) which is 427.47 MB. That is the one that should be flashed first. The OTA file is meant to bump the ROM from v1.0.0 to v.1.1.0, not to be flashed by itself. That's why it's of such a small size of 28.47 MB. ROMs are never that small a size.
Now, DON'T flash that ROM. It's not meant for this phone! If you want a similar ROM, there's ViperDHD by the same developer. And don't flash gapps for a ROM unless it's explicitly mentioned in the first post of the ROM thread. If you look throught the cfX and JellyTime threads, you'll see that it is. You will find the latest gapps (Android version-specific) at http://goo.im/gapps and you can read about gapps at http://wiki.rootzwiki.com/Google_Apps.
The reason you weren't able to see the options for full wipe and the modifications is because, apart from flashing a wrong device ROM firstly, you didn't flash the right ROM file, so the AROMA installer didn't show up. AROMA is an interactive installer that allows you to choose stuff rather than just directly flashing a ROM file. Try the same procedure with ViperDHD, following the instructions and downloading the right files, and you'll see everything properly. ViperDHD has an AROMA installer that provides options to wipe your phone automatically rather than doing it yourself, thus making it easier to flash the ROM. ROMs don't usually have this. Before flashing a new ROM (not an update to an already flashed ROM, but an entirely new one), you should ALWAYS wipe your phone fully. This can be done in recovery by going to 'wipe & format' and choosing 'wipe boot', 'wipe system', 'wipe data/factory reset' and 'wipe cache'. For example, if you want to switch from ViperDHD to cfX, then you need to full wipe. If you just want to flash an updated version of ViperDHD or cfX, then you don't need to unless you're testing for bugs to report to the developer.
Here are some guides to booting into recovery and the correct flashing procedure of a ROM -
http://forum.xda-developers.com/showthread.php?p=35937493
http://forum.xda-developers.com/showpost.php?p=30530565&postcount=179
I'm not sure about your internet issue, but first flash that ROM and try if it works.
Sent from my Desire HD using xda premium
sashank said:
I'm not sure about your other problems, but ViperSaga is a ROM for the HTC Desire S, not the Desire HD.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
Thanks Sashank,
downloading ViperDHD_v1.2.3.zip as I write, hopefully, hopefully that will fix my issue....
Thanks once again.
I just updated my post with a lot more info after you replied. I was in a bit of a hurry and I didn't read your post fully at first. Once I did I knew what you were doing wrong. So refresh your page and read it fully again. Good luck.
sashank said:
I just updated my post with a lot more info after you replied. I was in a bit of a hurry and I didn't read your post fully at first. Once I did I knew what you were doing wrong. So refresh your page and read it fully again. Good luck.
Click to expand...
Click to collapse
Hi Sashank,
Apologies for the delayed reply, I have just loaded the new ROM and it works.. it works!!!!!!!!
Thanks heaps for hitting the nail on the head and the very detailed email explaining what I was doing wrong.
Just one more question.. do i need to upgrade my radio??
Kind Regards,
Not necessarily. You only need to flash a different radio version if you are having low signal issues, dropped calls, high standby battery usage, and overall bad connectivity with your current radio version. If you feel calls sound good, and you're getting a good signal, then you don't need to. Radios are region specific, so newer is not always better. You just need to find one which works well for your region and stick with it. If your current one does, then leave it like that.
You don't flash radios in recovery the same way as a ROM. They are flashed in different ways. Here's a guide to flashing radios the easy way - http://forum.xda-developers.com/showthread.php?p=30552152
Also, point to keep in mind, when you see anything about flashing RIL after flashing radio - Corresponding RIL for a radio version should only be flashed on HTC Sense Gingerbread ROMs. Not on HTC Sense ICS ROMs and AOSP ROMs like cfX, Jelly Time, CyanogenMod etc.
Sent from my Desire HD using xda premium
As the title says, I am running gedeROM 1.55 for the past year, since I experimented with a couple ROM's and settled on this one. For the most part its been a decent daily driver but have found it a little 'sluggish' lately and it annoys me. The lack of deep sleep keeps me always scrambling to keep it charged and ready to go so I don't find it dead when I want to use it.
Of course in the process I am using an older version of FFF and TWRP, so I know an update of them would be necessary.
A couple questions, looking for opinions:
1. Is it possible to just use KFU and update FFF and TWRP without disturbing everything else? I'd like to get them up to date.
2. After reading for 2 hours or more I am unclear on the limitations of 10.1 JB and wonder if I should be changing to JB at all?
3. Are the 10.1 ROM's a better option than I am running for speed and reliability? If so, any shining star amongst them?
I know asking for opinions will bore most people to death reading this, but I need some guidance from those that have been active and keeping up with ROM dev on this unit while I left mine alone and got behind.
Thanks in advance.
This might help you:
1. Look on the first post of this thread. Theres a flashable zip for FFF1.4 (Just flash in TWRP)
2. Here is Ichigo's flashable zip for TWRP 2.5.0 (Just flash in TWRP) https://www.dropbox.com/s/b4idirzkmgvnm07/TWRP-Blaze-2.5.0.0.zip
Those will not disturb anything else.
And try This ROM first and see if you like 4.2.2. This is the OFFICIAL cyanogenmod 10.1. To me its by far the best in terms of stability and speed. Make sure you wipe everything BUT /sdcard in TWRP before you flash!
Moving to a recent JB ROM will be a good move compared to gede because not only will you have better battery life but you'll have almost another year of improvements made to the Kindle since then.
Thanks for the info.... I'm gonna give this a shot I think. Not much to lose, nothing mission-critical on my tablet anyway
I'll post back once it's done!
Thanks again.
Bozz5384
It seems to have gone well, thanks for all the info. Updated FFF, TWRP, and now on CM 10.1 ... I did the 5/20 nightly, wasn't sure which one to do -- seems pretty bug free at this point.
So I'm running into a wall on this.
https://play.google.com/store/apps/details?id=com.square_enix.ff7g_bike Updated a week ago to 1.2.0, and prior to that it would run fine (if a bit laggy at times). But since installing the update (required to play) it won't run. I'll tap on the icon, it'll load and show in the background with other running apps, but just won't run proper? I even updated to Android 4.4.4 cm-11-20141112-SNAPSHOT-M12-d2lte, from 4.4.2), used the Triangle Away app to reset things so the phone wouldn't appear to be custom/flashed, and still doesn't work.
I tested the update on a friend's S4 (un-rooted) and haven't had the same issue.
Is my phone (SGH-T999) just too old/no longer supported? The S3 is still on the device list: http://help.finalfantasy7-gbike.com/model but perhaps it wasn't updated.
So the last update to 1.4.0 at the end of April took care of the problem, which was great.
However..... they've updated to 1.5.0 today, and I'm experiencing the same exact problem I had prior to that update.
I don't know what to do, if there's anything that CAN be done.
Help, please.
Probably because you are using an aftermarket rom. Only thing I can suggest is to use a TouchWiz rom, or update cm. That zip is extremely old. Try the latest nightly. In case you didn't know, cm12 is available for the s3 under d2tmo in case you want to try it
It's possible.... so far unrooted/stock-rom devices are fine. However my friend let me root their S4 and that didn't cause an issue.
As for updating CM, I'll give that a try. I hadn't checked since March (and CM updater didn't give me any indications of a newer version oddly).
*edit* Ok I used TWRP 2.8.6.0 and updated to cm-12.1-20150614-NIGHTLY-d2tmo (along with gapps-5.1-2015-04-20-15-56-24), during the "Android is upgrading" screen (after a very long time on the CM splash) the phone rebooted.... currently back on CM splash screen... will edit in more details once beyond that screen.
*edit2* Past the CM splash, on "Android is starting".... optimizing apps 3 of 108.... and again with reboot.
*edit3* Again at "Android is starting" now optimizing app 198 of 199.... *fingers crossed*
*edit4* Finishing boot.... ok looks like I need to use a newer gapps... ok, updated to gapps-5.1-2015-06-02-15-19...
*edit5* Well everything appears to be working.... though the G-Bike game still won't load once updated to 1.5.0... it does at least switch to the horizontal position and the screen goes dark longer before returning to the homescreen... but that's about it. :crying::crying: Switching to TouchWiz may have no change either, correct?
*edit6* I've always used the default messaging app, but when I opened it it's seemingly stuck on "loading conversations", I read elsewhere that it may take a very long time to load if you have a lot of texts... which I guess given that one contact has 4,000+ texts saved in that thread, perhaps it's just a matter of time before all previous texts load?
A rooted rom shouldn't affect it. I mean aftermarket like cm or aosp. It could work fine on TouchWiz, especially since it's listed as a supported device. Yes, texts may take long time to load if you have many
Texts finally did load. I'm about to install CM on the S4, to see if the game no longer loads then. If that's the case, then I'll switch to TW on my S3 and hope that the game works afterwards.
Unfortunately I'm under a bit of some time constraint, the 1.5.0 update was for an event to gain a new support character, and that ends in exactly 1hr....
Given the time-frame, is there a "quick & easy" method to flash a TW rom without having to do various app data backups/nandroid backup (I will have to factory wipe, yes?), and not lose much/any data? I unfortunately don't have a high capacity SD Card (4GB, my 64GB one in the S3 stopped allowing write access a few days ago, seems to be an issue with that particular card), and 4GB isn't nearly enough to backup everything from the S3 to SD.
*edit* Well well..... 1.5.0 will not run on the CM rom on the S4!
You can back up to your internal memory. As long as you factory reset with custom recovery, you won't lose anything stored on it, except apps and settings
Great! One further question, is there any possibility that by switching ROMs, the game might think I'm on a different phone/new user (and if so, is there a way to fix this?)? Despite all the un/re-installs, I've never lost my progress most likely due to it being saved on their servers... but I'd hate to appear as a new user and lose month's worth of progress.
Yeah there's always that possibility. That's why you should always back up your apps with data so you can restore it in case
Thanks again. I wish I knew exactly what was being changed from version to version, that makes the game not work on an aftermarket rom. If it never worked from the beginning, that'd be one thing... but it's a yes/no/no/yes/no type of deal here. Shame I can't just take what works in the 1.4.0 version and compile it into the 1.5.0 ver... Or figure out what it's checking, and make it think it's a stock rom instead.
Note: This should go without saying since this is a very early beta build, but I'm not responsible for any direct, or indirect damage done to any phone or accessories from flashing/ using this rom.
Also please read the entire op before installing/posting.
Welcome to:
THE ARKO PROJECT
About the Rom:
I started this whole project when I had a G5, and development was still slow. I met someone who was kind enough to get me started, and give me the basic info I needed to start my journey in development. I had always wondered if I could, but never really knew where to start.
Seeing the lack of development for such a great device. I decided to take matters into my own hands (however inexperienced they may be). So far I've created basic tweaked stock roms for the G5 & G Stylo. I never released them however because I didn't make it too far. Because the devices ended up being damged (which is unusual for me).
Anyway that brings us to here & now. This rom is also very basic (for now). I plan however to add as many features as possible & plausible. While keeping it fast, smooth, and reliable. Rest assured I test every build for at least a couple of days before posting them here. Anyway onto the good stuff.
Source: Pulled from stock MM 6.0 30d
Boot img: Pulled from stock MM 6.0 30d (changed to insecured).
Android ver: MM 6.0 30D
Features:
Rooted (Sytem install)
Wifi, data, bluetooth etc. all working
Dpi set to 560
Debloated (More apps removed in future updates)
Busybox
All app multiwindow support enabled by default
Quick power on
Auto rotate in homescreen (tested with Nova Launcher)
Faster video streaming
Increased wifi scan interval
No ring delay
Enabled Adoptable storage
Jpeg quality 100% plus other media enhancements
Disabled error reporting
And some more I can't think of....
Planned features (feel free to suggest some):
4 way reboot
Volume button orientation mod
Possibly aroma installer
That's all I can think of off the top of my head but there is more.
I also plan to make a few color ui themes as well.
For example
Red & Black
Blue & Black
Green & black
Etc. Etc.
Feel free to request different colors as well (doesn't mean it will neccesarily happen, but you can ask
Install instructions:
*Make sure the version of TWRP you are using supports updater-scripts! This is very important! If it doesn't the rom will not flash! I'm using the latest version of multirom TWRP, and can confirm the rom flashes just fine.
1. Make a TWRP backup (optional, but heavily suggested)
2. Download and place zip on sd card
3. Do a full wipe
4. Install zip
5.Enjoy
Note: updates are disabled two minutes after booting the rom. No user action is required. The old method I had tried didn't actually work. Got the ota again a week later. However it is 100% fixed now.
New DL link: https://drive.google.com/file/d/0B1bdSH2f5u2UMzdBUlkzcTFBMU0/view?usp=drivesdk
I don't know if this would work since I have not really put much research in to it, but could you make the folder where the update is downloaded to read-only?
BoredKender said:
I don't know if this would work since I have not really put much research in to it, but could you make the folder where the update is downloaded to read-only?
Click to expand...
Click to collapse
Probably not a good idea. Folder also has a few log files too. If all else fails then I'll give it a shot. I also had a thought that perhaps it isn't named anything like lgdmsclient.
After some sleep I've got a couple days off work so I'm gonna try to get multi rom working. (Haven't used it since kk early android L. That way I can just go down the list remove lg services apk's one by one and hope that either multirom or twrp could save me from a brick if anything goes wrong. Right now I have been using the delete update.zip/reboot. To keep the zip off my phone. Only problem is it takes a while for the system to realize an update is available after that. So It would be easier to remove an apk, build, flash, repeat until I find the culprit. MR will really help though as it'll save a lot of time between flashes. I really do appreciate the help/input though.
Also I've randomly found myself booted into twrp and the update try to install itself. Just luckily had zip verification on so it didn't flash.
Removed build.
Deleted
The Rom now has it's own thread in Tmo Android development located here:https://forum.xda-developers.com/tm...t/rom-arko-project-g3-edition-6-0-mm-t3555919
Moderater if you will please, close this thread. Thanks.
Thread Closed.
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Akopps said:
If I reached a point where I don't understand what's going on and I am banging my head against the wall, I would download the latest stock firmware for my device from sammobile and flash it with odin. If I recally it correctly, that would be the November 2016 security release of Marshmallow, the last Samsung provided. This should wipe away everything you have on the tablet. Then, if you need to flash root or alternative ROM, flash TWRP and proceed from there.
Click to expand...
Click to collapse
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Merancapeman said:
Much obliged for your response, I've been up for a bit hoping maybe the boot process would just take a while, but no luck there. In the meantime I've been trying a few different Lineage nightly builds and they all seem to result in the same problem; surely they can't all be messed up and it's obviously something I'm doing wrong. My last recourse is to do this terminal fix I found that worked for someone else, but I doubt I'd be that lucky. I will assume that the Nov 2016 Marshmallow release is a google search away (or am I just bad at finding things...), and I'll post back here either within the hour or tomorrow night when I have time to find this build. Again, thank you.
Click to expand...
Click to collapse
Download the appropriate MM version from below. Boot to recovery, factory reset, flash with Odin.
First boot will take around 10 minutes.
http://updato.com/firmware-archive-...xact=1&r=&v=Marshmallow(Android+6.0.1)&rpp=15
Merancapeman said:
So, let me begin this tale with this disclaimer: I've worked with modding communities across a whole span of genres, from gaming to building computers. I will begin with the assumption that I am at fault in this case and I'm clearly doing something wrong. I've about reached the end of possibilities that I can explore on my own, so it's not like I tried one thing and gave up.
Once upon a time, I knew more about what I was doing than I do now. I first bought the T800 model several years ago, and the first thing I did was learn how to root it and flash CWM recovery. I went on all sorts of adventures with the device but never fully explored the potential; just installed awesome stuff that I thought I would use forever and got rid of bloatware and other useless crap. Flashforward to a few months ago, when I realized I had a really nice tablet that I had spent money on but didn't use like I had wanted to. I'm working more and more on audio mixing, and I wanted to install an app for the tablet that would allow me to remotely operate a mixing board. To my dismay, the app required an updated version of Android, and I hadn't a clue as to how to do that because the tablet was rooted and such and the thing wasn't going to update (was stuck on stock 4.4.2). I don't remember what I had done with it many years ago - at least not very well - and all I had learned was nearly gone. I refreshed a little, made a backup, checked to see what I had and noticed I still had the CWM recovery up, things were still rooted fine, and I was prime for flashing a new ROM and wiping everything. Found the Lineage ROM, slapped that puppy down, aaaand... Verification wasn't happening. Huh? It didn't even try to install, it just gave up and put the stock ROM back on. Tinkered with it for a second and thought, eh, whatever, I'll just let it update itself now that it's been wiped and everything. Only the device still wouldn't let me update it to Marshmallow or whatever update limit it's got.... Awesome... Did a little more research. Oh, my recovery is probably super out of date. Grabbed ODIN, slapped a brand spankin' new TWRP recovery that was geared for my device on it, and decided that I shouldn't go with Lineage. I'll just go with a stock Nougat ROM (can't post a link, but if it's important I can PM it to you if it's relevant).
Followed instructions to the T (as far as I'm aware) and this time did everything with a fresh new outlook into what I was doing. Flashed it, flashed GAPPS, aaaaaand.... Samsung logo won't go away.... -sigh-... Wiped it again, tried to make sure everything was wiped correctly, made sure everything was up to date. Tried again, but alas... Nothing working right for me.
Perhaps during this tale you've already picked up on something I royally messed up. Perhaps you're thinking, "Wow, how did this doofus not brick his tablet?" Am I getting old and stupid? Was there still research I missed? I started with the low road of easy modding and had to force myself to a higher road of deeper learning and STILL came up empty-handed, so now I'm asking this awesome community for a hand. I know you can't do this for me, but I'd appreciate a guiding light, or at the very least a link to an article that I really should have picked up on. Let me know if there's information I've missed that I should also be putting out, and thanks for reading regardless!
Click to expand...
Click to collapse
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
DarkExistence said:
Hello, Lineage dev for T800 here.
Did you flash the updated bootloader I link in the OP? Gotta be on the MM one for it to boot past that samsung logo
Can be flashed via ODIN, instructions are on there!
Lemme know if you get it!
Click to expand...
Click to collapse
Just got back from work, about to test it out and will update on both situations (should one not work out). Regardless of the success, I'm genuinely honored that you guys are helping me in this process and I didn't expect such a warm and welcoming bit of support. Too often I see the "well any bloomin' idiot with enough IQ in his head to tie his shoe could have done this" comment, although I'm almost positive I'm going to get this fixed with your help and realize I've done something super stupid.
Welp, I'm a right idiot. I went with the first option, which was to attempt to flash a stock MM ROM. I followed akopps and ashyx' advice and went to that website where I believed I found the appropriate file and downloaded it. For some odd reason it took about 8 hours to download almost 2gb, which is odd because my net is faster than that. Anyway, I let it sit overnight so no issues there. A while ago I attempted to copy it over to my SD card, which was met with a slew of problems thanks to the copy process being cancelled multiple times. Maybe because the size of it? I had plenty of space. At any rate, it wasn't going to be an issue because I knew it was something I was probably doing wrong and would figure out later. I skipped and went straight toward DarkExistence's fix, which was to make sure I had the MM bootloader (I saw this instruction in your thread but at the time wasn't sure what it entailed and thought I was perfectly safe, and this was sadly before I learned more about what I was doing). Went through that process just in case, wiped, flashed the Lineage ROM , flashed GAPPS, rebooted, aaaand...
Bugger me, it worked.
So now I feel like a proper idiot. I hope this ends up in a google search down the line so other doofuses can stumble upon my own mistake and see that sometimes overlooking one simple thing can make all the difference. Will update in the future should anything change and I find myself doomed once more, but so far things seem tip-top. I checked to see if I could install the mixer remote app I had initially begun this journey for, and lo and behold it is now available for me to download! Now all that's left is to figure out how to root it, and voila! Thank you all so much, I am almost as relieved as I am embarrassed.