Database Info

Lollipop OTA Upgrade Not working after Unroot on Stock 4.4.4 // which thread to read?

Hi folks,
I'm a little kerfluffled if you will by the sheer number of threads - search isn't pointing me to a thread that deals with this - so apologies if this has been answered before.
I originally rooted my phone with towelroot. I kept stock but installed a few things like Xposed, greenify, gravity box, etc... (also i switched to ART some time back).
Once i received the OTA notification, I deactivated greenify and gravity box, then uninstalled them, then "unrooted" the phone using SuperSU. I did forget to reset my "startup animation" but otherwise everything seems fine. The root checker confirms that the phone is no longer rooted. Since i forgot to backup the stock animation i just renamed the .zip and now when i boot the animation just says Android (with a little animation regarding the color of the letters).
I then DLed the update, restarted and approximately 30 ~ 40% of the way through the update screen it freezes up and then i get the little android dude with his belly open and the red error triangle. The text below says "error" but provides no further information. The only way to resolve the issue is to power off the phone and then turn it back on. It goes back into 4.4.4 and works fine but i can't get past that error and have no idea how to tell what the error actually is.
Any suggestions will be appreciated! I would prefer to not have to wipe my phone if at all possible.

You'll must wipe your phone as I am. Then you'll be able to OTA update your phone.
I do exactly like you, but error appears every time in the middle of update process. After wipe everything was fine

Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.

Lokke9191 said:
Fastboot flash the new factory images one by one. Reboot the bootloader in between each image, just to be safe. Then use chain fire auto root. It'll take you about 20 min. You will lose all info on your device though.
To save your information, you need to get back to totally stock, unmodified 4.4.4. So flash that in fastboot, just don't flash the user data. Then you can accept the ota.
Even modifying the boot image will cause an ota to throw out an error.
Click to expand...
Click to collapse
Since I'm not concerned about root in Lollipop for now - if i can find the original boot animation and "reinstall it" so to speak - will that allow me to use the ota without having to wipe my phone?

Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.

Lokke9191 said:
Not for sure. To guarantee it will work. Fastboot flash 4.4.4 system.img, boot.img, and recovery.img.
Click to expand...
Click to collapse
okay thanks! i'm going to try and find the original boot animation somehow and if that doesn't solve the problem, i'm going to fastboot everything.

Just dont flash userdata, or you'll lose your setup.

Lokke9191 said:
Just dont flash userdata, or you'll lose your setup.
Click to expand...
Click to collapse
thanks mate!

Update process for OTA 3.1.1 on noOTA Shield?

Hi folks,
My NEW (RMA) Shield is rooted / TWRPed / 3.1 / and I applied the noOTA process to it so that they couldn't force-push some future undesirable OTA (or accidental bricking) at me.
Of course, as soon as I get settled in to the new unit with all apps and data where I want them, they do this new OTA.
What's the process for applying the latest OTA, given a rooted, TWRP recovery system? Do I just boot to TWRP, flash the full OTA, reflash noOTA, and be done? But wouldn't the full OTA kill TWRP, so I should reflash it?
Before I mess up this thing I want to make sure I get it right. I've got a PC so I can ADB/Fastboot sideload stuff if need. My main interest is in not messing up my data and apps.
Thanks
:highfive:

Frankenscript said:
Do I just boot to TWRP, flash the full OTA, reflash noOTA, and be done? But wouldn't the full OTA kill TWRP, so I should reflash it?
Click to expand...
Click to collapse
that's correct. this update in particular doesn't upgrade the recovery too, so TWRP won't be affected, but if you have an unlocked bootloader, you can just reflash TWRP at any time. for root, you might also want to flash SuperSU from TWRP (it will ask before rebooting if you don't install it yourself)

Thanks Bogdacutu.
I copied the full US LTE OTA 3.1.1 over to the internal memory (I used the downloads folder), rebooted to TWRP, and flashed it from TWRP. Before rebooting, to be safe I also flashed nomoreota.zip and then supersu.zip. On first boot I got the typical post-OTA "android is updating" thing where it optimizes the apps. Any idea what this app optimization is? I've always wondered... This app optimization process actually took longer than flashing the OTA and stuff.
After finishing the first boot, SuperSU told me it needed to update the binary, which failed. It suggested a reboot.
I rebooted normally (not going into recovery or anything first). This boot stayed on the NVIDIA boot up screen a lot longer than usual. after about 10 minutes like this I turned it off. After it was all the way off I turned it back on again. This time I let it go about 20 minutes. Still nothing past the NVIDIA boot screen. Crap.
I turned it all the way off. Rebooted with volume down button and was relieved to see it give the usual options (continue, recovery, fastboot, etc.). I let it go into recovery and got to TWRP in short order.
At this point I turned it off, as the battery was getting a bit low and I have to take my kid to a soccer game. I'm charging it in powered off mode until I get home.
Any ideas what to do next to get this thing booting into Android again?
Thanks
Marc

After it charged all the way up, when I got back from my kid's game, I booted back to TWRP and reflashed the OTA update.
I then told TWRP to reboot... it said something about should it reflash SuperSU script to preserve root. I agreed and let it reboot. It came back up in Android. I'll explore the situation and report back.

All seems well at this time.
According to rootcheck my root is preserved. SuperSU successfully updated binaries in normal (non-twrp) mode. Checked for system update. It said I was up to date. I booted back to TWRP, flashed nomoreOTA.zip again. Rebooted again, no problems. Back to normal, fully updated. Phew.
I'm not sure what went wrong the first time, but it seems OK now.

Problem Flashing Factory Images

Wondering if many others of you have run across this, what causes it, and how to avoid it. Basically, I download the factory image from google's image page, flash-all using adb/fastboot. All looks good, every part of installation says OKAY, no fails. Then upon reboot it goes back to bootloader, but now with a yellow banner at the bottom - ERROR: LoadImageAndAuth Failed: Load Error. Sometimes the banner reads ERROR: Slot Unbootable: Load Error. (see attached pictures)
There's no way out of it, flashing images, bootloader or boot.img or whatever separately, flashing twrp, switching between a/b partitions, nothing changes it. Adb/fastboot is current. It's happened after regular flash-all, it's happened when "-w" is removed. It's happened with and without twrp installed. This last time I tried to avoid it by updating without flashing the image, removed twrp and tried to sideload the OTA in stock recovery, which also landed me in the same spot, in the bootloader with that yellow banner of death. Been hit by this using Dec., Feb., and March updates. I stayed on the Dec. update for a while because I've been afraid of it happening again... sure enough it did.
I've replaced a few pixel 2's because of this, every time Google willingly stands by their product and replaces it. One google worker told me this is a known issue they were working on, others said it isn't, and none have provided an explanation for why it happens or how to avoid it. I assume it's some kind of instability with the a/b partition system. I did the same process with my N5x a couple days ago (flashed image then added twrp, magisk, all that stuff) and as usual everything went swimmingly. Tried just flashing current image on p2 the next day and another one bit the dust. Another replacement is on its way now.
So I turn to you. Any of you run into this? What causes it? How can I flash updates without this happening again?

As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.

deepdvd said:
As you know, this happened to me partially. One of my bootloader slots is messed up. Just remember that you can always plug into USB and skip the bootloader and just boot using the boot.img directly.
fastboot boot boot.img
OR if you use Magisk...
fastboot boot patched_boot.img
This of course gets you booted up, so you can get your data backed up or whatever. You're basically tethered to a computer if you ever have to reboot or get back up after a power off.
I think I'll wait another month before having Google replace mine.
Click to expand...
Click to collapse
Tried boot.img but not working for me, still stuck in bootloader. But good to know, I didn't realize that was a possibility. Sucks having to be tethered like that though. I backed up double before messing with it, both nandroid and titanium, expecting I might run into this again.
The replacement process is relatively painless, only takes like 3 days to get a new one. Just be sure to do it while covered under warranty.

Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.

clcdev said:
Hope it works out. To have this happen to several replacements is either extremely bad luck, or some unknown external factor.
Click to expand...
Click to collapse
Thanks man, seems like it since not many people are experiencing this. Can't think of what external issue it could be other than something with my computer, but im sure not having any troubles doing the same stuff and more on my nexus.

@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.

craigacgomez said:
@trhacker01, have you tried flashing the latest full OTA image through recovery twice first (so that both partitions are updated) and then using the factory image? I had a similar (not same) issue where is displayed an empty yellow warning bar and did not let me update the bootloader, but after doing this, I no longer have this issue.
Click to expand...
Click to collapse
Well I tried flashing the ota in recovery and that's what triggered it this last time. But I didn't try doing each partition, maybe that's where it went wrong

Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.

COMpulse said:
Every update bricks me when I try flashing an OTA.
Pretty sure I had both of those errors. One for Feb, other for March.
Fastboot full factory image -w and back to normal, then reinstall twrp.
Going forward I will just plan on using the full factory image.
Click to expand...
Click to collapse
That's what gets me, can't simply fastboot the image to recover, that fail-safe isn't reliable for me.
Got the replacement and set it up so I can update normally. Just booted twrp but didn't install, so I could flash magisk. With no twrp and easily uninstall magisk I can just update via regular OTA when it shows up. Then temporarily boot twrp again to reinstall magisk. Just did that for the March update and worked fine.
A little inconvenient of a workaround but I'm updating without concern about this image flashing problem.

I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.

kkjb said:
I have the exact same problem as first post, even same picture yellow banners. I have tried everything too.
I removed using automatically remove Magisk rooted through Magisk Manager. I liked the edge plus modules.
I was going to Android P with alt flash bat/All and (-W) edit to keep the perfectly working Jan updates.
First of above troubles.
I then went back and tried all updates of 2018.
Same steps as above, re updated everything, different USB port, cable a no go.
The load boot from Fastboot is a no go. Deuce's scripts no go. Manual install of all files (instead of) bat file commands no go.
I bought device through Project Fi, so first go around for return is now escalated and awaiting further return of device.
Looking at web searches used what I could find for return to normal complete image install, NO GO.
Maybe I have the early reports of Flashing Factory Image files =return device= that a few users had back in Nov 2017.
Click to expand...
Click to collapse
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.

kkjb said:
Added: found I my bootloader was failing on updating. Fastboot message= (bootloader) Updating partition=0 Failed
(remote:Command Flash Error).
Some how thought to look over deuce flash all scrip instructions and followed exactly, which seemed strange to add script to expanded image file. Well even with lot's of error returns from running. Used same image that was installed Jan 1.17xx019.013 fixed bootloader and worked.
Odd that was not the usual process, but it WORKED.
Click to expand...
Click to collapse
Wow great to hear it worked! I tried the deuce script but couldn't get it to work either. I heard there was an issue with the bootloader in December and was supposed to have been fixed in January. But that bootloader error was one that I was also getting after the yellow banner started showing up, even on this last go around. Just before the initial bricking fastboot was reporting all successful on the flash.

More of my troubles
I have twrp 3.2.1-2, Magisk v16.1(1610) Jan 18 8.1.0. The device is working as before. So to recap...first post is what I HAD. My bootloader is stuck on 002.0059.00 this is the one from opd1.170816.025 which is 8.0.0 Nov 17. This some how flashed through Deuce's script and stuck. Now of course nothing will flash with Factory images because I have a botched up Boot.img. From looking back the trouble started with going to update to P. Removed Magisk through manager. It "patched" boot but some how on mine (with flashed twrp) recovery caused a flag I guess to set.
So some point I'm going to get Magisk to patch current Factory Boot.img 002.0067.00 which is in Feb, Mar 18 and P.
Need time to read though Magisk or wait for others to experience. I believe this is the warning message of TWRP and Pixel 2 A/B slots.

update to my troubles
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....

kkjb said:
If you have watching as myself to correct the troubles I'm having: recap: Bootloader is not flashing to current one
I'm stuck on 0059. I get a flash fail message (bootloader) ( remote:Command Flash Error ) Bootloader A 200002000 SZ=0000B000. Stuck on bootloader screen only.
Corrected back to before still broken flashable bootloader 0059. Used install TWRP and Magisk. Which I had before trying to update from Jan 18 update. So works as before..
I tried a path to some how get back to correct. So flash current tdbo and boot.img and bootloader. WRONG white G screen only.
So fastboot back into twrp.img use install script zip, install Magisk nogo.
So caution DON'T do it my way.
I was lucky I had a back up twrp file from a month ago. Now at least back to "working"
opm1.171010.013. again that is bootloader 0066 but mine is 0059....
Click to expand...
Click to collapse
That's pretty slick that you got it working again, especially with the bootloader error. I didn't think you could get the current OS working with an old bootloader at all. Hopefully at some point you will be able to update it all the way.

I soft bricked it..so don't do this.
See previous to catch up. Since I pulled the plug and had a Google Warranty phone in hand...21 hours later!
I decided to do all the things NOT TO DO.
Pulled factory Image file from last bootloader with 0059 bootloader.. Nov 17
Flashed tdbo.img, boot.img.
Didn't change same Flash failure device return message. Had to boot TWRP, flash twrp to get working again. Since phone needs to return for credit.
Nothing to lose, I have been on slot = A always. Moved to slot = B....
Now it is a brick.
First couple of power cycles, one line flash, vibrate. Then after 3-4 more cycles no more vibration. longer time to one line flash.
Warm to touch, overnight charge. Same.
So message is to keep backup of files used in first portion of Magisk and twrp installs. Must follow instructions if want to remove Magisk root.
Somehow my problem is a weird one off with the bootloader oddity.

Pixel 3 March 2019 Root

Okay. I'm late getting into the pixel 3 game because I got my pixel 2 late last year. But i've just purchased it recently and it's great. But iv'e been unable to root it & I've never had any trouble rooting any Google devices in the past, stretching back to the nexus 3. I've always been under the impression that Google encourages rooting, or at least, makes no attempt to stop it. So I'm surprised that I even feel the need to make this post. I can find plenty of people talking about rooting even up to February's security patch, but nothing for Google's current most recent security patch (March 2019). Nothing I do seems to make any difference, I've followed steps on several tutorial threads to the letter and still end up in a boot loop. I'm tempted to downgrade so I can root, but I'd like to avoid that if possible. Am I the only one having this issue? I'm not able to find a wealth of people complaining about it, which strikes me as weird. Has Google done something with this update to actively block Magisk, or what? I'm at a loss. Like I say, never have I ever encountered such a road block in rooting any device.
Anyways, hopefully someone can ease my frustrations by at least sharing in them. Thanks for any replies.

This assumes you have already unlocked the bootloader...
1. Fastboot boot TWRP.
2. If you don't want permanent TWRP, skip to step 5. Otherwise, go to step 3.
3. Flash TWRP zip.
4. Reboot to recovery.
5. Flash magisk zip.
6. Reboot to system
That's it. It's the same on every security patch.

This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.

You need to boot into system before flashing magisk.

watlingj said:
This is exactly what I am doing. I've also tried manually patching the boot image and live booting it as well as flashing it, but none of these methods render any different result. I've done it so many times I don't need to follow instructions, I only looked at tutorials because it kept failing. I've definitely got the bootloader unlocked but every time I install Magisk I get boot looping.
Click to expand...
Click to collapse
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:

wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've never had issues without booting back to system before flashing magisk.

Badger50 said:
Maybe a shot in the dark, but, in twrp, after you flash the magisk zip, reboot to twrp, flash the magisk uninstaller, then flash magisk again. I had the same issue when I updated to 9.0 on my P2XL :good:
Click to expand...
Click to collapse
Thanks for the suggestion but alas, still boot looping.

wangdaning said:
You need to boot into system before flashing magisk.
Click to expand...
Click to collapse
I've tried this, it didn't make a difference.

OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.

wangdaning said:
OK, try:
1) Flash factory image, remove -w if you want
2) Reboot system then reboot bootloader
3) Fastboot boot TWRP (if you flash install zip reboot system again, then back to recovery)
4) Flash magisk v18.1 (redownload it to eliminate bad dl as culprit)
Not sure what is causing your problems. The initial guide is the same as with the march update. I have done it several times without issue.
Click to expand...
Click to collapse
Sorry for the late reply, i actually ended up returning it to stock and swapping it for a different one, because my speaker was making a weird sound when i was calling and it was having bluetooth issues, this one rooted perfectly fine first try.'
Except, Magisk randomly can't detect it's self through it's own manager app, but all my installed modules are working.. but i can't... manage them..

Phone reboot to twrp and twrp doesnt decrypt data after OTA update

Hi,
So I followed this tutorial https://oneplus.gadgethacks.com/how...thout-losing-root-no-computer-needed-0192638/ (but I used more up to date downloads links than what was on the article) to update my phone to the latest oxygenos on my OnePlus 6.
The install went well, I could reboot on my phone without problems. The thing is when I ran magisk manager it said that magisk wasn't installed. So I rebooted to twrp and flashed again magisk then rebooted. Now when the phone rebooted and asked me for my pin number it automatically went to "Shutting down phone" and rebooted to twrp. So I flashed the magisk uninstaller but it didn't rebooted well. Then I thought I had to switch the active slot, so in twrp I switched to slot A. Then it rebooted on fastboot. I understood I did something really bad so I ran "fastboot --set_active=b" on my computer.
Now my phone cannot actually boot and everytime I get in twrp except that now it doesn't ask me to unlock the phone to decrypt it and just asks me if I want to get into twrp in read only mode. When I navigate to /sdcard, it is full of weird folder name which is because, if I understand well, twrp has failed to decrypt it.
Is my phone bricked? Can I recover data? Can I repair my installation?
EDIT: if you need more informations that I forgot to give don't hesitate to ask.
EDIT2: I tried to reboot to fastboot mode and issue on my computer "fastboot boot twrp-3.2.3-1-enchilada.img" to see if the official twrp could decrypt the data (I'm currently using bluespark's twrp). I get the following error: "FAILED (remote: unknown command)". I understand now I'm pretty ****ed. Right now I'd only like to recover my data (mostly hundreds of pictures) and then flash a stock rom (except if it's actually possible to repair the system and boot normally). How can I decrypt /sdcard if twrp can't do it?
Thanks in advance for your help, I'm pretty lost right now and it's quite an urgent situation.

I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```

Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?

noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).

Thank you for your answer, everything's back to normal
I'll make sure to follow the official tutorials next time.

only4dank said:
Once in your booted TWRP from 'fastboot boot twrp.img' ... Flash OOS (9.0.5 from xda forums), flash blu_spark-TWRP, reboot TWRP... Now you can root your phone (flash Magisk), flash a kernel. All should be good.
I would suggest in future, use these forums for download links, tutorials, and check this Q&A forum (literally 3-5 posts on first half of page 1 with similar problems. Just follow instructions to update if you don't know how (they are always on first page of the thread where you get your downloads from).
Click to expand...
Click to collapse
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.

thejase said:
Good advice. I'd also like to add so everyone is aware, it's a good idea to disable all magisk modules before an update. Also disable your lockscreen pin, fingerprint... Basically any security. You can always re-enable these once updated. It just makes for less complications when updating. I'd also recommend downloading magisk modules outside of the app and keep them in a folder called magisk modules. That way, if for some reason magisk didn't retain the ones you downloaded after disabling and installing an oos update, you don't have to rely on your memory to look up\install them.
Click to expand...
Click to collapse
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.

only4dank said:
I never disable/uninstall Magisk modules. Nor do I disable lockscreen pin, fingerprint.
Theres no point at all. If flash things logically (correctly) you won't reboot your system without non-stock recovery, or no root.
Click to expand...
Click to collapse
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.

thejase said:
There absolutely is a point. Many people have had encryption issues in twrp when updating. In addition, I myself have had a magisk issue where one of the modules wouldn't run properly when updating to pie and as a result, it didn't boot. Using a terminal magisk module uninstaller in twrp to disable the module fixed the issue. This is merely advice to eliminate all possible failures when updating. If it works for you without doing these things, mazel tov, but this is for those that have had issues and want to minimize the odds of that happening again.
Click to expand...
Click to collapse
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).

only4dank said:
Fair enough. But moving from Oreo to Pie is a little bit different then Pie OTA updates. I have 6-7 modules recently in Magisk - and never uninstalled Magisk or removed modules while updating Android Pie.
When I came from Oreo, I did a clean wiped system. To me, that makes sense - because it is a dramatic change in the system (whereas OTA updates for same android version are pretty minuscule).
Click to expand...
Click to collapse
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.

ante0 said:
The only module I had to manually remove, because OOS refused to boot after an update, was "OOS Native Call Recording Enabler".
And before I knew that was causing it... I factory reset, then everything was fine until the next update xD
I even made a Backup/restore magisk data script, but seeing as it backed up/restored that module too it would still refuse to boot after an update.
Click to expand...
Click to collapse
Same. But if you install it with version 8.0 after the update, it works again. Just f.y.i..

noom4_5 said:
I got a new error when issuing "fastboot boot boot.img" after I rebooted to System from twrp:
```
Downloading 'boot.img'
OKAY [ 0.692s]
booting
FAILED (remote: Failed to load/authenticate boot image: Load Error)
Finished. Total time: 0.719s
```
Click to expand...
Click to collapse
noom4_5 said:
Ok so now by restarting a couple of times to fastboot I successfully booted to official twrp using "fastboot boot.img" and it successfully decrypted my storage!!!
Now I think things are recoverable, how do I fix this bad boy? Reflashing last official oxygenos image could work?
Click to expand...
Click to collapse
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!

wwwryan said:
Can you tell me which TWRP image you used to get past this issue? I have tried both 3.2.3-1 and 3.3.0-0 several times with zero luck this far. Thanks!
Click to expand...
Click to collapse
Answered my own question but wanted to leave this here for others just in case it is helpful. Using twrp-3.2.3-x_blu_spark_v9.91_op6.img I was able to fastboot boot the img file and this version of TWRP offered to decrypt. From there first thing I did was adb pull my entire sdcard to my PC for save keeping.
My issue was a result of restoring from an earlier backup to recover some data. I had recently updated to 9.0.5 but accidentally deleted something I had no backup for so was restoring a previous TWRP back from 9.0.4. After the restore I couldn't boot the OS and all official version of TWRP would no longer offer to decrypt my data. Of course, I could not restore the backup I had just taken either since it was encrypted on the internal SD card. From now on I will just take TWRP backups to external storage via OTG USB and not even risk it.

Happened to me a few days ago
You can NOT recover your data. But you will be able to fix your phone.
Just do a Factory Reset from TWRP (Wipes Everything) and a wipe of system etc
Then just sideload or put the latest OOS back on the phone and install it.
Trust me, I have tried everything for trying to recover and decrypt the data... Somehow our phones did change the Encryption Keys from /data/unencrypted so there is no way to recover unless you can get the same key out of luck of using the encryption algorithm and salting process that Android uses.
https://imgur.com/y8ENw77
https://imgur.com/q7BPOCy

I've done this a few times. Actually... every time I update; save for the last two times. Just two notes that you already seem to have figured out:
1) Always remember turn off your active modules. (Just turn them off, you don't need to uninstall them.) Simply doing that seems to have fix OTA issues for me. I try to do it before I even download the update and definitely before I install it.
2) No matter how badly I foul up (except for the first time), I never wipe it when trying to fix it. Just side boot Blu Spark TWRP and flash the OS again. Boot it up once without root. Then go ahead to side boot Blu Spark TWRP again to root. I never install TWRP to the device at all. Even with Blu Spark, it seems to get iffy with me. If I want to flash something, I just let it wait until I'm home so I can side load Blu Spark.