3

Oneplus 3 dm-verity verification failed when i boot

  1. cezarvrabie Jelly Bean Dec 4, 2016

    cezarvrabie, Dec 4, 2016 :
    Thanks a lot man!
     

    #41
  2. vrda08 Eclair Dec 6, 2016


    #42
  3. SvenBee1961 Ice Cream Sandwich Dec 6, 2016


    #43
  4. vrda08 Eclair Dec 6, 2016

    vrda08, Dec 6, 2016 :
    yes it does
     

    #44
    SvenBee1961 likes this.
  5. F_Al_Imran_OcMS Cupcake Dec 8, 2016


    #45
  6. gkyrillos Froyo Dec 8, 2016


    #46
  7. G_Jeffery_McKinney_qWAa Cupcake Dec 14, 2016

    Last edited: Dec 14, 2016

    #47
    bhyde likes this.
  8. Kirakichi Jelly Bean Dec 14, 2016

    Kirakichi, Dec 14, 2016 :
    People who experience this, simply flash CB8 (adb sideload) and it will reset recovery with stock.

    DM verity will continue, once you get OTA to CB9, it will be gone!

    It worked for me, doing OTA update to CB9 made that dm-verity screen to disappear.
     

    #48
    ghostofcain likes this.
  9. Skhassay Donut Dec 14, 2016

  10. rameez0307 Gingerbread Dec 14, 2016

    rameez0307, Dec 14, 2016 :
    can someone put the basic function of call block feature in OnePlus 3 in the next update..please OnePlus 3 team urgently put this function as I am sick and tired of spam & network calls.. asap
     

    #50
  11. sammerasker Ice Cream Sandwich Dec 16, 2016

    sammerasker, Dec 16, 2016 :
    i've done a similar procedure to one mentioned on a previous post.
    1- on Freedom OS 1.7 (any rom should work), rebooted to TWRP (Official)
    2- wiped everything including internal storage. (if already on .28 TWRP wiping data to f2fs and wiping internal storage normally may save you some steps later on)
    3- fastbooted the official recovery (v1 downloaded from OP site)
    4- rebooted to official recovery and started install from ADB.
    5- sideloaded beta 9
    6- rebooted to beta 9 ( booted perfectly with no issues)
    7- reboot back to official recovery (now it will be v2)
    8- wipe cahce (and data if available)
    9- reboot to fastboot and fast boot mod TWRP .28
    10 - on TWRP the password issue might appear but it';; be fixed after this step
    11- on TWRP wipe Data to f2fs (even if it was f2fs) and wipe internal storage (it may show it as 0 size)
    12- reboot to system
    13- reboot back to TWRP and now it can access internal storage , flash SuperSU (sr5)
    finaly reboot to system.

    doing this i have beta 9 with TWRP and Root, without DMverity message. and everything works perfectly.
     

    #51
    sauron.cnp likes this.
  12. klaidliadon Cupcake Dec 22, 2016

    klaidliadon, Dec 22, 2016 :
    You can skip point 2. Worked for me!

    EDIT: Using Beta 9
     

    #52
  13. sauron.cnp Honeycomb Dec 22, 2016

    sauron.cnp, Dec 22, 2016 :
    I followed this guide but I had to invert steps 13 and 12 to make the twrp password issue disappear.
    Now I am on 9 with twrp 28 and I have no issues.
     
    Last edited: Dec 22, 2016

    #53
    sammerasker likes this.
  14. TommoTheBest Cupcake Dec 28, 2016

    TommoTheBest, Dec 28, 2016 :
    Hi, i've got a problem with "dm-verity verification failed", how I can solve this(sorry for my bad english). Please help me!!!
    EDIT: I do an attempt with "Install from ADB" but i don't have results it gives me "Installation failed" and in the cmd gives me this "error: protocol fault (no status)". What i can do?
     
    Last edited: Dec 28, 2016

    #54
  15. cvdr Eclair Jan 9, 2017

    cvdr, Jan 9, 2017 :
    Customer support has just told me on live chat that currently there was no way to get rid of the "dm-verity" message upon boot. A future OTA update would resolve this.
     

    #55
  16. bhyde Froyo Jan 13, 2017


    #56
  17. cvdr Eclair Jan 21, 2017

    cvdr, Jan 21, 2017 :
    For me the dm-verity message disappeared after the update to OxygenOS 4.0.2.
     
    Last edited: Jan 22, 2017

    #57
  18. rlramakrishnan Gingerbread Jan 27, 2017

    Last edited: Jan 27, 2017

    #58
  19. AyybeeShafi Cupcake Jan 30, 2017


    #59
    Alopez426 likes this.
  20. FlyingMachete Honeycomb Jan 30, 2017

    FlyingMachete, Jan 30, 2017 :
    Actually only one of the commands is enough to get rid of the message, not necessarily the "disable" one, it just depends on the rom you come from. People have to try because in some isolated case the procedure failed on entering both commands. I just thought this should be specified when sharing this already-super simple fix. ;)
     

    #60
    AyybeeShafi likes this.