Related
I'm not flashing etc. my SXS (or other cells) often, so I may missed some informative posts regarding my problems. Usage of
Report/Log of actions and problems
I tried to fastboot flash openrecovery-twrp-2.8.4.1-LT26i.img and openrecovery-twrp-2.8.5.0-nozomi.img but f2fs was not available and also installing uCyan-12.1-b04.zip gave me errors
Using adb "fastboot flash boot boot_carbon_3-11-14_with_twrp.img" I was able to use the included TWRP 2.8.0 to clean flash (wiped all except sdcard) "uCyan-12.1-b04.zip"
With TWRP 2.8.0 I also was not able to format all partitions except sdcard with f2fs (probably because of the carbon kitkat-kernel?)
(as expected) TWRP 2.8.0 was gone after the flashing
I tried to reinstall TWRP by installing eu.chainfire.supersu-2.46-246-Android-2.1.apk & com.jmz.soft.twrpmanager.apk in uCyan, this gave me errors and FC and then also forced System shutdowns
Vol+ (fastboot, blue light) und adb USB connect seems to not work with uCyan-12.1-b04 for me, but not sure what is the culprit.
I would like to achieve and ask how to do:
install TWRP 2.8.x permanently (into FOTAkernel)
format all partitions except sdcard with f2fs
install uCyan-12.1-b04
all of this possibly without using uCyan (or another ROM) and without App-Installation (Cell offline) so only with TWRP & adb also to make a clean backup of uCyan: is this possible?
ChriMo said:
I'm not flashing etc. my SXS (or other cells) often, so I may missed some informative posts regarding my problems. Usage of
Report/Log of actions and problems
I tried to fastboot flash openrecovery-twrp-2.8.4.1-LT26i.img and openrecovery-twrp-2.8.5.0-nozomi.img but f2fs was not available and also installing uCyan-12.1-b04.zip gave me errors
Using adb "fastboot flash boot boot_carbon_3-11-14_with_twrp.img" I was able to use the included TWRP 2.8.0 to clean flash (wiped all except sdcard) "uCyan-12.1-b04.zip"
With TWRP 2.8.0 I also was not able to format all partitions except sdcard with f2fs (probably because of the carbon kitkat-kernel?)
(as expected) TWRP 2.8.0 was gone after the flashing
I tried to reinstall TWRP by installing eu.chainfire.supersu-2.46-246-Android-2.1.apk & com.jmz.soft.twrpmanager.apk in uCyan, this gave me errors and FC and then also forced System shutdowns
Vol+ (fastboot, blue light) und adb USB connect seems to not work with uCyan-12.1-b04 for me, but not sure what is the culprit.
I would like to achieve and ask how to do:
install TWRP 2.8.x permanently (into FOTAkernel)
format all partitions except sdcard with f2fs
install uCyan-12.1-b04
all of this possibly without using uCyan (or another ROM) and without App-Installation (Cell offline) so only with TWRP & adb also to make a clean backup of uCyan: is this possible?
Click to expand...
Click to collapse
According to the first list, You had done most of the stuff correctly. You just didn't have partitions in f2fs and no TWRP, right?
The TWRP in carbon should work with f2fs conversion, but given that You get problems, we will need to go via a kinda lengthy method.
Flash the uCyan-12.1-b04 normally via the recovery.Don't bother flashing gapps or other zips now.
Then to get root, You don't need to install SuperSU. You can do so via Settings> Developer Options> Root option for adb and apps.
Then follow the procedure from here to flash TWRP.
After You have TWRP version 2.8.4.1, then reboot to recovery, now convert needed partitions to f2fs and flash the ROM and gapps!
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
SinusStudios said:
Hello forum,
i'm currently trying to find the best software solution for my Xperia Z1 Compact and i already got close to what's possible.
I found this ROM which is working almost perfectly except that it overrides the recovery with a dual recovery with an older TWRP version which prevents me from doing critical flashes and backups.
I only need TWRP 3.0.2 on /recovery, nothing else like PhilZ or anything else.
When i flash TWRP 3 for Z1C and reboot to recovery or press Vol-Up when booting i get a blackscreen boot loop which can only be fixed by flashing an old TWRP or wiping the entire phone from fastboot.
Another problem is that updater-script formats /system and /data to ext4 and mounts them like that which is a problem because i'd like to have F2FS on all of my partitions.
I already tried removing /kernel/ and /dualrecovery/ from the .zip and modifying updater-script to not format both patititons and mount them as F2FS, but when trying to flash this modded .zip it fails to flash (probably because an integrity check?).
So what i need to do is:
Remove recovery from .zip
Remove kernel from .zip
Modify updater-script to not format any partitions and mount them as F2FS
Any help, resources and tipps are appreciated. I'm running Windows 10 x64 but i don't think i'm able to build a ROM on my own as i have only little programming experience.
Click to expand...
Click to collapse
I don't know much, but I am surprised that flashing twrp 3 causes that problem. What method are you using? Try using Rashr to flash twrp 3 img, then try to boot to recovery. If vol up doesn't work, try vol down, (that's what works for me). Somehow I don't think you'll be able to just remove those things from the ROM and have it flash fine. Your better chance is to get twrp flashed, then figure out the F2FS, etc. Also, there are custom kernels for stock-based roms, and don't forget that twrp 3 is not official on Z1compact, so read threads thoroughly to make sure what you're trying to do is supported. I know many of us have twrp 3 on our phones, so I would look more into that.
Hi,
I had the same issues and maybe this helps.
- install your rom and go into dual recovery and choose twrp
- in twrp go to install and choose "IMG" and not "ZIP"
- you can now install the new twrp version via install !
Maybe you should not flash that ROM because it seems to contain malware. Have a look into the thread.
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.
Device: XiaoMi Mi 6
ROM: MIUI 9 China Developer 8.3.15
State: Unlocked + USB Debugging
So I tried to install TWRP 3.2.1.0 Sargit + OpenGApps ARM64 8.0 Micro + MagiskSU/SuperSU into the device
From all four of those, I only successfully installed TWRP but not really usable
******no-verity-opt-encrypt-5.1.zip is longer usable for the new update (tried to install and failed)
Here is the problem I'm facing:
1/ TWRP is installed, Format Data helps the Internal Storage to be usable but it keeps go back to 0MB after a reboot to the system then back to TWRP again, causing this to be impossible to flash anything after a system reboot without a Format. Tried Wipe Cache, System (re-flash ROM, stupid me), Data, and the rest, changed File System to EXT4 and the EXT3 and still did not work. And this is what I received when trying to install something if Internal Storage is 0MB.
HTML:
Could not mount /data and unable to find crypto footer
Unable to mount storage
Failed to mount '/data' (Invalid argument)
2/ Used TWRP and ADB (Format everytime so I could not put anything into the storage) to flash OpenGApps and the outcome is it booted into the system and 5 seconds later, it shows something similar to 'com.systemui has stopped working', should be the Google framework. Booted back into TWRP, performed a Format Data and the same thing happened. (so, re-flashed ROM)
3/ Installed MagiskSU or SuperSU (followed instruction step-by-step) through TWRP and ADB and System won't boot up through Power button, Reboot System of TWRP. MagiskSU led me back to TWRP after Boot and SuperSU simply bricked my device. (re-flashed ROM again)
So clearly, I have Root access from the China Dev ROM itself, but it does not really do the job.
I am in China so I want to use some China ROM's features and apps which cannot be downloaded from any appstores I can find from Global ROM.
I have not tried Rooting the Latest Global ROM, yet. So I don't know the result but I'm sure want to use China ROM instead!
Have not tried wipe system and flash official ROM zip from MIUI with TWRP but I guess it won't change.
And lastly I have data in Google and I need Google services so I can access those apps.
If anyone knows how to perform a fix for any of the above, I would be very appreciate!! I had spent a whole day trying to deal with this but it seems like!!!
1, I guess you installed wrong TWRP, you should donwload TWRP from here https://forum.xda-developers.com/showpost.php?p=75326288&postcount=90, this one can de-crypt Oreo Data partition.
2, Don't flash opengapps on any China rom, just download all needed apks from apkmirror and install them. If then you see play service FC, try to disable MIUI Optimization from Developer Options and set Selinux to passive mode. You can also flash xiaomi.eu rom, they are based on China rom but have gapps embedded. BTW, xiaomi.eu 8.3.15 beta and 9.5.3.0 stable supports xposed Oreo beta2.