Develop Bugs

Oneplus 3 decryption and stock recovery problem HELP!!!

I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible

aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
Click to expand...
Click to collapse
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.

I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.

aaditya98 said:
I have been trying to flash oxygen os open beta 9 on my oneplus 3
first i tried the official steps mentioned on the oneplus site
I flashed stock oxygen os recovery
but when i boot into recovery mode it asks for a pattern which upon entering does not decrypt
I then flashed official TWRP and tried to flash the full open beta .zip file but it shows this package is for oneplus 3 this is a ""
also if i try to flash the modified TWRP 28 then also it cannot decrypt the phone
I would prefer not to format the phone if at all possible
Click to expand...
Click to collapse
unfortunately no choice other than wiping everything.....

antisoma said:
I'm having a similar issue. So any advice would be great. Just updated to most recent unofficial TWRP (having been on a previous version). Now when entering my pin to decrypt it is not accepted. Would prefer not to have to format data.
Click to expand...
Click to collapse
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.

Hw4ng3r said:
I believe the decrypt is a known issue with TWRP and OB8/OB9 with F2FS /data partition. I don't think there's a work around at this time without formatting /data and rooting to prevent encryption.
Click to expand...
Click to collapse
So do you think there would be workaround in future?

0xelectron said:
So do you think there would be workaround in future?
Click to expand...
Click to collapse
Hopefully there will be, but it doesn't look promising right now. @eng.stk is the one that was modding the TWRP, but has since stopped doing TWRP dev.

kipue said:
Hi, I think you should try to format data. Probabby via fastboot, then install TWRP.
Not sure which are the correct commands for the full format, so have a look around or someone else will help.
Otherwise there is the unbrick guide here in the forums to try.
Click to expand...
Click to collapse
But I'm on official 3.2.8 with ext4 partition

Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.

nqk said:
Do you guy know where to get the stock recovery for openbeta 9? I downloaded somewhere a file recovery_OBT8N.img, but it still shows dm-verity issue.
Click to expand...
Click to collapse
Fastboot Format system and data
Then fastboot flash stockrecovery
Then boot to system
Sideload rom
Then fastboot boot twrp28
Then wipe data and install superuser in one go

candiesdoodle said:
Fastboot Format system and data
Click to expand...
Click to collapse
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.

nqk said:
you mean: fastboot erase userdata?
Btw, I just ignore the dm-verity message to enter stock recovery, and do adb sideload openbeta9.zip and when it boots up again, the dm-verity message is no longer there.
I would try to format (erase userdata) data and flash the modded twrp.
Click to expand...
Click to collapse
Yeah fastboot Format userdata
But since you don't have the dm-verity you can skip the fastboot Format. Boot into the modd twrp and when it asks for password, hit cancel and then format data (you will have to type 'yes').
Then flash SuperSU or superuser in the same session without booting. This will ensure dm-verity doesn't come up again as it will start in enforcing mode, thanks to SuperSU/superuser.
You may be able to flash twrp afterwards but I haven't tried it.

Encryption issues on Nougat firmware

Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.

You could try with other TWRP versions? Say 3.0.2-22

It's a known issue

Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).

Simone98RC said:
Hi guys,
just nowadays I installed OxygenOS Open Beta 10.
I was upgrading from Open Beta 7, but since I unlocked bootloader after doing that, we can say that I did a clean install (everyone should know that fastboot oem unlock erase all data).
However, I'm having troubles both with stock recovery and TWRP v3.0.2-1.28: pattern won't to be recognized.
If I disable pattern requiring at bootup, in recovery I need to type "a password" (that obviously is wrong in any case).
I tried to reinstall more times the firmware, also did factory reset both via stock/TWRP recovery and fastboot commands.
But nothing has changed.
System is working, but I can't access to recovery anyway.
Click to expand...
Click to collapse
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption

If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.

All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!

atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Password I hope can be managed with the new modified TWRP mentioned below by @abhibnl but I am more concerned with the dm verity message not going...
---------- Post added at 12:37 AM ---------- Previous post was at 12:30 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
confirmed password request gone...
dm-verity still exist...
phone does not boot past oneplus logo..can boot into recovery or fastboot but no system loading..
now i am sideloading os from twrp

mnishamk said:
You could try with other TWRP versions? Say 3.0.2-22
Click to expand...
Click to collapse
It's not working, because modded TWRP from .18 to .23 are designed for Marshmallow community builds.
dbabaev21 said:
Use twrp v3.0.2-1.19
Works with no issues, except a mouse pointer in the middle of the twrp. It does not interfere with anything, it is just there (a bug).
Click to expand...
Click to collapse
What I've said above (tried .19 too with same unsuccessful result).
atulclassic said:
go to fastboot..
fastboot erase recovery
fastboot flash stock recovery (Open Beta 8)
reboot to recovery
wipe data
flash OOS 4.0 via sideload
reboot..skip setup..reboot to fastboot
fastboot flash twrp (modified)
reboot to recovery
wipe data
advance wipe data to f2fs
reboot
No dm-verity and no encryption
Click to expand...
Click to collapse
Probably it would be risolutive, however I want to stay on latest Community Build.
I can say that sideload won't work with Open Beta 10: it can be flashed only via recovery (both TWRP and stock).
jim262 said:
All you have to do is wipe data partition. Reformat it as f2fs, all in TWRP and then reboot system and proceed with setup. Done!
Click to expand...
Click to collapse
That would be easy! The hoped behaviour
Obviously I've just tried with unsuccessful result.
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @abhibnl solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.

badmaash said:
Cannot find Open Beta 8 Recovery on the download link mentioned above. Looked else where but cannot locate.
Also I flashed recovery_OBT7.img (presumably Open Beta 9 recovery) and followed as mentioned above but DM Verity error does not vanish and TWRP also still asks for password.
Click to expand...
Click to collapse
The recovery should be linked in the official OB10 download page @ oneplus.net

Simone98RC said:
Are you referring to this recovery?
Yeah, I would be in love both with you and the developer, if it works properly
Tomorrow I should try, I'll keep you updated :good:
UPDATE: I've always loved Magisk, since v7 (when I've started using it).
Magisk is the workaround for encryption: just today I've flashed it together with Open Beta 10.
Now encryption is disabled, so goodbye to recovery troubles.
However the issue can't be considered solved because of a stupid workaround, this is not the right approach: I will try @atulclassic solution (re-enable encryption, then install latest blu_spark recovery).
Thanks all for answering.
Click to expand...
Click to collapse
Yes i was referring to that recovery. 1 user has responded that it worked fine on his f2fs encrypted storage, so i believe it's worth trying. I am not on f2fs so i personally can't test it for you. But i would advise you to atleast give it a try. You never know when you by mistake boot right after a fresh stock rom install with stock kernel, and it will immediately encrypt your storage. So, you can't always just keep formatting internal memory. A proper TWRP recovery is indeed required for both ext4 and f2fs. All i am waiting for is updated kernel sources for recovery devs to work on.

For the many having issues, here's a step by step:
step by step install for OOS 4.0 and twrp-3.0.2-1.28-op3.img
Have OOS stock recovery installed on your phone. You must also have adb installed on your computer.
connect your phone to your computer via usb and open a dos command session on your computer.
On your phone, reboot into fastboot (bootloader).
From adb command on computer, type fastboot boot twrp-3.0.2-1.28-op3.img.
First make a backup and copy it to a safe location.
Now wipe everything - Internal, system, data, cache.
Reboot to Recovery. This is the stock OOS recovery!
Go to install from USB and then enter sideload mode.
On your computer dos prompt, type adb sideload (path)OnePlus3Oxygen_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Allow the long and slow process to complete and reboot.
Upon reboot, it is encrypting the data partition as EMMC.
Upon bootup, enter setup and go through it quickly as you will have to enter it again so do not waste time configuring it.
Once setup is complete, reboot into fastboot.
From DOS command, enter adb and type command fastboot boot twrp-3.0.2-1.28-op3.img.
TWRP will boot up asking for encryption password. Hit cancel and then swipe to allow modifications.
Go into mount. Only the system and cache will appear. Back out and select WIPE.
select ADVANCED WIPE and data partition only.
Modify the data parition by selecting Repair or Change file system.
It will list the current mount point as emmc. Select Change File System.
Select F2FS and swipe.
This will wipe current data partition and reformat it.
Once you have done this, while in TWRP, select the ADVANCED button on the main menu.
Now select ADB SIDELOAD and swip to start sideload.
On your computer in ADB, type command adb sideload SR1-SuperSU-v2.79-SR1-20161221223537.zip.
Now reboot system and go through the usual setup and your done.

TWRP v11: the definitive solution
abhibnl said:
If you are on f2fs and encrypted, the blu spark kernel dev released a new recovery that supports f2fs decryption in TWRP. It may save you all the hassle. All you need to do is flash that updated recovery from fastboot and then try to decrypt. It should work fine.
Click to expand...
Click to collapse
FINAL UPDATE: the specified recovery is working with Open Beta 10 decryption.
Thanks all for answering :good:

[HELP] im stuck with no os and mtp wont work in twrp and also ADB isnt working

i flashed miui 9.3.28 and then booted twrp , but it was asking for password so i went to wipe and repaired data using ext4 ,and then procceded to wipe data, vendor, cache, system and now im stck with no os and i cant use adb sideload to install a rom please help :crying: :crying: :crying: :crying: :crying: :crying: :crying:

Reboot into fastboot(keep pressed power and vol - buttons until you plug cable to pc otherwise it can start rebooting system) and flash latest fastboot miui(you need to unzip it first): http://en.miui.com/a-234.html via XiaoMiFlash tool with clean all option. If you can't see your device in tool press refresh in MiFlash tool you have also Driver section check this. Another option is to install google latest_usb_driver via device menager(right click on your device->update-driver->browse pc -> and select usb driver.

I got the exact same problem after flashing the same beta build. Nothing worked for me so I had to flash the fastboot image and roll back the stable channel.

Op next time don't wipe vendor partition.In your case you should get recovery with supports MIUI on androind 9 and if ou had encrypted data you should format the data. Here you have similar situation: https://forum.xda-developers.com/redmi-note-5-pro/how-to/recovery-pie-update-miui10-t3916963 (I didn't try this one)

Remember For decryption it only needs to format data partition only.
How will it boot if you wiped system as well as vendor partition.
If you can get in recovery just flash the update file 9.3.28 and u r ready to go.

I did all that and formatted the data partition which was decrypted afterwards. The problem is that internal storage gets re-encrypted after I boot to system.

HeRoKaNe said:
I did all that and formatted the data partition which was decrypted afterwards. The problem is that internal storage gets re-encrypted after I boot to system.
Click to expand...
Click to collapse
Flash lazyflasher-no-verity-opt-encrypt after flashing custom ROM and then decrypt. Try if it's works.

Letrix said:
Flash lazyflasher-no-verity-opt-encrypt after flashing custom ROM and then decrypt. Try if it's works.
Click to expand...
Click to collapse
I tried that but every time the installation fails with ERROR: 1.

HELPPPP
I was on Masik X3.7
I want to install to another rom
so , I booted into TWRP and formatted data.
from then my laptop not recognizing device.
Also, not able to boot in to Fastboot mode !
it shows charging sign in TWRP.

rasik107 said:
HELPPPP
I was on Masik X3.7
I want to install to another rom
so , I booted into TWRP and formatted data.
from then my laptop not recognizing device.
Also, not able to boot in to Fastboot mode !
it shows charging sign in TWRP.
Click to expand...
Click to collapse
same problem here, please someone help!

ltv07 said:
same problem here, please someone help!
Click to expand...
Click to collapse
actually it was booted in fastboot mode only.
just that logo was not visible.
so u can connect device and try to run "fastboot devices" to check if its connected !

ltv07 said:
same problem here, please someone help!
Click to expand...
Click to collapse
Resolved installing older twrp version

ltv07 said:
Resolved installing older twrp version
Click to expand...
Click to collapse
Can you give the version of twrp which worked in Pie.

Regarding your problems
Copy any rom to a micro sd card and flash it through twrp if done ur done

Try using OrangeFox Recovery, I had the same issue ADB & MTP connection with TWRP for Whyred.

varunsngh786 said:
Copy any rom to a micro sd card and flash it through twrp if done ur done
Click to expand...
Click to collapse
rockstar1997 said:
Try using OrangeFox Recovery, I had the same issue ADB & MTP connection with TWRP for Whyred.
Click to expand...
Click to collapse
Thanks. My main problem was that mtp driver of Miui was wrong. And the decrypt error was solved by Redwolf recovery. i have yet to try OrangeFox one.

rockstar1997 said:
Try using OrangeFox Recovery, I had the same issue ADB & MTP connection with TWRP for Whyred.
Click to expand...
Click to collapse
You're a rockstar! I was also having the same problem and orangefox fixed it!
Thanks mate!

Question MI 12X system partition Corrupted/deleted Need Urgent Help Please. ??

my 12X system storage Corrupted/deleted after installing TWRP, I'm New A/B partition system. now I can't access the storage even flashing with MI Flash tool not work. PLz plz someone expert help me out. how to resolve it ? will be so grateful.

ajoy25 said:
my 12X system storage Corrupted/deleted after installing TWRP, I'm New A/B partition system. now I can't access the storage even flashing with MI Flash tool not work. PLz plz someone expert help me out. how to resolve it ? will be so grateful.
Click to expand...
Click to collapse
Check here that everything has been done correctly
https://forum.xda-developers.com/t/flash-tool-guide-use-xiaomi-flash-tool.4262425/

ajoy25 said:
my 12X system storage Corrupted/deleted after installing TWRP, I'm New A/B partition system. now I can't access the storage even flashing with MI Flash tool not work. PLz plz someone expert help me out. how to resolve it ? will be so grateful.
Click to expand...
Click to collapse
How did you install twrp? Did you flash the twrp to boot partition? If yes, you need to find out which system you had installed and then flash the suiting boot.img.
Background: In A/B partition scheme, recovery is part of boot.img. Boot.img needs to be patched by twrp. So normally you need to boot twrp by typing "fastboot boot twrp.img" and then, when twrp is booted, go to advanced and press "flash current twrp"

Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.

Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.

ajoy25 said:
Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.
Click to expand...
Click to collapse
Ok, you already deleted data. Try to format data via fastboot. Use "fastboot -w" and retry!

ajoy25 said:
Thank you for ur kind reply, I have flashed the TWRP as u said & its OK..I'm heaving problem with Flashing EU Rom after deleting data I flashed the rom but it's stuck in the boothloop then entering TWRP showing SD memory "0"..plz tell me the process of flashing rom & Magisk. Thanks again.
Click to expand...
Click to collapse
Maybe start one thing at a time.
Problem with twrp
Try flashing this Fastboot rom
Download the rom/extract it/open the folder /use first install.bat with the phone in Fastboot mode
https://sourceforge.net/projects/xi...13.0.5.0.SLDCNXM_v13-12-fastboot.zip/download
then install the TWRP and update the rom via OTA (do not put any security on the lock screen).
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img​
then in Twrp go to Advanced -> flash current TWRP->reboot TWRP
If that doesn't work/see post https://forum.xda-developers.com/t/...need-urgent-help-please.4491461/post-87424405

NOSS8 said:
Maybe start one thing at a time.
Problem with twrp
Try flashing this Fastboot rom
Download the rom/extract it/open the folder /use first install.bat with the phone in Fastboot mode
https://sourceforge.net/projects/xi...13.0.5.0.SLDCNXM_v13-12-fastboot.zip/download
then install the TWRP and update the rom via OTA (do not put any security on the lock screen).
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
Power shell
./fastboot boot twrp.img​
then in Twrp go to Advanced -> flash current TWRP->reboot TWRP
If that doesn't work/see post https://forum.xda-developers.com/t/...need-urgent-help-please.4491461/post-87424405
Click to expand...
Click to collapse
Thank you for ur kind support. I have managed to flash it with mi flasher & rooted it with masgisk.

Question (Please help me) Mounting problems

Hello,
I recently tried to flash a custom rom on my poco f3, but I couldn't install twrp, because I didn't have the option to install it when i boot to it.
So I followed some instructions online and formated data partition to ext2, and then back to ext4. Now I can't copy any files to the phone storage and can't do anything else.
I can reboot to fastboot, and I can boot to twrp, but it's pretty much useless because I can't sideload anything, and can't install twrp anyways.
Did I do something wrong? Is it easily fixable?
Thanks in advance.

f2fs?

aIecxs said:
f2fs?
Click to expand...
Click to collapse
I don't understand what you mean, sorry. I'm newbie.
Should I format the data partition to f2fs？

Idk depends on ROM. MIUI is f2fs

aIecxs said:
Idk depends on ROM. MIUI is f2fs
Click to expand...
Click to collapse
Oh. I tried a different twrp version and could install it on the phone. Now flashed crDroid and it said my system was broke so had to factory reset. It is working now. Thanks.

But now I can only access the crDroid recovery, how can I install back twrp? if I try to fastboot boot twrp.img it simply reboots back to system.

try to boot TWRP from other slot maybe? (don't forget to switch back)
Code:
fastboot --set-active=other
fastboot boot twrp.img
if that fails just flash TWRP into vendor_boot partition, and restore vendor_boot.img from crDroid right after