Database Info

Pixel switchting active slot without any action?

I'm having some issues with my pixel:
Unlocked, but Stock (no root, no twrp) on Android Beta NPG05E (7.1.2). Yesterday morning I've had some issues with hangouts (receiving, but not sending any messages), so I restarted my phone.
On the first reboot it was stuck with the dots animation, at some point i restarted it again by pressing the power button for a long time (like 30 sec?).
This time the phone was booting into OS but there are even more issues: Fingerprint reader not working ("hardware not available") - but gestures do, displays that mobile data is disabled (but is actually enabled), having no notifications at all, the navigation bar button to switch apps does not work (vibration feedback, but no action triggered) and probably a lot more.
Next I checked for Software Updates and also found one - the beta OTA! Seeing this I remembered that the beta dialog was not present at the last boot up and also noticed that Android Version is 7.1.1
This also explains all the issues - going back from Beta to stock is not supported without wipe.
(now i know: --> Somehow the phone might have switched between the two slots?)
While all this happened while I was still on vacation, I then applied the OTA once again and was back to 7.1.2 - but the issues weren't gone. Only Fingerprint reader was working again, the other problems remained.
So next I would probably need to do a factory reset - but I wanted to make a backup with TitaniumBackup first:
Booting TWRP RC1, flashing SuperSU 2.79 SR3, reboot --> no binary found (?)
So I checked and I was back to 7.1.1 again!
Using TWRP I could see that I was on slot B - the build.prop says NMF26U (7.1.1), while on slot A was NPG05E (7.1.2 Beta). So I switched the active slot to A and was on 7.1.2 Beta again - and SuperSU is running well (which means SuperSU installer actually installed on the correct slot, but somehow it got switched right after flash or during reboot).
Did somebody experience something similar? Do you know if there is anything else (besides an OTA) which changes the active slot?
I will probably go for a TB backup now, factory reset and restore the user apps.

Bootloader won't relock, and SafetyNet mayhem

Hi there
Two issues/problems here:
I rebranded my Oreo European MHA-L09 successfully to MHA-L29, everything went perfectly. Then I proceeded to flash RR. SafetyNet however is not helping : CTS mismatch doesn't seem to wanna go away. I tried everything I could find, Magisk does nothing, unrooting : same, can't relock bootloader (root is risk)... kindabummed as it even blocks Spotify from showing up in Play Store. After a week of proding, I'v given up.
So I go back to stock, and whaddayaknow, everything goes fine except... bootloader won't relock : root is risk. I tried reflashing using HWOTA, like, a billion times, couldn't get HiSuite to help either, can't really figure out how to use download mode - most tutorials I found were for P10 - sooooo... yeah.
Any ideas when it come to relocking bootloader (in a stock rom or nah) and passing SafetyNet when a GSI is flashed?

SomeRandomEngi said:
Hi there
Two issues/problems here:
I rebranded my Oreo European MHA-L09 successfully to MHA-L29, everything went perfectly. Then I proceeded to flash RR. SafetyNet however is not helping : CTS mismatch doesn't seem to wanna go away. I tried everything I could find, Magisk does nothing, unrooting : same, can't relock bootloader (root is risk)... kindabummed as it even blocks Spotify from showing up in Play Store. After a week of proding, I'v given up.
So I go back to stock, and whaddayaknow, everything goes fine except... bootloader won't relock : root is risk. I tried reflashing using HWOTA, like, a billion times, couldn't get HiSuite to help either, can't really figure out how to use download mode - most tutorials I found were for P10 - sooooo... yeah.
Any ideas when it come to relocking bootloader (in a stock rom or nah) and passing SafetyNet when a GSI is flashed?
Click to expand...
Click to collapse
So, bootloader relock won't happen if any of the stock images don't match exactly to what the system expects. (If it does, you brick.)
On any ROM, provided it passes the basicIntegrity check, Magisk, possibly with the universal props fix module, will get SN passing. (If it doesn't pass basicIntegrity in the first place, that's another thing, and Magisk can't fix that.)

irony_delerium said:
So, bootloader relock won't happen if any of the stock images don't match exactly to what the system expects. (If it does, you brick.)
On any ROM, provided it passes the basicIntegrity check, Magisk, possibly with the universal props fix module, will get SN passing. (If it doesn't pass basicIntegrity in the first place, that's another thing, and Magisk can't fix that.)
Click to expand...
Click to collapse
Thank you so much for your answer! I already tried installing huawei props fix but it doesn't want to flash - /data/magisk is not configure proprerly even after multiple reinstalls apparently - and when it comes to MagiskHide Props Config, I can't seem to find a fingerprint for the Mate 9. Would using the Mate 10's cause issues?

SomeRandomEngi said:
Thank you so much for your answer! I already tried installing huawei props fix but it doesn't want to flash - /data/magisk is not configure proprerly even after multiple reinstalls apparently - and when it comes to MagiskHide Props Config, I can't seem to find a fingerprint for the Mate 9. Would using the Mate 10's cause issues?
Click to expand...
Click to collapse
Near as I've been able to tell, the fingerprint only makes a difference to things like SafetyNet. You can add the fingerprint for the Mate 9 if you want, obviously, but you could just as easily use one swiped from anywhere else and it would work just the same.
How are you attempting to install Magisk? I've only ever done it, personally, through Magisk Manager, using "Patch boot image" or "Direct install". With the bugs that recently appeared (Magisk Manager 5.8, Magisk 16.6, saw lots of softbricks due to direct install or install via TWRP - it was unconditionally patching something it shouldn't have), I've been telling people to use Patch Boot Image in Magisk Manager always.

irony_delerium said:
Near as I've been able to tell, the fingerprint only makes a difference to things like SafetyNet. You can add the fingerprint for the Mate 9 if you want, obviously, but you could just as easily use one swiped from anywhere else and it would work just the same.
How are you attempting to install Magisk? I've only ever done it, personally, through Magisk Manager, using "Patch boot image" or "Direct install". With the bugs that recently appeared (Magisk Manager 5.8, Magisk 16.6, saw lots of softbricks due to direct install or install via TWRP - it was unconditionally patching something it shouldn't have), I've been telling people to use Patch Boot Image in Magisk Manager always.
Click to expand...
Click to collapse
Okay, thanks! Yeah, I installed it from TWRP. Gonna redo the install then.
Also, I just noticed that Bluetooth does not work - it doesn't even activate for some reason - so I'll probably restart from ,yet another, clean flash. Thank you so much for your help!

Updated TWRP and Magisk, now DRMFIX doesn't work

I'm still on 47.1.A.5.51 and was having some issues with my phone frequently restarting itself and I tried updating Magisk from 14.3 to 18.0 and TWRP from 3.1.1.0 to 3.2.X.X (can't remember offhand). It seems to have stopped the rebooting issue but now DRM fix doesn't seem to work anymore. I am using the kernel and fix provided by shoey63.
I did consider updating to Pie but it seems that there's still a bunch of bugs and stuff. Also couldn't find a proper step by step guide of what the flash order is for it to not lose userdata.
Help would be much appreciated. I just need to hold on to this device for another couple of months before XZ4.
EDIT: It's Magisk that is causing the problem, updating it makes the rebooting issue disappear. Can't update because the free version of DRM fix isn't updated for the newer versions of Magisk.
EDIT2: To heck with it, I installed the DRM and kernel from Janjan's thread even though my firmware is an older version and everything seems to work. It's on Magisk 17.1 and not the latest 18.0 but as long as it doesn't reboot it's mission accomplished for now. Bonus points because now it passes SafetyNet too.

Bootloop on OOS 10.5.7 (Global)

i just updated to latest 10.5.7 Global version via OTA, and before rebooting installed magisk to the inactive slot, and then rebooting resulted in bootloop..
restored to previous slot in fastboot and tried the OTA process again, and resulted in bootloop again..
now i have switched back to the old slot running 10.5.6..
anyone knows why the process resulted in bootloop, and any fix for this?
tia..
[edit]
resolved now..

Probably your mods. I have done same update resulting NO bootloop

Tracker31 said:
Probably your mods. I have done same update resulting NO bootloop
Click to expand...
Click to collapse
thx for the reply.. i dont have any magisk mod installed, apart from magisk itself..
(well theres the built-in systemless host module that i enabled, but i dont think this would cause any trouble as it has been there in the last few updates..)
and the same setup worked fine in the previous 10.5.4, 10.5.5 and 10.5.6 updates..
not sure what went wrong this time..

Try to download update package again. Maybe something broken

Tracker31 said:
Try to download update package again. Maybe something broken
Click to expand...
Click to collapse
already tried twice last night.. i had that doubt as well.. seems quite a few indian users are getting the update fast this time, so i thought maybe the wrong indian version was pushed to my device (global version)?
will try again tonight to see if anything changes.. thx..

Anyway it's not update failure, cuz it works for me

Tracker31 said:
Anyway it's not update failure, cuz it works for me
Click to expand...
Click to collapse
and your regional version is?

AC01BA

Doesn't matter which version you flash. I crossed flashed 3 times from EU to Global and vice versa. No issues.
Maybe you forgot to auto flash Magisk again after installing OTA. It is also recommended to flash Magisk to inactive slot after installing right away "before" reboot.

lekiaM said:
Doesn't matter which version you flash. I crossed flashed 3 times from EU to Global and vice versa. No issues.
Maybe you forgot to auto flash Magisk again after installing OTA. It is also recommended to flash Magisk to inactive slot after installing right away "before" reboot.
Click to expand...
Click to collapse
actually i did remeber to flash magisk to inactive slot after OTA before rebooting.. but seemingly im the only one with this bootloop, so probably certain config in my device caused the issue..
im now in the process of trying the OTA once more, and if this fails again, i shall try to just OTA without patching with maigsk..
if the device then boots, i shall root with magisk from scratch again then..

Strange, and yes must be something system-side. That's why they always say remove modules before flashing OTA or at least disable them. But in my case (only have another font module, iOS smileys and Ktweak) they didn't interfere with the last 2 Ota's. So updating went fine, but i might disable or uninstall them in future OTA's. To avoid such problems you are facing.

You need to uninstall all magisk mods before the update, buy you don't have any installed.
I also believe you need to download the full rom and not incremental. After the update you need to install magisk normally AND also to inactive slot before the reboot.
I haven't installed the latest yet but there previous updates are are installed without issues.

turned out to be a system modification i did back in the 10.5.4 times.. had no problem with it when updating to 10.5.5 & 6, so i totally forgot about its existence.. disabled the mod, updated to 10.5.7, and then enabled the mod again.. now everything is working fine..

Would you mind sharing what it was? I'm about to update and I got some system mods going on that could interfere, and I'm sire I'm forgetting about some too

ASTDEv3 said:
Would you mind sharing what it was? I'm about to update and I got some system mods going on that could interfere, and I'm sire I'm forgetting about some too
Click to expand...
Click to collapse
the magisk module created by smali patcher..

[Solved] WiFi not working after updating to LOS 18.1 and rooting it

Preamble / Rambling​Hello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The Problem​When trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here​
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information​
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)​
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:​
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
#2 For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.

TheAverageUser said:
Preamble / Rambling​Hello dear xda-community,
I am a little desperate right now. After hours of searching for solutions I am sadly out of luck and afraid I might destroy the system if I try to solve this issue any further by my own. :/
By no means I am an expert in flashing / rooting mobile devices, so please forgive me if I did something stupid.
But with that out of the way I hope you can help me. Thank you already for your efforts.
Have a great day,
TheAverageUser
The Problem​When trying to connect to a WiFi the connection disrupts and apparently the entire network management component (?) crashes and restarts.
I suspect it of crashing because the connection to the internet via my SIM card is disconnected as well for a short period of time after the WiFi tries to connect to a base station.
How I got here​
Upgraded from LOS 17.1 to 18.1 like so
Installed TWRP as described here
Installed Magisk as described in the "Custom Recovery" section of this guide
Additional Information​
After upgrading to LOS 18.1 I noticed that Magisk did not work anymore, so I tried to find a way to re-root my device.
A long search later I decided that I needed TWRP in order to root the device as many guides I found required this to be the case. Sadly I can't remember how I rooted the device the first time.
The mentioned method for installing Magisk seemed to be the only one working for me. (I did not find anything better.)
I would love to fix my current OS without having to start over, because setting it up again is very tedious.
Previous Setup (Before Upgrade)​
OnePlus 6 (obviously ^^)
Lineage OS 17.1
Magisk
Lineage Recovery
Updates:​
#1 Okay. Now I am even more confused. The phone just connected to my WiFi and it seems to work. I didn't do anything as of yet. I am going to investigate further to find out when exactly the connections fail. Honestly I don't like a 50:50 chance of it working ^^ (Just to be clear. My problem is not fixed as of yet.)
Click to expand...
Click to collapse
Is it not because of your base OOS version?

Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done

Hello @tiga016 and @Pundy,
so here is an update on my situation:
For some reason the WiFi is now working. The only thing that I can think of which might have solve the issue is that I have uninstalled and reinstalled the "F-Droid Privilgeded Extension" for Magisk.
@Pundy
Thank you very much for this guide. For now I will continue to use my device in its current state, but as soon as I try to do a major update I will come back to your guide in order to install everything in a clean manner.
@tiga016
Thank you for your interest in my issue. For now I will consider this problem to be solved.

Pundy said:
Just do this and you are 100% okay.
1. Use MSM Tool here (it is like a full factory reset with a clean install - you have to unlock your bootloader again!!!)
2. Download latest OOS Full Update here, latest TWRP here, NikGapps here (Magisk if you like) and copy them into Device
3. Flash OOS, TWRP & Reboot to Recovery
4. Flash OOS, TWRP & Reboot to Recovery
5. Flash LOS-ROM, TWRP & Reboot to Recovery
6. Flash NikGapps (and Magisk) & get back to Menu
7. Select Wipe and just swipe to wipe data
8. Reboot to system
9. Done
Click to expand...
Click to collapse
Hello Pundy,
I have updated from LOS 17.1 to 18.1 (clean install) sadly wifi was not working with 17.1 and also not with 18.1. Therefore I have installed OOS (without TWRP) one of the latest version and made an update via wifi to the current version. So wifi is ok. Following the LOS howto, I was successful in installing the latest LOS BUT again wifi is not working...
Sadly also using the MSM Tool is not working. The MSM Tool does not connect with the OP6 (Sahara problem). I have tried it many times...
Any alternative?
BR Martin