I already have the APK. I just need a way to get it onto the phone…
I wouldn’t put it past @sh7411usa to help you with twrp.
Don’t think this is gonna help but I had the same bootloop recovery situation when trying to replace some system apps and I reflasrd the super, but if you dont have that…
All fixed BH!!
Give thanks to everyone for being so kind and trying to help!!!
Got in touch with the guy that made the ROMs and got the partition I needed
Posted from my qin 
Amazing glad to hear!! Was in middle of a very lengthy reply I just deleted… Can you explain exactly how you did it in case anyone has a similar issue and does not have access to a computer.
We are always open to your posts of wisdom even if it’s not applicable anymore
First of all
Yeah, I’m sure others can gain from it
As I noted in my first post, the issue was with a APK in system_ext that I messed up and the end goal was to replace it back with the original one. What can be easier than getting the full system_ext - specifically from your ROM - and flashing with fastboot (in fastbootd) fastboot flash system_ext system_ext.bin
Possibly, yeah.
I see you sorted it out, reflash of exact firmware is always best.
Happy for you. I thought you mentioned not having access to a computer - wanted to see the “device only” solution. Either way, glad you got it working. At the point where you had the correct APK but not the full partition, I was going to suggest backing up your broken partition using mtkclient, using a pc to inject the correct apk, and the restoring the partition using spflash/mtkclient/fastboot. (In reference to an earlier post - it would seem overkill to build TWRP from scratch to restore a partition just to circumvent PC requirement, especially if he would’ve needed a PC anyway in order to flash TWRP).
I did mention that option. Also I wasn’t looking to build twrp. Was just checking if there are generic builds that work across devices. Also I did fastboot and everything from a second Android rooted phone. Only thing I couldn’t was mtkclient as the dependencies would fail to install in termux on that phone. I mentioned this in my long post
I understand it’s not relevant anymore, but I’m not at all convinced that it’s because the phone was missing the phone app.
It’s very probable that the phone was boot looping because there was an app in system and it didn’t have permissions XMLs.
I might be wrong, and both can cause boot loops.
I wonder - if he was trying to replace stock dialer or google dialer. Even if modded google dialer had different signature, the permission xmls would’ve been the same (or similarly unnecessary if they weren’t there). Guess it must’ve been stock?
We can ask him.
@flipphoneguy was the app you were replacing the same package name as the one you were replacing it with?
I’m not just asking for no reason, it’s something that I really want to know for the future.
Different package name