Database Info

FreedomPop Motorola Photon Q 4G LTE xt897c, want help with Cyanogenmod

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.

If you're getting a "select language" bootloop when installing Cyanogenmod 12.1

If you're getting a "select language" bootloop when installing Cyanogenmod 12.1
Hello everyone!
I'm opening this post because even though it does say so in the Wilson's ROM, there are suggestions to the contrary on other ROM threads. This might only be necessary for the 32gig version
I was desperately trying to get CM12.1 flashed onto my 32gig mi4i which comes stock with MIUI 5.9.15, and nothing was working. Wiped everything, formatted, tried different sets of GAPPS, tried different ROMS... no cigar. It would flash, optimize apps, reboot, go onto language selection screen, get stuck for a few seconds, and reboot. and reboot. and reboot. you get the idea.
You ABSOLUTELY need to flash MIUI 6.6.10 first. No other version of MIUI will work. I tried a couple of others first since 6.6.10 was taking forever to download to no avail. I put the patience in, downloaded 6.1.10, flashed the UBER ROM and voila! works first try.
I've only been toying with it for an hour or so but i'm really, REALLY loving it. I'm not a fan of MIUI but I could have gotten used to it, however the ****ty recent apps drawer and the useless lockscreen were deal-breakers for me. I'm a lot happier with my Mi4i purchase now!
Thanks a lot to everyone putting in the effort to port and compile these ROMs so noobs such as myself just have to hit a few buttons to get them working.

K I just saw this has already been posted. Please delete!

I wish i had the 32gb version, bought my mi 4i 3 weeks before it was announced.

m4gg0t said:
I wish i had the 32gb version, bought my mi 4i 3 weeks before it was announced.
Click to expand...
Click to collapse
I actually only bought the 32 gig variant because the 16gig was unavailable and i desperately needed a phone. I have a 20gig LTE data plan and stream most stuff...

I was also in the same spot. i ask if they had a 32gb version and they said no, only to release it a month later.

so after all what do u want to say in short amd simple language please
cos i have the same problem

Has Anyone Gotten a Custom ROM onto a BLN-L24 (US Variant)?

I have tried quite a few ROMs, and all ended up going back to stock firmware because they wouldn't boot. I know I have to format data, and some ROMs ask you to change the data partition as f2fs.
Still, I think that there may be no ROMs that currently work for the US variant. One guy said LOS 13 worked, but when I flashed it, it failed. If someone has gotten it to work, can you please post as many steps as you remember on how to get it work?

Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050

RedSkull23 said:
Debrand to BLN-L21 following this guide and you're ready to flash cooked ROMs https://forum.xda-developers.com/honor-6x/how-to/guide-successful-debranding-to-bln-t3701050
Click to expand...
Click to collapse
Thanks, but wouldn't there be more issues down the line with a debranded phone? What if I soft-bricked my phone, it seems like it'd be really hard to restore? Has anyone actually ever done this on a BLN-L24?

Hello all,
I too am having issues with flashing roms to this device, US variant (BLN-L24). In my particular case, the rom boots up (EliteRom v7.1) and will actually function. However, wifi does not work, as well as I have no sound whatsoever. Youtube also will not play, nor will any videos, which I'm guessing is tied to whatever issue is with the sound. I have flashed multiple times per the step by step instructions, as well as following the Youtube video, all with the same result over the last few days. At this point, my phone is effectively useless to me, though cellular data does still work, just no calls can be answered. Anyone have any suggestions I might be able to follow? Also, even my TWRP backup that I made before installing the rom will not restore at this point. Any help is appreciated, thanks.

Jessooca said:
You must be missing a step or something, because [Elite ROM][EMUI 5.1] Elite ROM v7.1 for Honor 6X by HassanMirza01 works on the L24 us variant without issues, I have none.
Perhaps go back to stock and start over. I haven't had any issues with his rom and I didn't do anything more than what's needed to root/install twrp and flash the rom per his instructions.
Click to expand...
Click to collapse
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop

i4ybrid said:
I just followed the instructions; I believe to the best I could, and I'm stuck in a bootloop now. Which version of EMUI were you on before flashing? I was on EMUI 5.0 which may be my issue.
I started from EMUI 5.0
Unlocked my bootloader
Let it factory reset
Installed the Elite TWRP on the page
Booted to Elite TWRP
Formatted all partitions excpet for external sd card
Reformatted Data to f2fs
Re-wiped data
Checked that it was f2fs
Installed Elite ROM zip
Installed open gapps 7.0 ARM64
Installed the patch
Rebooted
Bootloop
Click to expand...
Click to collapse
On one of the attempts that I did for installing, I installed the patch and it put me in a boot loop. Maybe not installing the patch can help you?

I cant get anything to work for the US version. Sure stuff boots but some of it is just broken. On octOS i am unable to use root unless i switch supersu to automatically grant root to apps. I cant get root access by using prompt because nothing pops up. On crdroid i have the same exact issue. Id rather have the prompt than allow any app root access without my knowledge. With ELITE ROM my first boot brings up a home screen with no keyboard. It completely skips any kind of setup screen. I can get the setup screen by flashing a keyboard from an aroma gapps installer but then i lose google services. The US version also seems to be forgotten as for most roms you wont see it anywhere under supported lists.

I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?

code_name_duchess said:
I've never been able to get a custom rom to work on my BLN-L24. Everything just ends in a never-ending bootloop of frustration.
Though, I have only ever tried with EMUI 5.0+. Maybe an earlier version of EMUI gets better results...?
Click to expand...
Click to collapse
It really sucks that nothing seems to work. Ive tried flashing using multiple recoveries and ive tried all kinds of flashing to fix issues with the ROMS. Nothing helps. If anyone has successfully gotten a ROM fully working on BLN-L24 they need to tell people exactly what they did step by step.

It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.

TurtlePwr82 said:
It seems that for the roms located here, they seem to all assume that the phone has been debranded to bln-l21 variant. I don't know if it has any bearing on the current issues we're all experiencing, but I did notice that all twrps available for this device on the forums state they are the "Open Kirin Edition". It's been a while since I've rooted or rom'd a phone besides this one, but I've never encountered a twrp with a custom name like that.
I know that the developer of the EliteRom had his custom twrp, but is there a different twrp besides that one that does not state it is an "Open Kirin Edition"? Like I said, not sure if it has any bearing on things here, but I've been very confused about that.
Click to expand...
Click to collapse
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing. Most recoverys say Open Kirin Edition when booting. What confuses me is why we need to debrand to get the ROMS to work. If the phone pretty much run on the same hardware then why is L24 having so many issues? Why are the devs not testing on these devices?

BakedOnSomeSour said:
For most phone i've ever owned you never had to change the recovery for each ROM. Its confusing
Click to expand...
Click to collapse
Right, that's what I was thinking. For any phone I've ever rom'd, there was always just one twrp that everyone worked from.
Edit: found this while looking through the roll back to stock forum. I don't know if it will help anyone else, but figured I'd put it here as well if it might. All credit for this goes to the original poster johnnyrichter:
johnnyrichter said:
Tried this method after being on LineageOS for a week or two and having poor LTE signal, no MMS, and voicemail issues so I'm trying to go back to stock so I can have a fully functional phone since I rely on it heavily for work. Followed all steps using BLN-L24 B360 firmware. On step 10 I rebooted to update and it went right to "5% Installing Update" and stuck there for 5 mins, then rebooted itself, has been sitting at "honor" boot screen for 14 minutes so I made it reboot to EMUI recovery, wiped/factory reset, rebooted, loaded EMUI afte 2 more minutes. Appears to have worked and hopefully my issues are fixed!
Edit: Signal, mms, and voicemail issues fixed.
Click to expand...
Click to collapse
Hopefully will benefit someone here as well.

When debranding the BLN-L24, and branding it to BLN-L21, are there any issues with the ROMs once they're installed? I imagine the radios, and such are different for the two models??

BakedOnSomeSour said:
Why are the devs not testing on these devices?
Click to expand...
Click to collapse
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?

galapagos said:
Devs can only test devices they have in possession. If they don't have your phone model, how are they going to test it?
Click to expand...
Click to collapse
well, many don't want to give them a phone because most developers here tend to stop work on a ROM and leave people hanging.

I have gotten several ROMs working on L24 variant...
Yes it seems to me any Elite kernel based ROM works or should work on the L24. But /data must be ext4 format. Then even that the ROM works, the fingerprint scanner never allows a complete successful scan. I think because it must be f2fs format for that encryption to work or something. This is the link to those ROMS https://hassanmirza01.blogspot.com/p/custom-roms.html?m=1
On the other hand the LOS based ROMs never work or at least they reboot and the screen is always black or the ROM branding just stays there flashing. This sucks cause I want to run the newest Resurrection ROM but I ask the developer about why I have that problem or how long that ROM takes to boot and I never get an answer. He also just put a new beta AOKP ROM up and it does the same black screen thing too.
I am also suspicious it has to do with the version of TWRP. I think some are capable of formatting f2fs correctly or the encryption or whatever. Point is some of the devs need to be a little more consistent answering questions at a minimum. I know it takes time to fix bugs but give us a little heads up.

Any problems with Magisk 20.2 update?

Is anyone having problems with the Magisk 20.2 update (stable channel)? I see reports of bootloops in the Magisk support thread, but none for Pixel phones. Many people do not mention what phone they have though.

Updated this morning. No problems.

qualitymove13 said:
Updated this morning. No problems.
Click to expand...
Click to collapse
Thanks. I bit the bullet and installed the update. The only problem I've detected so far, is Google Pay now detects a rooted phone. I haven't used it for a while, so that may not be the result of the update.
Looks like LG phones have the most problems with the update.

dcarvil said:
Thanks. I bit the bullet and installed the update. The only problem I've detected so far, is Google Pay now detects a rooted phone. I haven't used it for a while, so that may not be the result of the update.
Looks like LG phones have the most problems with the update.
Click to expand...
Click to collapse
I updated a Pixel 3XL and Pixel 3 to the newest canary as well as two Huawei Mate SEs and a Samsung S2 T713 on LineageOS 16. All were updated with direct install with no issues. I doubt the GPay issue is a result of the update since I have used it on both of my Pixels on canary (which likely would have impacted it already before stable yesterday). If you had never went through the "working: Google Pay" thread fixes in the Magisk sub-forum, you'll need to start there. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950

sliding_billy said:
I updated a Pixel 3XL and Pixel 3 to the newest canary as well as two Huawei Mate SEs and a Samsung S2 T713 on LineageOS 16. All were updated with direct install with no issues. I doubt the GPay issue is a result of the update since I have used it on both of my Pixels on canary (which likely would have impacted it already before stable yesterday). If you had never went through the "working: Google Pay" thread fixes in the Magisk sub-forum, you'll need to start there. https://forum.xda-developers.com/apps/magisk/magisk-google-pay-gms-17-1-22-pie-t3929950
Click to expand...
Click to collapse
Thanks. I looked at that thread, but I don't really need Google Pay, so will probably just delete it.

dcarvil said:
Thanks. I looked at that thread, but I don't really need Google Pay, so will probably just delete it.
Click to expand...
Click to collapse
The thread can certainly look daunting, but for the Pixel 3 or Pixel 3 XL (and in my case with the 3 XL various custom ROMs) it doen't have to go any further than the OP. No modules needed, and since everything is changed in user space it lives through updates. The only time I have had to touch it since making the changes the day day it was posted was the times I have had to do full wipes and start over with the OP.

OnePlus 7 Pro de-googled Custom ROM allow bootloader re-lock after flash

Hello,
Is there any OnePlus 7 Pro custom ROM with no GApps , and the bootloader can be re-locked after the ROM flashed?
Why re-lock the bootloader?
- I don't give a way phones, in case i lost the phone.​
Try LinageOS?
- I did, can't re-lock the bootloader, because they don't load the signing keys into the verified boot as GrapheneOS and CalyxOS do.​
If there's a ROM out there, please tell me where, if not, I'm sorry for any inconvenience.
Thank You

Did you find anything since this post? I've been playing with LOS 17.1 and 18.1 on my OP7Pro but can't get Safetynet to pass when I have Magisk on, and have issues trying to put TWRP on with LOS, as LOS hijacks the recovery. I'd like to get my banking apps and some other apps like Lyft to work without having google know my every keystroke and geolocation. I'm close with LOS 18.1, but am missing those 2 apps ability to work. I might try 17.1 again if that's going to make things easier.
From your post it looks like GrapheneOS and CalyxOS might be options. What's wrong with those OS? Will those not work with MicroG?

Lear31pilot said:
Did you find anything since this post? I've been playing with LOS 17.1 and 18.1 on my OP7Pro but can't get Safetynet to pass when I have Magisk on, and have issues trying to put TWRP on with LOS, as LOS hijacks the recovery. I'd like to get my banking apps and some other apps like Lyft to work without having google know my every keystroke and geolocation. I'm close with LOS 18.1, but am missing those 2 apps ability to work. I might try 17.1 again if that's going to make things easier.
From your post it looks like GrapheneOS and CalyxOS might be options. What's wrong with those OS? Will those not work with MicroG?
Click to expand...
Click to collapse
Hello,
First, Now I'm sure 100% that OnePlus 7 Pro is supporting verified boot and bootloader relock, but to achieve that, you have to load the signing public key used to sign the ROM during its build and it should be user build not debug mode build (ex. for debug mode build is the offecial LineageOS) to the phone verified boot partition.
I found this divestos [dot] org, but still not tested nor working on Oneplus 7 Pro. I tried but my phone never load the OS.
Now, I'm trying to go through the build steps from official LineageOS website to do my own build and do it user build, sure using my own signing keys, I hope it will work.
For GraphenOS and CalyxOS, unfortunately they work only with Google Pixel phones, ironic, isn't?, Lyft might work with you if you decided to go that way, because i tried Uber and it worked just fine with MicroG, but my banking app did not work, not because of microG or the OS, but because the app itself design to detect google play store and if you login or not, and if the app downloaded from the play store itself or not.
I hope my answer gave you some help.

ahmed.elsersi said:
Hello,
First, Now I'm sure 100% that OnePlus 7 Pro is supporting verified boot and bootloader relock, but to achieve that, you have to load the signing public key used to sign the ROM during its build and it should be user build not debug mode build (ex. for debug mode build is the offecial LineageOS) to the phone verified boot partition.
I found this divestos [dot] org, but still not tested nor working on Oneplus 7 Pro. I tried but my phone never load the OS.
Now, I'm trying to go through the build steps from official LineageOS website to do my own build and do it user build, sure using my own signing keys, I hope it will work.
For GraphenOS and CalyxOS, unfortunately they work only with Google Pixel phones, ironic, isn't?, Lyft might work with you if you decided to go that way, because i tried Uber and it worked just fine with MicroG, but my banking app did not work, not because of microG or the OS, but because the app itself design to detect google play store and if you login or not, and if the app downloaded from the play store itself or not.
I hope my answer gave you some help.
Click to expand...
Click to collapse
I actually took a senior member's' advice to just use Hydrogen (the Chinese (de-googled) version of Andriod) on my OP7Pro. So far it's working well and I just have to get things set up, but I'm rooted and Magisk works using the boot.img patch and hiding the app in settings. No need for Microg as it is a signed OS (or something like that). At the end of the day, I just needed something that worked right and didn't have big G tracking my moves. Some small tweaks and I'll at least have Hydrogen 10 working right. I might play with HOS11 after I get the backup functionality working correctly. I'm tired of downloading a ton of apps and getting all of my logins done and email accounts set up, only to make a tweak on the system and have to start over again.
Hope the custom LOS you're working on works for you. Thanks for getting back. This is a learning process for me. Take care.

Lear31pilot said:
I actually took a senior member's' advice to just use Hydrogen (the Chinese (de-googled) version of Andriod) on my OP7Pro. So far it's working well and I just have to get things set up, but I'm rooted and Magisk works using the boot.img patch and hiding the app in settings. No need for Microg as it is a signed OS (or something like that). At the end of the day, I just needed something that worked right and didn't have big G tracking my moves. Some small tweaks and I'll at least have Hydrogen 10 working right. I might play with HOS11 after I get the backup functionality working correctly. I'm tired of downloading a ton of apps and getting all of my logins done and email accounts set up, only to make a tweak on the system and have to start over again.
Hope the custom LOS you're working on works for you. Thanks for getting back. This is a learning process for me. Take care.
Click to expand...
Click to collapse
The same here, I hate this tracking and the feel that there is someone always looking over my shoulder .
Could you please tell me, where did you get HydrogenOS, I might give it a try.
Thank You, have a blessed life.

Best bet would be to run a debloat script. Universal Debloater (found here or on gitlab I believe) has the options for Google and OnePlus. Since you can use USB Debugging without unlocking bootloader, this might be the best option for you.
They will show the apps that are getting removed and a little description if you open up the list files in a text editor (notepad or whatever).

ahmed.elsersi said:
The same here, I hate this tracking and the feel that there is someone always looking over my shoulder .
Could you please tell me, where did you get HydrogenOS, I might give it a try.
Thank You, have a blessed life.
Click to expand...
Click to collapse
I just did an internet search (duckduckgo) and found a website with the complete zip file. Not sure if this is the one, but they offer the download for 10. (Mods can remove this link if I'm not allowed to share links with downloads) In any case, you can dig and find something if you chose to go this route. There are probably more HOS 11 downloads as of late since it's newer. I just wasn't able to get the Magisk app to work right on the 11 verison. That may have changed with the most recent update of Magisk. A de-bloat tool may work on OOS too. I just haven't tried it on OOS yet.
download HydrogenOS 10.0.10 Archives - RM Update News
Tech News
www.rmupdate.com