So.. first of all, I want to say that I am a complete no0b when it comes to bootloader unlocking/rooting/etc... just putting that out there..
So I just unlocked the bootloader on my m7, and everything went fine, until I actually turned on my phone again...
The first thing that shows up is a screen that tells me to enter my password to decrypt my device, even though I have never encrypted it.
Any password entered results in a screen saying:
Decryption unsuccessful
The password you entered is correct, but unfortunately your data is corrupt.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed to your google account.
I have tried to factory reset my phone in recovery mode, however it just returns an error message saying that it cant mount /data, and only formats /cache.
When I restart, I get the same 'Decrypt Storage' screen as before...
Is there ANY way I can solve this?
I have absolutely no clue :/
As I said, i'm just a noob
I dont care about any lost data, I just want a usable phone :/
I think I just solved it!
Installed twrp, formatted, rebooted, and everything is chill!
Glad I solved that...
how did you do it
hi im adrian
i to have the same problem with my daughters phone can you help maybe write a how to do it for me.
i would be so greatful its doing my head in lol and my daughter lol
thanks
adrian
my email. [email protected]
[InsertNameHere] said:
I think I just solved it!
Installed twrp, formatted, rebooted, and everything is chill!
Glad I solved that...
Click to expand...
Click to collapse
I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
hachamacha said:
I've now installed TWRP (of this flavor : twrp-3.0.2-1-oneplus3t.img ), and supersu after updating firmware to 3.5.3 on the 3t I received yesterday. It installs without problem. I've not touched encryption and I'm very wary of using TWRP at the moment, because it always asks me for the encryption password. When I initialized the phone after this setup, the only password/entry entities I entered were a) a 4-digit pin, and b) 3 fingerprints. They work fine.
When I try to boot to TWRP, I always am prompted for a password immediately. I have no idea what the password is, and have tried my known-to-be-correct PIN , no luck. I have tried hitting cancel, and then only if I agree to mount /system as RO can I enter TWRP without it trying and failing to decrypt everything which corrupts storage.
I've read the entire (TWRP) thread a couple of times, but maybe it was too late at night. I'm wondering if anyone can tell me what step I'm missing, or if I'm trying to do something that can't be done because of what was just said above (encryption isn't fully supported by TWRP yet?) , or if I just should know the password and let TWRP decrypt it. Finally, is there a way to just decrypt the phone while booted and is that even called for?
I'd like to use TWRP which seems fine in every other respect (well, I don't yet know if I can make a backup & restore, so that isn't fine), but am held up by the password entry at the start of each session. Many thanks for getting it this far and thanks for any help you might give.
Click to expand...
Click to collapse
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
cameljockey1 said:
I would start over. Get the stock recovery and flash it. Then factory reset the phone. Do not put a pin or a fingerprint at all after you have booted to the phone. Go straight to the bootloader and do the twrp flashing instructions. after you have flashed and i believe if you want to be decrypted you format data than flash supersu again. Boot into system and then back to twrp and see if that worked. I remember doing this on my nexus 6p but not sure if the kernel has to support the decryption. remember when you do a back up of your phone never never never back it up with pin or passwords or fingerprint. You wont be able to restore succesfully from my experince with the nexus 6p. make sure you back everything up before doing this and i am not responsible for any problems occured. and make sure you are on the latest update from oneplus. hope this helped
Click to expand...
Click to collapse
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
hachamacha said:
That's exactly how I did it the first time, without password, without setting up phone, and when it got to TWRP (the first time), I was presented with the password prompt. When I hit cancel it went by it, but then said it was decrypting (which I didn't want), and corrupted my storage.
When I reinstalled 3.5.3, I did the same thing again, and that time was not corrupted so I was able to install supersu. At this point I've entered some fingerprints and a pin. TWRP says it supports encryption so I'm wondering about where the password comes from.
Thanks for your quick response. I'm still awaiting some reply over in the TWRP forum as well.
Click to expand...
Click to collapse
Are you sure you had 3.5.3 the first time you did it?
c_86 said:
Are you sure you had 3.5.3 the first time you did it?
Click to expand...
Click to collapse
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
hachamacha said:
Yes, it was the first thing I did. After receiving the 3t, I skipped over all the prompts (to avoid entering accounts, waiting for sw upds and to not enter passwords) and went to software updates and allowed the 3.5.3 update to occur.
Then I did the things described above.
-----
In the interests of my trying to understand everything I'm reading about 6.x and encryption. I'm getting the drift that phones with 6.x + are encrypted as a matter of course. Is that the case (or how do I tell if it is)? If it is by default encrypted, then is there a default password before you have entered any specific pin or swipe pattern , etc?
Another question: When TWRP asks for a password, what exactly does it want to do? Does it want to decrypt the data for it's own operations (so just a twrp-level decryption) or does it actually want to completely decrypt partitions? If so, why? Is that the only way TWRP can work these days with default encrypted platforms?
Thanks.
Click to expand...
Click to collapse
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
ghettopops said:
Flash stock recovery, install stock 3.5.3 zip, flash TWRP beta 3 and then SR4. I went through same problem and this got me in(would accept my phone password. )
Click to expand...
Click to collapse
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
hachamacha said:
Is that the TWRP beta 3 from the TWRP thread? I thought I saw it mentioned in there. Thanks.
I've done the rest once so will give beta 3 a shot before I resign myself to putting the whole thing back together. Not that big a deal I suppose. I finally realized (after reading quite a bit) that 6.x + comes encrypted and that all versions of TWRP don't handle it right, so I suppose there's no easy way around it. (I'm wondering about this link I happened upon: https://www.androidexplained.com/oneplus-3-fix-twrp-restore-unlock-bug/ )
Click to expand...
Click to collapse
Yes page 9 or 10 OP gives me a link
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
This seems to happen when you've got the fingerprint method enabled with PIN or password for that matter.
My experience:
I update from Oxygen 4.1.6 to 4.1.7 with TWRP and something went wrong because the phone stuck in bootload for more then half hour.
I've reboot and it appeared 'Encryption Unsuccessful' and it locked my phone. I tried to go to TWRP and it required the password that was 'default_password' but after it not allowed me to mount data and it seemed that there weren't any data in my phone.
I couldn't wipe, format or install other rom because I received error like 'unable to mount X'.
I've solved downloading the Oxygen Recovery and with a USB OTG, flashing it on my phone (with 'mount image' in TWRP).
I rebooted in Oxygen Recovery and it also asked me the password. I've just pushed 'Forgot password' and it formatted my phone.
The phone rebooted without problems (and without any data :\)
Hope to be useful for someone else in my same situation
You can get back in, without loosing any Data.
Go to TWRP
Choose Advanced
Select Terminal
Type this commands:
Code:
dd if=/dev/zero of=/dev/block//bootdevice/by-name/misc
reboot
Use Android again
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
astralbee said:
I encountered this problem after I updated TWRP to version 3.2.1-0.
I regularly update my rom with TWRP and had never been prompted to enter a pin/password before. My lock screen pin was not accepted.
Seems this issue is a bug in a number of TWRP versions. I fixed it by flashing back to version 3.1.1-2. You can download and flash from a list of historical TWRP versions in Android by downloading the official TWRP app, so I didn't need to mess around sideloading it. Rebooted into TWRP, straight in, no problems.
Click to expand...
Click to collapse
Same problem on one of my 3Ts, the other is working with the Oreo based TWRP.
Oreo based Red Wolf Recovery is working: https://forum.xda-developers.com/oneplus-3/oneplus-3--3t-cross-device-development/recovery-red-wolf-recovery-project-t3805416
These things are weird:
1. Why does one 3T work, but not the other 3T ?
2. Why does (Oreo based) Red Wolf Recovery work?
3. Why is OOS Beta 29 able to decrypt Data perfectly?
I assume it's a decryption related bug in Oreo based TWRP.
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
SourPower said:
im stuck not able to get twrp to see any of my storage and i cant get into twrp twice in a row, so if i fastboot and flash twrp thru adb and then boot into twrp, it asks me for the password, if i hit cancel it just shows 0 storage. ive tried to go to adb sideload but it just sits there. I have the backup i made thru twrp before trying to update.
Click to expand...
Click to collapse
What exactly is it you're trying to do? What TWRP are you using? What ROM?
You sound surprised that you can't see your Storage when you haven't entered a Password to Decrypt? That is, after all, what it's supposed to do. What security have you set up on your phone? Did you have Boot time security?
With so little useful information to go on it's hard to help. I'd recommend trying Red Wolf Recovery in any case. It's magic at solving many issues.
Sorry lol what happen was I was updating to latest stable oos, and had standard encryption set up. I wipes caches, and flashed latest rom, then magisk and again twrp (which I should not have) and then my phone had a quick reset. From there it was locked with twrp, neither my pin or default_pw worked so I just formated my phone, after copying data and important things to PC. Everything is good now just had to waste my own time.
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
raeee1 said:
For those of you facing twrp encryption when you set a password on the phone, remove your lock screen password and twrp will no longer be encrypted.
Click to expand...
Click to collapse
Not so. I removed the password and TWRP still asks for a password.
hachamacha said:
The solution for me:
I received this reply in the TWRP thread in Development from the OP:
Quote:
Originally Posted by jcadduono
try setting a non-pin password on boot in your OS, like, an actual password, this should convince 3.5.3 to rewrite your crypto key in working format
then see if that new password works on twrp
if it does, you can probably set it back to pin and the pin might start working in twrp
if it doesn't, let me know
-----------------------
Yes, that completely fixed the entire mess and thanks to everyone else for their suggestions. Funny that I never had noticed the word "password" in the security settings, so I tried pin.
Now I've got an encrypted 3t with working TWRP, makes backups, tried a restore and f2fs, no real changes from stock aside from adding TWRP, picking a password, etc.
Click to expand...
Click to collapse
This did not work for me.
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share.
please...please....help
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small!
iantechie1979 said:
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small!
Click to expand...
Click to collapse
i guess you are trying to update with the small sized ota b130. Use the full Ota b130 instead
Cienight said:
i guess you are trying to update with the small sized ota b130. Use the full Ota b130 instead
Click to expand...
Click to collapse
I wish my friend. No it is the update.app from the full b130 update.zip. Anyhow I have downloaded the b102, the earliest version I can find and the b130 rollback from nougat to MM version. Gonna extract the update.app from both and try one after the other to install via 3button method. I am just waitingfor my Bro to lend me his laptop so I can copy the files on to my sd card. So wish me luck, he's just come round. I'll know in a couple of hours if it works
It's all gonna be fine
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?