Search results

I'm on SM-G981U1 and would be happy to side-load the update if that were possible.

I'm having an issue with Android Setup crashing continuously with OpenGapps Micro. Can anyone help me fix this?

Good afternoon, I can confirm that VoLTE is the problem. Mine is a clean install coming from data wiped factory stock following the install process on page 1 of this thread. Turning off VoLTE immediately resolved the issue with outbound SMS messages - and turning it back on immediately caused...

Do you think that they'll issue an update fixing VOLTE? Is there a way to tell the devs?

Thanks! I'll give this a try. Yes, Mint Mobile is an MVNO for T-Mobile.

I have Mint Mobile. I edited the APN data to what's on Mint Mobile's website but nothing changed. Very frustrating. Any other ideas? It appears to occur with both Google SMS and Pulse SMS.

I'm having an issue with Quartz 5 where I can't sent SMS messages - but can receive them. I can make and receive calls. I just can't send outbound SMS messages. I never had this problem on Quartz 4 and the SIM works fine in my other phone when I put it in there.

Has anyone had problems with Bluetooth Has Stopped Working continuously?

Does the OTA feature (if there is one) work with this ROM?

That's disappointing!

Will there be a Sept/October update for this ROM? It's by far my favorite!

I somehow accidentally turned my USA 1905 into the India version (has Indian features, Cloud storage) - but I need to return it to US Stock for return to OPO. Can I do that using the tools here, or do I need MSMtools?

So I should flash the vendor image to both slots, boot TWRP, flash TWRP installer, reboot to TWRP, wipe everything, flash this, flash the installer, and reboot? Do I need to reflash the TWRP installer after each update? What if I want Magisk?

Supposedly this is official now, no longer in Beta. Does that mean OTA works now, and if so how do I enable that and what recovery do I need?

As someone who took the plunge I used Freja to download the firmware and then flashed CSC_home to keep my apps and data. Netflix works, Google Store works. Everything appears to work fine. Your mileage may vary.

Will using the DBT version break Knox / CTS / Safetynet? I can come back to XAR like I never left later, right? I'm bootloader locked, etc.

Can I flash this on my USA wifi model?

I have a USA 860. What about us?

Good afternoon, Is it possible ro relock my bootloader with an ULM model? I basically need to go back to complete stock for OEM repair.

Using the smart battery feature causes the ROM to soft-reboot when toggled to on.

Wifi has always worked for me out of the box and was used in the initial setup process. I strongly suspect that it has to do with radios or bootloader or some partition from Q that includes things you need and don't have because you were on the P firmware. Try flashing January's Q update...

Actually I found that the module fixed it prior to the update to 20.4, broke it when used with 20.4, and upon uninstalling it from 20.4, CTS and safetynet now pass. I'm not sure why this is the case, but it may have to do with using Magisk Manager's rename feature.

I used flashall.bat to go onto Jan. Q build, then fastboot flash boot into TWRP on the opposite partition to the main one (I'm using an older TWRP rooted boot.img file for which I can take absolutely no credit but will attach upon request - touch works on this one in full), booted to slot B w/...

How do you get Magisk with this? Just flash it normally?

I got out of 9008 mode. I had to completely re-write the partitions using qfil. Now I'm on 20e and Pie, but my IMEI reads 0. Drat. Apparently it's forbidden to discuss it - so.... guess I'm out of luck.

I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't get into fastboot to install TWRP and Lineage OS, so I ended up trying to erase laf_a and laf_b like it says to do in the V40 Qfil guide. Big mistake. Qfil and windows both recognize it as a 9008 device on Com3, but can't access...

I'm having a similar problem, but in my case I managed to accidentally erase laf_b from QFIL and this has corrupted my GPT. Now the QFIL partitioner can't see my partitions. Can you help? I may need a flat pack or something? I'm stuck in 9008 mode. The bootloader was unlocked but I couldn't...

I'm having connectivity health services crash every time I boot. The phone works, everything appears to work normally. I just figured I'd mention it.

I can confirm that this works with the official Q release and 19304 Magisk (the one Banks told us to use). Thanks!

Mine was originally a Sprint device that's now carrier unlocked. Could it be that there's something different between my device and a fully unlocked one on which this might work?

What did you do to get it working? I tried installing it as a module through Magisk and couldn't boot after that.

I think this is probably my favorite of all the ROMs you've sent us. Do you have a Patreon or something, followmsi?

Sorry for the thread necro. I'm on AICP Pie and when I go into the play store for D3 BFG edition it says 'your device is not compatible' even though we've got an X1 chipset. What gives?

I'm running into some of the same issues as the other Pie threads: Lockscreen issues. What worked for me was going into TWRP --> File Manager --> data --> system and deleting the lockscreen file, then booting back up, going into settings -after- initial setup and creating my pin/pattern there...

Are all of the things in the OP still issues? Encryption, etc?

I currently have both light and dark legacy versions of your themes. Since I have the Project Fi version with Google apps for phone and messages am I missing anything by not moving to the substratum version? I do notice that some notifications don't get rounded off correctly but I'm assuming...

Mounted System in TWRP, navigated to each file that I moved from the posted zip, applied chmod-755 successfully, no change, no status bar, no nav-bar. I'm not sure what sorcery the person who got this to work did - but I'm jealous!

I replaced the SystemUI files in TWRP but when I boot I'm missing.... the system ui, no navbar or status bar. I'm sure I deleted the original 3 files then moved the provided 3 into the right spot.

I'm using the new version of Pie, and while it's overall excellent, I am having an issue where the Pixel 3 launcher becomes unresponsive, leaving me with no way to change apps or launch them (I have to restart the phone). I am using gesture navigation but have not otherwise made substantial...

Someone else probably already mentioned this, but the pull down for quick actions / the notification shade looks really strange. Specifically the icons for the quick actions go outside the menu borders and the notifications shade appears in the center even if I'm pulling down quick actions from...

I also have this issue.

I can't seem to get past the Lineage OS boot screen after installing the newest build for April. I'm fully updated, flashed the stock image entirely, then installed TWRP and followed your instructions. I'm not sure what I'm doing wrong. Do I just need to let it sit for more than half an hour...

I'm taking that to mean that the Pixel / XL DO, and that's why they're currently unsupported - but that my Pixel C should work fine. Correct? Sent from my Pixel C using Tapatalk

I know that Pixel / Pixel XL are unsupported at this time. Should I take that to mean that it also won't work on the Pixel C tablet? Sent from my Pixel C using Tapatalk

I remember reading in the OP that Pixel/Pixel XL aren't yet supported. How about the Pixel C (dragon) tablet?

I have an HP Spectre x2 M3, and (nearly) everything works. I'm getting errors connecting to the camera, which is an issue. More relevant to daily use is the fact that while it detects the keyboard and touchpad (and touch) just fine, it does -not- recognize when the detachable keyboard is...

I installed TWRP successfully, but because I'm an idiot, I didn't decrypt my internal storage first. This has put me in a situation where TWRP cannot access or mount internal storage, and the tablet won't boot to OS so I can decrypt it from the GUI. Can someone suggest something please? Thanks!

Mine also doesn't work.

Neither my G-tube nor Moto Buds (1st gen) show up when searching for bluetooth devices. It also failed to find my Moga Power Pro when it was in the A mode, but had no problem finding it when in the B, HID mode.

Thank you so much for your hard work! What are the odds of getting bluetooth speakers to work with this? My Nexus Player is hooked up to my monitor which has no sound output. You used to be able to use ES File Explorer to identify the speaker, and after that audio routed through it, but this...