Hi all
Recently I flashed Oreo 8.1 on my Pixel, rooted with latest magisk and flashed latest elementalX. On boot I noticed this strange popup-error (see attached image)
On every boot the popup is still there, I just have to press Ok and the popup goes away, but it's pretty annoying.
Reading here and there on internet I found that it's the DTBO error, this happens on Pixel 2s and there is a fix flashing dtbo.img, but since I'm on Pixel of first generation I can't because the factory image doesn't contain that image file.
Is there a fix? Someone knows why this is happening? (Of course it's not a big problem since it's just a popup and everything works perfectly, just wondering if I can remove it btw).
Thanks in advance.
No solution. Commonly experienced by some/most users these days. See Magisk and/or kernel threads.
This only happens after installing a custom kernel. Don't worry, there is nothing wrong with your device.
Related
Hello and thank you for viewing my thread!
To start, my device is the OnePlus One, and i am running the latest Release of CyanogenMod 13 with the Latest Lightning Kernel for it's kexec/hardboot patch
I have tried multiple times, installing the multirom files, as well as flashing a factory image and flashing from a fresh install. Nothing seems to work.
The exact problem would be, even after performing the inject boot sector action, multiboot or the boot menu fails to appear.
I have no idea how to view kernel logs or anything of the sort. However i will gladly provide any logs or files if needed! Ill just have to figure them out is all.
Any help is greatly appreciated. Thank you in advance!
Edit:
1. I think i have the kernel ruled out as the problem as i have already tried a modified stock kernel, as well as bouffla's kernel.
2. The rom also doesnt seem to be the problem as i have tried both COS 12.1 and CM 13
3. The recovery seems to be ruled out as well. I rolled back to a previous version of TWRP and still have the same issue, no multiboot menu after proper installation.
4. This is really confusing. I even tried using the files built into the multirom manager application and that fails as well.
P.S. (on a semi-unrelated note)
I currently have a strong feeling it is a very low level issue (at least for my experience) due to the fact that kali nethunter is also failing to install and causing my device to brick every time i attempt an install.
I recently ran into the issue during custom rom work. I reflash the stock android ZIP, it starts booting, then I hard reset it with the power button and try to reach bootloader again. This, as it turns out, is terrible to do if you want a fast setup. The moment it starts and you reboot it, the boot image is corrupted (that's my guess) because escaping the boot screen during a clean flash bricks your phone. If you're reading this, it happened to you as well.
The answer is so flipping obvious and it took me an hour to figure it out - nowhere on the internet is there a "solution" for this problem, no matter how frequent it is. But there are lots of people who deal with this, whether still on their factory images (like the Pixel 3 EDL issue) or like me bouncing from custom to stock. So here's the answer:
ALL YOU HAVE TO DO IS SIDELOAD THE CURRENT SOFTWARE OTA OR A BETA OTA FROM ANOTHER FUTURE VERSION.
It doesn't recognize timestamps before your current software, so you'll need to assume you're on the latest of whatever you're on and do that. Future versions work as well, so if you wanted to reach 12 in one shot, your phone's bootloader would fully accept it as long as the file isn't corrupted. If you need a sideloading or flashing guide, here you go.
For me, I flashed the latest build of Android 11 (August patch) and rebooted during the boot up. What I did was download the OTA of the same exact file to my laptop, and entered adb sideload coral.xxx.x.zip. (The name of the file) It ran all the way through and it started up perfectly normal.
I hope this helps someone!
P.S. I don't have any pictures or tutorials, I only wrote this to help others understand what happened and how to fix it. Probably wouldn't have needed to say it if the forum for it existed.
Hi all,
Installing a custom rom on an XZ Premium; it's my first time dealing with this so its possible I missed something. I successfully installed TWRP and adb sideloaded the most recent Cherish OS rom. I was able to set up the phone with no issue, but upon rebooting for the first time back into system, it hits the boot logo, which animates correctly, but then hangs there indefinitely. I have wiped system memory, reformatted, and reinstalled, and the issue persists. I have also tried other ROMs. Arrow had the same issue, as did the Pixel experience, which leads me to believe that it's not an issue with the rom, but something with how I have configured the set-up.
I looked around for solution, but wasn't able to find much on the specific issue of only having issues on second boot, rather than initial. Any help would be appreciated.
I think your TWRP version is the Problem... (I think there were a lot of complaints about 3.3.?.? and higher) I had a similar Problem; TWRP wanted to use /data and if i formated the device, it would endless bootloop (I think because of the encryption the OS uses by default) So i decided to flash a older version (were this wasn't a problem) and I picked twrp-3.2.2-0-maple.img (maple because i have single SIM variant) and I didn't even needed to format the device and it still works (after i flashed Magisk and some other stuff/ "enhancements", that don't impact he OS) and everything still works smootly.
Maybe you should just flash a older version of TWRP (like 3.2.2-0) But i can't guarrantee, that it'll work on Pie(since i don't have it).
Hi all
I have a bit of a problem after flashing the Google GSI (android 13) on my Lenovo Tab P11. Everything seemed to work well. Rebooted into the OS without any issues, everything seemed to work (Wifi included). I then swapped and deployed LineageOS 20 GSI which again, seemed to go okay but I had a google play protect issue.
During a quick check, I was planning on just rolling back to the Google GSI one, but accidently locked my device with
./fastboot.exe flashing lock
instead of unlock. And, taking no notice of the on screen prompts proceeded to relock the device which effectively bricked it. Nothing would load, not even recovery or fastboot.
A fair while later I managed to get recovery/fastboot working again by redoploying the boot.img, recovery.img and vbmeta.img from the stock ROM. I then discovered my current-slot had changed from b to a, so swapped that back too. This allowed the device to at least go into fastbootd so I ccould reflash it. I put the LineageOS back on, but now Wifi isn't working. Rolled back to Google GSI and the same.
I've tried following guides to re-install stock, but that's failing as well. I have read a couple of posts detailing issues with Wifi on GSI but the fixes didn't do anything or weren't necessarily inline with what I had. I suspect I have missed something I need to push back out to the device, but at this point I'm a bit stuck.
Anyone came across this before, or can point me where I can get some more information on it?
ta
whether some partitions are deleted or corrupted. You have the original backup qcn . try restoring it or trying to fix the partitions
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.