Search results

My tablet was completely wiped with no OS so I just pushed the ROM, pico gapps, and magisk over USB onto internal storage with MTP/TWRP. Flashed it all from there and it worked fine. No issues or errors. I don't think it's at all necessary to sideload to use an external SD.

Thanks for setting up a distinct thread. Things were getting confusing!

Pardon my ignorance, but will these 16.0 builds not work on a pre K1 tablet? All are erroring out for me in TWRP with Status 7. I had always assumed the K1 rebrand was just a marketing thing and that the internals were the same. If so, does anyone have a later 15.1 build? The yellowstone rep...

Is there a fix for the messed up strings in settings? It's been this way for me for the last few updates but it's starting to get annoying

dirty flashed fine for me

I picked this up on an OB some time ago but didn't pay it much mind. Must have grabbed a zip on here that had it. It hung around through several OB and stable OTA updates. Good to know it can be removed.

Gmail was quitting (not FC), but an app cache clear fixed it.

Seems that doesn't mean anything. I just did System Update -> Local Update, TWRP A/B retention, Magisk to inactive. No wipe. I'd imagine the TWRP process would work fine too.

Via local upgrade or TWRP? Local upgrade warns of factory reset.

Triodexe the modified dtb is optional though right? The OP, before you edited it, kind of made it seem compulsory. At least that's how I read it, but I didn't have any issues. Some might be willing to forego the chance of working QC to avoid headaches.

Great build! I haven't been on an LOS build for a tablet that's run this smooth.

QOTD right here

When you look at your strava map, are there straight segments away and back from your actual track? Mine has done this since I started using strava about a year ago. I believe the phone is losing GPS signal, and the location services are falling back to wifi location, since these 'spurs' always...

What exactly is: Fixed and removed white bar below the keyboard? All I get now in the blank space below the keyboard is a hide arrow. There's still a huge gap (black since I'm on dark theme). Also using gboard.

Didn't bootloop, but setting is broken and no calculator. Steps below fixed everything. just FYI, vanilla TWRP 3.3.1-11 threw an error 7 when attempting to flash OB5. Had to use mauronofrio 3.3.1-18.

magisk too?

Solid Explorer

Flash SafetyPatch in magisk (in the repo). Reboot. Profit.

I'm on the "official" OTA (arrived a few days ago) and just lost ctsProfile (GPay contactless and Play Store uncertified). Magisk Hide alone did not work, but along with Safety Patch it did.

It just appeared OTA for me. Edit: OTA + TWRP retention + magisk 20.3 to inactive worked fine. No complaints from Gpay or Play Store so far.

Did this get pulled back from OTA? I'm still showing up to date on OB32. Not interested in updating via other methods.

were you having any other problems on OB4 while unlocked and magiscked? Play Store works ok and all that?

OnePlus 6 and not 7T. Is what it is.

In terminal or adb run su wm overscan 0,0,0,-130 This is not an actual fix however. It does move the keyboard down (adjust the -130 to you preference), however it also moves toast notifications off screen and can cause issues with some other apps. To me it's worth the tradeoff. Revert with wm...

Should have flashed the A/B TWRP retention script. Bet that'll be the last time you don't.

+1 for the lazy!

Works fine here

OnePlus Roaming (data-only esim) is still there on mine. Have not tested its functionality, but the option is there and I see the rates for different countries.

Google pay working here. My other banking apps aren't strict with root or unlocked bootloaders.

I believe 0,0,0,0 will revert your changes.

Q B1 -> B2 will be no different than Pie OB's. There was never a problem with the OB themselves, it was with magisk. Download/Install OTA Flash Magisk A/B retention script Install Magisk to inactive slot Reboot --or-- Download full OTA zip Reboot Recovery Flash OTA zip Flash TWRP installer...

Yes. It will complain as usual about you being rooted but the full OTA will download and install to the inactive slot. Before you reboot, you will need to use the magisk TWRP A/B retention script module and install magisk to the inactive slot in order to keep both. The A/B retention module does...

from adb or terminal (run su first) wm overscan 0,0,0,-130 Play with the last value to your preferences. -130 puts gboard right at the bottom without clipping anything.

Future OB updates will work the same way as before now that magisk has been patched. You can do an OTA update and use the A/B retention script + install to inactive slot too if you prefer. Never been on stable so never flashed between stable and OB. YMMV there.

You were able to confirm the A/B retention script module works on Q? Can't see why it wouldn't, but what do I know?

If you have an unlocked bootloader you'll need magisk. At least for Netflix. Can't speak to Disney.

I don't use any modules and lost orientation and ambient sensors when rooting. They came back after a factory reset.

I ended up having to do a factory reset, and then I was apprehensive about rooting again but once I remembered what life was like without adblock I rooted again and was fine. Some people have reported they start working after a few reboots.

If you already have 19.4+ TWRP you can direct install 20.1 from magisk manager. It may also "bring back" TWRP if you were running 20.0 but I can't say for sure. OOS updates going forward should be no different from pie. Either flash ROM in TWRP, then TWRP installer, reboot to recovery, then...

Wouldn't work for me either. AT&T.

Works fine here, but my head unit gave me some grief about the BT pairing. Once I clicked through the AA setup, it was able to reestablished the BT connection. Some head units can be funky with this, so I would suggest removing your device from the unit before reconnecting AA. FYI - my head...

No luck here. Tried two reboots to recovery + system reboots. And two full power offs. Oh well.

what's the fix?

Anecdotally - I didn't have the issue (after a reboot after upgrade) when unrooted. After root (magisk 19.4) and TWRP, I now have the sensor issues.

I haven't bothered looking in to it much, since the effect is rather minor for me. I do however remember this being an issue on an old CM/LOS build years ago, and I was never able to find a fix. I suppose hardcoding a MAC address or something to that effect is common when testing new versions...

My MAC appears to have changed as well. My ISP wide area WiFi did not recognize me after the update.

Heads up, I followed that procedure and lost proximity and ambient light sensors. They worked on stock after a reboot. Everything else works as expected.

Sorry for this low effort post, but I've been out of the country without internet for a few days and digesting all this has been difficult. If I'm on OB25 + magisk 19.4 + TWRP, can I safely perform a local (no TWRP, no fasboot) upgrade for stock Q OB1? I'll want magisk later (TWRP can wait, but...

Just to throw this out there, if anyone is able to build a booting LOS16, I can host.

Are 16.0 builds available anywhere?