Develop Bugs

[Help] OOS 4 dm-verity and locked Bootloader

I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,

Unlock bootloader.
Use ADB side load to flash stock rom.
Lock back bootloader. Voila!
Hope it helps. Thanks!

i tired
I tired but after the OTA update i get the dm message again

K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
this

cpt.macp said:
this
Click to expand...
Click to collapse
I will try Tomorrow

cpt.macp said:
this
Click to expand...
Click to collapse
When i do this a have to unlock the bootloader so i have 1 message again ...

K3v1990 said:
When i do this a have to unlock the bootloader so i have 1 message again ...
Click to expand...
Click to collapse
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk

millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
ill go try that, thanks

millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
for full restet u mean Factory restet in the settings?
Edit: found it

Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Official Recovery ( Oxygen OS ) - https://www.androidfilehost.com/?fid=24591000424943319
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.

millicent said:
I had to solve same problem the other day. I unlocked, flashed stock recovery from 3.2.8 then adb sideload 3.2.8, locked bootloader, reboot and let it update to Nougat, between all steps full resets.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
It worked thank you very much

When dm-varity warning is there, i flash openbeta 7 firmware &modem . Problem solved! Never see this warning. Phone works fine.when i flash openbeta 8 firmware &modem,i wil get back the dam-varity warning

LELBOT said:
Here are the Proper Instructions to Install Oxygen OS 4.0 without DM - Verity Error and F2FS -
For Unlocked Bootloader + TWRP + Rooted users (Having any Rom installed before) -
Requisites -
Backup All your internal Storage Data - Sync all Google Stuff - backup all Messages or stuff.
Downloads -
Oxygen OS Official OTA Full Zip - https://docs.google.com/uc?id=0BzS3n...xport=download
Official Recovery ( Oxygen OS ) - http://oneplusroms.s3.amazonaws.com/...BmI3Z1Dri5Q=
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-...1211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/one...s-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/one...-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/one...stock-t3521946
Procedure -
1.) As mentioned, BACKUP EVERYTHING.
2.) Flash stock oxygen recovery though fastboot or in twrp.
3.) Boot to stock recovery, sideload Official 4.0 ota via adb.
4.) Reboot and dont set up device ( not necessary ) enable developer settings and usb debugging.
5.) Flash TWRP .23 NOT .28 (.28 is bugged with decryption and f2fs errors)
6.) Boot to twrp, wipe /data to f2fs and /system and /cache to ext4.
7.) As wiping everything, copy any custom oxygen os build and supesu 2.79
8.) Flash any custom oxygen os build ( all these 3 builds flashes supersu itself, so no need to flash supersu, buy keep it for further later use.)
9.) Reboot, Setup and copy all ur stuff.
This method will surely get u a Rooted, decrypted, f2fs /data partition Oxygen Os 4.0.
For Stock/Twrp Recovery, Encrypted/Decrytped, Locked/Unlocked Bootloader, Unrooted Users (Those who dont want to root or decyrpt) -
1.) Backup is necessary as internal storage will be wiped, its a one time process as for now every Oneplus update will be f2fs /data compatible.
2.) ADB sideload 4.0 ota.
3.) Reboot and dont set up device ( not necessary )
4.) Go to backup and reset in settings, do a factory reset with internal storage ( This will wipe everything, BACKUP NEEDED )
5.) Let the process complete and check /data partition via DiskInfo app.
6.) If it isnt, do a factory reset again via stock recovery.
7.) If nothing helps, follow first method.
I cant guarantee this will work, but many users have reported this as working.
I think this will be sufficient
Edit : New recovery by eng.stk - https://forum.xda-developers.com/devdb/project/dl/?id=22429&task=get
supports f2fs decryption.
Click to expand...
Click to collapse
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?

m_reyna_16 said:
Will this method continue working if I install a custom rom after? Also, what do u mean by the new recovery supports f2fs decryption? Does it mean that your method doesn't or that we don't have to do these steps?
Click to expand...
Click to collapse
Yes, it will work.
For the new recovery, it supports f2fs decryption and u have flash it to follow the steps.
These methods will work.

Dm-verity
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca

cryptofer said:
Hi, sorry is there any side effect if I don't correct the dm-Verity issue?
For now phone seems to work good.
Thanks in advance!
Luca
Click to expand...
Click to collapse
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk

K3v1990 said:
I need help im stuck with my OP3 with OOS 4.
I want to remove any annoying screens while booting so i need to lock the bootloader (done)
and i need this dm-verity screen away and i need help with this
can somebody give me a tutorial to do it?
Greetings,
Click to expand...
Click to collapse
Hi,
to be synthetic:
From TWRP recovery, change filesystem to Ext4 for both Data and Cache, then full wipe everything (System too);
Go back to OxygenOS v3.2.8;
Be sure to replace TWRP with Stock Recovery (download from 3.2.8 official thread);
Lock bootloader (both from Developer Options and Fastboot);
Sideload via recovery OxygenOS v4.0;
Consider to factory reset for a clean installation.
For more clarifications, I'm at your disposal

https://www.androidfilehost.com/?fid=457095661767116249
flash it
Test by me

millicent said:
The only pb I had was safetynet tests not passing. that surely disables Android pay.
Sent from my ONEPLUS A3000 using Tapatalk
Click to expand...
Click to collapse
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!

cryptofer said:
O yes this is true but I think android pay doesn't work at all on rooted devices, even without dm-Verity issue, is it true?
Thanks a lot!
Click to expand...
Click to collapse
I haven't tried it yet but I read a few reports already about systemless root with magisk being able to preserve Android pay
Sent from my ONEPLUS A3000 using Tapatalk

Root for OxygenOS 4.1.6

Hello everyone, I am using OOS 4.1.6 on my new 3T, however I am unable to get root even though I have already tried with latest TWRP, magisk 12, and SuperSU 2.82. Nothing worked everytime I've got not rooted on root checker.

Please describe in steps what you did.

AcidNoteZ said:
Please describe in steps what you did.
Click to expand...
Click to collapse
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.

mittal.bti said:
Hi,
We unclocked the bootloader, then we did flash with twrp 3.1.0 and installed SU 2.82.
After doing all this, the phone was not restarting.
Click to expand...
Click to collapse
Same here! The phone freezes in boot animation screen. Even the animation stopped!

Guessing it's about the f2fs file system. I used to have a situation like this with Oneplus 2. My step was to format data and cache partitions back to ext4, and that worked.
Using 3t now, still not rooted. Don't want to start over after bootloader unlocking
Sent from my ONEPLUS A3003 using Tapatalk

I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.

AcidNoteZ said:
Well first of all, format your whole phone over TWRP. (System too, but make sure you have the full Oxygen OS zip on a computer.)
After formating all partitions, move the full OOS zip and Magisk 12.0 on your phone. Flash the OOS zip, restart your recovery and flash Magisk after it.
That worked 100% for me all the time.
If you still need assistance with that, we can setup Teamviewer so I can guide you through this.
Click to expand...
Click to collapse
Should I flash whole os using twrp. Or should I flash Via adb sideload?

ajsonofgod said:
Should I flash whole os using twrp. Or should I flash Via adb sideload?
Click to expand...
Click to collapse
If you still want root, twrp, if dont flash it over adb

AcidNoteZ said:
If you still want root, twrp, if dont flash it over adb
Click to expand...
Click to collapse
Ok, I will try and update here then.

I'd say wipe everything possible in TWRP except for system partition, then boot the system and then eventually flash some kind of a root package - either Magisk or SuperSU. I always do it that way and it works. I am not really sure but otherwise it might have something to do with the data encryption.

Use following and you should be all set (just did it 2 days ago):
1st Flash Stock Recovery (go back to stock - https://forums.oneplus.net/threads/...-3-3t-and-go-back-completely-to-stock.456232/
Flash TWRP after you achieve STOCK OS 4.1.6.
Use this TWRP version for now (there is some issue with 3.1.1-2 i saw on forums):
twrp-3.1.1-0-oneplus3t.img
To Root just use Magisk-v13.3.zip (IMO way better than SuperSu + has MagiskHide for AndroidPay/Snapchat/SafetyNet checks):
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
That is it, done!

Showbiz81 said:
I had the same problem and was solved with twrp 3.0.4-1 and SuperSU-v2.82.
Click to expand...
Click to collapse
Thanks you are a life saver

I had the same problem and was solved with twrp 3.0.4-1 and Magisk-v13.3

Unbricking after a hard brick not working out.

So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.

yawarkhalid said:
So my OP3 got bricked and I used @Naman Bhalla guide to unbrick my phone using the second method which flashes an old OOS after unbrick. I was successful in unbricking my phone, however once the phone restarts after the unbrick tool it gets stuck in the OOS boot animation (The rotating O animation) and then it reboots and this continues.
I've tried,
1) Sideloading another Stock ROM (OOS 5.0.1.) via stock recovery: Just rebricks my phone
2) Flashing TWRP 3.1.0-0 and tried to install zip for 5.0.1 : TWRP does't recognize phone, (ERROR 7, This ROM is for OnePlus 3, This device is " ") and thus it doesn't flash.
3) Tried upgrading TWRP to 3.2.1. : could'nt do it - Lost recovery, phone just restarts to a black screen with white notification light.
4) Tried flashing OOS 4.5.1 (Nougat) via TWRP 3.1.: Does't boot up. Doesn't even go to the animation and restarts after OnePlus Logo.
Yes, I was stupid enough to not have done a nandroid backup. Desperately need help.
Click to expand...
Click to collapse
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.

tnsmani said:
Try with eng.stk's TWRP: https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Item 5 in the list.
Click to expand...
Click to collapse
Gave this a shot. Not booting up again. Goes to blank screen with white notification light.

Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.

yawarkhalid said:
Update: I've even tried rooting phone and flashing custom rom: Doesn't even go to animation
I've also tried method 1, erased the system via fastboot and reflashed the official OOS 3.1.2. zip file via adb sideload. Still the same result on official zip.
Click to expand...
Click to collapse
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.

tnsmani said:
If Method 2 doesn't work, Method 1 will definitely not work.
After flashing TWRP, are you able to boot to it (without flashing any ROM)? Flashing OOS or Open Beta will overwrite TWRP. So try this: wipe everything and flash TWRP, boot to TWRP and flash ROM and again TWRP, then flash Magisk and boot to system.
When you get white LED, hold power button for 7 to 10 seconds, it will switch off. Then press power button again and you will boot to the options menu to choose bootloader, recovery etc. You may not have to use Method 2 every time if this works for you.
Click to expand...
Click to collapse
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.

yawarkhalid said:
Hey thanks for the help. Will give this a shot now. Can you tell me what method I should use to flash magisk?
Also, I am able to access TWRP but when flashing a rom via TWRP it gives me error 7 i.e. can't install this since because it is for OnePlus 3 this device is " ". Also, with method 2 I already have a stock rom installed, I've tried wiping system via fastboot and sideloading another ROM too, that doesn't work.
Click to expand...
Click to collapse
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.

tnsmani said:
Magisk to be flashed through TWRP.
If you know how, remove this first line from the updater script and then flash it: getprop("ro.build.product") == "OnePlus3" || abort("This package is for "OnePlus3" devices; this is a "" + getprop("ro.build.product") + ""."); This is what is preventing TWRP from flashing the ROM. Removing this line will result in no checks for device type while flashing the ROM.
Click to expand...
Click to collapse
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:

yawarkhalid said:
Hi, already did that, still is't flashing.
Lastly, I managed to lock my bootloader now somehow by running the 3.0.8 version of the MSMTool. Now I have no working OS, A locked bootloader and no way to flash TWRP. I should should throw my phone in the garbage now. Shouldnt I? :crying:
Click to expand...
Click to collapse
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.

Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/

jeffrey268 said:
Take a look here:
https://forums.oneplus.com/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
or here:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
Click to expand...
Click to collapse
ummm thanks jeffery. But that tool is exactly what i've been using and what isn't working for me in ways i mentioned above. Thanks though.

tnsmani said:
NEVER GIVE UP, atleast not so soon. Contact OnePlus and ask them for a remote session, they may be able to restore it.
Though you are not able to flash TWRP, you can boot TWRP by using the adb command "fastboot boot twrp.img" and then play with it. Place the TWRP within the adb folder while trying this. (Replace twrp.img with the name of your TWRP or rename your TWRP as twrp.img)
Either you have encryption issues or you have a hardware issue if you are not able to flash anything successfully.
This is the end of my knowledge.
Click to expand...
Click to collapse
Gives me the error, "Unlock device to use this command"
I am able to flash rom via MSMTool, it even dash charges and all. But I can't boot into the system. It gets stuck in OOS animation while booting. Been at it for 3 days. Can it really be a hardware issue if my bootloader and recovery both are working?
Lastly, do you have any way I could unlock the bootloader without system permissions?

Putting an end to this madness. after 4 days in front of my laptop. Had a remote session with a OnePlus tech support team. Discarding my phone unfortunately. Thinking of shifting to a Xiaomi Redmi Note 5 Pro since I can't afford a OnePlus 5T anymore. Thanks to everyone who helped. This thread can be closed now.

Question about TWRP.

I wanted to install Lineage OS and was curious if I could install it without having TWRP flashed into recovery. I mean, I'll still use fastboot boot twrp, ill just won't have it in my recovery.
I'm asking because when I tried to do fastboot flash recovery twrp it said failed antirollback check. Would like some help if possible

Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.

corkiejp said:
Once you temporarily boot twrp, you can it flash twrp image from within it.
It would work without, but you won't be able to update LOS, unless you boot twrp again.
See: - https://forum.xda-developers.com/redmi-note-5-pro/how-to/index-everything-anti-roll-t3816219
And don't downgrade MIUI firmware/rom.
Click to expand...
Click to collapse
Thanks for your help !

Anti rollback is such a pain in the ass.

Stock ROM update to V12.0.2.0.RCOMIXM Android 11 - Magisk bootloop

My ginkgo had stock ROM V12.0.6.0.QCOMIXM (A10) and I updated to stock ROM V12.0.2.0.RCOMIXM using TWRP recovery (twrp_ginkgo-willow_3.4A9_23-12-2020_BL) However after flashing the rom zip, and after flashing magisk, my phone got into "MIUI" icon, then bootloops into recovery again with alphanumeric directory names.
I tried Disable Dm Verity Force Encrypt after flashing magisk.zip but same problem.
I have tried the following recoveries so far:
twrp_ginkgo-willow_3.4A9_23-12-2020_BL
twrp-3.5.2_10-2-ginkgo
orangefox R11.0_1 (with Disable DM-Verity, Disable Forced Encryption and Aggresive stock recovery deactivation all enabled).
But whenever I flash magisk, I still get the bootloop and alphanumeric directory names, and the only way to restore my phone without having to wipe data is to flash the recovery zip again (but without magisk).
Any suggestions on how to get around this?

bomberb17 said:
Any suggestions on how to get around this?
Click to expand...
Click to collapse
i already answered you here
use this DFE