Database Users

Tablet unusable (systemUI crashloop) after the OTA 5.0.2 > 5.1

Well, what a surprise.
After sideloading the OTA (as usual, no errors or anything strange) and waiting for the "Updating android app 1/1xx", the screen goes black. I can't do absolutely anything but to press the power on button to turn on/off the screen (which is black illuminated), and if I hold the button I clearly see the "Power Off?" message in the white box as usual over the black background, and the animation of "Android is turning off" if I turn it off..
Sometimes a SystemUI error appears and after pressing OK it reappears again and again, sometimes showing the live wallpaper behind it. It ends up with an infinite loop of SystemUI crashes.. It may be a prob loading the launcher? it's not even showing status/navigation bars..
This sideloading the OTA on an stock N7. Really google??
When cleaning cache on recovery, it does the updating apps again, then shows for few secs that some app failed and goes black again.
This N7 is stock with the bootloader locked, any way to fix this without needing to unlock (and so wipe)?
Thanks in advance.
EDIT: I'm definitely in a SystemUI crash loop. Even rebooting to safe mode doesn't work at all.

MD5?
I've just downloaded the OTA myself, and thought I'll check out xda just to be sure there is nothing to worry about, and then I see This!
First thing ofcourse would be to make sure the OTA file was not incomplete/damaged. Would you mind confirming the MD5 you've got? Mine is "d394ba9a61f8f6a206b8c427844b5427", file size 106,509,760 bytes.

Silver-Hawk said:
I've just downloaded the OTA myself, and thought I'll check out xda just to be sure there is nothing to worry about, and then I see This!
First thing ofcourse would be to make sure the OTA file was not incomplete/damaged. Would you mind confirming the MD5 you've got? Mine is "d394ba9a61f8f6a206b8c427844b5427", file size 106,509,760 bytes.
Click to expand...
Click to collapse
Hello,
Using "HashMyFiles",
MD5 is d394ba9a61f8f6a206b8c427844b5427,
SHA1 is 9f163586073265c54d86679efd63513a4477cfd8.
Size: 106,509,760 bytes
So yeah, good download file.
And there is no problem with the cable or "Minimal ADB and Fastboot" version since I used it to flash the partitions directly in my other N7 (rooted and such) and also tested applying the N5 5.1 OTA on my N5 and both results were good.
There is no bad stuff here, the REAL file ota 5.0.2 to 5.1 "semi-bricked" my not rooted n7 in 5.0.2..
Google really has QA? I still don't believe an ota did this to a pure n7 stock rom that used otas since the real first 4.1 build to these days.

S**t happens!??
Well, don't know what happened in your case, but all I can tell here (for someone else in a similar situation maybe) is that it worked perfectly fine for me. I updated using adb sideload on a totally stock device as well. Never rooted, no custom recovery, only difference being mine was already bootloader unlocked (don't know if that's why it didn't work for you, though I doubt it). Unlocking the bootloader was the first thing I did out of the box actually, for situations exactly like u're describing.
As for you, I hope it's still being recognized on USB connection so you can pull most of your data atleast. All the best

adb logcat gives me:
[ 03-12 20:52:48.421 29480:29480 E/AndroidRuntime ]
FATAL EXCEPTION: main
Process: com.android.systemui, PID: 29480
java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.android.systemui.statusbar.phone.PhoneStatusBar.isKeyguardSecure()' on a null object reference
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.isCameraDisabledByDpm(KeyguardBottomAreaView.java:260)
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.updateCameraVisibility(KeyguardBottomAreaView.java:237)
at com.android.systemui.statusbar.phone.KeyguardBottomAreaView.onFinishInflate(KeyguardBottomAreaView.java:168)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:814)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:916)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.parseInclude(LayoutInflater.java:916)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:802)
at android.view.LayoutInflater.rInflate(LayoutInflater.java:809)
at android.view.LayoutInflater.inflate(LayoutInflater.java:504)
at android.view.LayoutInflater.inflate(LayoutInflater.java:414)
at android.view.LayoutInflater.inflate(LayoutInflater.java:365)
at android.view.View.inflate(View.java:18532)
at com.android.systemui.statusbar.phone.PhoneStatusBar.makeStatusBarView(PhoneStatusBar.java:638)
at com.android.systemui.statusbar.phone.PhoneStatusBar.addStatusBarWindow(PhoneStatusBar.java:3047)
at com.android.systemui.statusbar.phone.PhoneStatusBar.createAndAddWindows(PhoneStatusBar.java:3043)
at com.android.systemui.statusbar.BaseStatusBar.start(BaseStatusBar.java:561)
at com.android.systemui.statusbar.phone.PhoneStatusBar.start(PhoneStatusBar.java:588)
at com.android.systemui.statusbar.SystemBars.createStatusBarFromConfig(SystemBars.java:106)
at com.android.systemui.statusbar.SystemBars.onNoService(SystemBars.java:58)
at com.android.systemui.statusbar.ServiceMonitor.startService(ServiceMonitor.java:228)
at com.android.systemui.statusbar.ServiceMonitor.access$000(ServiceMonitor.java:49)
at com.android.systemui.statusbar.ServiceMonitor$1.handleMessage(ServiceMonitor.java:73)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.app.ActivityThread.main(ActivityThread.java:5254)
at java.lang.reflect.Method.invoke(Native Method)
at java.lang.reflect.Method.invoke(Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:903)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:698)
[ 03-12 20:52:48.425 468: 484 W/ActivityManager ]
Process com.android.systemui has crashed too many times: killing!
Silver-Hawk said:
Well, don't know what happened in your case, but all I can tell here (for someone else in a similar situation maybe) is that it worked perfectly fine for me. I updated using adb sideload on a totally stock device as well. Never rooted, no custom recovery, only difference being mine was already bootloader unlocked (don't know if that's why it didn't work for you, though I doubt it). Unlocking the bootloader was the first thing I did out of the box actually, for situations exactly like u're describing.
As for you, I hope it's still being recognized on USB connection so you can pull most of your data atleast. All the best
Click to expand...
Click to collapse
Yeah I saved all the stuff via adb, but it SUCKS to have to format because an OFFICIAL OTA did this. Thanks mate!
And I now recognize the error of not having the bootloader unlocked. I NEVER suspected to get in such a situation only sideloading otas on a device never unlocked. Google really fails at delivering an stable platform.

Have same problem after sideload update. No root, no unlock and same problem in the logs. I have updated wife's nexus 5 and it works well, but mine stuck on start-up.
Any ideas how to fix it w\o full wipe ?
---------- Post added at 11:20 AM ---------- Previous post was at 10:24 AM ----------
Btw @RusherDude, have you used something like 'Lockscreen Policy' app to disable camera or lock screen ?

Kaspian said:
Have same problem after sideload update. No root, no unlock and same problem in the logs. I have updated wife's nexus 5 and it works well, but mine stuck on start-up.
Any ideas how to fix it w\o full wipe ?
---------- Post added at 11:20 AM ---------- Previous post was at 10:24 AM ----------
Btw @RusherDude, have you used something like 'Lockscreen Policy' app to disable camera or lock screen ?
Click to expand...
Click to collapse
Same prob? So we may not be alone on this.. Google really messed up this OTA.
No, I didn't do anything of that to this N7, it was pure stock lock screen and nova launcher.

@Kaspian
EDIT:
Yes now I remember I had one from the 4.2 times, Lockscreen Policy
https://play.google.com/store/apps/details?id=com.wordpress.chislonchow.deviceadminkeyguard&hl=es
Now I should be able to uninstall it via adb but I get this:
adb uninstall com.wordpress.chislonchow.deviceadminkeyguard
Failure [DELETE_FAILED_DEVICE_POLICY_MANAGER]
Checking the doc:
static int DELETE_FAILED_DEVICE_POLICY_MANAGER
Uninstall return code
uninstall fail if the system failed to delete the package because it is the active DevicePolicy manager.
Any way I can delete this app or deactivate his DeviceAdmin status with ADB and no root? :S I can't find any way.. this is frustrating.

I'm not sure uninstall will help now. I think you need to revert the changes made by "Lockscreen Policy".
I didn't find the solution quick enough and just wiped my nexus 5

Kaspian said:
I'm not sure uninstall will help now. I think you need to revert the changes made by "Lockscreen Policy".
I didn't find the solution quick enough and just wiped my nexus 5
Click to expand...
Click to collapse
It seems that I just need to disable it from the Device Admin rights window (the same reason why you need to disable its device admin rights before uninstalling it normally), but the prob is seems that there is not a way to do that without UI interaction. I can lauch the system activity or even the device admin activity from ADB, but I don't see them in the tablet so I can't interactuate.
It is really, really frustrating. This is the last non-rooted Android device I own, for sure. What a traition....

Yep, this time I unlocked bootloader also...

Kaspian said:
Yep, this time I unlocked bootloader also...
Click to expand...
Click to collapse
Same, just wiped it, unlocked the bootloader and rooted it.. never had this intention but it's terrible that on Android you're forced to wipe because an OTA made an app ruin the tablet (and thank god I had ADB debugging enabled before, otherwise I even wouldn't had be able to save the data via ADB before wiping), it's incredible, Google epic sucks compared to Apple on this.

RusherDude said:
And I now recognize the error of not having the bootloader unlocked. I NEVER suspected to get in such a situation only sideloading otas on a device never unlocked. Google really fails at delivering an stable platform.
Click to expand...
Click to collapse
if you go to the android factory image website
https://developers.google.com/android/nexus/images
in the flashing instructions they give you they specifically tell show and tell you to unlock the boot loader before applying an update. after the update they also instruct you on how to lock the bootloader again. do not start to bash google because you do not follow their instructions.

phrozenstare said:
if you go to the android factory image website
https://developers.google.com/android/nexus/images
in the flashing instructions they give you they specifically tell show and tell you to unlock the boot loader before applying an update. after the update they also instruct you on how to lock the bootloader again. do not start to bash google because you do not follow their instructions.
Click to expand...
Click to collapse
I was NOT flashing a factory image, I was SIDELOADING an OTA.Nothing to do with that.
In fact, my problem would be reproduced if anyone being pure stock on 5.1 downloaded that app and gave it device admin.

Possible way to save any bricked Nexus device!

Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!

That explains why the OTA for the N preview was the same size as the image, and why after upgrading to March security release I didn't have to download a different OTA to get to N

So is this usable in all situations? If yes then should download it & store it safely

Interesting thing, can this update bypass factory reset protection?

iluvatrix said:
So is this usable in all situations? If yes then should download it & store it safely
Click to expand...
Click to collapse
I would assume this could be used in any situation where you have a paper wait. So say you're on marshmallow build and somehow things go wrong ,bootloader locked USB debugging not check ,with this ota you can still sideload but it will be an N build which is fine at least you'll have a working device that now you can revert back to your original build. So I'm keeping this as well. I really don't need to but its nice to have just in case. I normally keep my bootloader unlocked at all times anyways just in case things go haywire... Someone correct me if I'm not correct please. Have a nice weekend all?
---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------
Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Good question..

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
Most likely not, because normally when receiving an OTA all of that remains intact but, I think it's worth a test.

This will NOT bypass factory reset protection. This is just an update.zip that is a signed "FULL" image rather than a "DIFFERENCE" image. That means that it just doesn't need to perform the verification step before proceeding to install the update.
There is also another "problem" with relying on these as the ultimate unbrick files, which is that if you happen to install some official build that is NEWER than N-pre1, then the recovery will refuse to "downgrade". So while it may be useful for now while nobody is running anything newer than N-pre1, it isn't a permanent solution.

This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish

Displax said:
Interesting thing, can this update bypass factory reset protection?
Click to expand...
Click to collapse
doitright said:
This will NOT bypass factory reset protection.
Click to expand...
Click to collapse
The first N preview apparently has a bug that will allow a user to bypass FRP (if they are on the first N preview)
http://www.androidpolice.com/2016/0...ory-reset-protection-workaround-on-android-n/

flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
I'm glad to hear it worked for you

Works for me boss
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:

mowgli762 said:
Thanks for finding this one - one of my 6's was soft bricked ( could only get to fastboot or recovery etc. could not complete reg. boot after signing up for android beta program OTA ).
I was able to ADB sideload the system OTA as described without a hitch. All data / set-up on phone was intact and functional.
Just for the record this Nx6 was only bootloader unlocked - no other mods/changes prior to original Beta OTA.
:good::good:
Click to expand...
Click to collapse
Why didn't you just flash the system.IMG if the bootloader was unlocked?

holeindalip said:
Why didn't you just flash the system.IMG if the bootloader was unlocked?
Click to expand...
Click to collapse
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).

mowgli762 said:
I could have but I don't have any experience with flashing system images and retaining my settings and data (removing the wipe command in the batch file if I remember correctly).
I was pleased just to be able to handle it as an OTA instead. When I'm working at/near my experience limits I try to take smaller chances. I know working with a alpha release is risky and I'll face the consequences at need. Must have been a considerable number of folks in the same boat as me for Google to have come up with a lower skill level solution (for the likes of me).
Click to expand...
Click to collapse
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.

holeindalip said:
Download the system image
Extract system.img
Fastboot flash system system.img
This will retain all data on phone
Your boot loader is unlocked so...
A. You used a toolkit and don't know the commands that the toolkit uses
B. You bought the phone used with an unlocked bootloader
Toolkits are for just ease of use if you already know the commands , because if you unlocked your bootloader manually this is a simple 5 minute fix if the factory image is already downloaded. sorry for the rant not trying to be rude, just enlightenment.
Click to expand...
Click to collapse
Good - case specific information needs no apology - Diplomacy has never been alluded to as being in my skill set (too much glass in my house to throw stones).
Thanks for your interest and info.

TriguyRN said:
Hey XDA,
I think google may have just created a way to save any nonbootable bricked nexus with recovery access. Due to some N OTA failures, they just released a side-loadable OTA through recovery. This OTA is actually a full system image and from what I am reading it can be used to saved any bricked device that won't accept another sideloadable OTA. Here is the reddit post and the AP article on it.
https://www.reddit.com/r/Android/comments/4a0ox6/marshmallow_ota_hose_your_nexus_device_just_flash/
http://www.androidpolice.com/2016/0...t-bricking-some-devices-but-google-has-a-fix/
Good luck guys. I would love to see some success stories here if it works for you and if so, spread the word!
Click to expand...
Click to collapse
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
flash4yish said:
This is a ligit Fix. Confirmed by me.
Only thing I did different was to use an app called "Nexus Root Toolkit v2.1.4"
Upon launching the app (and there was plenty of prep to get it going on my Windows Vista laptop-my Mini Mac had problems loading in VMWare as WIndows XP so it did not work for me on a Mac)
I clicked on the "Advanced Utilities" section and clicked the "Launch" Tab.
The Advanced Utilities has a section called "Sideload OTA Update", I then clicked on "Sideload Update" and followed the instructions.
It pretty much asked me to select the file location of the Google Patched Image file called "shamu-ota-2659757-073c33ae.zip" (which stays zipped-do not extract it).
Then I followed the instructions on the screen. It did take me several attempts to get right, but in the end it worked as stated... I was so tired of trying to get this work for the last 7 days that I got lazy and despirate and did not take the time to read the instructions on the Nexus Root Toolkit. I had already filled an insurance claim for this because I was sure I could not get this phone back from this problem.
The trickiest issue I had was getting to boot the device into "Recovery" "ADB Sideload" because when I switched it to ADB Sideload, it would stop seeing the device. This is obtained by Power Down, Press Power and Volume Down at the same time, this brings up the Boot menu. You have to use the volume keys up or down to select "Recovery" and press Power again to select it. After about 3 or 4 seconds you see the Dead android with the Red Exclamation Point. That is what you want. Next Press Power and Volume Up, quickly release both and Press the Volume up again. You will finally see the Recovery screen where you will find the "ADB Sideload" option. This missing tidbit I was able to find at the Motorola Nexus Support page.
So, Yes. this worked for me! ...and I am going to cancel that insurance claim after all. :good:
Thanks again to whoever posted this and Google for being man enough to make things right for all the people that got in too deep with this "N Preview" gone wrong.
flash4yish
Click to expand...
Click to collapse
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .

atef79 said:
Man you are life saver i donno how to thank you
you saved my nexus 6p with this post , i sent my problem about 2 months ago in nexus 6p question and answer about my device which bricked while installing the ota update with looked bootloader and have tried everything to save it but noway you are the hero who saved it XD
(btw my device is nexus 6p and it worked )
i really appreciate your help and sharing your information
thanks
---------- Post added at 01:52 AM ---------- Previous post was at 01:46 AM ----------
thanks buddy for sharing your experience
i tried to sideload the ota file by sdk from stock recovery and apply ota from adb manually by command adb sideload (filename)
but it stopped at 89% , so i give shot to your way and it works fine by the toolkit so i have to thank you too .
Click to expand...
Click to collapse
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face

TriguyRN said:
The best way to thank me is sharing your experience and this thread to help people in need. Already put a smile on my face
Click to expand...
Click to collapse
I already shared your post in my topic that I made in the Nexus 6p section to help all who bricked there devices with locked bootloader, and thx again .
This is my topic link
http://forum.xda-developers.com/nexus-6p/help/command-t3308390/post66086939#post66086939

just want to ask would this method work if the phone has not been authorized to a specific PC ?

iluvatrix said:
just want to ask would this method work if the phone has not been authorized to a specific PC ?
Click to expand...
Click to collapse
I'm not sure what you mean by "if the phone has not been authorized to a specific PC". As far as I am aware Android phones are not authorized to a PC, that is an Apple thing...

Encryption unsuccessful

Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.

laofan said:
Running on stock 6.0.1 MMB29M
locked bootloader
after recovery reset, the phone went into " Encryption unsuccessful" screen. Even after press reset or do factory reset in recovery again, the phone still bootloop into this page.
Could someone help?
Thanks.
Click to expand...
Click to collapse
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...

Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
5.1 said:
Hello... Try sideloading a full OTA of your choice from here: https://developers.google.com/android/ota#angler
It needs to be newer than the installed version. Not sure it will solve your issue though. Maybe someone else will chime in with a better solution...
If nothing works, RMA your device.
Good luck...
Click to expand...
Click to collapse

laofan said:
Thanks for the advice.
I tried to manually flash OTA but it falied because of the locked bootloader.
I am not sure if there is anyone could point me to do it via ADB. I tried using ADB but the phone is not recognized by my computer yet.
Click to expand...
Click to collapse
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...

I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
5.1 said:
Hey...
Reboot into Bootloader. Select recovery mode with the volume rocker and press power.
Once you see the Android guy laying down with his belly opened, press power and tap volume up once.
On the menu select: apply update from ADB
From here type in a command prompt:
adb sideload "name of the full OTA zip you downloaded without quote"
Supposing you have prior knowledge with ADB. Let me know if something is not clear here...
Good luck...
Click to expand...
Click to collapse

laofan said:
I finally get ADB recognized Nexus 6p. But the ota stop flash at 46%. failed to read command: No error.
Click to expand...
Click to collapse
You might have to RMA. I believe "no command" means the emmc has died.

dieselbuddeh said:
You might have to RMA. I believe "no command" means the emmc has died.
Click to expand...
Click to collapse
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..

laofan said:
That is too bad. The warranty was expired in January.... It can't be RMA.... I wished there are some hopes there
Click to expand...
Click to collapse
If you bought the phone direct from Google, you will likely get a one time exception.

v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.

5.1 said:
Hello...
Try sideloading the 7.1.2 OTA. Nothing to loose... If it fails yet, sorry, I don't know what else to do.
Good luck..
Click to expand...
Click to collapse
I almost tried all the major OTA, none of them could pass 46%... oh well......
v12xke said:
If you bought the phone direct from Google, you will likely get a one time exception.
Click to expand...
Click to collapse
tommyg562000 said:
Yes, call them anyway if you purchased from Google. I was 5 months out of warranty for my 6p and they replaced it because I was having battery issues.
Click to expand...
Click to collapse
It is not from google. And the warranty ended in January... I am fxxked.....

Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.

v12xke said:
Probably so. There is one guy who found a 6P with a shattered screen for sale and paid a local repair shop to have the motherboard swapped out. Claims it cost him less than USD $100 but he is in South Korea. You're probably better off cutting your losses and finding another phone... after Huawei tells you NO three times.
Click to expand...
Click to collapse
posted it on craigslist now.
( I noticed that you are in the Woodlands area. I missed the time when I am in Houston. One of the best memories)

just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.

laofan said:
just a follow-up to somebody might see encounter the same thing. I was not able to fix the phone.
With a locked bootloader and "encryption unsuccessful" page, you might try warranty first. If that does not work, you might want to take rescue OTA from google and flash it in recovery via " install update via ADB".
Please be aware that rescue OTA is different from system image and should be flash via ADB in recovery.
Good luck.
Click to expand...
Click to collapse
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...

5.1 said:
Hello,
What rescue OTA? Something different than the usual OTA you would sideload with ADB?
Cheers...
Click to expand...
Click to collapse
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)

laofan said:
Here are Rescue OTA. One would need to flash it with ADB in recovery. https://developers.google.com/android/ota
The following one is firmware/factory image. One would need to flash it with fastboot while in bootloader mode : https://developers.google.com/android/images
Use the correct zip file according to your flashing mode ( recovery or bootloader)
Click to expand...
Click to collapse
Hello,
I see nothing different than hmm an OTA here. I thought that was a "special" OTA, but no.
Not sure why it's called rescue OTA, lol.
Thanks for the links, but i know exactly what an OTA and a factory image are. :good:
Thanks...

Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!

fredmoro said:
Hello!
I have the same "Encryption unsuccessful" issue. It happened many times recently. First I replaced the battery, because it produced early sudden shutdown at 30-40%, and could run only for a few hours from 100% to 40%.
The new battery is enough for 30-40 hours as I use it, and can operate the phone down to 1-2% before shutting down.
But if I have to restart the phone, the encryption unsuccessful problem still comes up randomly after battery replacement. I can restart several times without problem, then randomly just fails. Mostly after software updates I guess... I have stock firmware, stock rom, etc. the only thing was made that I have installed TWRP, and wiped user data. Hope that helps. Can it be the defect of the emmc ? If so, how shall I diagnose it?
I'm very newbie android user, I changed from Windows Phone ( ) only a few months ago...
The question is what could cause the Encryption unsuccessful error? It's interesting, that if I enter any random numbers as unlock code, the phone tells that it appears to be valid, but unfortunately cannot decrypt data.
So I would like only to disable forced encryption, maybe that helps. Could someone point me to the right direction about what exactly should I do? Is it enough to flash a modded kernel to disable encryption? I don't want to root, or experiment with custom roms and I would stick to the factory firmware as much as I can, but without encryption of corse...
thanks!
Click to expand...
Click to collapse
Same. The data decryption being unsuccessful happened to me as well on stock oreo 8.1.0. not rooted
Anyone know how to fix it and doesn't happen again?
Thanks

[TOOL/UTILITY] Script to fix bootlooping Nexus 5X / Nexus 6P for Android O and lower

Script to fix the Nexus 5X / Nexus 6P Bootloop problem
Credits
99% credit goes to @squabbi for teaching how to patch files yourself and @XCnathan32 for discovering the fix itself.
1% for me for making the script .
DISCLAIMER
THIS PROCESS WIPES ALL YOUR DATA (unless your bootloader is already unlocked) AND PROBABLY YOUR WARRANTY TOO! USE WITH CAUTION! I AM NOT RESPONSIBLE IF YOU BRICK YOUR PHONE!
THIS PROCESS WILL MAKE YOUR PHONE SLOWER (6P 2 times slower, 5X 1.5 times slower)! PLEASE USE ONLY AS A LAST RESORT!
PLEASE CONTACT YOUR WARRANTY TO TRY AND GET A REPLACEMENT BEFORE PROCEEDING!
What does the fix do?
The problem with those phones are the cores of the Cortex A57, and they need to be disabled.
What should you do?
Before proceeding, make sure you have OEM Unlocking enabled on your device, or the flashing won't work!
1. Download the zip below
2. Extract the zip
3. Extract the boot.img from the image you've downloaded (the script explains how to do it if you don't know how) to the folder you've downloaded
4. Open "Script.bat"
You should also download a factory image from this link (unless you live in Japan, don't download the Softbank versions, and unless you live in Australia, don't download the Telstra versions):
6P - https://developers.google.com/android/images#angler
5X - https://developers.google.com/android/images#bullhead
The script itself was not tested, but the method did work on my 5X so it should work.
If you have any requests, you can comment them here, and maybe I'll add them. One day.
I do plan on adding TWRP, Elemental X and Magisk patching one day, and if there will be many requests that day will come earlier.
Links to original posts and videos
https://forum.xda-developers.com/nexus-6p/general/guide-tutorial-nexus-6p-bootloop-death-t3716330
https://forum.xda-developers.com/nexus-5x/general/untested-nexus-5x-bootloop-death-fix-t3641199
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279
https://youtu.be/PhObuifEp3Y

I get error of adbwinapi...What can I do? (N5X)

Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it

R3tro7 said:
Hey! I've changed the post and the script a bit, so please follow the new steps and download the new script, but can you please explain more of what and when happened?
EDIT: I think I know what happened, but please try the steps above, and if they don't work tell me and I'll try and fix it
Click to expand...
Click to collapse
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.

Yea, it did that for me too and then booted

Mehr_DaD said:
Thanks, I did the new script and it's kinda getting too long on that boot (circle things) screen. I hope it gets to "android" thing in the end
So I flashed the March rom, It stuck on those circle things. Turned it off to cool down a bit and will power on in an hour. Let's see what happens next.
Click to expand...
Click to collapse
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.

R3tro7 said:
For my 5x, it booted, but then I've tried to update, but it started bootlooping again, so I've flashed it again and again with no luck. Then I've turned the phone off for some time to cool down, and after that when I've powered it on it just magically worked, and is working since.
Click to expand...
Click to collapse
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!

Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Click to expand...
Click to collapse
I'm glad to hear! If you could please "Thank" the post, it will be much appreciated. For your question, I haven't used my script on my phone, I've just followed the steps in @squabbi 's video, and then I've decided to create an automated script (which is the script in this thread) to patch it automatically. Which basically means, yes, I have flashed a BLOD "workaround" patch.

Mehr_DaD said:
That's a good news! Mine just loaded to Homescreen and I don't want to mess with it this time, Turned on Wifi and it didn't restarted, inserted sim and didn't restarted. I hope it never freezes again. Thanks again. By the way did you flashed any recovery, kernel, BLOD "workaround" patch or just your fix script?
Update: Again, As soon as I login my Google account and went to Play Store to turn auto update thing off, the phone froze!
Click to expand...
Click to collapse
Still frozen?

R3tro7 said:
Still frozen?
Click to expand...
Click to collapse
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?

Mehr_DaD said:
Did system wipe from recovery and after some time (Cooling down process!) it boots again and this time I didn't entered my google account. However it freezes time to time even though I've only installed Telegram & Instagram. Is it ok?
Click to expand...
Click to collapse
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.

R3tro7 said:
When you say freezes do you mean that it lags?
I guess that's ok, as you've disabled the cores, it should get slower. And please (I don't know if you've done that, but I'll still say) NEVER disable oem unlocking on this phone, because maybe it will happen again.
And by the way, I'm a newbie. I've just made a script that automates the patching process but I don't really understand that much about it. I would recommend you (and that's what I've done) to download the newest image, open the flash-all.bat file to flash it onto your phone (this will wipe everything, and install the newest version), power your phone on (it should start bootlooping again) once, and then do what you would do (boot to bootloader, run the script). Maybe the problem is that you've downloaded a wrong version of the boot.img (that means that you haven't downloaded your version, but the newest one. What I just said insures that you flash the right one). To check the right version, go to about > build number, and where you download your image, search for the exact build number. If the problems continue, maybe it's the script. I'll patch the files myself and send them to you. And if all of the above doesn't work, I will redirect you to @XCnathan32 or @squabbi, they will probably help you more.
Click to expand...
Click to collapse
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...

Mehr_DaD said:
No it just freezes for 3 to 5 seconds and then the phone restarts. But the boot image is also from march update...
Click to expand...
Click to collapse
Please try to do what I've said

R3tro7 said:
Please try to do what I've said
Click to expand...
Click to collapse
Flashed the March ROM again. Used the script and it successfully installed. On the first boot it stuck on those 4 circles. Sounds like cooling down is the only answer. I can't use my phone constantly :/

Mehr_DaD said:
I get error of adbwinapi...What can I do? (N5X)
Click to expand...
Click to collapse
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.

theBeachBoy said:
Same here, I get an error
After selecting that I am unlocked...
The pop up is fastboot.exe - syetem error
The code execution cannot proceed because AdbWinApi.dll was not found. Reinstalling the program may fix this problem.
It does pop up a second time after you click ok...
and then your script says it's done.. but it's not.
=====
I added the dll whicih can be found in the adb tools, I don't get the pop up but then your script says "waiting for any device" so there is something wrong somewhere as my phone is plugged in, and ready.
Click to expand...
Click to collapse
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.

R3tro7 said:
I fixed the AdbWinApi.dll error, download the script again and tell me what happens. Maybe the original fastboot.exe in my zip was a different version of the AdbWinApi.dll that you added and that's why it didn't work.
Click to expand...
Click to collapse
the script worked.
Now should I flash TWRP 4 core recovery (edit seems so) and use the AK injector or not needed?
What is Elemental X?
p.s. Thanks!

theBeachBoy said:
the script worked.
Now should I flash TWRP 4 core recovery and use the AK injector or not needed?
p.s. Thanks!
Click to expand...
Click to collapse
I'm glad it worked. There is no need to flash TWRP and use the AK injector as you've already flashed a 4 core boot image. If you want, you can flash 4 core TWRP, but that's optional.

Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.

theBeachBoy said:
Last question hopefully.
I have tried sooo many things to fix this phone, unblod thing, flashing various files and the boot-safe.img, twrp 4 core, AK injector, factory image, in various order and multiple times. None of them worked, well unblod worked but no WiFi and when I fixed WiFi, BLOD restarted...
Is there a way the phone needs to be for the script to work? Factory image I guess?
Your script worked, but now at the Google logo stuck there. Not sure I should force reboot or wait. I't not in bootloop but doesn't move past the Google logo.
Click to expand...
Click to collapse
I did a quick search and some website said try resetting the phone. If that doesn't work, try to flash a factory image to make it bootloop again, and try the script. If all of that doesn't work I suggest asking @XCnathan32 or @squabbi because they probably understand it better than me.

Your device is corrupted. It can't be trusted and ...

After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???

azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724

azzinder said:
After rooting and decrypting OP6T complains during boot about a corrupted device that may wont work properly....
This is not a problem: If the power key is pressed as indicated by the error message the device boots properly.
But that is exactly the problem!!!
If not pressed then nothing happpens!
Thats mean that it wont boot for example after a reboot...
Tried to clean install latest rom at both slots -via fastboot, via twrp, via system update-, tried factory reset, tried re-encrypt, even locking the bootloader again...
Does anybody have any idea about how to fix it???
Click to expand...
Click to collapse
You're not waiting long enough.
And by the way it tells you to press the power button to PAUSE booting.
It's only a few second wait (possibly one second longer than the default unlocked message on other devices). I just timed it. It's 8 seconds. A regular device will display that message for 3-4 seconds.
It just means that your bootloader is unlocked.
Sent from my ONEPLUS A6013 using Tapatalk

genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
Had this issue on my op6. This solution fixed it for me. not sure if we have this tool for the 6t yet. If the message is orange then it's the unlocked bootloader message. If it's in red it's the corrupt message and you gotta hit the power button twice to boot.

The message i get is in RED color. Not in ORANGE.
And yes if you press twice the power button it boots normally.
My question is about how to get rid of this!!!
If for some reason the device is gonna reboot -like in Settings-> Utilities-> Scheduled power on/off- it wont boot until I get action...

Fear!!!
genbu said:
I remember seeing this long time ago.
You can take a look at this, maybe it will apply to you as well
https://forum.xda-developers.com/oneplus-6/how-to/pie-how-to-fix-device-corrupt-boot-t3841724
Click to expand...
Click to collapse
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!

I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.

azzinder said:
I am thinking to try this solution but i am scared...
This tool is gonna try to install Oxygen os Oreo for the OP6 as far as I understand.
But the OP6T never had this.
I wonder that maybe it wont boot after process and if it boots gonna refuse to upgrade to Oxygen OS Pie for OP6T
:confused
***Just found the OP6T version here***
As soon as i find a pc with Windows installed i'll try it!!!
Click to expand...
Click to collapse
And password

iaTa said:
I have the same issue and have a remote session booked with OP support today.
Hopefully I will be able to grab a copy of MSMTool for the 6T and share it.
Click to expand...
Click to collapse
Waiting patiently for news...

azzinder said:
Waiting patiently for news...
Click to expand...
Click to collapse
Rescheduled to tomorrow

https://forum.xda-developers.com/oneplus-6t/how-to/tool-6t-msmdownloadtool-v4-0-oos-9-0-5-t3867448
Done

Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter

This works! It is a lot easier than the MSM download tool solution. However, I wonder if it just mutes the notification, or solves the problem indeed?
I flashed a TWRP backup afterwards and that did not go well. I wonder if that could be caused bij the corrupt problem?
[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Doesnt working for me. after reboot also i can see same error. however i can boot after twice pressing on power. i do not want to use Msm tool as it will format data. seems no other way as of now

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Hey that's amazing! I think this has finally solved this for me on my OnePlus 6. I was perfectly content to just put up with that warning forever, but this seems to have cured it ... And simple too! Thanks ?

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
Thanks, this worked.

That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.

vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.

vikram.mohal said:
That is only for hide your message. But device is still corrupted. You have to relock your bootloader for that problem.
Click to expand...
Click to collapse
No the device is not corrupted. Unlocked bootloader warning vs the device is corrupt are 2 different things. My bootloader ia unlocked since the day 1 and never had the corrupt warning until I flashed OOS 9.0.5. The step above resolved the device is corrupt issue.
---------- Post added at 07:26 AM ---------- Previous post was at 07:22 AM ----------
kitcostantino said:
i had this happen when i went to update to 9.0.13. ended up backing up to usb otg, reflashing the full update via msm tool, and having to unlock bl again, reflash twrp again, installing magisk again, etc. then, and only then was my device no longer corrupt. i tried many things prior to that, but this was my only fix long term.
ive heard its die to A/B having different security patches, but reflashing both A/B with stock full 9.0.13 did not stop the issue. only msm tool reflashing to 9.0.12 did. and i then did the same on my second partition for good measure.
as far as trying to run decrypted, unless im remembering wrong, unlike the op6, the op6t will not abide that without the corrupted message unless i missed progress. id love that personally, but last i had read here it made op6t unstable. which sucks bonkey dalls.
Click to expand...
Click to collapse
Yeah I agree its something to do with the slot A and B. I was running the phone with unlocked bootloader since day 1 and had flashed multiple twrp updates, kernels etc and never had the issue. It's when i recently flashed OOS 9.0.5 and then twrp on it is when this started.
Not sure about OP6T but on my OP6 the terminal commands helped.

[email protected] said:
Just type in terminal
su
reboot "dm-verity enforcing"
Hit enter
Click to expand...
Click to collapse
This worked on my 6T ! Thanks !