Develop Bugs

Op3 only boots into twrp after failed update

Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...

I have the same problem

Here the same but with CM14 after a wrong download & install now Recovery Loop
How to solve???

I had this problem too. Flash the Oxygen recovery OB7. It will update automatically and turn on. But be patient because it takes a lot.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
The way I found works is to start from scratch and yes you will lose all data on the phone. Had to do this yesterday because I messed a few things up.
Make sure you have the modified recovery (1.28), Beta 9 Full (1.3GB), and SuperSU (SR5) if you want root, on your computer. And you will need your computer for these steps.
1. Boot to TWRP > Wipe > Format Data. There's a warning screen you just type yes and press enter. This should set your /data partition to F2FS; all other partitions will remain EXT4. (The TWRP MTP didn't pop up on me so then I had to reflash twrp from fastboot). If your PC see's your device after this step, skip to step 9, but my guess is, when you format data, the required files for MTP disappears with it.
2. Power off your device.
3. Put device into fastboot mode (start device by holding volume up + power)
4. Connect device to PC.
5. fastboot flash recovery modded_twrp.img
6. Disconnect device from computer and shut down phone.
7. Load recovery (start device by holding volume down + power)
8. Connect to PC
9. TWRP MTP should be working; transfer the recovery file, beta9, and super SU (if you want root) to your internal storage.
10. I usually disconnect my phone from my PC at this point.
11. Go to Install > sdcard > media folder (your files should be here).
12. Flash Beta 9 zip.
13. Reflash modded TWRP (click Install Image button and you should see your TWRP file).
14. Reboot to Recovery (I noticed that click on Reboot and Recovery freezes TWRP on me, so you can manually power down by holding power button down).
15. Swipe to accept modifications
16. If you don't need root, you're all done. The first boot takes like 5 min.
For some reason for root, it doesn't work if you try without freeing up some space in the system folder. What you can do is:
1. In TWRP > Mount > tick off System > head back out to main menu
18. Advanced > File Manager > > system folder > app folder > and delete some google apps (ie. calendar, gmail, chrome; should be enough; can be downloaded from play store later)
19. Flash SuperSU SR5.
20. Wipe Cache and Dalvik, reboot.
I've noticed that if you don't root, your device will be encrypted on first boot of beta 9 (which causes some issues in TWRP not being able to mount the /data partition and decryption passwords not working in TWRP.

Same problem here, **** broken OB9 update.
EDIT: For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.

I used twrp-3.0.2-22 to reflash beta 9 all is well.
I have same problem with twrp-3.0.2-1.28. Just boot into bootloader and flash twrp-3.0.2-22.

Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.

No need for clean installation like hw4ng3r said.
I'll copy my other post's edit here if someone needs it.
For those with the same problem, download stock recovery from here, flash it using adb, boot into recovery (might say that installation of update failed, it did for me) and then reboot to system.
Now it booted successfully and says that I have Open Beta 9. TWRP and SuperSU installations worked just fine after that.
Click to expand...
Click to collapse
Got 145849 AnTuTu result with OB9. Might be able to get a better result if I were to clean install, but I've just dirty flashed every update since 3.2.5.

karliyo said:
No need for clean installation like hw4ng3r said.
Click to expand...
Click to collapse
Very true.
I interpreted the OP's comment as:
1. Already on TWRP
2. Tried full wipe and install (all data lost anyways)
---------- Post added at 12:23 PM ---------- Previous post was at 12:19 PM ----------
Tumpster said:
Can I flash that twrp-3.0.2-22 after I'm already on beta 9?
Nevermind I saw that it encrypts on first boot. I'll just wait for root again until after the final comes out.
Click to expand...
Click to collapse
I've read that .22 TWRP doesn't have decryption issues of the /data partition like .28 has, but don't take my word for it. And the encryption happened to me when I flashed Beta9 from TWRP .28 and rebooted system without flashing Super SU.
The decryption of the /data partition in TWRP seems to be an issue if the file system is F2FS on Beta 8 and Beta 9. I haven't had any issues with EXT4.

sibmon said:
Hello,
I wanted to update my op3 from Beta8 to Beta9 while using ota. I didnt realised that I had twrp installed. So after booting into recovery nothing happened.
Now I cant reboot my op3. It only boots into twrp. Even a normal flash and a full wipe + install cant restore anything...
Click to expand...
Click to collapse
Download stock recovery from OnePlus site (on very bottom) ,flash it using fastboot and than sideload new beta 9

failed to flash ob 10 and can only boot into recovery now

Tried to flash flash ob 10, but twrp said the zip was corrupted. I could not boot into the system anymore.
The problem is the system partition is ok ( verified from twrp file manager), but every time I choose reboot system, it will go back to twrp. I tried to re-flash ob 9, but twrp again reported another error. Log is attached. How should I solve the problem?
By the way, I wipe all data, including storage in twrp by mistake. Is there any way to recover the data? I am traveling now, just got several hundred pictures.:crying::crying: It seems to be impossible to do it on a computer in MTP mode, but I could not boot into the system neither.

Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.

You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?

zTweaked said:
Download the modded twrp from here and install it. Use it to flash community builds and all other roms from now on.
About the file recovering part, I wouldn't know.
Click to expand...
Click to collapse
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Update: flashing stock recovery seems to be effective ( of course, twrp does not exist anymore ).

SoybeanYoung said:
I am always using the modified one. I am encountering a weird error.
The message is like
'E: unknown command [log]
........
script succeeded: result was [1.000000]'.
Click to expand...
Click to collapse
Unknown command is a known and harmless issue on all 7.x.x roms. Just ignore it and go ahead.
And I think I saw 3.0.2-1 twrp version in your log.
---------- Post added at 09:20 AM ---------- Previous post was at 09:18 AM ----------
pmbabu said:
You need to flash stock recovery, ADB sideload the official Open Beta, and boot into ROM.
By any chance, did you trigger an OTA update with TWRP installed?
Click to expand...
Click to collapse
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.

After you flash any rom, reflash recovery. Reboot to RECOVERY & then to system.
The red message it's on almoust every Nugat rom. And it's about some log .

zTweaked said:
Open Beta builds can be flashed via modded twrp, no need to use stock recovery and adb sideloading. Plus even if he installed an OTA update, it won't get installed on twrp ~ and no harm will be done.
Click to expand...
Click to collapse
He said he could only boot into twrp. That occurs (reboot to system will take it back to twrp over and over) only if someone tried an OTA update with twrp.

I don't think this is the case for you, but if you tried the other suggestions don't work try the below. I had a similar issue and found that my recovery partition was corrupted. However, an additional symptom I had was that my TWRP would hang completely when selecting reboot after any successful flash. I think modded TWRP does not like internal storage wipe from within TWRP (rather than through fastboot format userdata).
Boot to fastboot
Fastboot erase recovery
Fastboot flash recovery filename.img
Boot to recovery and flash your desired ROM+supersu which you can sideload via MTP (drag and drop from Windows) or adb push C:\SourceLocation\filename.zip /sdcard
I recommend ADB push over MTP.

Had the exact same problem as op, after some issues i was forced to use the unbrick method to get phone back as it wasn't even booting. Now im using beta 10 perfectly.

Did you manage to fix it? I have the same probem.

OnePlus 3 dont decrypt + dm-verity error at boot

Hey XDA m8s,
i want to decrypt my OP 3. So i completely cleared it and fresh installed OOS Beta 10. Now its still encrypted. I did this 5-10 times.
Bootloader: Unlocked
Recovery now: Stock
1. Tried fastboot wipe userdata
2. Tried TWRP Data Reset
3. TriedAndroid normal Factory Reset
4. Tried to install OOS with Stock and TWRP Recovery
Everytime I install OOS 4 or Beta 10 TWRP asks me for a password after installation to decrypt File System. I dont have any password and i dont encrypted my device.
And now there is coming a dm-verity error everytime i boot. I dont know what that means...
The device is working but i cant flash TWRP and install SuperSU or other Zips cause of this ****ty password that i dunno.
Any ideas??
thx m8s
blackjan

blackjan said:
Hey XDA m8s,
i want to decrypt my OP 3. So i completely cleared it and fresh installed OOS Beta 10. Now its still encrypted. I did this 5-10 times.
Bootloader: Unlocked
Recovery now: Stock
1. Tried fastboot wipe userdata
2. Tried TWRP Data Reset
3. TriedAndroid normal Factory Reset
4. Tried to install OOS with Stock and TWRP Recovery
Everytime I install OOS 4 or Beta 10 TWRP asks me for a password after installation to decrypt File System. I dont have any password and i dont encrypted my device.
And now there is coming a dm-verity error everytime i boot. I dont know what that means...
The device is working but i cant flash TWRP and install SuperSU or other Zips cause of this ****ty password that i dunno.
Any ideas??
thx m8s
blackjan
Click to expand...
Click to collapse
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process

Hw4ng3r said:
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Click to expand...
Click to collapse
I flashed the official nougat update yesterday using the stock recovery and I somehow got the dm-verity error? I heard somewhere that I had to reflash the stock recovery even tho I already have it? I used to have TWRP but that was back in 3.2.2 of Oxygen OS but I switched back because I wanted OTA updates too work

Hw4ng3r said:
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Click to expand...
Click to collapse
Is the Dm verity error cause of android 7?

blackjan said:
Is the Dm verity error cause of android 7?
Click to expand...
Click to collapse
That DM verity screen is not an "Error" screen its just "Warning" screen meaning that the FW files were not digitaly signed. Its something Google introduced a while ago but has really started pushing since Nougat. There's no way to avoid it (except to flash a seperate script to disable it) theres one floating around here but might have been in Nexus thread. Personally i flashed 3.2.8 Fw after flashing OOS 4 and it got rid of the "Warning" but that might cause issues down the road. As of now though all is running as it should. hope this helped
Sent from my OnePlus Pixel using XDA Labs

blackjan said:
Hey XDA m8s,
i want to decrypt my OP 3. So i completely cleared it and fresh installed OOS Beta 10. Now its still encrypted. I did this 5-10 times.
Bootloader: Unlocked
Recovery now: Stock
1. Tried fastboot wipe userdata
2. Tried TWRP Data Reset
3. TriedAndroid normal Factory Reset
4. Tried to install OOS with Stock and TWRP Recovery
Everytime I install OOS 4 or Beta 10 TWRP asks me for a password after installation to decrypt File System. I dont have any password and i dont encrypted my device.
And now there is coming a dm-verity error everytime i boot. I dont know what that means...
The device is working but i cant flash TWRP and install SuperSU or other Zips cause of this ****ty password that i dunno.
Any ideas??
thx m8s
blackjan
Click to expand...
Click to collapse
Goto TWRP and wipe>factory reset
copy SuperSU zip using TWRP MPT support and flash now boot systems the twrp wont ask for password nor wil you ge DM-verity error

Hw4ng3r said:
The encryption will always occur if you don't flash supersu before first boot.
Dm-verity error is strange if you flashed the open beta or oos 4 from stock recovery. This warning only happens when you flash from twrp.
You need to do a format data from twrp or wipe data cache > erase everything from stock recovery to "decrypt" but you will lose all your files in the process
Click to expand...
Click to collapse
Scronix said:
Goto TWRP and wipe>factory reset
copy SuperSU zip using TWRP MPT support and flash now boot systems the twrp wont ask for password nor wil you ge DM-verity error
Click to expand...
Click to collapse
is there a method to flash systemless SuperSU without doing a Factory Reset? // What is the password when i boot to TWRP when Android installed? On Android 6 was it possible? Is it new that Android encrypt the Filesystem or what??

blackjan said:
is there a method to flash systemless SuperSU without doing a Factory Reset? // What is the password when i boot to TWRP when Android installed? On Android 6 was it possible? Is it new that Android encrypt the Filesystem or what??
Click to expand...
Click to collapse
ich hab gerade das selbe problem aber ich fürchte das nur ein entschlüsseln hilft ( also fastboot format userdata ). Und vor dem 1. start der systems eben supersu flashen.
english: I have the same problem and I think the only solution is a complete decrypt. And after this, flash supersu before you boot the system the first time.

blackjan said:
is there a method to flash systemless SuperSU without doing a Factory Reset? // What is the password when i boot to TWRP when Android installed? On Android 6 was it possible? Is it new that Android encrypt the Filesystem or what??
Click to expand...
Click to collapse
The New Android 7.0 Nougat Introduced a bit of a secure partition Which Encrypt the system without asking The New Twrp Isnt Completely Compatible yet Due to New Kernel Sources not released This is a workaround to have root you have to factory reset in TWRP once to get it working

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,encryption and dm verity will be gone and 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.

oneplus fooling us??
is the open beta 10 and oxygen os OTA same????? they havent uploaded any links on the oneplus downloads page

You worry to much for a 2 seconds message...

Phone always boots into twrp not able to see one plus boot logo.Pls help

I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue

Flashing a lower version and then the 28 version back helped me... Had the same problem

jaganmohans said:
I had formatted all things including internal storage using twrp. After that I flashed oxygen os 4.0 with USB using twrp.Installation is successfull.But when I rebooting the system it still boots into TWRP screen.I am not able to see one plus boot logo as it always boots to twrp screen even after successfully installation.I am wondering why even after succesfull flashing still the phone always boot into twrp screen.Pls help in resolving the issue
Click to expand...
Click to collapse
1 ) flash stock recovery and sideload full zip of 3.2.8 oxygen os
2) boot to system
3) reboot to stock recovery
4) sideload full zip of 4.0.1
5) boot to system
6) boot to bootloader and flash twrp -28 recovery (adb fastboot flash)
7) after flashing boot to twrp recovery from bootloader
8) flash SU SR2 v2.79 and boot to system

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