Search results

On my PH-1 with Q beta 3 Keep Notes was yesterday updated to version 5.19.191.07.40. Still white Does anyone have Keep with a dark mode

It's possible root is messed up because of a previous version When root is there and not working properly, there's a solution by flashing Magisk zip again in TWRP. You could try the latest canary build https://github.com/ianmacd/MagiskBuilds/raw/master/Magisk-v19.3-2019052002-ianmacd.zip

When you have 058 working without root, then one of patched images in post #2373 will give root access. https://forum.xda-developers.com/showthread.php?p=79477775

When you have a working ph-1 with stock boot, you only have to flash Magisk version 19.x EDIT What version of Android is now active?

You need to flash patched boot images to the active slot and make sure the version matches the unpatched boot images.

It's about 'when' the N6 is unencrypted. To get Nitrogen working the phone needs to be unencrypted. So completely wiped and formatted. I think the N6 was already wiped, before you received the OTA.

When a previous rom wasn't Nitrogen, it's possible the data was still encrypted. Maybe poster doesn't remember...etc

My versions: EX kernel 4.00, EX manager 5.01 Magisk 19.2 canary, Magisk manager 7.1.2 EDIT Last 3 days... Every day once dead buttons. Needs a soft reboot. EDIT2 1 day without issues; no dead buttons. Q beta 3 - daily driver EDIT3 clsA Again after a day normal use dead icon-buttons; not all...

I mentioned modules, but it has to do with software/apps that needs root.

TWRP 3.3.0.0 TWRP 3.3.0.0. flashed to recovery and working on my N6. EU link for latest TWRP https://eu.dl.twrp.me/shamu/twrp-3.3.0-0-shamu.img.html US link https://dl.twrp.me/shamu/twrp-3.3.0-0-shamu.img.html

Same here. Could be solved with a reboot. But after removing all modules in Magisk no dead buttons since 1 day....

You already got response about the Sprint issues. But I'm interested in your fine Wifi in Q beta 3. I noticed that Wifi won't connect when Wifi scanning is off. On my PH-1 I need to switch Wifi to automatically turn on (WiFi scanning turned on). I'm curious if your WiFi will work when Wifi...

Good to know. But wifi in Q beta is not 100% reliable on my ph-1. Auto connect is not always working. EDIT Removed Magisk modules for Fonts and systemless theme overlays.

Remove stuff with root access; theming apps and modules in magisk

Theming apps that needed root access, caused Issues when I tried Q beta 3. Uninstalled those apps and tried again. I want to keep my data and settings. In my view all apps that need root access may cause issues. Combined boot image with the canary version of the EX kernel 4.00...

Below two patched boot images that I used when trying Android Q beta 3 for the PH-1. First trials were not quite succesfull; see previous posts. Issues with the data partition were solved by uninstalling theming apps that needed root access. (Swift overlay installer). Another issue was about...

Did you wipe the data partition for Q beta3? I didn't and Wifi couldn't set to ON when rooted.

https://www.androidfilehost.com/?fid=1395089523397963832 This is the 4.4.179 q beta3 boot.img patched with Magisk 19.2 It worked on my PH-1 but with issues, because I did not wipe the data partition (factory reset) When rooted Wifi could not be swithed to on. Without root the Wifi is working as...

A patched 4.4.179 Q-boot image with only Magisk 19.2 worked on Q beta3. WiFi couldn't switched on. When TWRP is patched too, the ph-1 gets boot issues. A reboot ends in TWRP. Probably Q beta3 does something with the data partition. After switching to the slot with Pie, the data partition...

I didn't try it yet. I've Q beta3 working in slot A, but without root. After switching to Pie in slot B, I got a boot issue. Reboot always ends with TWRP. I had to restore all partitions to get Pie booting again. As soon as I have both Pie and Q beta3 running, I'll report here

New EX 3.19 version 4.4.178-ex319-twrp-m192.img - EX kernel 3.19 for PH-1 patched with twrp and magisk 19.2 https://www.androidfilehost.com/?fid=1395089523397962081

https://www.androidfilehost.com/?fid=1395089523397962081 Patched boot image for PH-1 EX 3.19 - TWRP + Magisk 19.2

Yes, working on my ph-1

A How-to: https://romprovider.com/2018/01/twrp-root-nextbook-ares-8a/

Settings > system > advanced > system update: What date is shown ?

On my PH-1 the date shown in setting-about is May 5 2019. Updated by downloading latest OTA and than flashed with TWRP.

PH1 boot images 4.4.178 May 2019 4.4.178-stock-boot.img - extracted from PH1-OTA-PQ1A.190105.058.zip https://www.androidfilehost.com/?fid=1395089523397960738 4.4.178-stock-twrp-m192.img - stock boot.img patched with twrp and magisk 19.2 https://www.androidfilehost.com/?fid=1395089523397960736...

PH1 boot images 4.4.178 May 2019 4.4.178-stock-boot.img - extracted from PH1-OTA-PQ1A.190105.058.zip https://www.androidfilehost.com/?fid=1395089523397960738 4.4.178-stock-twrp-m192.img - stock boot.img patched with twrp and magisk 19.2 https://www.androidfilehost.com/?fid=1395089523397960736...

Before flashing back to stock, you could try to flash a patched boot image of April like below https://androidfilehost.com/?fid=1395089523397933013

I would clear caches in TWRP and hope the message is gone after reboot. And update the radio (to 45R). When update message persists... Wait till next update. At last ... a clean flash.

Only when you want to switch slots. I've always a copy of the latest TWRP zip on my PH-1. I use this TWRP-zip directly after flashing the monthly OTA (before reboot and still in TWRP) Than TWRP is installed to both slots. https://twrp.me/essential/essentialph1.html

Some reported issues when using older versions of adb/fastboot. When you're sure TWRP is installed you may download the latest OTA from the essential site directly on the ph-1 and flash the OTA zip file etc.... Then fastboot is not needed. Even after a reboot it is possible to start TWRP and...

Because of the monthly updates I've copies of the current zip files with TWRP and Magisk. When a new OTA is flashed in TWRP it's important to also flash the TWRP zip before a reboot, so TWRP will be installed to both slots. After a reboot there's no root access, but TWRP can be started to flash...

Yes. Thx In previous posts the path is not complete; 'hw' is omitted

Noticed that some flashed it in TWRP as 'system', instead of 'boot'

I've just copied the file and reboot. In the quick menu NFC was switched off. I had to toggle it on.

Link to that file: https://www.androidfilehost.com/?fid=1395089523397937152 https://www.androidfilehost.com/?fid=1395089523397937152 [email protected] as mentioned by hasitCN in post #11192

Thx, added that file from a previous version. NFC working again.

This worked for me. Combined ex317-twrp-magisk 19. Flash to the active slot containing latest April update. https://androidfilehost.com/?fid=1395089523397933013 Edit: flash as boot images.

You need to go back to stock. Under point 4. you'll find the 'back-to-stock' files of April. https://forum.xda-developers.com/showthread.php?p=74437484

Combined EX 3.17 boot image for PH-1 Flar2 released an updated version of ElementalX 3.17 zip file. Below the afh-link 4.4.176-ex317-twrp-m19.img https://androidfilehost.com/?fid=1395089523397933013

Combined EX 3.17 kernel for PH-1 April 2019 Flar2 released an updated version of ElementalX 3.17 zip file. Below the afh-link 4.4.176-ex317-twrp-m19.img https://androidfilehost.com/?fid=1395089523397933013

Strange... I've pasted the url's. Corrected. Thx

When the flashallwipe.bat updates to April's security patch - Yes.

Boot images PH-1 of April 2019 Just the boot image extracted from the OTA zip of April 2019 4.4.176-stock-boot.img https://androidfilehost.com/?fid=1395089523397931240 EX kernel 3.16 combined with TWRP en Magisk 19.0 4.4.176-ex316-twrp-m19.img...

Boot images PH-1 April 2019 Just the boot image extracted from the OTA zip of April 2019 4.4.176-stock-boot.img https://androidfilehost.com/?fid=1395089523397931240 EX kernel 3.16 combined with TWRP en Magisk 19.0 4.4.176-ex316-twrp-m19.img https://androidfilehost.com/?fid=1395089523397931239...

https://github.com/ianmacd/MagiskBuilds?files=1 Download from this link the MM apk version 7.0.x and a Magisk zip file version 18.2. Flash the Magisk zip first in recovery or with TWRP if that is available. Than you should have root.

See my post #2330 here above

Patched EX kernel for PH-1 EX 3.16 arrived Patched kernel PH-1 March 2019 EX version 3.16 with twrp 3.2.3.0 and Magisk 18.2 for root. 4.4.174-ex316-twrp-m182.img https://androidfilehost.com/?fid=1395089523397920126

Patched EX kernel for PH-1 EX 3.16 arrived Patched kernel PH-1 March 2019 EX version 3.16 with twrp 3.2.3.0 and Magisk 18.2 for root. 4.4.174-ex316-twrp-m182.img https://androidfilehost.com/?fid=1395089523397920126