Related
Does anyone have a link to the new Nov security patch that came through last night for Fi?
Even with uninstalling Magisk, my phone doesn't want to install the update, so i'll just flash manually with fastboot.
I've checked https://mirrors.lolinet.com/firmware/moto/payton/official/FI/ but haven't seen the Nov firmware yet.
Thanks in advance,
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
NeoandGeo said:
You will either have to do a factory reset on your current version and root after you apply the OTA November update or wait a few weeks for it to be posted to Lolinet.
Click to expand...
Click to collapse
Same situation here as Enemy Lines, but to be clear N&G, the only way updating this security patch is happening is with a factory reset, correct? Either one right now to install the OTA, or flashing the full updated firmware once it's on Lolinet which means a reset as well. According to Magisk, it should handle this with no problem. But apparently can't in this case.
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
I just went ahead and reflashed the Oct rom (minus the userdata delete), let the Nov update install, then repatched for magisk.
I must have changed something in the system partition and didn't realize it ?*
KrisM22 said:
lolinet should have it in 2-3 weeks, but that would mean a full flash.
lmsa doesn't have it.
I don't know if it is possible to download an OTA sec patch - haven't seen it offered to me.
I trust you know that if you have a modified recovery, like twrp, the patch will fail because the install needs to reboot through (stock) recovery to finish installing it.
Click to expand...
Click to collapse
Didn't know that, but suspected that was the case. Thanks for confirming. Guess I'll just full flash it when it hits Lolinet.
If you are going to be getting the latest OTA stuff by doing a full flash you might want to reflect on just how much, or little, you would gain. We all like to think that if we have the latest security patch we are somehow more safe, though I don't believe I have ever heard of a phone being affected by something just because it is not on the latest patch. I was running my old Moto z play on an aug '18 (if I remember correctly) patch with no problems up until a few weeks ago when it was done in by an expanding battery envelope which cracked the display. Consider, also, that many of the custom roms that are available are not updated at all - it takes a ton of work to try to get/keep a custom ROM current, AND working! Yet you never hear of viruses or the like. I will post this as a new thread.
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
SilverPosition said:
Don't disagree Khris. Heck I ran 8.0 until about a month ago and flashed up to 9.0. What I really want is to get that damned annoyed perpetual update from interrupting my phone every five minutes. I turned off Automatic Updates in Dev Ops but that doesn't seem to have helped. Anyone have a useful solution.
Click to expand...
Click to collapse
LOL I have heard that complaint before and I know of no way to stop the notification. Go for it!!!
I'm going to give Enemy's October approach a try. It's all tediously [un]necessary, I suppose. Anyway, thanks for everyone weighing in. Always useful stuff here.
That should work with no problem. and no waiting!
EDIT - I found when I was doing that a lot, I used Nova launcher as it would save apps and desktop and made setup after flash much faster.
If you are just looking to get rid of the update notification you can use Titanium Backup or similar to freeze the 'Motorola Update Services' process.
Thanks Kris and Neo. Nova launcher certainly helps and I appreciate the tip with Titanium Backup and Motorola Update.
That said, here's this for anyone interested:
Like Enemy Lines I went to Lolinet and downloaded the October firmware. I used @munchy_cool’s useful firmware flash guide because he’s got the right Flash-All.sh or .bat scripts in his links. (Link below.) Before flashing I opened the Flash-All.sh and deleted the following command: ./fastboot erase userdata
That preserved my stuff which I’d have lost in a straight flash or factory reset. I downloaded the November patch, updated, reinstalled TWRP and Magisk.
Mac people, once you’ve opened terminal, you may have to activate the Flash-All.sh script with the following command and your password: sudo chmod +x flash-all.sh
If you’re unsure about any of this, read Munchy_Cool’s guide and watch the included vid.
https://forum.xda-developers.com/mo...-to-flash-official-factory-t3808348?nocache=1
No idea why this posted twice.
Thanks!
The stock firmware repository updated a few days ago, new date showing for last activity. No new uploads as of yet, but I believe the updated date precedes the actual firmware being available.
39-6-2 for fi - yeah that's the "Nov 1" one I ota'ed on 11-27, and 11-27 is the date of the ota. So it takes about 4 weeks for us to get it and another 3 weeks for lolinet to post it. So, yeah, if you're in a rush, grab the latest and then let it ota. - at least on retus ATT prepaid...
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Palaryel said:
Since people have trouble getting the boot images, here is my GoogleDrive folder containing stock boot images for Nokia 8 TA-1004 (NB1). Versions uploaded as follows:
2018 patches: October, November, December
2019 patches: January, February, March, April, May, Juni, July, August, September, October
2020 patches: January, April, July
You can root the images via Magisk manager and then flash the rooted versions as needed, or flash them directly to restore stock.
GoogleDrive link:
https://drive.google.com/drive/folders/1S5LkbSWECQN2GzKbGOSLZwSAM8238DXb
Click to expand...
Click to collapse
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
iMaterial said:
Thank you kindly. :good:
Should I uninstall magisk and flash both slot_a and b with a stock img or is it enough with a or b?
Click to expand...
Click to collapse
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
If you want to be able to receive OTA updates it still might fail (generic error "Installation Problem") depending on what you did with root. If that is the case you'll have to reflash completely via NOST (but in most cases you can do so without erasing user data, hence keeping your apps/settings).
Palaryel said:
Depends on what you want to do exactly. If you purely wanna go stock again, check your current active slot (fastboot getvar current-slot), reflash it to the proper version and then flash the other slot with a stock image thats one version lower than the current slot (as each OTA update does install to the opposite slot and swaps active slots on reboot).
Click to expand...
Click to collapse
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
iMaterial said:
Ahh ok, so it switches slot for updates, so it has redundancy if the new boot doesn't work. Makes a lot of sense.
I flashed slot a with the current and the b with the one before, but I'm getting "installation problem" when trying for the july SP OTA.
Click to expand...
Click to collapse
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Your only option now is to actually reflash everything with NOST (if you want to keep user data uncheck the "Erase user data" box before flashing). After the flash your system should update without any issues (will update 3-4 times, takes a while). In case you reflash like this and it doesn't want to update, the only option is to reflash again while deleting all user data, apply all updates and the re-root.
NOST download:
Code:
https://tmsp.io/fs/xda/nb1/tools/nost/NOST-v0.6.exe
Stock image (NB1-5150-0-00WW-B05):
Code:
https://tmsp.io/fs/xda/nb1/firmware/NB1-5150-0-00WW-B05.qlz
Palaryel said:
Something you did as root screwed up the system partition (using Adaway withotu systemless hosts enabled in Magisk will do that for example).
Click to expand...
Click to collapse
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
iMaterial said:
So basically, if I want to keep getting the OTAs, I can do TWRP on one slot, but I shouldn't ROOT? Hmmpf, I wish we had LaOS.
Click to expand...
Click to collapse
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Palaryel said:
Actually the rooting process itself isn't whats hindering the OTAs (as long as you restore the original boot images before the OTA). Its what you do with root.
Since I only use 2 apps which require root (Adaway and Titanium Backup) I found out that what has disabled me to use OTAs before was Adaway modifying the hosts file (which as I've said before you can avoid by enabling systemless hosts in Magisk - after I started using that option getting OTA updates was without problems). Having TWRP will require you to manually reflash it every time before installing an OTA (not really a big issue considering the phone is getting an OTA once every 3 months now).
Honestly HMD did quite some **** with this phone by not updating it to support Treble (considering the Hardware specs the phone is quite usable even today). I'm considering getting a Pixel 4a (or 5) once its available in the EU, I'm getting sick of HMDs carelessness.
Click to expand...
Click to collapse
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
iMaterial said:
Ach so! Leider! Yeah the phone is smooth as a rocket and I got it new in a box for €149 and I hate BIG clunky phones and not having 16:9 / 16:10 screen so. Flashing TWRP a few times a year wouldn't be a problem and I don't use Adaway, but greenify and file explorer Root. I do most of my backups via TWRP. Bleh! Es ist sehr wahnsinnig!
Click to expand...
Click to collapse
Actually I forgot about File Explorer, which I also use in root mode. Also nothing Greenify does should actually compromise the system partition in away that prevents updates. But like I said, with this phone its a bit tricky, I've never been able to pinpoint the exact issue thats doing so. For OTAs to work seamlessly the phone has to be reverted to stock (unroot, stock recovery, stock hosts, unchanged system partition, etc), but apparently theres something more to it since at times even after flashing everything back to stock the updates would fail (in which case only a full revert to stock, including user data fixed the issue).
Also, what you wrote about big, clunky phones: thats exactly the reason I'm thinking about Pixel 4a/5, theyre both under 6'', hence relatively small and perfectly usable with one hand. Nowadays its become the trend to go 6,5+'' for flagships which I'm not really fond of.
Does somebody have that latest and last stock MR for October 2020 (00WW_5_16A) ?
Someone please help me.
"Fastboot devices"
(My device show up)
But after that, I can't enter any command.
It says Waiting for device.
My device show up in fastboot device as well as in Manage Devices in settings as Fastboot.
My Sp is October 2020.
I root my phone last July SP, bit lost root access after update.
Can somebody post the link to the latest Full OTA October 2020? Thanks
How to check your current security patch level. I want to root my phone, bootloader already unlock
Please someone help me
My current bulid no is
00WW_5_15G
Which image i use in above list
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..
Or wait a couple of months for them to tweak it a bit?
I only run Magik and not Xposed, not that it matters!
I'm not rooted, but I've been running R since the first public ßeta.
It's been the smallest update so far in a long time for Android. Very little has changed, compared to previous major version upgrades.
If you can root (and from what I read i think you can with Magisk), make a full backup and try it.
Sent from my Pixel 4 XL using Tapatalk
I don't really know what you'd be waiting for. I don't think a non-rooted person would notice much in terms of drawbacks. Magisk modules level, there were some issues... but I think most things are getting worked out. Xposed technically works, but more than half of my modules broke in a way that probably won't be fixed for a while. I still feel like I'm at a net-negative in terms of phone features. A11 brought little and broke a lot of my QoL tweaks that used Xposed.
I make no claims about SafetyNet as I use no apps that even check it.
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
I tried it and reverted back to 10 - as mentioned didn't gain much but broke a lot. Even in stock form I can't get videos to load a subtitle file because of storage permissions and what not. A tweaked out install of 10 is faaaar nicer imo so that's what I'm running, probably until a new phone comes out sadly.
Kris Chen said:
I think A11 has been released formally by google and most of issues have been fixed or addressed.
I used magisk and edxposed. That's not a problem for me(I used Edxposed for fingerface only). Regarding of safetynet issue, it also has solution to make it pass by magisk modules and kernel side.
Until now, I'm happy with A11.
Click to expand...
Click to collapse
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
A11 is not too bad, but as others have said little things here and there that break. Like for me I listen to SiriusXM app on mobile and for some odd reason it will stop playing all of a sudden and close. It's like the aggressive memory management kills the app for no reason. I even have battery optimization turned off and still does it.
Thinking about moving back to A10 from August, not really much I have to have to stick with latest A11 updates.
qman66 said:
can i ask how you upgraded to A11? Im on 10 rooted with magisk and keep hearing mixed messages on upgrading. And is it necessary to wipe? I really don't want to.
Click to expand...
Click to collapse
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
You do know the latest version of magisk has a11 support?
GjorgiDxc said:
Flash the factory image, but remove the -w in the flash-all file. Then in Magisk Manager switch tot he beta channel and patch the boot image with that. Flash it and you're done.
Click to expand...
Click to collapse
Ok so I shouldn't install it via the ota? I keep getting the pop up to update every day.
Does using Magisk to dl / install the OTA, then patch the non-live and newly flashed partition, then finally rebooting not work?
When I was rooted that was always the easiest way.
And based upon the post 2 above this one, Magisk now supports A11 without ẞeta, right?
From Coral, with Tapatalk.
kdoggy said:
I ended up doing a full wipe and upgrade to Android 11 Oct 2020.
I have Magisk running with the SQL Lite mods for Google Pay and obviously I have root so I'm basically back where I was on Android 10.
I hadn't use Xposed yet and I don't know if I will yet. I was using Viper Audio mod but I don't know if I noticed a major difference, mostly I just stream bluetooth in my SUV.
So far, so good.
Click to expand...
Click to collapse
How is 11 for you going so far, I am thinking in reverting back to 10, battery is awful on 11
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
behel1t said:
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.
I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).
I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.
My phone will successfully take an OTA and not boot loop if I'm not rooted.
I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.
Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers
EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
Click to expand...
Click to collapse
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
azoller1 said:
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
Click to expand...
Click to collapse
Hi, correct I am not using twrp. I tried unlocking the boot loader and not rooting. Receiving an OTA works and I can reboot. But oddly enough if I do a --set-active=otherslot, i get a qualcomm crashdump.
It appears that whenever I or magisk force change the active slot, I get a crash dump.
EDIT - Still unsuccessful. I've tried numerous times using MSM Download and the fastboot unbrick method by coomac. I haven't been able to --set-active=b a single time, it always ends up in a qualcomm crash dump. I suspect slot is B is corrupt.
Try to restore both slots with an older version of rom using local update. Then take ota and try.
kjslabber said:
Try to restore both slots with an older version of rom using local update. Then take ota and try.
Click to expand...
Click to collapse
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
behel1t said:
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
Click to expand...
Click to collapse
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
kjslabber said:
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
Click to expand...
Click to collapse
Thanks for the reply. I do yes. I'll give this method a shot. Cheers
UPDATE - Just finished using msm download to restore OOS 11.0.5.6 and then used local upgrade to flash OnePlus8TOxygen_15.O.20_GLO_0200_2011132216 (both 11.0.5.6). I can now successfully boot both slots!
Now I am going to root. install riru and safetynet fix in magisk.
When I am ready to take an OTA, the correct process would be to uninstall the safetynet fix and riru. Then uninstall magisk using restore images, download and install OTA but do not reboot. Go into magisk and install to other slot. Then providing a successfully boot, reinstall safetynet and riru. Is this correct?
UPDATE 2 - Qualcomm crashdump happened after taking an OTA using the method I outlined above. So I reverted back to the previous slot and am in the process of doing a local upgrade again using 11.0.5.6 to hopefully restore that slot to working.
Something about magisk installing to the other slot and forcing a slot change is causing this crash dump.
I had 11.0.5.6 on both slots. I rooted. I then completely unrooted (not restore images). Took an update. That booted. I booted that. Rooted it. Then for testing, completely unrooted again. Then I received the latest OTA. That installed and booted. So I'm rooting now on the latest getting ready for daily use.
I have no idea why using magisk to install root to the other slot and forcing a slot change is not working. I'm grateful that, with extra steps, i can at least reliably receive OTAs and continue on living rooted life.
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
azoller1 said:
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
Click to expand...
Click to collapse
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
behel1t said:
Yup. Doing exactly that results in a Qualcomm crash dump every single time.
Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
Click to expand...
Click to collapse
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
azoller1 said:
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
Click to expand...
Click to collapse
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
behel1t said:
I'm on v23, I haven't tried Canary.
This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.
At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
Click to expand...
Click to collapse
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
azoller1 said:
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.
EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://forum.xda-developers.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
Click to expand...
Click to collapse
Thanks for bringing this to my attention. This is definitely what is happening. You just just saved me from spending any more time on this mess. Cheers!
I just wanted to add that I had same problem with my OP8T and couldn't reflash the ROM and had to send my phone to OP to get the ROM put back on. Slot B still doesn't work. You at least were able to get the phone back working with MSN.