Develop Bugs

Can't install inremediatepack or any ROM

Hi guys,
I need some helps to fix my phone, here is what i did :
I used to have a custom ROM ( CM 11 by Spanorg ) and yesterday i wanted to downgrade to an official Stock ROM (B315)
I wiped out all data and system of my phone using TWRP recovery, then I installed stock recovery.
Next and in order to install my stock rom (b315) I had to first install the intermediatepack there my troubles started.
As recommended I formated my SDCard and created a folder named "dload" where I put the UPDATE.APP file of the intermediatepack
After reboot on download mode it doesn't work ! I have " Version list verify fail! " error message.
Same error is I try with the B315 stock ROM directly
worse I can't even install custom ROMS like my old one ( CM 11 by Spanorg ) : I get signature error
I can't even change my recovery software, when in booloader mode ( Volume down + power button ) My phone is unrecognized by my computer : "UNKNOWN USB COMPOSITE DEVICE".
Any idea on how i can fix this ?

nobody has a clue ^^ ?

finally it worked, I kept trying to access bootloader mode ( Volume down + power button ) without success until once i tried while my phone was connected to PC and Yooopi ! it was recognised and I manager to install a custom recovry

Cannot update 3.2.8 to 4.0.1 without getting dm-verity warning

So i had 4.0.1 rooted before. I decided to return to stock by flashing full 4.0.1 on TWRP. That's when I started getting the error. I flashed 3.2.8 on stock recovery 2.0 and dm-verity error is gone. But installing 4.0.1 on stock recovery 2.0 results to dm-verity error again. I cannot use adb sideload as my computer is too slow
More details: before, I successfully updated my OP3 with 3.2.8 to 4.0.1 without the dm-verity warning. After that, I flashed blu_spark's TWRP v11, swiped to allow modifications and rooted it with SuperSU 2.79 and flashed some mods, still no warning. Yesterday, I decided to return to full stock. I updated my TWRP to the unofficial 3.0.3-0 (the official one wasn't available yesterday yet), wiped system, cache, and data excluding internal storage, then flashed 4.0.1. The dm-verity warning started to show. I followed your guide and other guides here on XDA, I cannot fix it. The only solution I found is to rollback to 3.2.8, I installed the zip file on the stock recovery from your guide (flashing the recovery before). I'm having problems with adb sideload, PC lags so much and sideloading never finishes, so what I do is copy the zip file in the internal storage. After I flashed 3.2.8 and rebooted, the recovery was replaced by the V1.0 version that doesn't have the function of installing zip from internal storage, so I flashed your stock recovery again. Booting to the new recovery, I flashed the 4.0.1 zip and the dm-verity warning shows again.
Right now, my OP3 is on 3.2.8 with stock ROM, kernel, and recovery. No dm-verity warning. I don't know how to update to 4.0.1 without getting that again

Simple. New bootloader added that warning and the old one never had a dm-verity nag screen. Flash it and ignore it. It shows up due to TWRP installed.

Check the freedomos thread and download the 3.2.7 fw and flash with TWRP and its gone, I am not using the nougat fw on 4.0.2, always make nandroid backups

install beta 7 firmware

Don't bother! It's not worth it! It's just a stupid message!

I have tried by following these steps (I initially had twrp-3.0.2-1.28-oneplus3 installed):
1. booted to TWRP recovery;
2. copied recovery_OBT8N.img to phone;
3. installed stock recovery_OBT8N.img via TWRP as image > recovery;
4. booted to stock recovery (directly from TWRP);
5. while in stock recovery, I have wiped the phone (for a clean flash);
6. installed OxygenOS 4.0 (N) via ADB;
7. once the installation got completed, I rebooted the phone;
8. once the phone started, I did not finished the startup setting;
9. switched-off the phone and booted in fastboot mode;
10. flashed TWRP recovery - twrp-3.0.2-1.28-oneplus3 again;
11. switched off the phone;
12. started the phone in TWRP recovery; TWRP asks for a password to decrypt - ignore it;
13. wiped the phone (I wanted to do so to make sure it is a really clean install, even if this wipes everything);
14. rebooted again to TWRP recovery; this time I did not get any password prompt;
15. from TWRP, I copied SR1-SuperSU-v2.79-SR1-20161221223537.zip to phone storage (while connected to my laptop, obviously);
16. installed SR1-SuperSU-v2.79-SR1-20161221223537.zip, wiped data & cache and rebooted system;
17. everything went fine, with no dm-verity and rooted.

It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .

cpt.macp said:
It will Keep showing Because You flashed Oxygen OS from TWRP . Try flashing this just after flashing the OS .
it will disable DM verity and disable force encryption .
Click to expand...
Click to collapse
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.

bkcheah75 said:
Please try this method. Tested and it works for me.
step
Assuming your bootloader is unlocked. Copy
1. fastboot boot twrp twrp-3.0.2-1.28-oneplus3.img
2. Now you will be in TWRP, perform wipe -> Format Data, perform Wipe -> Advanced wipe "All folder" except USB-OTG
3. Reboot to recovery
4. adb sideload OnePlus3Oxygen_16_OTA_037_all_1701041839_401.zip (if adb cannot read, because filesize too big. Use laa_2_0_4.zip to fix the adb.exe first.)
5. After adb sideload done, reboot to TWRP immediately, enable MTP to copy the file: no-verity-opt-encrypt-5.1.zip into your internal storage and install no-verity-opt-encrypt-5.1.zip immediately.
Then everything will be fine.
Click to expand...
Click to collapse
I was not having any Issue . But Surely Your Help and concern is much appreciated
and Yes this is also one of the way to remove DM verity and use the zip

Currently using:
ROM - FreedomOS-2.1
TWRP - blu_spark_v11-oo3
Phone - Encrypted
I have the DM-Verity message at boot. Would reflashing FreedomOS-2.1 Through TWRP & then immediately flash no-verity-opt-encrypt.zip get rid of the message?
Thanks

PLEASE Help | DM-Verity and PASSWORD when loading

Hello. OnePlus 3. Strange problems. I can see DM-Verity 50/50. And 50/50 need type password to start system. Need press "BACK" or type password from system (standard android, pin-code/graphical key, etc.)
I flash stock OxygenOS via stock recovery with full wipe (erase everything) but have bootloop, if force reboot - loading successful, but reboot next time, modem(connection) don't working.
I tried this method and deleted DM verity, but entering the password is also required.
Next reboot DM-Verity remains.
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
Also i tried mega unbrick method, using programm (1GB)
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
This installed OxygenOS ~3.1.2. But problems remains.
TWRP now. I can't flash stock recovery via fastboot flash recovery recovery_op3.img
Ok it's flashes, but when i try enter - black screen and smartphone off.
What need make, that would completely remove DM-Verity and password. And flash latest stock recovery and OxygenOS.
Mega Please Help.

GO!

SunEpicMist said:
Hello. OnePlus 3. Strange problems. I can see DM-Verity 50/50. And 50/50 need type password to start system. Need press "BACK" or type password from system (standard android, pin-code/graphical key, etc.)
I flash stock OxygenOS via stock recovery with full wipe (erase everything) but have bootloop, if force reboot - loading successful, but reboot next time, modem(connection) don't working.
I tried this method and deleted DM verity, but entering the password is also required.
Next reboot DM-Verity remains.
https://forum.xda-developers.com/oneplus-3t/how-to/fix-dm-verity-warning-final-fix-4-0-3-t3555094
Also i tried mega unbrick method, using programm (1GB)
https://forum.xda-developers.com/oneplus-3/how-to/guide-mega-unbrick-guide-hard-bricked-t3405700
This installed OxygenOS ~3.1.2. But problems remains.
TWRP now. I can't flash stock recovery via fastboot flash recovery recovery_op3.img
Ok it's flashes, but when i try enter - black screen and smartphone off.
What need make, that would completely remove DM-Verity and password. And flash latest stock recovery and OxygenOS.
Mega Please Help.
Click to expand...
Click to collapse
try this
https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685

Restore to latest Marshmallow firmware.
Be sure to have locked bootloader (both from ADB and developer settings), then upgrade via OTA.
You just have to check and confirm for update.
It worked for me

startup problem after installing new ROM by TWRP

after receiving a phone with a problem Gyro sensors and aceelérmetre, I tried to solve the problem by installing twrp and trying other ROMs, but one moment the phone does not want to start and stays every time in the start screen installation infinitly
i still have access to twrp, and i tried all knowns solutions except flashing throw EDL mode
Please help me

More details required!
What rom did you try to install.
And before testing other roms. You should have checked that it wasn't a hardware problem (faulty device) with stock rom.
^^^ Tap on kernel version a few times in about would open a service menu, where it is possible to test hardware.
MIUI doesn't boot with TWRP installed if you don't flash lazyflasher or use a TWRP version that includes it.

Question: does your phone stay permanently in this mode? What rom did you install and what type of ARP do you have? What version of twrp do you have? I remember I had the same issue because I force encrypted my phone accidentally but then it just didn't start sometimes. That's why I am asking.
Option 1: go back to twrp -> format your device (should erase all sort of encryption and it has the same effect as a factory reset as well) -> reinstall custom rom and your stuff again -> flash lazy flasher or Magisk (that should take care of dm verity & force encryption as well).
Option 2: check your ARP version (fastboot getvar anti) custom roms usually don't have any firmware whatsoever and as long as you don't downgrade you are safe anyway. Just to be safe: if you are on version 3 everything should be fine, if you are on 4 you have to do some research what to do but it's not a big deal to be honest.
Option 3: Install redwolf instead of twrp (then you don't need to flash lazyflasher as well) -> install rom.
Tell me if anything has worked.
Installing recovery either via fastboot flash recovery recovery.img -> power off -> power on + volume up -> allow modification to system partition.
Or do it like fastboot boot recovery.img -> install (in your recovery) -> select image (bottom right) -> flash recovery.img (works especially good with ARP v4)
Either way after that do your thing in case you want to change/update your twrp or redwolf.

Boot screen problem
I am using orange fox recovery r10. When i flash havoc os 3.0, evolution x os and other os it always stuck in boot screen. It just opens with the pixel experience rom only. And when i tryed to restore my phone rom it shows "mount read only" . I am using redmi note 5 pro (whyred). Please help me to solve my problem.

if i were you, i will boot to twrp - boot to fastboot - flash miui using fastboot. if you're not confident google how to do it.

Question Find Device storage Corupted. Your device is unsafe now.

Find Device storage Corupted. Your device is unsafe now. This messgae keeps popping now and then anyway to fix it. Using Stock MIUI 12 13.0.10. Device is Mi 11x (Aliothin).
tried recloking and full flash of firmware erasing everything still no hope.
Any fix

Hi,
Read my post,
CTS doesn't pass even with locked bootloader.
I have poco f3 and i installed a custom ROM on it but then i wanted to use MIUI but when i locked bootloader i got device memory corrupted issue which someone suggested me to fix by flashing persist img and i did that but another problem arise...
forum.xda-developers.com
I hope it helps.

Thanks @johnr64.
Followed these steps using OrangeFox Recovery. TWRP had persmission issues.
1. Boot to OrangeFox Recovery ( Command below only works if booted to OrangeFox Recovery, if you dont have recovery installed just use fastboot command : Fastboot boot ornagefoxrecovery.img)
2. Go to 3 dot menu at bottom and choose terminal
3. type: dd if=/sdcard/persist.img of=/dev/block/bootdevice/by-name/persist
4. After its finished reboot to the system, finished and fixed.