Develop Bugs

the dm verity is not started in enforcing mode

Hi,
I get on my OP3 this issue when I start the phone.
it dissappeers in 5 sec. Phone is working fine.
"the dm verity is not started in enforcing mode".
Help? kiss

YourTheBest said:
Hi,
I get on my OP3 this issue when I start the phone.
it dissappeers in 5 sec. Phone is working fine.
"the dm verity is not started in enforcing mode".
Help? kiss
Click to expand...
Click to collapse
It is just a warning. This is no issue and from the kernel.
I managed (i do not know how i have done this) to install oos beta 8 with supersu and without this message.
I experimented a little bit. I flashed the extracted beta 8 firmware and flashed the system via fastboot.
But i do not know why this message is completly away from my phone.

If you don't want to see it flash stock recovery

I did the following..
1. Sideload OxygenOS 3.2.6 from TWRP
2. Flash stock recovery from OnePlus downloads
3. Sideload from stock recovery Open Beta 8
Stock recovery is rewritten by new recovery and no more dm error.
Oneplus 3 dm-verity verification failed when i boot

https://forums.oneplus.net/threads/...ailed-when-i-boot.476968/page-3#post-15476095

But what is causing this problem in the first place? Is it because twrp is give permissions to make changes to the /system partition? And this dm-verity thing, will it cause any problems if left as it is?

ali.jujara said:
But what is causing this problem in the first place? Is it because twrp is give permissions to make changes to the /system partition? And this dm-verity thing, will it cause any problems if left as it is?
Click to expand...
Click to collapse
No, you can leave it there, it's just a warning.
Sent from my OnePlus 3 using Tapatalk

I found simple fix.
just flash CB 7 firmware and modem throuth twrp.
https://www.androidfilehost.com/?fid=457095661767116249

ZeppeMan said:
I did the following..
1. Sideload OxygenOS 3.2.6 from TWRP
2. Flash stock recovery from OnePlus downloads
3. Sideload from stock recovery Open Beta 8
Stock recovery is rewritten by new recovery and no more dm error.
Oneplus 3 dm-verity verification failed when i boot
Click to expand...
Click to collapse
.
So no more twrp in build 8. you're rocking stock recovery right? if yes, how you're able to gain root? as far as I know, there are no ways to root oxygen os 8/9 from inside.
.
Ps. I wanna lock my bootloader. flash build 9 with stock recovery. like new intact phone. plus, I wanna gain root from inside (without the help of twrp). any help or opinion?

I was on OB10. i unlock bootloader and flashed twrp. after this dm-verity error keeps coming at every boot. I tried formatting to ext4 file system but no luck. After some time i gave up and flashed OB10 again. Any idea on how to unlock and flash custom roms without dm-verity error? If I revert back to 3.2.8, can i flash the nougat roms without error?

Search the forum . Everything is answered
here

stuck in twrp after OTA update

i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!

You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.

neeraj679 said:
You messed up! Everyone knows that before flashing ota you should be on OnePlus recovery now you can sideload oos or flash through twrp.
Click to expand...
Click to collapse
should I flash any other rom or the oos 4.0...???

pranav_j619 said:
should I flash any other rom or the oos 4.0...???
Click to expand...
Click to collapse
which twrp version are you using? also do you have encryption issues in twrp? you might not need to reflash the rom butmay be reset the phone and install updated twrp. there are couple of threads. i myself saw this issue on my device

I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.

You can flash newest BluSpark TWRP and the the 4.0.2 Full ZIP, then it should work

This is the solution that worked for me
MM MaD said:
I faced the same issue. Just flash the stock recovery and boot the phone. The update will fail and you'll be back on.
Click to expand...
Click to collapse
I had the same issue, flash the stock recovery 2.0 on the phone (the one that takes 64Mb) and then boot the phone. As mentioned it'll fail but then you get out of the loop and can flash whichever recovery and rom you feel like. And thanks for the people that mirrored the recovery while it was not on the official page, and to the people that suggested this, it was a pain to fix the first time.

pranav_j619 said:
i installed the official nougat update via VPN. Then rooted my op3 with nougat using modified twrp. Today i receieved OTA of 30mb, i downloaded it and click reboot. And then the problem started. The device continues to boot in twrp and im not able to use my op3.
Please HELP.......!!!!!!!!!!!!!!!
Click to expand...
Click to collapse
Had this issue before, just look on your internal memory, there is a folder called ".OTAsomething", in there the OTA zip is stored, delete it and the phone will boot to Oxygen OS again.

The terrible fate of refurbished N5X

Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?

Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.

negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.

CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?

negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.

CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.

negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.

CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader

sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot

[AOSiP, Android 9] Not booting after OTA on encrypted device

I hope that someone here can help me rescue to rescue my data.
I was on the AOSiP build from september and than decided to encrypt my device. That worked perfectly. Now I wanted to install the latest update. The internal updater didn't work (just booted into TWRP recovery without further action, so I moved the update file to microsd and than updated manually by flashing the zip file via TWRP). Prior to the whole action, I updated TWRP through the app to the latest version.
Now my phone doesn't boot anymore, it is stuck in the AOSiP boot animation. Reverting to a previous TWRP version (3.2.3.2) didn't help, also flashing the september build again didn't help.
In TWRP I was unable to decrypt data, because TWRP keeps asking me for a password (but I don't remember putting a password in the first place). Therefor I switched from TWRP to OrangeFox recovery. Here decryption worked, put still after flashing the phone doesn't boot.
Anyone that has further ideas how to fix this without loosing all my data? Any help appreciated!

Have you tried installing another kernel?

kotobodj said:
Have you tried installing another kernel?
Click to expand...
Click to collapse
No, but as my system was running before without problems I don't expect the kernel to be the problem .. Or why would that make sense?

SOLVED: I noticed that flashing the update manually didn't automatically flash Gapps right afterwards. So flashing the Gapps helped and the phone now boots normally!

TWRP+ Magisk issues. HELP?

Hi! I have a moto z2 play with the Pie stock rom flashed. Bootloader is unlocked but when I try to flash TWRP (used twrp_albus_treble_3.2.2_r23_64) via fastboot after the first system reboot it is always overwritten by default recovery. I tried to boot first to bootloader and than to TWRP, also tried booting the TWRP image and installing TWRP from phone storage, nothing works after system reboot it is always replaced by stock recovery. What am I doing wrong?
I also tried to install Magisk but it wont install, tried flashing through TWRP and also by patching the boot.img than flashing that.
Could use your input!
Thanks!

I have the same problem
I have the same problem

L7noop said:
I have the same problem
Click to expand...
Click to collapse
Did you find a working solution?