I had received incremental Update which I went through with. Then after incremental update was done, Downloaded the full ROM from oxygen updater and flashed patched boot, vendor boot and disabled dm-verity with vbmeta. Now the phone still shows orange state after flashing the patches and vbmeta. Is it because I rooted the phone on an incremental update? Will flashing the full zip (same version) and then rooting work? Or will it brick the phone. Will the orange state message go away if I do a full zip flashing via local update and then disable dm-verity with vbmeta. Please help me
Currently on NE2211_11_C.22
sinduchari said:
I had received incremental Update which I went through with. Then after incremental update was done, Downloaded the full ROM from oxygen updater and flashed patched boot, vendor boot and disabled dm-verity with vbmeta. Now the phone still shows orange state after flashing the patches and vbmeta. Is it because I rooted the phone on an incremental update? Will flashing the full zip (same version) and then rooting work? Or will it brick the phone. Will the orange state message go away if I do a full zip flashing via local update and then disable dm-verity with vbmeta. Please help me
Currently on NE2211_11_C.22
Click to expand...
Click to collapse
same with me, after check with fastboot oem device-info the device is unlocked
Wrong thread. Sorry.
Related
I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.
Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.
do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?
przemcio510 said:
Afaik you have to downgrade to Nougat, disable and enable dm-verity and upgrade again to Oreo.
Don't use SuperSU, Magisk will be better solution.
Click to expand...
Click to collapse
I cant find the proper files. Can you please link me a thread from which i can follow the step and find the files.
Bradl79 said:
do u mean u are getting the second screen during boot up about the dm_verity not in enforcing mode?
Click to expand...
Click to collapse
Yes
FOLLOW THIS GUIDE TO DISABLE DM-VERITY
READ POST 2 IN OP, I HAVE ALSO DESABLED DM-VERITY FOLOOWING THE GUIDE BELOW:
You will need to reinstall custom ROM+gapps package if you are using custom ROM but if your are using official oxygen OS or oxygenOS based OS like theOne3t, you will not need to reinstall the full ROM at the end of process.
Have a look and carefully proceed. It works..........
https://forum.xda-developers.com/oneplus-3t/how-to/disable-dm-verity-force-encryption-op3t-t3688748
usually happens when u install stock OxygenOS without root or no_dmverity, u can install 4.0.2 fw via twrp and go to fastboot and type via cmd
Code:
fastboot oem enable_dm_verity
then u can reflash current fw of what u r on.
malikahmed205 said:
I triggered dm verity on my Oneplus 3t (8.0 oreo 5.0.0 oxygen OS) while trying to root my device. Is there anyway i can fix this. I installed superSU on my phone thru TWRP but it didnt get rooted. And now an update is available but I it is just rebooting everytime i try to install the official update.
Click to expand...
Click to collapse
dm-verity should not (in itself) prevent the update from installing. I have dm-verity tripped (warning screen on boot) and have updated many times (maybe 5-6 updates) with no problems at all. I suspect something else is going on. What version TWRP, and how big is the update file?
When you try to update, how are you doing that, following the notification when the phone is booted to OS? Or are you in TWRP, and try to flash the update?
This happened to me as well when trying to root.
If you are getting warning that dm-verity is not enforcing, then see this thread: https://forum.xda-developers.com/on...e-red-warning-dm-verity-t3727959/post75022331
I also had to use the latest version of Magisk (15.3) for rooting to work properly.
Sent from my OnePlus3T using XDA Labs
Is there any alternative method to lock bootloader and unroot the device? I have read other topics that it will required to flash back to 4.0.1 version and install stock recovery.
Possible to have adb lock bootloader and reflash latest OOS 5.0.5 without flashing Magisk module?
Sent from my [device_name] using XDA-Developers Legacy app
Switched last week from Pixel Experience 9.0 (unencrypted) to OOS 5.0.5 and locked the bootloader.
Flashed the latest OOS from TWRP (with all wipes done before);
Waited for the phone to boot OOS 5.0.5 once - without root the TWRP is gone ,replaced with stock recovery;
Rebooted to stock recovery and performed another factory reset;
Waited for the phone to boot OOS 5.0.5 again (to be sure everything it's fine);
Rebooted to bootloader (fastboot) and executed: fastboot oem lock command;
Done!
P.S. - Backup your files before any wipe or bootloader re-lock.
[d]amour said:
Is there any alternative method to lock bootloader and unroot the device? I have read other topics that it will required to flash back to 4.0.1 version and install stock recovery.
Click to expand...
Click to collapse
Do what the previous response says. Just flash the 5.0.5 full zip, reboot to wipe TWRP. Then relock bootloader.
I suspect the only reason the guide you mention, says to flash 4.0.1, is because the guide is old, and 4.0.1 was just the latest version at the time. There isn't any requirement to "downgrade" to an older version, to return to stock/unrooted/locked bootloader.
lesbianu said:
Switched last week from Pixel Experience 9.0 (unencrypted) to OOS 5.0.5 and locked the bootloader.
Flashed the latest OOS from TWRP (with all wipes done before);
Waited for the phone to boot OOS 5.0.5 once - without root the TWRP is gone ,replaced with stock recovery;
Rebooted to stock recovery and performed another factory reset;
Waited for the phone to boot OOS 5.0.5 again (to be sure everything it's fine);
Rebooted to bootloader (fastboot) and executed: fastboot oem lock command;
Done!
P.S. - Backup your files before any wipe or bootloader re-lock.
Click to expand...
Click to collapse
Didn't you face DM-verity warning?
If yes, then how you removed it:-by
"ADB sideload" command or by any other means?
Please specify..........
If I had extra problems, for sure I would warn you about them. No warning, no problem, full stock "like out of the box"!
lesbianu said:
If I had extra problems, for sure I would warn you about them. No warning, no problem, full stock "like out of the box"!
Click to expand...
Click to collapse
As per my knowledge, if you flash oxygen OS OTA without magisk then DM verity flag must be triggered, which only goes by sideloading the same OTA file or updated OTA zip file.
No idea, I told you the steps I made few days ago. They worked for me! Want to believe, good. Don't want to believe, even better.
Was on OOS 5.0.4 (bootloader unlocked), decrypted to test Pixel Experience 9.0 for 2 days and then returned to "full stock" OOS 5.0.5 (bootloader locked) to send the phone in service for upper speaker problems. I know it was not necessary to lock the bootloader, but it was my personal choice.
P.S. - Stop quoting the previous post, it's not necessary.
ersandeepkr said:
As per my knowledge, if you flash oxygen OS OTA without magisk then DM verity flag must be triggered, which only goes by sideloading the same OTA file or updated OTA zip file.
Click to expand...
Click to collapse
DM verity is triggered when changes are made to the system/kernel. If you flash a stock OTA file (with no Magisk or other changes) then DM verity is not triggered. Maybe it will be triggered when TWRP is still on the device (not 100% on that), but that will be taken care of when TWRP is overwritten.
You can sideload the OTA as described on the OnePlus website, if you like. But I don't think the result will be any different.
Hello everyone,
Today I had a notification telling me that there is a new version of both magisk manager and module. Therefore I first updated the manager successfully and proceeded to update the module through in-app flash. After the flash completed, app prompted me to reboot. However, the reboot process never finished and the phone got stuck while booting. Since then I only tried factory reset which only booted the phone to let me enter my sim card password but after that, it rebooted itself to boot loop again. Some info about the phone:
TWRP installed and still working,
Latest xiaomi.eu from that won't boot anymore,
Only viper4droid and youtube vanced modules were installed.
AdAway for obvious reasons.
and that's it. Now I am planning on flashing crdroid ROM to make the phone work again but the installation process requires me to do:
Flash MIUI11 eea with miflash : min V11.0.8.0.QFAEUXM note : if already on v11.08.0 there's no need to redo
Flash vbmeta.img with "fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification" note : if already done there's no need to redo
Flash TWRP in fastboot and boot into TWRP
Click to expand...
Click to collapse
is there a step that I should skip? It's been 6 months since I handled the initial process to be able to flash xiaomi.eu from therefore I don't remember how I exactly did that as I have only been OTA updating the from since then. I don't remember or know how to flash V11.0.8.0.QFAEUXM nor vbmeta.img nor TWRP. I don't even know if I "should" flash those. I am open to any different suggestions or help to let me achieve my goal of flashing crdroid to get out of this mess.
Thanks in advance!
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
in my personal experience, if you get rebood to twrp, flash Disable Dm Verity ForceEncrypt to boot into rom
title
Was Magisk installed before the update? Since you are saying it rebooted to TWRP without you knowing, were you able to restore stock images before updating? Could you also provide information concerning the update? For example, miui version (updating from vXXX to vXXX)
jjsan said:
i saw an update on Redmi Note 8T (11.0.9).
I'm rooted with TWRP, so I just tried to update. New update was downloaded into directory downloaded_rom.
phone was automatically rebooted into TWRP, but I didnt know there is update in that directory. I just rebooted device into system.
I got a message that update failed. I click update and started to look for file/folder created during download process. So i discovered directory downloaded_rom in root folder.
phone was automatically rebooted into recovery (twrp) and it was flashing update without my help.
after reboot, device was updated. the only thing to do was flash TWRP (i have paid version of TWRP) and flash magisk.
everything works fine and my phone is rooted on 11.0.9.
i thing, that second file was whole ROM (1.9GB)
Click to expand...
Click to collapse
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
jjsan said:
Was Magisk installed before the update? - yes, device was rooted, with Magisk installed
were you able to restore stock images before updating - dont understand this, after downloading update and clicking on install, device was rebooted into twrp
miui version (updating from vXXX to vXXX) - update from 11.0.7.0 to 11.0.9.0
Click to expand...
Click to collapse
What I meant was whether you uninstalled Magisk/restored original boot img prior to the update because sometimes not doing so tends to result in bootloop (happened to me before). I needed some information before I attempt the update myself. Thank you for replying.
P.S. One more question: All data was preserved, right?
So i just Got the REALME UI 2.0 update via System Updater and i downloaded is IMMEDIATELY.
But when i tried to install it via ORANGEFOX RECOVERY. It gave me error saying "this Package is for RMX1931L1" and couldnt install on this device.
Can please someone explain what it means, and how can i install this package.
EDIT. 1 : First i installed unofficial TWRP
than i installed C.38 ozip to get Stock recovery than i Relocked Bootloader (which wiped everything internal memory and everything) than i rebooted and checked for update. Got the A11 update downloaded it and Flashed it.
And now i am on A11 stock Locked bootloader and Working Fine.
BTW i live in INDIA
I think you're going to hard brick your device if you've got the bl unlocked and try to flash the official update through OrangeFox. My suggestion is to move the ota file to your pc, relock the bootloader if you're on rui1.0, then move the file and flash it clean, with the bl locked.
How did you even get the update, where do you live?