Hi xdadevelopers,
I ordered a Motorola Photon Q 4G LTE (xt897c) phone from FreedomPop for $25 and 28 days later it has arrived. My experience with FreedomPop has been decidedly mixed. Lots of hassle from customer service combined with a product that is sometimes very useful and always cheap. (Unless you use over 2GB of data per month) The phone itself seems very adequate for an excellent price. I would like your assistance in putting Cyanogenmod or another appropriate ROM on it.
Here's where I am,
The phone appears to have been rooted out of the box according to "Root Checker Basic" from Google Play
I installed "Superuser" from Google Play and that seems to work correctly
Busybox seems to be present already according to "Online Nandroid" from Google Play
I have created a TWRP Backup using Online Nandroid without modifying the recovery
The phone currently has Android 4.1.2
Where I want to be
I want to install a custom recovery, preferably one I can make backups from
I want to update to a more recent version of Android such as the stable one found here DUCK RULES cyanogenmod bot org /?device=xt897c or another version where everything just works
Notes. I have ADB and Fastboot installed from "Android Studio". I have an appropriate USB cable. I do not have a microsdhc card right now. It appears "Sandisk 64GB Extreme Micro SD (SDXC) Card + Adapter 60MB/s Class 10 U3 UHS-1" at DUCK RULES amazon bot com /gp/product/B00N98QLRQ is a good choice for a good price. I have this on order and should have it within the week.
I understand this phone has a locked bootloader. The "Messaging" app from FreedomPop available in Google Play seems to control messaging and the phone dialer. I went to the official Motorola Bootloader unlock page DUCK RULES motorola-global-portal bot custhelp bot com /cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-b I booted into recover with Power and volume up and volume down held, selected fastboot, connected to the computer , ran fastboot, as described, got the code, put the code in the webpage as described, and got a blank page. This happened 2x, with no emails form Motorola. I tried a third time 6 hours later, and it loaded a page with more instructions and I had the bootloader unlock code in my email instantly (There were no preceding messages, they didn't go to spam or somewhere else). I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Also thanks to the xdadevelopers community for your past and future efforts. I threw in my lot with Android when the neXus One launched after watching the keynote, buying it full price and paying extra for next day air shipping. I stayed stock despite the cool stuff being done by the development community until Google fell behind in updates. Then I started with CM6 and later went to CM7. That was wonderful software, thanks everyone who was involved in that. Unfortunately way late in the life of my phone I was homeless and got robbed for it. I got a used HTC HD7 Windows Phone for free from a friend. It was great for movies and music with a great screen and touch sensor but it was very early in the life of the new Windows Phone and there wasn't a lot of quality software being developed. That, and it just wasn't Android, and I longed for freedom. The integrated Web browser IE 9 variant sucked, and T-mobile denied me the final Windows Phone 7 update. The phone has gotten less and less useful as time went by though it always sucked for web browsing. This fall I got a One Plus One, it made a wonderful Wifi phablet, but when I tried to use it as a phone I found the radio was severely deficient in range, possibly due to defective manufacture as it got better range in colder weather. I had to initiate a chargeback with my credit card company to get support to talk to me and then ultimately get a refund. That's how I got where I am now and this is the first time I've needed to register for an account here. Thanks again xdadevelopers.
What is the best way to proceed? Semi detailed logical instructions please, as while I am intelligent and not a noob, I have been out of the game since CM7
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Holy wall of text. This seems to be the crux:
Aslan_ said:
I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Click to expand...
Click to collapse
Why would you flash something that is OBVIOUSLY not for your device!? I sincerely hope it did nothing because you could do some permanent damage to your device by flashing stuff that's not made for it.
Did you bother looking for any recovery threads? Say my TWRP thread?
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Flash it per my directions using fastboot in my TWRP thread.
Got it thanks, now which rom?
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post. I like apps, they make me feel like there's less risk in my actions, though after some poking around I see it's probably the opposite. People are doing so much more low level stuff in apps compared to CM7 it's amazing.
arrrghhh said:
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Click to expand...
Click to collapse
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
I'm always hated vague it's broken posts that don't adequately describe the problem, the hardware used and the environment, so I head in the opposite direction with mine.
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Aslan_ said:
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post.
Click to expand...
Click to collapse
I no longer use this as my primary device, so my threads are basically stagnant. fastboot always works, where apps come and go... I'll try to find some time to adjust the post.
Aslan_ said:
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
Click to expand...
Click to collapse
Reason for stopping at 2.7.1.2 was they implemented MTP in 2.8.x, and I could never get it working right for both Win & Lin. I spose my bar was too high and I should've just released it, but I hate releasing half working stuff. It was a new feature that didn't work right.
Again, this is no longer my primary device so I'm not working on it very much at all. I have to pry the thing from my roommate's hands to even play with it, I haven't flashed CM12 yet (because it's no longer my device really).
I'd like to update the official TWRP, but in the meantime the CM maintainer has taken care of updating it so F2FS can be utilized.
Aslan_ said:
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Click to expand...
Click to collapse
Well obviously some of that does go down to choice - if you want CM, it is a little confusing. The device started out in CM10 as its own device, xt897 for GSM xt897c for CDMA. Then in CM11 they merged the devices into moto_msm8960. Of course they had to split again when the new bootloaders were released for the other moto_msm8960's (Razr HD, Atrix HD, etc) and moto_msm8960_jbbl was kind of a stopgap device at the end of CM11. Again, reading is your friend here although I realize all of that history is hard to glean. At least read the OP of the CM thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
Good luck. The device is now semi-unified (GSM & CDMA), as xt897.
Aslan_ said:
[*]I have created a TWRP Backup using Online Nandroid without modifying the recovery
Click to expand...
Click to collapse
Would you mind terribly to share this? My device shipped with a Sprint branded ROM and I'd like a proper backup.
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
turbozapekanka said:
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
Click to expand...
Click to collapse
You don't update PRL/Profile in CM, you do that on the stock ROM. Make sure EVERYTHING works on stock before flashing CM.
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Correct.
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Can you share this "another APN fix"?
already shared here http://forum.xda-developers.com/showpost.php?p=60153295&postcount=18
Anyone still have issues? I was running a June Nightly and it was working somewhat. It would randomly lose connection and I would have to flash the APN.zip. It happened again a few days ago and I decided to go up to 722 Nightly and now I haven't been able to connect. When I go to APNs the list is empty and even if I manually add one it does not seem to stick. The APN zip doesn't help either. The phone is connected but shows an exclamation mark next to the signal and I have no data.
Sort of solved my own problem
Flashed back to stock Spring using RSD lite and a modified XML that didn't flash the system.img since it kept giving me errors. Found a stock TWRP dump on the forums and flashed that. Updated PRL and Profile, reflahsed back to CM11 Snapshot and flashed the 2015 FreedomPOP APN fix. Working for 1 day now.
I'm fairly new at using custom ROMs on my phone (Moto G 2013 XT1304) and I want to get some answers that I've not been able to find, at least clearly, on my own. I'll ask all in one go in case others might benefit. I appreciate any help or confirmation in response.
GAPPS
Following the guide on xda, I installed CM 12.1 successfully and also installed the gapps package from July located in the cgapps site (can't post links yet). I was confused about the other option being called "OpenGApps" and thought they were the ASOP vs Google version. Once booted, Google Play Services updated but I've still had a few "Google Plays Services has stopped working" issues. My question is this, should I reflash and use the latest nano install from OpenGApps or does the play store update these relevant apps and framework once up and running anyway? Which is best?
Nandroid Backups
I want a way to fully backup the entire phone and system so that I can fully restore if something should get botched - something like a full drive image on a computer. Using TWRP backup, if I were to backup the system, data and boot partitions, would restoring those to a completely wiped phone bring it back to the state it was in when backed up? And do those partitions need to be wiped before restore or does the restore process do that anyway? Last, is is this the best way to do this sort of backup?
ROM updates
First, if "Check for Cyanogenmod updates" is set on the phone, and I have a snapshot installed, will this only provide an update if another snapshot is released? If not, how does that work since there is a new nightly releases every day.
Second, I've read a lot of negative about downgrading ROMs, but it seems ok to flash a newer version of the same one while keeping the data in place. Is this correct? Is there a "best practices" post on this somewhere?
I'm experienced with Linux, and feel somewhat at home with Android because of that, but I only switched to CM12.1 recently because Motorola had done nothing about the choppy bluetooth audio in the Lollipop update for the Moto G 2013. I use the feature extensively and it was left too broken to enjoy, but works perfectly in the CM ROM. Now I'm hooked and want to go further. Thanks for any help or direction.
Moto G 16MB (2013)
CyanogenMod 12.1 (Snapshot 11/17)
TWRP 2.8.7.0 (h2064)
Disclaimer: I know this could be a bit OT here, but these experiences could help my Z friends to avoid to brick their phones... so MODs, be patient... and read!
Yesterday afternoon I made my first "soft brick" of my "long" career... on an Oukitel C4!
(...*great* phone for the price! )
I after fixed it in less than an hour (including download time... ), BUT the interesting is *how* this happened.
I haven't done anything wrong BUT trust my TWRP... or, better, my twrp...
When I first time tested my new Moto Z I liked a lot the TWRP officially realized for it... now I'll explain better why.
There are some wide spreaded statements about TWRP (and recovery in general...):
- TWRP/recovery is not involved with normal system booting (e.g.: a not working one for-whatever-reason can't interfere with standard system boot);
- Kernel (boot.img) & system are not involved with TWRP (e.g.: you can even have formatted boot/system partitions and you can still boot to TWRP;
- boot.img & recovery.img are two partition where boot from in indipendent way. Normally of the same size. In some emergency cases, it is even possible to (with intention...) flash a recovery on boot.img to try to fix some soft bricks...
- more...
All these statement are often true *but* not ever, as I teach myself... the hard way! :silly:
If I should base my knowledge on what I've directly experienced on some LG (p880, d802...), Sony (X10 mini, Xperia U) and, *probably* on Moto Z, I will say they are right. Ever.
BUT then I've had some opposite experiences with other devices that I'll list with no comment for now:
- Samsung Galaxy Tab 10.1 3G: CWM recovery "hardly flicker" with some ROM versions become unusable. Fixed with successive update anyway...
- Samsung Galaxy Tab S 10.1 4G: both stock & TWRP recovery suffer of "black screen bug until timeout" only with Lollipop+ installed ROMs...
- Oneplus X: first version of TWRP available is able to boot and/or can be flashed only to phones with Lollipop until a xx release. After that release a new TWRP version is mandatory, otherwise it doesn't boot (and will be substituted by stock one if just flashed at first system boot) and system is booted instead...
- and now yesterday, Oukitel C4: double!
1. flashing TWRP interferes with normal system boot, giving a continuous bootloop. Only way to fix it is by flashing SuperSU, then the system boots up fine again!
This weird behaviour is reported/confirmed on a thread on 4pda forum too (if you know russian... )
2. flashing Magisk v.9 (that, as developer says "it modifies only boot.img"...) produces a bootloop too (different from the above). Ok, this can happens...
No problem I said "...I've my stock TWRP full backup just in case... ". Yes.... problem is that this time bootloop affects TWRP too!
Only way to fix: flash again stock boot.img by PC... (recovery don't even needed..!)
This last one is the one which worried me most, since this could be happen on Moto Z too, during my "hacking experiences"...
How all this could happen?
I don't know for sure... but I've some theories...
One is that while some TWRPs are developed to be "fully indipendent" from boot/system firmware (LG d802, Moto Z??) other (let's call them twrps...) are developed not only "based" on a specific system software version (and this is often "declared" too, but it wouldn't be a problem...) but probably "call" some boot.img parts too, becoming "system (kernel) dependent" to work...
My knowledge is not so deep to give a "certain" answer (and if somebody with the needed knowledge wants to correct me/explaim better is the welcome!), BUT on the meanwhile, try to use needed cautions... :fingers-crossed:
@erfanoabdi, @janjan, any thoughts on this?
I know what you meant. In my moto X I flashed a boot of a Chinese version that was completely incompatible with the American model. And I have to wait until the boot of the Moto X pure version was updated. I think that the problem is when you mess with a "newer" bootloader that makes the system incompatible with older versions. In my experience by itself the TWRP doesn't mess with the boot unless you request it.
That's the reason when you make a full backup you include boot and system, to avoid incompatible things.
What are your thoughts?
Sent from my XT1650 using XDA-Developers mobile app
juliospinoza said:
I know what you meant. In my moto X I flashed a boot of a Chinese version that was completely incompatible with the American model. And I have to wait until the boot of the Moto X pure version was updated. I think that the problem is when you mess with a "newer" bootloader that makes the system incompatible with older versions. In my experience by itself the TWRP doesn't mess with the boot unless you request it.
That's the reason when you make a full backup you include boot and system, to avoid incompatible things.
What are your thoughts?
Click to expand...
Click to collapse
This (probably true anyway...), would explain only a minimal part of the above issues...
Even I, in my "previous experiences", would have said for sure that "twrp doesn't mess with boot" too, BUT after what happened on C4 to me (AND confirmed on 4pda by another user too!), this is not true anymore too.
After a single TWRP flash C4 goes to bootloop on normal boot and only flashing SuperSU is able to fix it (how is still a mistery!). So recovery and boot are connected and not indipendent.
More, bootloop created by Magisk (that by what developer says, it touches only boot.img), affected TWRP too and remains even after reflashing it! Only a flash of boot.img is able to fix it!
So, again, recovery and boot are (both ways...) connected and not indipendent.
At least on that device/recovery combination...
On Moto Z I don't know, but some bricks occurred on Nougat are a bit suspect in that way too...
Just found that on C4 SuperSU v.2.78 installs in systemless (on boot.img) mode...
So, what flashing TWRP apparently breaks, SuperSU is then able to fix...
Definitely they are connected on (at least...) that device!
Strange is that SuperSU fixes it and instead Magisk breaks it totally (neither TWRP is still able to boot after flashing it!!)
Quite the opposite than on Moto Z where Magisk seems to have "good influence" even on SuperSU (in system mode!) installation too
tl;dr - TWRP touch screen won't work after installing custom ROM, much hassle to unbrick, looking for a "bumped" (still not actually sure what that term means) or otherwise modified version of TWRP that won't go haywire when installing a custom ROM.
tl;dr 2 - Also interested in the LATEST "stock-based" ROM recommendations anyone may have... G3 backports or whatever. She needs her Camera to work well but older 4.4.x and 5.0.x OS is missing a lot of new functionality and compatibility with new apps.
I'll just start out by saying that I've figured out just about every way to brick and subsequently un-brick this device that is feasibly possible, and am considering starting a thread specific to those various methods... but that's not what this is for.
This is an issue I've encountered a few times now, definitely on my girlfriend's T-Mobile LG G2 D801 with Lollipop (30B and now again on D801 30C), and iirc, also on KitKat.
I'll explain what I can remember, most of this has been done in the middle of the night after many frustrating hours of attempting various methods... I have to say, this phone has been much more difficult to mod compared to my previous experiences with Samsung and Nexus devices.
I had gotten this device all the way through to CM12 or 13 a year or so ago but recent issues made us decide to attempt to revert back to a Stock-based ROM.
Steps:
1. Root (ioroot / Autorec, can't remember which or for what reason, I have multiple versions of each)
2. Install TWRP Custom Recovery (most recently and successfully using a modified version of the "30B Freedom Tool", although I haven't tried that on 30C - yet.
3. Transfer custom ROM & Kernel to SDCard.
4. Boot into TWRP and install custom ROM & Kernel - most recently GoogleEdition 1.5 and then DorimanX 12.0 Kernel
5. Clear Cache / DALVIK Cache.
6. Reboot device. This is where the trouble begins...
Results: Won't boot into OS at all, instead I end up at the text-based "fastboot" screen, which after multiple tries I can eventually get back into TWRP or into Download Mode.
Once in TWRP after installing custom ROM, the bottom ~1" of the screen won't respond and all other touches aren't accurate... playing with it, I can usually eventually get into some of the TWRP screens, but for most purposes it's about useless.
I managed to restore a backup of the original 30B system image via command line over MTP using ADP TWRP commands, but that bricked the phone in an entirely separate manner where I couldn't access Recovery anymore and the system wouldn't boot at all... I ended up using the LG Update tool to get it up to 30C, and was surprised to find that it still had the restored backup data (apps, pictures, settings, etc), and the phone is now working again, albeit back to stock recovery.
Now, as I mentioned, this isn't the first time I've run into this "phantom touch" issue in TWRP on this device, although the circumstances seem to be a little backwards this time vs when I was taking the device over to CM12/13. I think I remember something about a "bumped" or otherwise modified version of TWRP being out there, but I can't find it now or put my finger on what the changes were.
Has anyone else run into this? I am hoping I've just overlooked something, but days of digging through threads hasn't turned up much.
/edit/ To give you an idea, attached is the folder I've got files stored in... with tons more in Archive and Stock-Based... I've used them ALL at some point. I'd like to get enough info in here to write a Step by Step guide for new owners who are picking these devices up on the cheap, and would appreciate if anyone wants to help out with this!
And by debloated I mean Google too. I prefer zero crap on the phone but baked in"features"aren't bloat hahhaahaha. I've gotta run microg that's what I bought it for lol. Prefer toot so I can do what I want.
Well since no one knows, has tried all three, or is afraid to offend sunshine, I'll chime in myself.
The Omnirom build is very good and let's me do everything I need but not everything I want. I've read that it's better than using a GSI (generic system image - I think). Omni has been very stable to be as old as it is. I was able to remove the gapps and install microg.
Microg won't install in twrp, and won't work in magisk unless you make 100% sure Google play services are gone.
An easy way to check if things are on the right track with microg is to look in settings under system, if it shows up at the near the bottom it's going to work.
I was unable to get microg working with stock but I think I could now.
With big red ( Verizon) wifi calling is available on stock but not in omni. This is expected as I've never had to work on anything other than a stock rom in the past. So if you're at the edge of signal coverage or like I am at the edge and about the same distance between 2 towers in two states with different service in both lol, you might want to keep stock if you need that feature. If not I'd say Omni all the way.
Perhaps I'll add to this as time goes on.
If you are just starting out tahr note that fastbootd isn't the bootloader, and use the latest adb and fastboot from Google, even on Linux I downloaded the most recent to be sure but that's up to you.
The Lenovo Recover works great but fastbootd works well for fixing small blunders too.
Fastbootd says Fastboot in huge letters at the top you can't miss it. Hahaha
One thing I find peculiar is that I was able to use the Fastboot command in the bootloader mode to install twrp. This gave me a false sense of hope.
And I falsely assumed I was in Fastbootd. Fastboot has been around for years I just never used it. I think it was around in the Droidx days but I could be mistaken.
Good luck!
We are very fortunate to have vache and other devs working on these devices. As well as users who can test and stuff.
Another user asked this previously without any response ... Could you post a degoogled Omni ROM without gapps? Or give any advice how to remove it ? You were the one to put it all together so surely for you it must be easy removing it? As for me, I've been stuck.
Sorry i never saw this until now but I'm not a developer just a microg and self-hosted nextcloud user.