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.
Related
My phone is f'd up.
I tried installing Liquid Smooth 6/10 version, and I got nothing but system UI FC's over and over. So, I held power and volume up until the screen rebooted, and then volume down to get to bootloader.
Then, I selected recovery from there. When I got into recovery, there was nothing in the internal memory, so I did the "fix" where you type in adb on your computer. Every thing went well, I suppose, but when I tried to reboot, it went to the splash screen and did nothing else.
Well, I went back into recovery to restore a backup, a stock Sense back up, and TWRP rebooted. It has been doing this every time I try to get into recovery. I can't do anything. I even installed a previous TWRP by going into bootloader and using an SD converter card with my PC, because ADB doesn't even recognize the device anymore.
I was using Cpt Throwbacks recovery, the newest one, and then I tried reverting to an older one.
Any help....PLEASE!?
Have you tried formatting data and internal storage?
Do you have a recovery log?
Captain_Throwback said:
Have you tried formatting data and internal storage?
Do you have a recovery log?
Click to expand...
Click to collapse
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
mcwups1 said:
I tried redoing a wipe of dalvik, cache, system, and data....have not tried to do internal, but it reboots before it finishes anyway.
I will try again to do internal.
Click to expand...
Click to collapse
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Captain_Throwback said:
Sounds like an RUU might be in your future. Some partition(s) seem to be corrupted.
Click to expand...
Click to collapse
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
mcwups1 said:
Capt, I did this "fix".
http://forum.xda-developers.com/showthread.php?t=2773203
Could this mess up my partitions?
Click to expand...
Click to collapse
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Captain_Throwback said:
I honestly don't know. If you used that command I assume you also had the random encryption issue, which could mean you have a different problem altogether.
Did you try using the partition repair options in TWRP?
Click to expand...
Click to collapse
I will try partition repair, but is that on the newest version only?
I can still get into bootloader, and when I plug it in to my computer, it still makes the connection sound, but recovery will not stay active. After about 10 seconds, it reboots to splash screen, but goes no further because I don't believe there is anything installed now.
Well, it won't stay in TWRP long enough to do anything. My internal is there now at least. I just don't get it.
Running RUU as we speak. I hope that since I have the .13 firmware installed, that it won't mess up.
Wow. Again.
I made a mistake by doing a backup, then trying to install another ROM, but forgot to wipe data. Went through the process (splash screen, boot animation, updating apps) and it booted for a second and rebooted. I figured it would happen, since I didn't wipe correctly.
Try to go into TWRP, and the damn thing reboots out of TWRP! I can't stay in TWRP for more than 5-7 seconds, before it reboots on its' own. Went to flashboot to reinstall TWRP, no change. I can't even do a restore.
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
I searched for an answer, and this is all I got! My phone must be borked. Guess I'll have to RUU again.
I had this issue last night and I got it to restore a backup by unplugging it from the wall first. I think the voltage is too high or something during a flash or something.
mcwups1 said:
I know I installed a ROM once through fastboot with a "fastboot flash zip rom.zip" command, but that isn't working either. Can't get a log, because I can't stay booted in anything other than fastboot/bootloader.
Click to expand...
Click to collapse
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Captain_Throwback said:
You can't install a custom ROM this way, unless it's been built into an image file. This is only for flashing image files that have been zipped up with an android-info.txt file.
Have you tried updating firmware, then booting back into recovery?
Click to expand...
Click to collapse
I already RUU'd, so I should have had the appropriate firmware.
mcwups1 said:
I already RUU'd, so I should have had the appropriate firmware.
Click to expand...
Click to collapse
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Captain_Throwback said:
I was suggesting flashing the firmware to normalize your device, so that maybe you could get back into recovery. I wasn't suggesting it because I thought you were on the wrong firmware.
Click to expand...
Click to collapse
I ended up RUU'ing again.
If it happens again, I will take your advice and report back.
So I had successfully used MOFO to flash the rooted 5.0 img and when using Titanium to freeze some stuff I must've accidentally added a required system apk to my custom filter and I intended to only have bloat so I deleted all of them on the list including the apk and my phone restarted and whenever i try turning it back on, it shows a black screen after the verizon logo shows up than it gets hot and burns up. I can still use fastboot and I tried reflashing rootjunkys rooted img again but that didn't work so i also tried the stock img and that didn't work either. I also tried Motorola device manager and after it checks for update it says no update is needed and my devices' system is n/a. So help please?
I also tried to factory reset but i cant even get into recovery.
sonic1675 said:
I can still use fastboot and I tried reflashing rootjunkys rooted img
Click to expand...
Click to collapse
RJ's 5.0 rooted image does not work.
Get into fastboot mode, connect your phone to your PC and use mofo.exe to flash the 5.0 pre-rooted image that is linked to in the OP of the MoFo thread.
http://forum.xda-developers.com/general/paid-software/mofo-root-turbo-t3064404
ok ill try that and lyk the results. Thanks.
sonic1675 said:
ok ill try that and lyk the results. Thanks.
Click to expand...
Click to collapse
quote me if you do b/c otherwise i may not notice you responded.
JulesJam said:
quote me if you do b/c otherwise i may not notice you responded.
Click to expand...
Click to collapse
So I reflashed every img available on maikos mofo page and the phone still gives me a black screen after the boot logo and whenever i try to get into recovery i get this message:
hab check failed for recovery
failed to validate recovery image
sonic1675 said:
So I reflashed every img available on maikos mofo page and the phone still gives me a black screen after the boot logo and whenever i try to get into recovery i get this message:
hab check failed for recovery
failed to validate recovery image
Click to expand...
Click to collapse
I think you are going to have to try to flash back to stock. It looks like somehow your recovery got messed up. Check out my Noob Guide for instructions on how to flash back to stock 5.0:
http://forum.xda-developers.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
JulesJam said:
I think you are going to have to try to flash back to stock. It looks like somehow your recovery got messed up. Check out my Noob Guide for instructions on how to flash back to stock 5.0:
http://forum.xda-developers.com/moto-x-2014/general/noob-guide-rooting-verizon-moto-x-2014-t3097375
Click to expand...
Click to collapse
I tried it but it didn't work. I had to go delete everything through fastboot and flag each IMG separately. But though everything got deleted I got a fresh install of 5.0 and I'm not bricked Lol.
Hello, I'm new to these forums and have come to them under some unfortunate circumstances.
I went to update my device (MOTO G 2014) and had an error (cant remember what it said), anyway I rebooted my device and it wouldnt load after the 'BOOT LOADER UNLOCKED' warning screen. I went into TWRP and went to reset my device and wiped the system. (feel like an idiot, then again I am..) So then I downloaded all the USB drivers and Android SDK along with adb+fastboot and attempted to sideload. during the sideload I got this error..
* failed to write data 'protocol fault (couldn't read status): Invalid argument' *
EDIT: the error is no showing up at * failed to write data 'protocol fault (no status)
I have swapped USB ports and tried a different USB cable, does anybody have any tips or do I have a paperweight on my hands?
Thanks in advance
Flash stock firmware.
motofirmware.center
Sent from my XT1031
If I understand, right now you have wiped system, and bootloop in Motorola logo.
If you can boot in recovery, then transfer a ROM to an microsd and flash from there.
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
PJT95 said:
UPDATE: managed to put 3 ROMs onto my sdcard but only one of them actually allows me to install it, but after I install it I am stuck at the boot screen, guessing I got the wrong ROM for my model, cm doesn't flash, it just says 'Failed!' and so does the most recent one from the website previously linked. Any tips? Model is XT1072. I have been sat at the boot screen for around 15-20 minutes, is it taking so long because of me clearing the dalvik cache?
Click to expand...
Click to collapse
Lemme guess u tried to flash "titan" CM and not "thea" one?
LuK1337 said:
Lemme guess u tried to flash "titan" CM and not "thea" one?
Click to expand...
Click to collapse
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
PJT95 said:
I have tried both, both are returning the same error
"E: error executing updater binary in zip"
Is this something to do with my TWRP being at v2.7.1.1?
Click to expand...
Click to collapse
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
LuK1337 said:
http://forum.xda-developers.com/mot...recovery-twrp-2-8-6-0-touch-recovery-t3088800
get this recovery.
Click to expand...
Click to collapse
Thanks for your help and thank you to everyone else who replied to the thread. To anybody else who will maybe see this thread and who are stuck with the same errors, I fixed this by simply flashing the latest recovery using 'fastboot flash recovery [NameOfRecovery].img' then proceeded to install the ROM compatible with my device which I downloaded to my external SD Card.
Again, thanks
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.
I am fully stock since MRA58K came out. I applied the security update today via the factory images but left user data alone. I am now getting the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?
what's the exact message?
jj14 said:
what's the exact message?
Click to expand...
Click to collapse
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot
GMoGoody said:
Sorry, I thought it was inherently known with the phrase corrupt during boot. But this with the Red Status
https://support.google.com/nexus/answer/6185381?p=verified_boot
Click to expand...
Click to collapse
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)
jj14 said:
what's the exact message?
Click to expand...
Click to collapse
jj14 said:
So your device is still booting ok . That message shows up if your device is rooted or has some other changes (recovery perhaps).
If you want to stay stock, just reflash the factory images using fastboot (all files skip userdata)
Click to expand...
Click to collapse
Which I have tried three times and I am still getting this message. The second and third time I tried Flashing MRA58N over itself it did not optimize or anything. I guess I will wait for the next security update, or flash back to MRA58K reboot and try flashing MRA58N again
Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)
flash a custom kernel and it should go away
GMoGoody said:
.>....... the Corrupt Message during Boot. I accidentally booted TWRP 2.8.7.1 from Fastboot but did not flash it. Just selected reboot. Any Ideas on ways to get rid of it without a factory reset?
Click to expand...
Click to collapse
Flash a custom kernel like Franco's kernel
jj14 said:
Did you flash everything? bootloader/boot/recovery/system/radio/cache? (reboot bootloader after flashing radio and bootloader)
Click to expand...
Click to collapse
Yes I flashed everything but the userData even though some things like the radio and bootloader didn't change
Strange. Hopefully somebody else will chime in.
NLBeev said:
Flash a custom kernel like Franco's kernel
Click to expand...
Click to collapse
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order
jj14 said:
Strange. Hopefully somebody else will chime in.
Click to expand...
Click to collapse
My thoughts exactly. When I get home from work I will go back to MRA58K , reboot, then reflash MRA58N. Hopefully this fixes the issue. I will report back tonight. In other threads I saw people were having to go all the way back to 5.1.1 when they saw this when first upgrading to MRA58K
Edit:
This worked. I flashed back to MRA58K, Let it optimize, Verified no corrupt message. then Flashed MRA58N and did the same. So far so good. Also note there is an update to platform-tools in the SDK
GMoGoody said:
I want to use android Pay. So I am staying stock. I am trying to figure out why this message suddenly started appearing between MRA58K and MRA58N. If Others are seeing it and potentially how to recover from this state with staying stock but not doing a factory reset. Seems like factory reset may be in order
Click to expand...
Click to collapse
I think it has to do with TWRP. You used it temporary with fastboot, but it is pushed to the phone's memory. You could try to fastboot flash stock recovery.
SOLVED
I'm getting the same as OP. flashed manually bl/reboot/radio/reboot/system/boot/recovery/cache then tried again with a fresh D/L through Wug's NRT. No joy. Maybe there is something different between the OTA and factory image that would require a data wipe with the latter. Is there an OTA in the wild that I could dissect? Also having bluetooth problems after dirty flashing MRA58N as stated above.
EDIT: Flashed back MRA58K, all is better.
Also noted that after flashing MRA58N the cache didn't rebuild. Hmmm.
SOLUTION: Update platform-tools in your SDK. Just updated and manually dirty flashed, no corrupt message and app cache is rebuilding. :good: