I have been trying to install an update (B405) manually, however as soon as the phone reboots into the updater, it just comes up with an error after around 5 seconds. How can I fix this and install the update? Just letting you know, the phone was previously bootloader unlocked, however was relocked.
Solved, do not reply
Related
A friend of mine is getting the update OTA but it keeps failing with a red error triangle and an android. So every day it asks her to install the update and each time it fails. Everything is stock, never unlocked, never rooted. Do you think she should try to install it manually? Anyone else had this problem?
Best way to update a nexus is via fastboot. But it requires an unlocked bootloader
Sent from my TH3M3D NEXUS S
Hi, today I got the notification on my G (India-Dual Sim version) that the 4.4.4 was available to download.
I tried to go back to stock recovery to do the upgrade but for some reason it didn´t work, I was able to flash but the stock recovery never came up. In the end I decided to give a shot and see what happened.
I have the CWM recovery, and it notified me that the file used for the update had not a correct signature, decided to continue, no problems so far. In the end it notified me that maybe root may have some issues (the same warning when you root the phone the first time), told it to fix it and it rebooted.
All smooth and so far no problems, but it did show a warning on the main screen (after being all loaded) that something went wrong, but the phone booted OK and the system version is 4.4.4, maybe something to do with the stock recovery or something, don´t know, but so far, is you have CWM, I believe you can do the OTA update withouth problem.
Will let you know if something comes up.
Hi everyone!
I've just received and successfully installed a system update for Android 5.1.1 and it says exactly zero about itself. Even Android's version hasn't changed.
Does anyone have any idea what it fixes? I surmise it fixes two recent holes but 10MB sounds a little too much for that.
I also got but nothing happened
Sent from my Nexus 5
I got it, I'm updating manually since for some reason my phone never wants to update the regular way.
It addresses the Stagefright vulnerability
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
ApTeM said:
How can I apply this update manually?
It doesn't apply automatically - there are no errors, nothing. I've rebooted my phone three times already and it wants to install it again.
Click to expand...
Click to collapse
flash it through ADB
I use this thread as reference just to make sure I don't miss any step but there are a few others threads like this. http://forum.xda-developers.com/google-nexus-5/general/guide-update-rooted-device-to-5-1-lmy47d-t3050789
OTA install error
I got the OTA notification to download & install the Stagefright patch. Every time I try to install it, it says "error!" shortly after it starts to install and shows the android with a red exclamation point.
My nexus 5 is stock & unrooted.
Any idea what's causing this and how to force the install? If not, I can sideload OTA with ADB later tonight.
Thanks!
I think the build number should have changed to LMY48I.
vagosto said:
flash it through ADB
Click to expand...
Click to collapse
adb fastboot
I've had my first freeze and first complete blackout since this small update
This should be the monthly update mentioned on main page
This update is worthless: http://www.theregister.co.uk/2015/0...efright_fix_wont_be_resolved_until_september/
I will skip it.
URGENT HELP
On installing the update of 16.1 mb. The droid shows a error while installing after the reboot.
Nothing happens after that and the phone reboots
Right now it it running on 5.1.1
Same problem, LMY48B
I have the same problem, OTA update comes in a few times a day and never works, i simply get the message "Error". My update is 10.1 Mb. I am on build nr LMY48B and have Android version 5.1.1. When restarting using the power and volume button, the error message says "Empty". I tried Nexus Root Toolkit to update, no result.
Has anyone an idee to eather update or kill the updates all together?
Solution found !!Huraay!!
I just found a solution to this problem. You ll have to flash your nexus to stock (it is formatting not rooting)
Here are simple steps to it:
1. Enable Bootlegger
2. Turn on developer mode, enable USB debugging
3. Use a flash factory image (download it from any source)
Now you ll get 3 back to back OTA updates in settings, just install them and finally you ll get Marshmallow update of 403mb.
DONE.....
Cheers.
Contact if you still have a problem.
Thanks for sharing this. I tried to follow your instructions, using NEXUS Root Toolkit. At first i tried factory image 5.1.1, but this did not work , it just stopped. After that i tried to flash Hammerhead 6.0.0. Wich actually looked very promissing during the proces. After finishing reboot started, and it won't get out of reboot. I tried several times, up to 15 minutes. I also tried a factory reset, but it still keeps running the marsmellow startup grafic. Since i can't get into unlock mode, i do not have the opportunity to reflash the phone. Any ideas how to get out of reboot?
Hi,
We need to know more, what's actually failing. We could try and flash the update with TWRP, we'll get some output from there. Might be your radio or bootloader versions, for example.
And you using a toolkit, it doesn't help.
So, go learn some fastboot and some adb while you're at it, because you're going to need it. Guides to both are stickied everywhere around here.
Also, don't see the point on flashing a 5.1.1 factory image at this point, if the goal is to update to 6.0 (looking at the other user posting on this thread): just flash 6.0 factory image.
Sent from my Nexus 5 using Tapatalk
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.