So, I think the only thing I've done to my phone was root it using this thread:
http://forum.xda-developers.com/z3/general/d6603-5-0-2-flashable-stock-23-1-0-690-t3056361
I've been getting the prompt for the Sony upgrade software OTA thing for a while and just ignored it since I didn't want to accidentally break things.
Today, I decided to try to install it (Maybe it was the marshmallow update). My phone rebooted and is now stuck with an error that looks like this:
ERROR - Update Failed
Anyone have any idea how I can fix this?
Also, how would I go about getting updates either to Android or Sony software without breaking anything?
Yesterday my completely stock 701 (B003) rebooted itself and on reboot came the following message -
"Update failed..." the rest I can't remember as I was very busy at the time and simply rebooted.
I later checked and there were as usual no updates available.
Anyone else seen this? It's very strange.
Phone is completely bog standard, bootloader still locked and never attempted to root it.
I've recently been playing around on my shield tablet with a couple of different roms and rooting, but I ended going back to stock - albeit with root and twrp installed. I downloaded the stock image from Nvidia's own download site and everything well and now it wants to install 5.4 over OTA. I figured that was fine, I'd have to re-root and, possibly, reinstall twrp, but that's not a hassle so I went ahead with the update.
Unfortunately, when it rebooted to install it actually rebooted into twrp. I figured that was OK, since I could just flash the update manually. I found it from /data/data/com/nvidia.ota/ and went to flash it. It failed, however, with error e3003 - complaining about the update file being older that the existing system file. The only solution I could find on googling was to make suer you went through the updates systematically and in order. Since my tablet had been restored to 5.2 I tried flashing the 5.3 update, but it gave me the same error.
I'm now somewhat stumped as to how I can actually go about getting my tablet back up to date again...
My phone no longer sees OTA updates so I have been stuck using the factory images for the last few months. This month when I run flash-all.bat I end up with:
Code:
fastboot flash bootloader bootloader-sargo-b4s4-0.2-6355063.img
< waiting for any device >
Sending 'bootloader' (8361 KB) OKAY [ 0.214s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
and the update fails. I am currently using the 4/27/2020 copy of platform-tools and validated that bootloader bootloader-sargo-b4s4-0.2-6355063.img is in the local directory so Im a bit stumped.
I ended up having to sideload the OTA update.
Dunno if you've tried this yet, but you can factory reset your device and backup, then see if OTA works.
I had the same issue. Apparently, last month's update didn't write the new bootloader. I was able to sideload the OTA in recovery mode.
Different-But-Similar Issue
darkmeridian said:
I had the same issue. Apparently, last month's update didn't write the new bootloader. I was able to sideload the OTA in recovery mode.
Click to expand...
Click to collapse
In my case, I uploaded the wrong boot image via flash.android.com; what I thought was beta 1 of Android 11 was a pre-Developer Preview of Android 12 (S). Since I still had the last full image of Android 10, I went back and flashed that (to scrub my flub). The OTA of 11 beta 1 came in on schedule once I had done that. Tomorrow, I'll hopefully (barring heat) take the new Google Camera for a drive - looking at changes since 7.2 - which shook things up merely on the NightSight/Astrophotography end. I seriously doubt that this will be 7.4 (which was unique to the Pixel 4), as I had seen nothing indicating that even Google was going to cross-port any of 7.4's feature set to the rest of the Land of Pixel.
I tried using flash-all for the first time for the June update and also got errors and an unbootable phone. So I went back to the sideloading method that has always worked fine for me and that fixed the problem. My phone is also rooted with magisk.
Hey all, I'm not new to this, but I'm looking for some guidance and explanation of the root cause so I don't break my phone worse than it is.
I bought a Pixel 6a last fall, and I have been using it non-rooted since. I have accepted each OTA update since Android 13 was released and as of today I am running on TQ2A.230505.002.
I took the OTA update for May 2023 as soon as it was released before rooting. After it successfully installed, I downloaded the matching factory image zip and extracted the boot.img from the ROM, patched it with Magisk, and then flashed by doing fastboot flash boot magiskboot.img.
It was working fine for a few days, until today when my phone reboot and I was greeted with the "Your device is corrupt" message. If I continue, the phone boots successfully and it works like normal. Magisk says it is loaded and modules are active.
I have reboot my phone several times since I rooted it, and I never received this error. However, the last time I reboot before I received this error was Sunday night. I have not installed any apps since then.
Looking around on this forum and others, I have seen posts from other users who got this error, but their situations are different. In those cases, they received the message only after accepting an OTA on a rooted device or got stuck in a boot loop, but neither of those scenarios apply to me. The solutions in other threads also seem to be a mixed bag of results, so I'm hesitant to do anything until I understand the root cause and ask for guidance.
Since I am unlocked and booting, my hope is that it should be easily recoverable. However, what could cause it to suddenly become "corrupt", and how would I diagnose or remediate the issue with minimal disruption or risk to data? My main concerns at this point are not knowing how it got into this state, and how to quickly recover from it if it happens again.
---- Edit below with more info ----
I found another user with a very similar issue from a month ago. While the issue seems to have been inflicted differently, their symptoms are very similar. The suggested solution is linked here: https://forum.xda-developers.com/t/your-device-is-corrupted-message-on-bootup.4578141/#post-88446647
The other post states the issue is caused by "the bootloader is looking for a new/updated OS without corruption errors so it will go back to restart mode rather than being stuck in the RED eio mode which displays that message."
Since my phone was working, what corruption could I have experienced over the past two days of regular usage? I did not install any updates or make any changes that failed.
Also, what would be the recommended solution in my case? Should I try flashing an older boot.img and then reflash the newest? Or should I do "fastboot --disable verity flash vbmeta vbmeta.img"? Are there any risks with either approach?
Your bootloader is unlocked, hence the message.
dexlemaffo said:
Your bootloader is unlocked, hence the message.
Click to expand...
Click to collapse
This is not the "your bootloader is unlocked" warning. This is the eio message saying the system is corrupt and requires manual intervention to boot.
After doing a bit more research and learning more about the "eio" mode that it was stuck in, I decided to take a stab at it.
Since I have the May update installed, I downloaded the April factory image. I also downloaded platform-tools r33.0.3 because I read there was mixed results with the latest version.
I extracted the boot.img from the bluejay-tq2a.230405.003.e1 April image and flashed it to my phone with fastboot. I then reboot the device. It failed to boot, as expected. However, I immediately noticed the error was gone and I only had the regular unlocked bootloader warning.
I boot into fastboot again and flashed the boot.img from the bluejay-tq2a.230505.002 May image matching my system version. After it flashed successfully, I reboot and the error did not return.
Edit:
I proceeded with rooting again. This time, I did "fastboot boot boot-magisk.img" and flashed from Magisk instead of from fastboot, though I doubt there is any difference.
It reboot successfully. I am back to being rooted without any error message and without any factory reset.
I still don't know what would have caused the bootloader to think there was corruption after it was working for several days. Can anyone reading this can provide some insight?
This whole issue has me very uneasy. I'm worried something else could be wrong - whether it's a bug with Android, or a hardware fault, or a bug in Magisk.
I'm wondering if I should be concerned.
Today, when my phone reboot, it was sudden. I did not initiate the reboot. I thought it was a benign crash as I have experienced many times before. However that was when I saw the "your device is corrupt" message.
I'm reading up on dm-verity and the dm-verity driver here: https://source.android.com/docs/security/features/verifiedboot/dm-verity
I suspect the dm-verity driver is used to hash and verify the system partitions on the fly? If so, could it be that when I was using my phone, it was trying to access some data and the hash failed, the signature mismatched, and it triggered the bootloader to mark the system as corrupt?
If that is what happened, is that cause for concern? Would that be the result of actual system file corruption or bad NAND? Or is it some bizarre Android glitch when running rooted?
Youll likely need to do a factory reset to get rid of that message.
That is incorrect. Based on the other reports of users with the same issue, this is a bootloader message and a factory reset has nothing to do with it. Additionally installing a factory image and wiping the phone would not get rid of the image either. Only an upgrade can supposedly remove the message, unless it is caused by something else.
He said it's the device is corrupt message, not the normal unlocked bootloader one.
afaik thats a bug in Android Verified Boot.
what you did is exactly the "normal" method to solve it, e.g. flash boot.img of the prior version, try to reboot and then flash the correct version again.