Related
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.
Hello,
I've just installed the new OOS4.0, and I also wanted to update the filesystem to F2FS:
I've managed to get everything working with twrp-3.0.2-1.28 (ext4 cache/system - f2fs userdata) but then, I enrcypted the data via the settings menu, and now the TWRP fails to decrypt (password invalid). I understand that this is some kind of incompatibility since if I try with the official recovery it decrypts without problems.
Since I still have to copy all my userdata to the phone and install everything, what should I do before?
a) Keep data encrypted and wait for a TWPR fix, and eventually flash with the official recovery if needed?
b) Reformat and keep the data unencrypted?
c) You tell me?
Thank you for your help.
This is the only reason why I am still waiting for a proper twrp first. Don't want to decrypt my storage, and move all the data from my phone to laptop and then back to phone. Too much of a hassle.
Hurizen said:
Hello,
I've just installed the new OOS4.0, and I also wanted to update the filesystem to F2FS:
I've managed to get everything working with twrp-3.0.2-1.28 (ext4 cache/system - f2fs userdata
Click to expand...
Click to collapse
I can't answer your question, but can I ask how you converted the data partition from ext4 to f2fs? I have TWRP 3.0.2-1.28 and OOS 4.0 already installed, and was wondering what the best way to do it is.
Do custom ROMS such as CM14.1 and XenonHD support f2fs?
Now, if I'm on OOS 4.0, no root, stock recovery; how can i get F2FS?? Thanks!
Hurizen said:
Hello,
I've just installed the new OOS4.0, and I also wanted to update the filesystem to F2FS:
I've managed to get everything working with twrp-3.0.2-1.28 (ext4 cache/system - f2fs userdata) but then, I enrcypted the data via the settings menu, and now the TWRP fails to decrypt (password invalid). I understand that this is some kind of incompatibility since if I try with the official recovery it decrypts without problems.
Since I still have to copy all my userdata to the phone and install everything, what should I do before?
a) Keep data encrypted and wait for a TWPR fix, and eventually flash with the official recovery if needed?
b) Reformat and keep the data unencrypted?
c) You tell me?
Thank you for your help.
Click to expand...
Click to collapse
Well, I have tested this method both on OpenBeta9/10 and OSS4.0-
MOST IMPORTANT - FLASH TWRP .23, .28 HAVE BUGS WITH DECRYPTION AND F2FS (TESTED AND REPORTED BY MANY USERS)
1.) Flash 4.0 through stock recovery for dm verity error or flash 4.0 modem + firmware through twrp, skip this step if u r already on 4.0
2.)Copy all internal data to pc and make nandroid backup if needed.
3.)Wipe data to f2fs and cache/system to ext4.
4.)As wiping all these partitions, decryption will be gone and rom will be wiped, flash ur OSS 4.0(I prefer Builds like Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 OR HyperStock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-t3521946 , this one doesn't tiggers encryption and dm verity error.)
5.)Wipe cache and dalvik and reboot.
6.)Setup and install DiskInfo app to check partitions.
I know this method is bit lengthy, but u will get as u needed, decryption and f2fs for data with no dm verity errors.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
abhibnl said:
This is the only reason why I am still waiting for a proper twrp first. Don't want to decrypt my storage, and move all the data from my phone to laptop and then back to phone. Too much of a hassle.
Click to expand...
Click to collapse
Pachulongui said:
Now, if I'm on OOS 4.0, no root, stock recovery; how can i get F2FS?? Thanks!
Click to expand...
Click to collapse
Well, u can try flashing stock recovery and do factory resets for 1-2 times.
I have tested this on ob9 and got f2fs without wiping storage( As told by devs)
If this method doesn't works, then simply unlock bootloader, flash twrp and decrypt data with fastboot or through twrp cos someday u have to decrypt ur data.
Grab a holiday or sunday, copy all data and backups.
Enjoy F2FS life. :good:
LELBOT said:
Well, I have tested this method both on OpenBeta9/10 and OSS4.0-
MOST IMPORTANT - FLASH TWRP .23, .28 HAVE BUGS WITH DECRYPTION AND F2FS (TESTED AND REPORTED BY MANY USERS)
1.) Flash 4.0 through stock recovery for dm verity error or flash 4.0 modem + firmware through twrp, skip this step if u r already on 4.0
2.)Copy all internal data to pc and make nandroid backup if needed.
3.)Wipe data to f2fs and cache/system to ext4.
4.)As wiping all these partitions, decryption will be gone and rom will be wiped, flash ur OSS 4.0(I prefer Builds like Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259 OR HyperStock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-t3521946 , this one doesn't tiggers encryption and dm verity error.)
5.)Wipe cache and dalvik and reboot.
6.)Setup and install DiskInfo app to check partitions.
I know this method is bit lengthy, but u will get as u needed, decryption and f2fs for data with no dm verity errors.
---------- Post added at 09:35 AM ---------- Previous post was at 09:29 AM ----------
Well, u can try flashing stock recovery and do factory resets for 1-2 times.
I have tested this on ob9 and got f2fs without wiping storage( As told by devs)
If this method doesn't works, then simply unlock bootloader, flash twrp and decrypt data with fastboot or through twrp cos someday u have to decrypt ur data.
Grab a holiday or sunday, copy all data and backups.
Enjoy F2FS life. :good:
Click to expand...
Click to collapse
I was using OOS 3.2.7 official and yesterday I thought of getting OOS 4.0 on my OP3. And I did flash the Experience ROM via Twrp - 3.0.2-1.28, but I was still on ext4 file system.. And I was getting a dm-verity error.. Then I decided to change the /data file system to f2fs and reflashed the Experience ROM. Now Diskinfo does shows my file system as f2fs but how to get rid of this dm-verity error with this Rom intact as I've done the setup of all my apps that I had before...
sanjeevrai97 said:
I was using OOS 3.2.7 official and yesterday I thought of getting OOS 4.0 on my OP3. And I did flash the Experience ROM via Twrp - 3.0.2-1.28, but I was still on ext4 file system.. And I was getting a dm-verity error.. Then I decided to change the /data file system to f2fs and reflashed the Experience ROM. Now Diskinfo does shows my file system as f2fs but how to get rid of this dm-verity error with this Rom intact as I've done the setup of all my apps that I had before...
Click to expand...
Click to collapse
Brother, as u have flashed experience rom which already contains 4.0 modem + firmware, then dm verity shouldnt pop up.
Try to download and flash 4.0 modem+ firmware again through twrp, if this didnt help then try Hyper Rom.
If nothing helps, then follow the procedure i mentioned, backup all apps through titanium backup and sync all google stuff, make nandroid if any thing goes wrong, download official 4.0 full zip, flash stock oxygen recovery and do a adb side load.
Then flash twrp and clean flash experience or hyper rom u needed and restore apps back with titanium backup.
Report if something goes wrong
LELBOT said:
Brother, as u have flashed experience rom which already contains 4.0 modem + firmware, then dm verity shouldnt pop up.
Try to download and flash 4.0 modem+ firmware again through twrp, if this didnt help then try Hyper Rom.
If nothing helps, then follow the procedure i mentioned, backup all apps through titanium backup and sync all google stuff, make nandroid if any thing goes wrong, download official 4.0 full zip, flash stock oxygen recovery and do a adb side load.
Then flash twrp and clean flash experience or hyper rom u needed and restore apps back with titanium backup.
Report if something goes wrong
Click to expand...
Click to collapse
I did try to do the last thing that you mentioned. I flashed the official 4.0 through sideload. And dm-verity issue did vanish. But I thought of changing everything to f2fs. So I changed the type of system, data and cache. And flashed the Experience rom. But then, a strange thing started to happen. I just couldn't save any screenshot or pics I click but I was able to install or delete apps. So, I again went to TWRP (was really a hassle because I had to delete everything on phone and change system and cache to ext4 leaving just the data on f2fs and then doing several reboots and factory resets to get everything working). And then I flashed Experience Rom and I'm back to square one with dm-verity...
Still, I'd try to flash 4.0 firmware + modem files explicitly. And then I'll report. Thanks for the info, brother. :good:
EDIT: I tried to flash the 4.0 firmware + modem files but no luck with dm-verity issue..
Btw, I've a question. What's the downside of having this issue besides having that splash screen of warning on every boot up?
Can anyone properly give instruction on how to install OOS 4.0 without getting dm error + F2FS?
there's a lot of instruction in other thread that making this confusing.
sanjeevrai97 said:
I did try to do the last thing that you mentioned. I flashed the official 4.0 through sideload. And dm-verity issue did vanish. But I thought of changing everything to f2fs. So I changed the type of system, data and cache. And flashed the Experience rom. But then, a strange thing started to happen. I just couldn't save any screenshot or pics I click but I was able to install or delete apps. So, I again went to TWRP (was really a hassle because I had to delete everything on phone and change system and cache to ext4 leaving just the data on f2fs and then doing several reboots and factory resets to get everything working). And then I flashed Experience Rom and I'm back to square one with dm-verity...
Still, I'd try to flash 4.0 firmware + modem files explicitly. And then I'll report. Thanks for the info, brother. :good:
EDIT: I tried to flash the 4.0 firmware + modem files but no luck with dm-verity issue..
Btw, I've a question. What's the downside of having this issue besides having that splash screen of warning on every boot up?
Click to expand...
Click to collapse
As, I posted above, wipe data to f2fs and sys/cache be ext4, no changing them.
you have to follow the procedure i mentioned.
U can check this also, he posted almost the same as mine - https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
burningDew said:
Can anyone properly give instruction on how to install OOS 4.0 without getting dm error + F2FS?
there's a lot of instruction in other thread that making this confusing.
Click to expand...
Click to collapse
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 - http://otafsc.h2os.com/patch/amazon...en_16_OTA_035_all_1612310359_e10cadfb2af7.zip
Official Recovery ( Oxygen OS ) - https://www.androidfilehost.com/?fid=24591000424943319
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-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, 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.
^thanks for the instructions
LELBOT said:
As, I posted above, wipe data to f2fs and sys/cache be ext4, no changing them.
you have to follow the procedure i mentioned.
U can check this also, he posted almost the same as mine - https://forum.xda-developers.com/oneplus-3/how-to/fix-device-mapper-verity-simple-trick-t3530685
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=0BzS3nWITUqU_Sk5yQkRqWkhFY3c&export=download
Official Recovery ( Oxygen OS ) - http://oneplusroms.s3.amazonaws.com...694818&Signature=DSUZrSJyV46Dd/JKBmI3Z1Dri5Q=
TWRP Recovery 3.0.2 - 23 (IMPORTANT) - https://www.androidfilehost.com/?fid=529152257862684308
SuperSU 2.79 Stable - http://downloadmirror.co/Utz/UPDATE-SuperSU-v2.79-20161211114519.zip
Custom Rom Based on OOS ( Choose any) - Freedom OS - https://forum.xda-developers.com/oneplus-3/development/rom-freedomos-1-0-t3409348
Experience Rom - https://forum.xda-developers.com/oneplus-3/development/rom-experience-rom-v1-0-t3522259
Hyper Stock - https://forum.xda-developers.com/oneplus-3/development/hyperstock-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, 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.
Thank you for root users.
But if you flash Oxygen recovery & Oos 4.0 via adb you have just to wipe all in Oxygen recovery and your partition data make f2fs ?
After flash Twrp and custom Oos build.
I read in many post for flash Oos 4.0 you must have Twrp modify 28 ? With the 23 work too.
The problem they are no solution for root user to format data f2fs and flash custom Oos 4.0 directly with Twrp ?
Many root users flash custom Oos 4.0 with Twrp 27 but don't format to f2fs ! Stay in Ext4 and that run great. Ex : Fos.
---------- Post added at 06:49 AM ---------- Previous post was at 06:22 AM ----------
Hi ! Every body good news the dev blu_spark realese the new Twrp work with encrypt f2fs ?
Thanks blu_spark ?
Twrp-3.0.2.0_blu_spark_vll-op3
Click to expand...
Click to collapse
i used this method to solve the problem
On my phone what ever oos i install, 4.0, 4.0.1, 4.0.2, data it's formated to F2FS.
To remove DM-verity message it's easy.
Boot to FASTBOOT and type this commands one after another:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Now i'm on FreeDom 2.3 (oos 4.0.2) with twrp-3.0.3 x v.15 blu spark 23.01.17
null0seven said:
On my phone what ever oos i install, 4.0, 4.0.1, 4.0.2, data it's formated to F2FS.
To remove DM-verity message it's easy.
Boot to FASTBOOT and type this commands one after another:
fastboot oem disable_dm_verity
fastboot oem enable_dm_verity
Now i'm on FreeDom 2.3 (oos 4.0.2) with twrp-3.0.3 x v.15 blu spark 23.01.17
Click to expand...
Click to collapse
For dm_verity, only the enable command is necessary, not the disable one.
It was like that in original post.
I'm currently running my OP3 on Resurrection Remix 5.7.4 (MM 6.01), the phone has the latest version of TWRP and I've flashed other ROMs in the past without any issue
RR has proven to be quite unstable for me, the system UI keeps crashing, which renders the phone unusable until after a reboot so I wanted to flash Freedom OS as that worked quite well for me previously. When I tried to flash the ROM in TWRP the ROM seemed to flash successfully but when I rebooted, only the boot logo showed and then the screen went black and the phone refused to respond at all for about two hours, after that exactly the same thing happened. I managed to boot into recovery and tried flashing a different ROM but the result was the same every time, the only way to get the phone to work normally was to flash RR again/restore from a Nandroid backup, either way, the result is the same, I'm stuck on an unstable ROM and I don't know why, the last time I flashed these ROMs they worked fine, I followed all of the instructions for flashing said ROMs to the letter, I have the latest version of TWRP, etc.
Also it seems TWRP can't mount /system, in TWRP under "mount", system is unchecked, I checked it and tried again but found that whenever I rebooted the phone or attempted to flash a new ROM, it would always uncheck itself and flashing the ROM would fail, however strangely flashing the same version of RR was always successful. Is this why the flashing keeps failing and does anyone know what the problem could be?
Thanks!
bronderb said:
Go into your bootloader and format system, cache, and userdata (This will wipe EVERYTHING so be sure to backup). Then latest official flash stock rom and reboot. This should fix it. If this helped hit thanks!
Click to expand...
Click to collapse
Bootloader? There is no option in the bootloader to delete everything as far as I can see, do you mean in recovery? And if I wipe everything off the phone, how do I get the stock ROM onto the phone to flash it? When you say wipe userdata do you mean wipe internal storage or am I misunderstanding and you're telling me to wipe the usual dalvik, cache and data as you would for a normal clean flash?
bronderb said:
No, go into fastboot and plug into pc. Open cmd and type "fastboot format userdata" "fastboot format cache" "fastboot format system"
Click to expand...
Click to collapse
Okay, thanks, and then what? Do I flash TWRP then push the stock ROM to the phone and flash that? And exactly how do I do that?
bronderb said:
You just go into twrp (no need to reflash) then adb sideload oxygen os
Click to expand...
Click to collapse
Thank you, I am now running OOS, hopefully everything else will go smoothly now, planning to go back to FOS again
I didn't even have to use the fastboot commands to format, just sideloading the OOS file wiped everything anyway
Turns out the issue isn't actually fixed, "system" still appears unchecked in TWRP. Could the fact that I didn't actually format everything first have made a difference, given everything was wiped in the process anyway?
Looks like I'm going to be living the sideloading life...
Edit: Sideloading freedom OS failed, ended up having to restore from my TWRP backup. I don't know what I'm going to do, my main reason for using custom ROMs is installing a black theme, and OOS doesn't support Layers or Substratum fully so I can't stay on that
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
frickinjerms said:
Is the thing that says "mount system as read-only" enabled in the mounts menu? /System isn't ever mounted when TWRP starts, you have to manually mount it, but as long as the updater-script tells /system to mount, it will. However, if that option to make it read-only is enabled, then nothing will ever write to /system. Last resort is deleting the .twrps file from /sdcard/TWRP folder to remove current TWRP preferences and then when you boot into TWRP, that first screen has the swiper to allow modifications, and you'll swipe that
Click to expand...
Click to collapse
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
evilkitty69 said:
It isn't set to read only, I have tried updating and resetting TWRP but nothing has helped, in fact it's got worse, I managed to sideload OOS but my attempted install of FOS failed so I tried to restore from a backup and that also failed, something which didn't happen back when I was on RR.
Click to expand...
Click to collapse
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
tnsmani said:
Which version of TWRP are you running? The official 3.1.0-0 is good for OOS and OOS based ROMs only. Try eng.stk's version.
Click to expand...
Click to collapse
I was running 3.0.2-2 when the issue started, I updated to 3.0.3 and 3.1.0-0 but nothing changed. Thanks for the suggestion, I will give it a try
null0seven said:
Use the latest eng-stk twrp.
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
In recovery go to Wipe > Format data (this will wipe ALL in youre phone).
It's youre Data in F2FS? If yes you must change it to ext4, in recovery Wipe > Change file system. Reboot recovery. Check if it's changed.
Reboot to Bootloader (Fastboot). From PC reflash recovery.
Now copy Oos rom to the phone memory. Flash rom. Reflash recovery (the rom will overwrite the recovery). Reboot to recovery to see if it works. If not do it again.
I sugest to NOT restore old data. This way you'll have all new in youre phone.
Click to expand...
Click to collapse
Help! I attempted to do this and the process failed, I didn't manage to wipe data because "/data could not be mounted as device or resource is busy"
Edit: Device now has nothing but TWRP and fastboot, no OS, no ADB, no data, no internal storage
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
I managed to get hold of a few factory images and attempted to flash system.img through fastboot, resulting error was
"target reported max download size of 536,870,912 bytes" (system image is 3080 MB)
"invalid sparse file format at header magi"
null0seven said:
If you can reflash twrp from PC. If not reflash recovery from twrp recovery : Instal > Image > Select Recovery (you must have TWRP.img in youre phone memory )
Click to expand...
Click to collapse
I reflashed the modified TWRP successfully. The second suggestion wouldn't have worked, given my phone has no internal storage
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
null0seven said:
You can't see internal storage because of the recovery does not work write.
If you have a working recovery you can do all you want.
Click to expand...
Click to collapse
The recovery was working at this point, the issue turned out to be the data partition, system was formatted to ext4 but I didn't realise data was in f2fs which caused the problem in the first place. I formatted to ext4 and everything worked, I was able to install paranoid android and everything worked...
...until I flashed the wrong firmware and now I've hard bricked it! I'm going to try the hard brick toolkit
Edit: After 12 hours of being an unresponsive brick, the phone suddenly booted, system doesn't work but it has recovery. Unfortunately I seem to be back to square one, if I try to flash something it appears to succeed but then the phone doesn't boot up into system
So I am now back to the original issue of system not mounting, in terminal if I type "mount /system" I get following error:
"mounting /dev/block/sde20 on /system failed: Device or resource is busy"
Anyone know how to solve this?
I formatted everything, reflashed recovery and tried to flash OOS, got following error:
Code:
[FONT="Courier New"]"This package is for OnePlus3 devices, this is a oneplus3t" (it isn't)
"Updater process ended with ERROR: 7
Error installing zip file /sdcard/OOS3.2.6.zip" [/FONT]
Issue was "solved" by flashing PA, GApps and the correct firmware
Hopefully that's the end of all this drama, thanks to everyone for their suggestions
Hi, I'm pretty new at rooting and I seem to have a similar error. I'm getting the "can't mount /system" error in TWRP. I am able to boot into OOS 4.1.3 and run the nandroid backup but, I keep getting the same error and am unable to select "system" when choosing the mount option in TWRP.
Do I need to have all partitions in f2fs? My system partition is in ext4. Is this what solved your issue?
It seems my phone is functional even with the error active but, I've been trying to get systemless SuperSU and MagiskHide working and I think that's what is preventing me from doing so.
So I've been running Oreo Omnirom and I'm looking at moving to Android Pie. I have never installed any of the OnePlus Beta's or any other Pie based ROM.
I am currently running TWRP version twrp-3.2.3-0-20180822-codeworkx-dumpling and from the date code, it looks like to could be a little old. When I jump into TWRP, I get errors that no vendor partition is found.. I have always ignored this as I was on Oreo and didn't need/care about a vendor partition. This also led me to believe that the version of TWRP I am using support the vendor partition.
Is there an easy way to create and format the vendor partition? Is my TWRP version too old? I tried running twrp-3.1.1-x_blu_spark_v8.55-op5_op5t as recommended in another thread (even tho it's older) and I had to re-flash TWRP via fastboot because that IMG file no worky...
I am trying to avoid formatting my data since my phone has a larger drive than my computer. If someone could point me in the right direction, it would be very much appreciated.
Flashing twrp-3.1.1-x_blu_spark_v8.55-op5_op5t or twrp-3.2.3-0-20190311-codeworkx-dumpling.img (both TWRPs for PIE) wont boot to recovery. Both boot to a blank screen with the notification LED turned blue. I assume that this is because I am still on Oreo firmwares... Seems like I have a chicken and egg sort of situation going on here....
Flashed OxygenOS_5.1.4 full OTA. /vendor partition was not created, but I only booted until I reached the lockscreen at which point told me that my password was incorrect. Do I need to remove my lockscreen password in Omni and try again?
crakerjac said:
Flashed OxygenOS_5.1.4 full OTA. /vendor partition was not created, but I only booted until I reached the lockscreen at which point told me that my password was incorrect. Do I need to remove my lockscreen password in Omni and try again?
Click to expand...
Click to collapse
Remove your security before flashing anything and then try 5.1.4 full OOS zip. If that works, great. OTA up to latest, or as far as it will allow and then use the full zip files available in the forum to get onto latest Pie. You'll need to fastboot flash latest Pie TWRP (codeworkx) when you get up to date.
If you run into security problems you might have to try a clean flash, or even format. Make sure you are in front of your PC before beginning and backup everything.
Still having no luck here.
Here is what I have done to try and get TWRP to recognize a /vendor partition:
Formatted Data
Side loaded OnePlus5TOxygen_43_OTA_037 in TWRP
Flashed OTA_037
Booted OxygenOS and completed setup
Rebooted to bootloader
Flashed twrp-3.2.3-0-20180822-codeworkx-dumpling
Rebooted to TWRP recovery
At this point I am STILL getting 'Failed to mount '/vendor' (invalid argument)'.
WTF am I doing wrong? How to I create a /vendor partition?
crakerjac said:
Still having no luck here.
Here is what I have done to try and get TWRP to recognize a /vendor partition:
Formatted Data
Side loaded OnePlus5TOxygen_43_OTA_037 in TWRP
Flashed OTA_037
Booted OxygenOS and completed setup
Rebooted to bootloader
Flashed twrp-3.2.3-0-20180822-codeworkx-dumpling
Rebooted to TWRP recovery
At this point I am STILL getting 'Failed to mount '/vendor' (invalid argument)'.
WTF am I doing wrong? How to I create a /vendor partition?
Click to expand...
Click to collapse
hi, may be this will help you, see post #2 from this thread:
"..... (because 5.1.4 creates the vendor partition and 5.1.5 fills ot)"
https://forum.xda-developers.com/oneplus-5t/help/solved-twrp-error-7-vendor-partition-t3846181
My thought process was that if 5.1.4 creates the /vendor partition, then TWRP should still be able to recognize it and mount that partition... I'm not sure if I care if it's full or empty at this point... I fear that I will download another 1.6GB of data just to find that the update wont happen because /vendor cannot be found... Unless I am completely wrong...
Well dang... I was wrong. Flashing 5.1.5 patched the /vendor partition and removed the error in TWRP.
Thanks for the help guys.
Mods please close (solved).
Hello! I'm very new to building custom recoveries, and haven't even completed a successful build yet. I have a OnePlus 7T model HD1905 (aka North American model/Global) running OOS 12. I've tried to find guides on how to make a TWRP recovery, but nothing has worked for OOS 12. I am able to extract the OOS 12 stock recovery.img with Payload Dumper, and am able to create a basic TWRP device tree for android 12.1 using the official TWRP 12.1 Github manifest, but I'm not able to find a good guide to create a TWRP-ready device tree from my stock recovery.img I mentioned earlier. I've tried updating to OOS 11, and using the twrp-keep module on the magisk modules github to keep the official TWRP installed. (It support OOS 11, but not OOS 12). I've also tried flashing the unofficial build made by Mauronofrio, but none of the specified methods have worked. Can someone please either make a OOS12-compatible version of TWRP for the OnePlus 7T, or if they can't do that, guide me in a step-by-step process on how to do i myself? Any help would be greatly appreciated.
Oos12 does NOT support twrp nor does A13
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
I just flashed it, and it booted successfully! I'll let you know if I can format /data.
Format /data works.
For confirmation, I flashed the .img of the OOS12 version to the recovery partition.
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
SiegeDaBoss said:
So... upon further inspection, there's an issue with decryption. I can successfully flash the image to the recovery partition, and it boots just fine. When I tap on "Mount", all of the options are unchecked. One of the buttons is called "Decrypt Data". I currently don't have face unlock, fingerprint unlock, password or PIN set up, and it still promts me for a password when I tap on "Decrypt Data". I've tried entering "default_password" and "password" (but without the quotation marks), but neither of them work. Is there a way to solve this? This is on the OOS12 TWRP, btw.
Click to expand...
Click to collapse
I just tested the non-OOS Android 13 TWRP file, and it has the same issue.
Can u back up all partitions except data? At least that would be helpful
HueyT said:
Can u back up all partitions except data? At least that would be helpful
Click to expand...
Click to collapse
Nope. Even when I de-select Data, and select everything else, it still fails with the "Failed to mount /data" error.
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
HueyT said:
Yeah, I was afraid of that. No one has cracked twrp for oos12 yet
Click to expand...
Click to collapse
I mean, at least both of them boot.
rabilgic said:
I compiled it but i didn't test it with oos12 (fbe) and custom rom a13 (erofs). I hope it will work..
Device Tree
Sourceforge
Click to expand...
Click to collapse
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Thank you for testing the builds and for the feedback . I've been on oos11 for a long time, but today I'm going to flash oos12. Because i would need recovery log files to fix errors.
I don't have no time for some fixes, i will try to fix errors whenever possible.
did you not ttry to use the twrp and the twrp installer builds that are on official twrp site for one plus 7t
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
SiegeDaBoss said:
Hi again. As I've mentioned, both TWRP images boot just fine. However, I am unable to mount /data, as when I enter the "Mount" section of TWRP, nothing except the Cache partition is checked. It doesn't ask me for a password upon booting into TWRP, however it DOES ask for one when I tap on the "Decrypt Data" button in the "Mount" section. I've tried entering "default_password" (without the quotation marks), "password" (again, without the quotation marks), and also my password that I set up when I flashed LineageOS 20. I'm curently running LineageOS 20 on the device. I'm able to access USB OTG in TWRP, but I'm not able to flash anything from there. I'm also unable to change boot slots, or backup any partitions. Formatting Data doesn't allow me to access the data partition on rebooting, and the only fix I've been able to find is changing the data partition format from ext4, to ext2, and then back to ext4. This only works temporarily, and only with OxygenOS installed. Even then, after I change the data partition's format like I mentioned above, it resets my data, as is expected. After setting up the device again, and rebooting into TWRP, the /data partition goes back to being un-selected, and I have to repeat the process over again, and once again lose my data. I am unable to carry out the process described while running LineageOS, and its respective TWRP file that you have made. Any help would be greatly appreciated, and if you know the password that TWRP is asking for in the Mount section (when I select "Decrypt Data"), I'd like to know what it is so that I can hopefully get the rest of TWRP to work. Even with these issues, I'd like to give MASSIVE thanks to you, because you were able to do something that my inexperienced self was able to: That is, create a TWRP file that boots, made from the latest custom rom files, and the latest OxygenOS versions' files.
Click to expand...
Click to collapse
Hi again, i updated my repo and download links.
-OOS12 decryption working.
-Flash zip working . "I installed with zip by the Magisk and copy partititon, i flashed los20 & stock oos12 .)"
-Adb sideload working, i tried stock oos12 flashed successfully.
-Format data working.
-Mtp working.
-Otg working.
-Adb working.
-Vibration working.
* Backup data working, but restore data on oos bootloop
* i use swift backup instead of nandroid backup
When i have free time, i will work on twrp a13 fbev2.
mrk2815 said:
then how are folks then flashing roms to one plus 7 t devices if there is or isnt a working twrp .
Click to expand...
Click to collapse
Every ROM comes built-in with its own recovery. So you'll have to flash the ROM via that recovery's ADB Sideload feature.
lets hope you can get a working twrp going for both andrid 12 and 13 .as my one plus 7t is just been put away in my drawer after seeing that one plus has given up on these older devices. when there is a working twrp i would probably want to flash something down the road. my primary driver unfortunately is a samsung S21 plus .
rabilgic said:
Hi again, i updated my repo and download links.
OOS12 decryption working.
Mtp working.
Adb working.
Vibration working.
I installed with zip by the Magisk and copy partititon.
Backup/restore boot.img working.
I haven't tested: flash rom, format data, needs some testing
When i have free time, i will work on twrp a13 fbev2.
Click to expand...
Click to collapse
All works until I tried to restore. Then it got stuck at red dot going around in circle. When I tried to go back in twrp again to format data, it won't mount data after that. Ended up having to restore all over using msmtool.
It mounted data fine before I tried to restore the data part, then it messed up decryption of data despite not having a lock code, no fingerprint, no pattern-lock, or lock screen enabled.