Jump to content

d

Members
  • Content Count

    17
  • Joined

  • Last visited

Community Reputation

16 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Do you have any idea why aptx does not seem to be working on the stock rom? Thanks!
  2. Yeah, I definitely need to do that next time. edit: I messed up and had to do a factory reset.
  3. Magisk does not modify any system files, but adaway modifies a hosts file, so the integrity checks fail. At least that's how I understand it. I'll be restoring the factory rom and then installing the OTA updates to slot a.
  4. Ah, damn. While reading your link I remembered that I've used Adaway and thus modified a system file. That is probably why the OTA fails. Thank you!
  5. The same thing happens. I just tried restoring the backup from slot b to slot a, but it didn't change anything.
  6. A few days ago, I flashed a patched boot image to boot_a. I used the image from here and patched it with the Magisk app. It worked wonderfully, I had root and the phone would pass safety net checks. After flashing the patched boot image, I backed up boot_b. Today I got the OTA notification and switched to slot b using fastboot --set-active=b and then rebooted and tried installing the OTA, I got the following error message: Install fail Reason: 20 Magisk is not active on slot b, so why can't I install the update?
  7. This has happened to me exactly once now. It happened before the OTA and has not happened again, but I don't think the OTA has anything to do with it. I am using Swiftkey for portrait mode, but it also interferes with hw keyboard settings. Maybe it has something to do with it, but I don't think so.
  8. I've installed the update, but the phone still doesn't pass safety net checks. I'm assuming we're still waiting for google certification to come through?
  9. I've gotten my Pro1 seven days ago. My sn is fxtec000098. The one on ebay has sn xxx2, so there probably were about 100 devices sent out.
  10. Nokia 3310 → Some Siemens phones → Benq-Siemens EL71 → Motorola Milestone → Motorola Defy → HTC One X → Samsung Galaxy S4 → LG G3 → Moto Z2 Play → F(x)tec Pro1
  11. There currently no OTA updates available, it was the first thing I checked. Guess we'll have to wait for that first update. I think this is a software fix.
  12. Well, it can support Google Pay, it just fails Google Pay Security Checks at the moment. This can be circumvented with Magisk Root, but I don't want to use it, unless I have to. It's a pain in the ass to have to constantly keep Magisk up to date, to be able to keep using Google Pay.
  13. I just got my pro1 and it's pretty great so far. Google Pay says that this device is not supported. Will this be fixed or should I just flash Magisk?
×
×
  • Create New...

Important Information

Terms