Database Develop

"Device failed verification" error on boot?

Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?

RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.

RealROGWaffle said:
Flashed the M preview two days ago, working completely fine. I rebooted the phone for some reason, and there was an error right after the Google screen stating "Your device has failed verification and may not work properly"
I know people have been getting this, but I haven't seen anything on how to get rid of it. The phone still boots and operates fine after the message started popping up, but its a bit annoying. I thought if I just formatted all the partitions on my phone that would go away. Apparently not. After formatting in TWRP, I wanted to see if that would pop up even after I wiped everything, and it does.
Does anybody know how to get rid of this error?
Click to expand...
Click to collapse
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?

simms22 said:
its a normal m error. flash a custom kernel to get rid of it. despair has one, elite has another, and there are more out there.
Click to expand...
Click to collapse
Awesome, thank you very much.

cam30era said:
This error is often a result of system/bootloader mismatch. Do you have 5.1.1 with M bootloader?
Click to expand...
Click to collapse
Nope, running M with the M bootloader.

Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).

jasoraso said:
Did you flash TWRP recovery or the M (factory) recovery?
If TWRP, did you allow it to try and flash SU?
I didn't have that error until flashing TWRP and allowing it to try and root upon exiting TWRP.
I was a able to clear it by flashing a different kernel, booting to TWRP, and wiping caches (I didn't do a Factory Reset).
Click to expand...
Click to collapse
everyone who flashed m without a separate kernel got that error. its a m thing for now.

my phone wont boot up after it flashes that.. dont know what to do..

dave2metz said:
my phone wont boot up after it flashes that.. dont know what to do..
Click to expand...
Click to collapse
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.

simms22 said:
what did you flash? .img files or via twrp flashable zip? did you flash the bootloader? you have to or it won't ever boot.
Click to expand...
Click to collapse
My device keeps flashing as well. I fastboot .img files

I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue

md1008 said:
I only had this error when I flashed twrp. When I was stock M and no twrp didn't have this issue
Click to expand...
Click to collapse
Same... flashing twrp kills my M install. Say's it's booting but all I get is a black screen.

Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?

sbrownla said:
Now it's my turn to join. Any fixes for those that won't boot up at all? I think I may have a brick. How did you get out of this?
Click to expand...
Click to collapse
you have to flash the m bootloader before flashing m, or it will never boot up.

How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?

How to flash Android M, TWRP, & SuperSU with out getting red corrupt triangle @ boot?
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks

I wonder the same thing. I tried to get rid of the red triange but it's impossible. I've tried a full wipe and flash everything from stock but no dice.
Also i'm unable to boot to recovery. It just freezes... Same thing if I flash back the 5.1.1 image. TWRP is working though.
Any ideas?

Does anyone have a solution to get rid of the triangle WITHOUT twrp or root? I flashed TWRP to see if I could install a custom HOSTS file and the message started popping up on boot, but even after reflashing everything from the official M image and wiping data and cache it still pops up. Any suggestions? o_o

Did you flash userdata too? Tried factory reset on top?

pszyman said:
Did you flash userdata too? Tried factory reset on top?
Click to expand...
Click to collapse
I formatted userdata because I have a 64GB device and the userdata image included is for 32GB. this is what I did without the file names because I'm mobile:
Code:
Fastboot flash bootloader mboot.img
Fastboot reboot-bootloader
Fastboot flash mradio.img
Fastboot flash system msystem.img
Fastboot flash boot mboot.img
Fastboot flash recovery mrecovery.img
Fastboot format userdata
Fastboot format cache
And then I booted and got the device corrupt message. I did all of that a few times to make sure I didn't miss anything and I have no idea what it's detecting as modified. I haven't tried factory resetting from the device itself, I figured formatting userdata would be enough but ill try that tomorrow unless anyone has other ideas.

I had this same issue today too after I flashed twrp. The only way to resolve it was to flash stock and unroot using nexus toolkit to a lollipop stock image. In time I'm sure it will be a smoother process to go to android m with twrp and root, but until then, I'm sticking with lollipop.
Sent from my Nexus 6 using Tapatalk

530farm said:
Is there a method to flash Android M with TWRP and supersu that will work with out giving the red triangle stating the device is corrupt at boot?
Thanks
Click to expand...
Click to collapse
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.

Well, the issue is this corrupted message stays even after the full stock reinstall. Some say it went away after the factory reset but returned back after a while later, after spontaneous reboot or so.

thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks

What I've done to get back to stock was - flash clean image and next factory reset. No corrupted message. So far so good.

I believe to get rid of it...you will have to lock and unlock bootloader again...which will factory reset in the process. Hopefully someone finds a workaround for a factory reset...I am going to continue to run it with the error message until someone does. I dont want to factory reset. The message doesnt cause any issues to my knowledge...its just a warning to the user.

dansoh said:
Experienced this too, until I found this article that shows different TWRP, SuperSU, etc versions.
http://wccftech.com/root-nexus-6-android-60-mra58k-marshmallow/
I flashed it without the errors.
Hope it works for you. After a few minutes of Marshmallow I went back to Fusion 6.0 which was a bit more features based on CM12.1. I just got the Shamu yesterday coming from OnePlusOne running SultanXDA's CM CAF.
Click to expand...
Click to collapse
kidhudi said:
thanks the dispair kernel worked with twrp 2.8.7.1 and su 2.49 beta.
now i have no more corrupt and i am rooted and not encrypted
thanks
Click to expand...
Click to collapse
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message

inspiron41 said:
I have confirmed this works. I had the "Device is Corrupt" message non-stop. Basically go to that link and download all the stuff.
Have TWRP install.
From TWRP install the Despair.R20.6.Shamu.zip
then flash BETA-SuperSU-v2.49.zip.
Reboot
PRESTO, Device Corrupt is GONE
I had tried Despair.M.CFS.R31.2.Shamu.UBER.zip and UPDATE-SuperSU-v2.46.zip before, which did not eliminate the Device is Corrupt Message
Click to expand...
Click to collapse
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.

I flashed the kernel from here http://forum.xda-developers.com/nexus-6/development/kernel-stock-kernel-root-color-control-t3218958 and it went away.

PhantomGamers said:
Which one makes the message go away though, the kernel or supersu? Or both? I wasn't looking to root my phone so at this point I'm just trying to get the message to go away lol
EDIT: Can confirm it's kernel related, just flashed a lollipop kernel and the message vanished but of course it bootlooped Lol.
Click to expand...
Click to collapse
Custom kernels that have the flag edited out will will get rid of the Corrupt message.

djkinetic said:
Custom kernels that have the flag edited out will will get rid of the Corrupt message.
Click to expand...
Click to collapse
I guess I'll have to resort to that if factory resetting doesn't fix it, sucks though cuz I would have been happy with stock.

P10 VTR-L09C432 restore failure (semi brick?)

Hi all,
Recently I got a P10 (VTR-L09C432) which I unlocked and flashed with TWRP-3.1.1-0-VTR. I made a full backup on the SD card and tried to run Lineage 15.1, unfortunatly this didnt work so I had to revert back to the backup. Sadly this isnt working properly either, the phone boots to Nougat but keeps telling me to setup my phone. When the phone lets me choose if I want to go for a fresh install or login with an existing account the setup process just restarts.
Weird thing is that the phone has gone back to the stock recovery without flashing the recovery, this shouldnt be in the TWRP backup, right? I cant seem to flash it back to TWRP either. When I flash it with fastboot and try to go into TWRP recovery it just loads Emui.
What to do?
Thanks!

Try doing a factory reset in the EMUI recovery and see if that fixes your set up problem

SeanTho said:
Try doing a factory reset in the EMUI recovery and see if that fixes your set up problem
Click to expand...
Click to collapse
Unfortunatly that is impossible, when I boot EMUI the only option I have is to 'download update and recover' or to reboot. The download option fails every time, even with connected WIFI.
This morning however I got the device to load TWRP again. Dont ask me why, but it seems to work now. I could load another ROM, but which?

88-BLUE-88 said:
Unfortunatly that is impossible, when I boot EMUI the only option I have is to 'download update and recover' or to reboot. The download option fails every time, even with connected WIFI.
This morning however I got the device to load TWRP again. Dont ask me why, but it seems to work now. I could load another ROM, but which?
Click to expand...
Click to collapse
You can check out the custom room section of the P10 as there are some stock roms that have added customization but I think they require you to rebrand to a certain model. You can always try another Treble rom such as RR. It's probably the most stable Treble rom for the P10. If you are to go along the lines of RR make sure your phone is on Oreo firmware and once the system.img has been flashed to do a factory reset without wilign the system so it boots. Hope this helps ?

I am kind of lost now. Tried AICP, but this gives me errors on flashing. (Failed to mount /system: No such volume).
I tried to go back to my recovery image again (that I made with TWRP), but no cigar. Same weird problem with looping through the initial phone cq. account setup.
I guess I am missing something here. =)

Allright, just installed Nougat (from this source) and now this seems to be working allright. Will make a new backup and try to go from there.

Verification Failed - Bootloop. Brand new Note9, twrp + magisk flash....

Hi all - Australian here with Optus Note 9.
Got my Note9 this morning. Flashed twrp (from https://forum.xda-developers.com/ga...t/recovery-twrp-galaxy-note-9-exynos-t3833933). Flashed magisk from page 1 in same thread.
Now can't boot. Stuck on a black screen saying;
VERIFICATION FAILED
unable to restart your device. The ingerity verification has failed. You need to reset your device to factory default settings. This will erase your data
[ RESET].
Click on 'reset', it goes to twrp then loops around.
Anyone know how to fix?

Im with optus too. If you can get back into twrp just flash stock rom or a custom rom.

ciaox said:
Im with optus too. If you can get back into twrp just flash stock rom or a custom rom.
Click to expand...
Click to collapse
I just tried flashing a custom rom - stuck with it in boot loop.
So whilst I re-download the stock stuff, I tried deleting my data in twrp and I'm just about to try a no-verity-opt-encrypt6.zip with custom pie rom. Fingers crossed .

hmm strange. first boot takes a good 5mins tho. good luck

Worked fine.
Not sure whats changed, but I needed to flash the no-verity-ope-encrypt6.zip, and now it boots just fine.
Very strange. Oh well, onwards and upwards to Pie goodness (like my old Huawei mate10pro)

Mod feel free to close this one. ty

Toldorn said:
Worked fine.
Not sure whats changed, but I needed to flash the no-verity-ope-encrypt6.zip, and now it boots just fine.
Very strange. Oh well, onwards and upwards to Pie goodness (like my old Huawei mate10pro)
Click to expand...
Click to collapse
flashing magisk v16 and up would have also fixed it. but format data and factory wipe in twrp was a required step before flashing custom rom.

SHRP Recovery bootloop after flashing a ROM (although rom is fine)

Hello,
As the title suggests, I've flashed a custom rom (EvolutionX to be exact), upon booting it up, mediatek Ims stops working, but that appears only on boot so it's not that big of a deal.
However, Upon rebooting into recovery (through system or via vol up+power) i get greeted by the SHRP logo but it powers off and on.
Fastboot mode works just fine, ROM works too, the recovery doesnt want to work though. I had the phone modded for 2 weeks and this is the first time this happened.
Any idea on i can fix it? I've already tried flashing the same recovery via fastboot but to no avail, i get an error saying:
fastboot: error: cannot load 'SHRP_v3.1_stable-Official_CD6-1630047089': Permission denied
That's weird, because my phone has an unlocked bootloader.
Any help would be greatly appreciated!

Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned

HaroldTech312 said:
Friend Maybe you had a small error in the firmware of your device, if I'm not mistaken I think that later the equipment will be in a hardbrick and you will have to wait for the bootloop cycle to pass, which is when the battery runs out and you will have to resort to SP Flash Tool to fix mobile
I hope I have helped you, it is something that I have learned
Click to expand...
Click to collapse
i will try flashing stock xiaomi and then install a custom rom again

NewtonPL said:
i will try flashing stock xiaomi and then install a custom rom again
Click to expand...
Click to collapse
try it I can't guarantee you anything but if it comes back and the same thing happens it means that the rom is not compatible with your mobile and you will have to look for another one
If you still have doubts tell me that I can try to help you

the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now

NewtonPL said:
the ROM was glitchy and broke the recovery, i flashed miui a11 and flashed everything again, works now
Click to expand...
Click to collapse
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.

Mineplayerminer said:
did you flash the .zip using the SHRP recovery or did you use the fastboot method? I just used the Install Magisk feature and now my phone it bootlooping. I can enter the SHRP and fastboot. It just bootloop after the lock icon disappears.
Click to expand...
Click to collapse
what zip? this isnt about magisk mate.

NewtonPL said:
what zip? this isnt about magisk mate.
Click to expand...
Click to collapse
I mean the MIUI ROM in zip. But I figured it out, I unbricked mine by installing the MIUI from the SHRP.