Database Develop

[SOLVED] December-Update Softbrick

Hi,
My P4XL is/was rooted with Magisk. Then today i tried to install the december update exactly like written here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
After clicking on reboot in magisk, booting up took ages. After 20min. i forced another reboot and waited another 20min. At this point i quit waiting and decided something went wrong.
I tried to go back to the november update by flashing the full factory image 10.0.0 (QD1A.190821.014, Nov 2019) from the google download page.
Now when i try to boot or go to recovery or rescue mode i alwas get to the fastboot screen with the following information:
Code:
Bootloader version: c2f2-0.2-5799621
Baseband version: g8150-00014-190826-B-5830341
Device state: Unlocked
Boot slot: a
Enter reason: error booting boot.img
Is it, cause i already made the update and cant go back to november?
Any ideas how i get my device fixed?

How about your slot-b system ?
Try to switch into slot-b and boot it !
Kris

Kris Chen said:
How about your slot-b system ?
Try to switch into slot-b and boot it !
Click to expand...
Click to collapse
That seems like a good idea. Thanks. I will try that later when i get home from work. Will report back.

Update: Switching slots did nothing, sadly.
I tried to flash the November Factory Image and December Factory Image. I always end up stuck in bootloader mode: "Waiting for device".
So, for everyone with the same issues finding this thread, here is the solution:
Now (not with a lot of confidence) i sideloaded the full ota image for december (bootloader mode, select corresponding option), that is thankfully now available from the google page, aaaaaaaaaaaand its booting again. Yay.
Just to be sure that everything is alright, i flashed the whole factory image again, this time it was working fine.
Now all is ok again and im on the december update. Thank god. That was a stressful day haha.
Still weird that i couldnt flash the factory image, but the ota was fine... Any idea why?

Aiakio said:
Update: Switching slots did nothing, sadly.
I tried to flash the November Factory Image and December Factory Image. I always end up stuck in bootloader mode: "Waiting for device".
So, for everyone with the same issues finding this thread, here is the solution:
Now (not with a lot of confidence) i sideloaded the full ota image for december (bootloader mode, select corresponding option), that is thankfully now available from the google page, aaaaaaaaaaaand its booting again. Yay.
Just to be sure that everything is alright, i flashed the whole factory image again, this time it was working fine.
Now all is ok again and im on the december update. Thank god. That was a stressful day haha.
Still weird that i couldnt flash the factory image, but the ota was fine... Any idea why?
Click to expand...
Click to collapse
Just a couple of ideas as to why the factory image failed. Were platform-tools up to date? How long did you wait when the output screen said "waiting for device"? I had to wait a couple of minutes for mine to kick in. Could've been a cable issue as well

Badger50 said:
Just a couple of ideas as to why the factory image failed. Were platform-tools up to date? How long did you wait when the output screen said "waiting for device"? I had to wait a couple of minutes for mine to kick in. Could've been a cable issue as well
Click to expand...
Click to collapse
Platform tools is always up to date. First thing i check before i use adb/fastboot.
Ok well, i didnt give it much time. Maybe i was to impatient.
Cable is original google. Everything worked fine so far with it.

At least, sideload saves your phone. But I cannot understand why factory full image cannot be flashed? I never have this problem.
Try to get into recovery mode and wipe every thing and try it may have help.( Ofc, you will lose every thing after doing that. Be carefully.
Aiakio said:
Update: Switching slots did nothing, sadly.
I tried to flash the November Factory Image and December Factory Image. I always end up stuck in bootloader mode: "Waiting for device".
So, for everyone with the same issues finding this thread, here is the solution:
Now (not with a lot of confidence) i sideloaded the full ota image for december (bootloader mode, select corresponding option), that is thankfully now available from the google page, aaaaaaaaaaaand its booting again. Yay.
Just to be sure that everything is alright, i flashed the whole factory image again, this time it was working fine.
Now all is ok again and im on the december update. Thank god. That was a stressful day haha.
Still weird that i couldnt flash the factory image, but the ota was fine... Any idea why?
Click to expand...
Click to collapse

Did you boot after flash magisked boot.img of december?
I got december update by fastboot & flash.bat file, and flash magisked boot.img,
but my Pixel4 gets bootloop. (after boot, it goes to the 'Google' boot screen, and repeat on and on.)

dev311k said:
Did you boot after flash magisked boot.img of december?
I got december update by fastboot & flash.bat file, and flash magisked boo.img,
but my Pixel4 gets bootloop. (after boot, it goes to the 'Google' boot screen, and repeat on and on.)
Click to expand...
Click to collapse
I tried to. But didn't work. I was stuck at the G-Logo. No bootloops though.
Maybe try to flash and boot with original boot.img? Can flash magisk still after that.

Aiakio said:
I tried to. But didn't work. I was stuck at the G-Logo. No bootloops though.
Maybe try to flash and boot with original boot.img? Can flash magisk still after that.
Click to expand...
Click to collapse
Maybe we have to wait next Magisk

I'm using Magisk Canary. Running great so far on December update. GPay is working too.

Aiakio said:
Hi,
My P4XL is/was rooted with Magisk. Then today i tried to install the december update exactly like written here: https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
After clicking on reboot in magisk, booting up took ages. After 20min. i forced another reboot and waited another 20min. At this point i quit waiting and decided something went wrong.
I tried to go back to the november update by flashing the full factory image 10.0.0 (QD1A.190821.014, Nov 2019) from the google download page.
Now when i try to boot or go to recovery or rescue mode i alwas get to the fastboot screen with the following information:
Code:
Bootloader version: c2f2-0.2-5799621
Baseband version: g8150-00014-190826-B-5830341
Device state: Unlocked
Boot slot: a
Enter reason: error booting boot.img
Is it, cause i already made the update and cant go back to november?
Any ideas how i get my device fixed?
Click to expand...
Click to collapse
Don't bother trying to preserve root -- I often find it causes more problems then anything. This may take a little longer, but it has always worked for me:
- download and extract the factory stock image from Google and place into your adb folder
- extract the boot.img file and copy it to your phone (I place mine into the download folder)
- edit the flash-all.bat file and remove the "-w" from the script. '-w' is the command that wipes your phone's personal data
- reboot phone into bootloader
- run the flash-all.bat and let it do it's thing. When it gets to <waiting for device>, don't touch the phone and be patient. After 2-3 mins, it will run through the update gauntlet
- let the phone reboot and wait for the updates to finish
Proceed with re-rooting using the Magisk Manager method, but a quick summary:
- Open Magisk Manager and patch the boot file
- copy magisk_patched file to your adb folder
- boot into bootloader and flash the patched image
A little slower than the OTA, but definitely will be rooted without any issues. I just updated to Dec and re-rooted without any issues.

patched dezember boot.img please

hanschke said:
patched dezember boot.img please
Click to expand...
Click to collapse
This is the stock, and patched December boot images. Your welcome :silly:
https://drive.google.com/file/d/18FqwDgmCE6zsiENxNTlrUqlEa35X64E7/view?usp=drivesdk

An FYI, yeah, you can flash almost anything with the cable in the box, what you'll have problems flashing is the full factory image. You need a USB A to C to reliably flash the full image. Yeah, I know it's crazy that the cable in the box doesn't work and it sounds stupid and I must be wrong. I'm not asking for trust, just have an A to C on hand and try it after you fail with the C to C from the box. Don't get all jiggy, do nothing else other than try flashing again but with the A to C. You should be ok and just need to flash the boot afterwards.

krabman said:
An FYI, yeah, you can flash almost anything with the cable in the box, what you'll have problems flashing is the full factory image. You need a USB A to C to reliably flash the full image. Yeah, I know it's crazy that the cable in the box doesn't work and it sounds stupid and I must be wrong. I'm not asking for trust, just have an A to C on hand and try it after you fail with the C to C from the box. Don't get all jiggy, do nothing else other than try flashing again but with the A to C. You should be ok and just need to flash the boot afterwards.
Click to expand...
Click to collapse
Welcome to the Wonderful World of Pixel Craziness... Been this way since the 2XL. Lol Just keep preaching the word whenever you can. Folks are hard to convince until they experience it themselves. ?

Yeah, I've had most of the Nexus and following them Pixel devices among many others, there has been some real headscratchers along the way. I've read the conspiracy theory that they do it on purpose to deter flashing. I've no idea on that but it is a reported bug so they know.

Okay, I Need Help (Like a Brick, Sort of.. Just read thing below)

So, I had Xiaomi phones before and I know that they can get little bit buggy sometimes, because of that I always keep "allow OEM unlocking" checked, just in case something happens. Okay back to what happened, I was running latest Pie version when I got notification that update to Android 10 was available, so naturally I tried to update and got stuck in a bootloop. This had happened before, so i decided to just roll back to the previous update and try again but no, even tho i have my bootloader unlocked and I can flash in fastboot mode, It doesn't work (I tried with just running .bat file and with MI Flash). It writes 'success' but when it reboots it can't past android one logo (and after few attempts to boot it gives error 'can't boot would you like to retry or power off' or something like that), I have tried to flash many 'update versions' but to no avail, only thing to work is first official ROM (android 8.1)
after flashing that it boots and works normally, it successfully updates once, to Android P and than same thing, It downloads file, applies update and when I reboot phone to finish update it gets stuck in bootloop.
Please help me, thanks in advance.

My advice is to unlock the bootloader and install the Pixel experience ... It is much better than the official Android 10 ... And get rid of Xiaomi's update issues.

Badotti said:
My advice is to unlock the bootloader and install the Pixel experience ... It is much better than the official Android 10 ... And get rid of Xiaomi's update issues.
Click to expand...
Click to collapse
(My bootloader is unlocked) something strange happened I tried again installing latest pie update and for some strange reason ( to be honest I tried to boot 30-50 times) it worked and it successfully updated to Android 10 ( again after ~50 or so tries to boot) so yeah.

Booting issue after logo? Status bar and back button flashing

So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?

Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.

Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.

DarkusRattus said:
So I've had this issue on three separate Pixel 4 XL phones now and I'm pretty sure this is due to my error somehow.
My issue is after the phone passes the Google logo, a black screen pops up with the status bar flashing on and off, and occasionally the back button like this: https://imgur.com/iRzD1Jk
I've installed Magisk and EdXposed to use GravityBox and FingerFace, however I haven't done much more than that.
Flashing the factory image over while retaining data does not fix it, although I'm not sure why.
Factory resetting seems to fix it for a short time, but it seems to always come back, even if I don't install EdXposed.
Safe mode does not help.
I had also recently tried updating by flashing the February image over the January (without wiping data), and that seemed to let it boot. But unfortunately I decided to continue with the exchange as I had requested one before the update was released.
Does anyone have any similar experiences or any ideas for me to try?
Click to expand...
Click to collapse
This happened to me too, I originally thought if was the Rom however dirty flashing the Rom again didn't fix it nor did dirty flashing stock image
What I do know is, this happened to me as soon as forced stopped gms services and removed GMS dose from magisk. As soon as I rebooted, this happened

Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It's kinda strange because I didn't touch anything for some days, and after a normal reboot this happened.
I tried restoring the stock boot.img from fastboot -> same issue
Reflash entire factory image without the "-w" so without wiping -> same issue
Even reboot in safe mode -> same issue
I don't think it's magisk fault because happened randomly the last 2 times, but I'll give your method a try if this happens again

It sure is giving off system UI crashing vibes. I definitely agree that this is an issue caused by something you did, not something inherent to the Pixel 4. Like suggested already, I would uninstall magisk as a next logical step since you've tried many of the other things I would have suggested. I wholeheartedly agree with Tulsa that this is a bad flash. Since you didn't wipe userdata when you flashed the factory image, the bad flash is still present so it's pretty safe to assume that you have a bad module installed or a bad combo of modules that don't like working together.

Tulsadiver said:
Have you tried uninstalling magisk then, if necessary, flashing system images? Fastboot boot the modified boot.img from my boot recovery thread that removes magisk. I believe it is due to a bad or incompatible flash as I've gotten this same thing before.
Click to expand...
Click to collapse
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?

DarkusRattus said:
It was the last link on this thread correct? https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I tried booting that and all it did was try to boot, restart before it finished, and boot back into the flashing UI.
Was this the correct image?
Click to expand...
Click to collapse
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.

Tulsadiver said:
Yes. What is the flashing UI? I just ran it on my Pixel 2. It ran just fine. Yes it reboots during flashing as the script reads "rm-rf /data/adb/* && reboot" After it reboots, click on magisk manager. It should say you need to install additional files. It will then your phone will reboot again. Modules should be gone.
Click to expand...
Click to collapse
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.

DarkusRattus said:
Check the link in my first post. That's what it looks like when it boots. I cannot get through that screen. It stays that way even if I dirty flash the factory image.
Click to expand...
Click to collapse
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.

Tulsadiver said:
Is your phone rooted still? You must have root. Flash the magisk_patched.img again to make sure and try again.
You could also try the other boot image that installs a .disable-cache file.
Click to expand...
Click to collapse
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.

DarkusRattus said:
I flashed both of your images as well as my original generated magisk_patched, and the original boot.img from the factory image. They all lead to the same booting issue.
I can tell when the Magisk modules are disabled because the modules that affect the clock position in the header returns it to its original position from center to left. But that's the only thing that changes. I can reflash the whole factory image and the issue still persists.
Click to expand...
Click to collapse
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.

Tulsadiver said:
What order did you flash them in?
1. Flash magisk_patched.img then reboot.
2. Boot back to fastboot and boot one of my boot images.
If you have done this and still have a problem you will probably have to do a factory reset.
Click to expand...
Click to collapse
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.

DarkusRattus said:
I appreciate you trying to help me.
I did this with the same results.
I am totally fine with doing another factory reset. My issue is that I've been having this issue across three different phones, and I believe the issue has happened a total of about 10 times, the longest time I've gone without anything happening appears to have been almost two months. I'm trying to understand what I'm doing that is leading to this problem more than anything.
When I install Magisk, I believe everything installs to partition B.
The issue is not caused by EdXposed because it has happened some times without it being installed.
I believe the modules I've used each time are:
-IOS 12 Emojis
-Systemless Hosts
-Call Recorder - SKVALEX
I believe I was also using FDE.AI, but I don't think that would cause this until after I pass the unlock screen, which I can't.
I've been using ElementalX as the kernel.
The issue comes up randomly, and sometimes I can reboot several days without anything happening. I can't see anything I'm doing between the final successful reboot and the issue coming up where this starts to happen that could be causing this.
The ONLY time this seemed to have been fixed was when I updated to the February factory image. However I already had a replacement phone coming, so I decided to still send the old one in.
Click to expand...
Click to collapse
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).

Tulsadiver said:
That is a weird issue, for sure. I know of people that recommend flashing factory images and magisk to both slots but I've never have and have not had these issues on any of my Pixels (except on a bad flash).
Click to expand...
Click to collapse
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.

DarkusRattus said:
Question that may be related. Is it normal that I can never boot from when it's set to slot A? Even manually flashing boot.img and magisk_patched to that slot doesn't work. The factory image seems to install everything to slot B and only seems to reference A a few times.
Click to expand...
Click to collapse
I don't know how old your phone is but the slots are used for when you receive firmware updates and don't change unless you receive one over the air. You can change it manually in fastboot
fastboot --set-active=a
Try that then install your firmware again. It should now just reference B a few times.

TENN3R said:
Finally I found someone with the same bug that happened to me 2 times. I can't understand why this happens.
The first time happened when I rebooted my phone when dark mode was active, but looks like it happens randomly. I got that in november and then 2 days ago, without an apparent reason.
Looks like some UI related crash/bug, but I really can't undestrand what's causing that. Removing root/mods with a dirty flash of the rom doesn't fix it, only wiping.
Hope someone can point out a way to fix this really annoying bug, or a way to prevent it. It's really frustrating.
Click to expand...
Click to collapse
Did you have FDE.AI installed by any chance? And what kernel were you using?

DarkusRattus said:
Did you have FDE.AI installed by any chance? And what kernel were you using?
Click to expand...
Click to collapse
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue

TENN3R said:
Yes, I had FDE installed for 2 or 3 days, and I was using Kirisakura kernel.
Edit: I just found out that there's a pretty big discussion going on with the FDE module on it's thread, same on the arter account on twitter. It's possible that this is the cause of the issue
Click to expand...
Click to collapse
I also feel that it's the issue, although I was using the FDE.AI app, so I guess both methods of installation can cause it. After the nth time resetting my phone, I just changed kernels and uninstalled FDE.AI and for a solid week now I've been booting fine.
Edit: wow I just looked at the thread and it looks like something went down over there.

DSU Loader - your device is corrupt

I am running Dev Preview 1 on my Pixel 4 XL.
I decided to try out the DSU Loader within the Developer Options. It downloaded the GSI and rebooted, however on boot it immediately shows the message "Your device is corrupt. Yaddayadda". Pressing the power button and it just hangs at the Google boot logo forever.
Force reboot and it boots back into the corrupt error then bacl into Android as normal where i can then discard the DSU/GSI.
I still get the error on boot, but everything works as normal
Has this happened to anyone else? Anyone know how to get rid of the corrupt message without factory reset? Flashing the OTA file see doesn't get rid of it.
TL;DR tried the Dynamic System Update in R Dev Preview and ended up with corruption error on boot.

xdatastic said:
I am running Dev Preview 1 on my Pixel XL.
I decided to try out the DSU Loader within the Developer Options. It downloaded the GSI and rebooted, however on boot it immediately shows the message "Your device is corrupt. Yaddayadda". Pressing the power button and it just hangs at the Google boot logo forever.
Force reboot and it boots back into the corrupt error then bacl into Android as normal where i can then discard the DSU/GSI.
I still get the error on boot, but everything works as normal
Has this happened to anyone else? Anyone know how to get rid of the corrupt message without factory reset? Flashing the OTA file see doesn't get rid of it.
TL;DR tried the Dynamic System Update in R Dev Preview and ended up with corruption error on boot.
Click to expand...
Click to collapse
Nevermind!

You might need to wipe data in recovery, but if you don't want to lose your data then I'd suggest trying to roll back by using an OTA.zip
Sent from my Pixel 4 XL using Tapatalk

superchilpil said:
You might need to wipe data in recovery, but if you don't want to lose your data then I'd suggest trying to roll back by using an OTA.zip
Click to expand...
Click to collapse
Have you tried booting a GSI yourself within the Developer Options? Any success?

xdatastic said:
Have you tried booting a GSI yourself within the Developer Options? Any success?
Click to expand...
Click to collapse
The ROM I'm running is a GSI but I flashed it through recovery, not the web tool.
Sent from my Pixel 4 XL using Tapatalk

Hey
Pixel 3a user here. I've encountered exactly the same issue but I've not been able to fix it either.
I'm going to roll all the way back to Q later anyway, R is just a little too buggy still for me. (My banking app crashes and GPay thinks my phone is rooted)
Attempts at reflashing the DSU after discarding it result in... Nothing happening. So I'm at a total loss.
Attempting to flash the 11DP1 OTA again does not resolve the issue either. "Phone corrupt" warning every time.

Apparently the Android 11 GSI is signed with the Android Q public keys....hence why it won't boot. Apparently this has been fixed in AOSP and hopefully is included in DP2.
Not sure if DP2 OTA will fix the corrupt error or not. I might wait it out to see as rolling back to Android 10 for me is a pain. Luckily my bank app still works for tap n pay so o use that instead of Google Pay for now.

xdatastic said:
Apparently the Android 11 GSI is signed with the Android Q public keys....hence why it won't boot. Apparently this has been fixed in AOSP and hopefully is included in DP2.
Click to expand...
Click to collapse
That was silly of them!
Perhaps I'll hold off then for DP2 and see if it fixes the majority of my problems rather than doing a wipe and rollback.
I think it's expected early March, right?
Also, if it's an issue with signing keys, surely just flashing the DP1 OTA atop it should fix that?

MilesKjeller said:
Also, if it's an issue with signing keys, surely just flashing the DP1 OTA atop it should fix that?
Click to expand...
Click to collapse
The DP1 OTA apparently contains the wrong keys for the GSI, so flashing that doesn't fix it.

xdatastic said:
The DP1 OTA apparently contains the wrong keys for the GSI, so flashing that doesn't fix it.
Click to expand...
Click to collapse
Yeah, I reread other posts and that makes sense.
I ended up rolling back to 10, too many niggles in 11DP1 at the moment.

The corrupt error on boot is resolved in build rpp1.200123.020 released today.
I haven't tried to boot a GSI yet, but at least the error is fixed when booting normally.
EDIT: Tried booting the GSI again from Developer Options - ended up with same corrupt error again...

xdatastic said:
The DP1 OTA apparently contains the wrong keys for the GSI, so flashing that doesn't fix it.
Click to expand...
Click to collapse
superchilpil said:
You might need to wipe data in recovery, but if you don't want to lose your data then I'd suggest trying to roll back by using an OTA.zip
Sent from my Pixel 4 XL using Tapatalkthe same thing happened on my phone (BLU G91 MAX ANDROID 11) I INSTALLED THE DYNAMIC SYSTEM UPDATE RESTART IT TO FINISH AND IT SAYS PHONE CORRUPTED PRESS POWER BUTTON WITHIN 5S TO BOOT BUT ALOT OF STUFF LIKE AUTO ROTATE AND OTHER PROBLEMS sone1 on here told to unlock my bootloader which stoped all the problems with auto rotate but I still everytime I boot get the corrupt message I press power button to boot then I get your phone is in yellow mode it can't be trusted cause I have my bootloader unlocked so my question was about the OTA.zip idk what that is but I don't have a computer but anybody no how to get rid of the corrupted file so I can close my bootloader?
Click to expand...
Click to collapse

xdatastic said:
I am running Dev Preview 1 on my Pixel 4 XL.
I decided to try out the DSU Loader within the Developer Options. It downloaded the GSI and rebooted, however on boot it immediately shows the message "Your device is corrupt. Yaddayadda". Pressing the power button and it just hangs at the Google boot logo forever.
Force reboot and it boots back into the corrupt error then bacl into Android as normal where i can then discard the DSU/GSI.
I still get the error on boot, but everything works as normal
Has this happened to anyone else? Anyone know how to get rid of the corrupt message without factory reset? Flashing the OTA file see doesn't get rid of it.
TL;DR tried the Dynamic System Update in R Dev Preview and ended up with corruption error on boot.
Click to expand...
Click to collapse
Yes I have a (BLU G91 MAX ANDROID 11) and the same thing shows up on mine but I have to leave my bootloader unlocked because when it was locked and I installed dynamic system update when I restarted I got the same message press power button within 5s to. Boot but when my bootloader was locked I was a lot of apps weren't working and auto rotate screen didn't work until I unlocked the bootloader but still to this day I still have the message but everything working but I would love to get rid of the problem so I can close my bootloader

superchilpil said:
You might need to wipe data in recovery, but if you don't want to lose your data then I'd suggest trying to roll back by using an OTA.zip
Sent from my Pixel 4 XL using Tapatalk
Click to expand...
Click to collapse
Yea I can't loose my data but how do I go about using a OTA.zip?

Yea I can't loose my data but how do I go about using a OTA.zip?

Phone stuck in bootloader screen after enabling encryption

I recently installed the latest Arrow OS 10 sanders version on my phone, everything was working fine so I decided to encrypt it as I needed to install some apps from my work. I did it in the Security options in the OS, not using TWRP in recovery mode.
It's been 3 hours since the phone is stuck in the bootloop screen, it already rebooted alone once but nothing else. What should I do? Keep waiting more time or what?
Thanks!

Hello,
same over here:
If I use lineageOS (lineage-17.1-20200720-UNOFFICIAL-sanders.zip - see https://forum.xda-developers.com/showpost.php?p=83100891&postcount=24), the phone gets stuck in bootloader screen when encrypting the phone (I let it run for 12 hrs). The same applies to HavocOS.
If I use EvolutionX (EvolutionX_4.6_sanders-10.0-20200810-0503-OFFICIAL.zip - https://forum.xda-developers.com/mo...nt/rom-evolution-x-4-0-moto-g5s-plus-t4031813), the phone gets into a reboot loop, once I order it to encrypt.
I've also tried an earlier version of lineageOS (lineage-17.1-20200105-UNOFFICIAL-sanders.zip), which used to work since February 2020 - with encryption but without any hazzle.
Any ideas on that?
I've tried it with
twrp-sanders-r20.img (twrp-3.2.1-r21) and twrp-3.4.0-0-sanders.img (twrp-3.4.0).
What is also strange: even if I format the system/data partitions, the phone still has the Microsoft Exchange services installed (I installed them during this entire mess, since I'm required to use it for company access). I thought, I should have been removed by formatting the phone... not?
Thanks a lot.
kniffte