I was considering attempting to use the f2fs filesystem that is discussed in original android development but I'm a bit confused with what to do to load a new rom. Can anyone explain if it will work with the purity rom and what I need to do to get it working? Or also let me know if its not possible.
Yes, I have used Purity with F2FS, but this filesystem is unstable because the system hangs usually (I have also tried with SlimKat and RastaKat with same hangs copying many files).
Basically:
- You must flash "twrp-unofficial-2.7.1.0-f2fs.img" as a normal recovery and change /data, /cache and /system (optional) to F2FS.
You will find this option under Wipe -> Advanced Wipe, then select only one partition and press the "Repair or Change File System" button for change to F2FS. Use Wipe -> Format Data also (you will lost data in /sdcard).
- Install Purity ROM (if /system is converted to F2FS, you must use "convert2F2FS.jar" for modify ROM zip and must install this new ROM).
- If /system is F2FS, install "KTManta_F2FS-26-06-2014-ALLF2FS.zip" Kernel or "KTManta_F2FS-26-06-2014_CACHE_DATA_PARTITIONS.zip" else.
patzzz said:
Yes, I have used Purity with F2FS, but this filesystem is unstable because the system hangs usually (I have also tried with SlimKat and RastaKat with same hangs copying many files).
Basically:
- You must flash "twrp-unofficial-2.7.1.0-f2fs.img" as a normal recovery and change /data, /cache and /system (optional) to F2FS.
You will find this option under Wipe -> Advanced Wipe, then select only one partition and press the "Repair or Change File System" button for change to F2FS. Use Wipe -> Format Data also (you will lost data in /sdcard).
- Install Purity ROM (if /system is converted to F2FS, you must use "convert2F2FS.jar" for modify ROM zip and must install this new ROM).
- If /system is F2FS, install "KTManta_F2FS-26-06-2014-ALLF2FS.zip" Kernel or "KTManta_F2FS-26-06-2014_CACHE_DATA_PARTITIONS.zip" else.
Click to expand...
Click to collapse
Where do you get convert2F2FS.jar?
Using f2fs with omnirom. All partition were formatted with f2fs. Having no issue with last update. You will find all resources in my thread
How to format your phone properly
Guide updated on 14/05/15
Disclaimer:
#include <std_disclaimer.h>
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this tool
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
Click to expand...
Click to collapse
This process will wipe all of your data off your phone. This includes all of your apps and system storage. Make sure to backup all of your apps and data to the cloud or onto a computer
Make a backup!! Why am I saying this again? Because there is always a few careless people who do this process and complain how they lost all of their data.
All users of android 4.0.x are warned that factory resetting your phone will hard brick your device. To check if you have brickbug, follow this link: brickbug check Also, a custom recovery is not a custom kernel! Brickbug occurs at kernel level. If you are affected, you will need to install a custom kernel like siyah kernel
Here are some of the ways you can format your phone:
- Manually via recovery
- Using a pit file
- Using hawker's scripts
Formatting manually via recovery:
If you don't have a custom recovery already, flash Philz recovery using odin: https://goo.im/devs/philz_touch/CWM_Advanced_Edition/i9100/philz_touch_6.48.4-i9100.zip.md5
Reboot your phone to recovery. If your current ROM doesn't have the option to do this, you can use the app quick boot or you can shut down your phone then use the button combinations to get into recovery (volume up + home + power). Note: Root is need to run the app.
Once in recovery, select and confirm factory reset
Select and confirm wipe cache partition
In mounts and storage, select and confirm format /system and /preload (wiping preload is necessary when switching between stock and custom roms).
Go back to the main menu and go to advanced menu. You will now have to select and confirm to wipe dalvik(or art) cache.
Once all of these has been done, you can install a rom normally.
If you are on TWRP recovery, follow these steps:
Reboot your phone to recovery.
Once in recovery, go to wipe
Tick: Data, system, cache and dalvik cache
Swipe the bar to confirm to wipe
Go back to the main menu
You can now install a rom normally.
If you get errors when formatting the preload partition, you will have to flash this first then you will be able to format the preload partition: http://bit.ly/13ojAEh
Formatting via pit file:
This process will wipe all of your data off your phone. This includes all of your apps, system storage and internal sd card. It doesn't wipe your external sd card. Make sure to backup all of your apps and data to the cloud or onto a computer
Make a nandroid backup onto your external sd card or PC (VERY IMPORTANT!!! All backups in internal sd card will be deleted so move them!)
Download the system pit files (attached in OP)
Extract the zip file
Open ODIN (Attached in the OP, JOdin for linux and OS X)
Connect your phone to your PC via USB while in download mode (make sure your phone is detected on ODIN, it should say COM:{number})
Click on the PIT button and locate and select your desired pit file
Click on PDA or AP and select your kernel .tar file (look at this thread if you don't have one: http://forum.xda-developers.com/galaxy-s2/development-derivatives/convert-kernel-zip-to-tar-t2994381)
Make sure that re-partition has been ticked then click start. If your phone successfully flashes, move onto the next step. If not, try changing usb ports, changing ODIN version, changing pit files or seeing if your device has a corrupt nand (or broken). If your nand is corrupt or broken, you won't be able to flash with ODIN (and you will need to buy a new motherboard). If you are still unsure what to do, look at the screenshot in the attachments.
While your phone reboots, you need to perform the button combination to get into recovery (home button + power button + volume up)
If you have CWM recovery, go to mounts and storage then select format /sd card0 or /internal sd card. Select default and your internal sd card should successfully format. If not, try ext4 format. If you have TWRP recovery, you will need to go to wipe>advanced and select format /sd card then swipe to confirm . If you can successfully format your phone here, skip steps 11, 12, 13, 14.
----IF FORMATTING FAILS IN RECOVERY----
If formatting sd card in recovery fails, connect your phone to your PC. While still in recovery (CWM), go to mounts and storage and select mount mass storage. If you have TWRP recovery, go to mount and select mount sd card. It should prompt you that the storage isn't ready yet and you need to format. If your PC still doesn't detect your phone, check if the proper drivers are installed (in attachments). Also, if your phone doesn't get detected and you've done everything in this step, try changing usb ports, computers and even usb cables.
Click format
You can leave all of the settings to default, I personally like to change the allocation size to 4KB (4KB is good if you want to make the most out of your phone's storage while having enough speed)
Click format.
----AFTER SUCCESSFULLY FORMATTING----
Go back to your phone. You can choose to restore from your backup or install a new rom. If you choose to restore from a backup, skip all of the remaining steps. (Note: DorimanX kernel recoveries can not format /data partition more than 2gb, use an alternative first when restoring a backup then flash back if needed)
In mounts and storage, choose format /data, /cache and /system (Note: DorimanX kernel recoveries can not format /data partition more than 2gb, use an alternative first then flash back if needed)
Now you can flash a ROM as you normally would
Formatting via hawker's script:
Copy HawkerCoreV???.zip onto your device. I have included the zip in the attachments.
Reboot into Recovery
Install zip from SD card>Run HawkerCoreV???.zip
When you are at a stage whereby you want to flash a new CUSTOM ROM and want to do a FULL WIPE before doing so (which I would ALWAYS recommend) the steps are as follows:
If you have not previously done so, download and install the core zip HawkerCoreV???.zip. This will create a folder called /sdcard/HawkerCore
A nandroid backup is recommended beforehand
Install zip from SD card>Run /sdcard/HawkerCore/Scripts/ROMNuke
Install zip from SD card>Flash your new ROM
Reboot
If you are installing a new STOCK ROM and want to do a Nuke then:
A nandroid backup is recommended beforehand
Install zip from SD card>Run /sdcard/HawkerCore/Scripts/ROMNuke
Reboot into Download mode using the button combinations (volume down + home + power button)
Install your stock ROM via Odin
Huge thanks to hawkerpaul for his awesome scripts. Also huge thanks to ElGamal for providing the modified pit files and metalgearhathaway for providing the stock pit file.
Although I know all this already, I find your continued support of our prehistoric S2 to be very helpful to others. I can vouch that these methods are the best way to ensure a full wipe and avoid issues with flashing whatever ROM suits your needs. I personally use a mix of all 3 methods to ensure a fully functional phone. Many thanks for your continual posts throughout the S2 forum here on XDA!
So a while back I posted about getting F2FS working on the international M8 GPE. No one replied. But I figured it out anyway
Here are the steps you need to take to get /data/, /system/, and /cache/ to be the much faster F2FS file system, instead of the slow EXT4.
Keep in mind this will completely wipe the entire phone.
1: Install captain_throwbacks multi-rom twrp.
Regular twrp won't work because it won't let you convert partitions to f2fs.
http://d-h.st/Wtd Downlaod it from there
2: Transfer this rom:
http://forum.xda-developers.com/showthread.php?t=2716306 (LolliGPE by digitalhigh)
And this kernel:
http://forum.xda-developers.com/htc-one-m8/development/kernel-hypernova1-3-0-t2955537
to your EXTERNAL sd card. Internal will be wiped in the f2fs process.
3: Open twrp, go to the wipe option.
Select /data/, press the "repair or change file system" option. Then select F2FS and confirm the switch.
Do the same for /cache/ and /system/
4: Now install the LolliGPE rom.
important: Be sure to select the EliteGPE kernel option, this step is crucial! The other options don't matter.
5: After installing, do not reboot! Instead, go to install, and install Hypernova. The options you choose don't really matter in this step, but I personally like to disable fsync, and keep the rest stock.
6: Reboot! If done properly, you will see the digitalhigh logo for a long time! Like, really long! Don't worry, it hasn't bootlooped, it'll do it's thing for about 10 minutes and then boot up.
7: Congrats, you now have an M8 running the F2FS filesystem!
I'm currently still testing performance. If anyone could post before/after storage benchmarks or comment on performance, that'd be cool!
Cheers!
if i convert to f2fs, can i then restore a backup from a different file system format or would that cause issues?
If you are asking about nandroid backup it would not work.
Sent from my m8 using Tapatalk
josh.walker.9242 said:
if i convert to f2fs, can i then restore a backup from a different file system format or would that cause issues?
Click to expand...
Click to collapse
Works fine on Samsung's, you will just get a warning about the file system mismatch, but f2fs will be retained.
All,
I have a SM-G35FD which is in a bad state. My phone started boot looping one morning after it was fine the night prior (3 days ago now) and I believe an auto-update may be the root cause. I am trying to find any way to access the internal memory to recover data, however I am not able to mount /data or /sdcard. I have not done much with my phone besides adding root, no CFWs ever, and no custom recoveries (prior to today). Also, I lock my phone with my thumbprint. I did not go through any encryption setup on my device.
Details about the initial problem:
It started boot looping several times and at some point it shows a black screen with red text. after letting the battery drain (because I could not force reboot) i was able to get into stock recovery and wipe the cache and reboot; this led to occasionally getting to the security screen which would freeze 1-2 seconds after logging in.
Things I have tried (19mar2017)
got into stock recovery, wiped cache, rebooted. Freezes at security login screen
Installed TWRP to get more functionatity. Was able to install TWRP
used TWRP to try to mount Data, but it will not mount (only System, Cache, EFS, and USB OTG will mount)
used TWRP to wipe Dalvik and Cache only. Errors show "cannot mount /data"
used TWRP to install CWF, freezes during extraction (4-5%)
can use ADB to run shell
UPDATE 20mar2017: Ran "Wipe -> Advanced Wipe -> *Select System Partition -> Repair or Change File System" on /system. I think this was a bad move as now I can access the /sdcard folder and its missing all data. I didn't think it would matter since the options under Wipe show "System" and "Internal Storage" separately.
Perhaps data does not mount because it needs my thumbprint? Is there anything I can try to backup the internal user memory partition and my fingerprint signatures? any way to access the user data?
Thanks to all for their time!
I found a video ( https://www.youtube.com/watch?v=VJRKuQf0puE ) which suggest that I can use TWRP to "change the filesystem" for the /System (and other) mounts in order to fix the /data mount. This can be accessed using Recovery(TWRP) -> Wipe -> Advanced Wipe -> *Select System Partition -> Repair or Change File System -> Change File System -> Options { EXT2, EXT3, EXT4, FAT, exFAT, F2FS }. Since my goal is to recover the "User Data" partition, I would not perform this on "Internal Memory" but would on the other partitions. Hopefully this would allow me to reinstall the Stock FW and allow me to login to the Internal Memory to access my files.
Does anyone know if using "Repair or Change File System" will impact the Internal Storage?
Try to reinstall the Stock Firmware Through Odin, I had this problem also when I used to own a J5... All I did was just Reinstall the stock firmware... if you want to find the stock firmware.. just go to sammobile.com
Hello.
I was recently updating from the stock oxygen os (5.0.1) from an android 7.1.1 version of oxygen OS (23 OTA) to the newer android version 8.0.0 , from which I received an error 7. I have a custom recovery and an unlocked bootloader. I used the zip file I downloaded through the stock oxygen os rom, and got an error. My recovery files are encrypted, so I can't flash/restore anything from the phone. I'm trying to install either the xXx_No_Limits rom or the oxygen os android 8.0.0 rom through my usb OTG. The toolkit installs recoveries properly, but the xXx_no_limits file doesn't exit the aroma installer. I can force it to reboot after it attempts to exit the aroma installer, but then it gets stuck in a bootloop.
I can still see my phone in the fastboot devices list. The fastboot menu has productname: QC_reference_phone, my serial number, secure boot = yes, and device state = unlocked. Using the all in one tool kit I can boot into twrp. When I boot into twrp all my system files are encrypted, but my USB otg is not. I have a backup of my 7.1.1 version of android I can restore, but I can't restore it without decrypting.
I have been trying to adb sideload through twrp and the stock oneplus recovery, but regardless of which rom I try I get the following error. I can flash smaller zips like the no verity file, but I don't think that will help this late into the problem.
cannot read 'filename.zip'
Pretty lost as to what options are left.
Thanks in advance
" I have a custom recovery "
Error 7, The problem is that, your Recovery is compatible with Oreo? You must use TWRP compatible, the best is [RECOVERY][cheeseburger] TWRP 3.2.1-0 for Oreo (8.0 and 8.1) by codeworkx
because this TWRP version is universal 5/5T and also can decrypt 8.0/8.1 Oreo versions
Ok, I downloaded the universal version provided by codeworks. I then run this command:
"fastboot flash recovery twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
I get a confirmation. And then i proceed to boot into the recovery with:
"fastboot boot twrp-3.2.1-0-universal-codeworkx-cheeseburger.img"
Here is a link to my cmd commands: https://pastebin.com/ARGP6yqw
I accept the allow system modification on twrp 3.2.1-0.
My data is still encrypted throughout, so my recovery file names and file folders are unrecognizable. I then select source, and switch to my usb otg with the OnePlus5Oxygen_23_OTA_028.1.zip (1.6gb)
I get a successful installation message, install the twrp app, and reboot.
I don't think I need to flash gapps on an official OTA. I then leave my phone plugged in and charging for a while while the dots are spinning in the boot up process.
It's been about 75 minutes, and it's still doing the whole dots spinning. When I did this yesterday, it sat on the boot process for 35+ minutes and didn't get further.
Even after I do flashed the recovery file, it occasionally boots into oneplus recovery
I think everything you can do is to format all partitions including internal storage and start from scratch by flashing codeworkX TWRP, stock OxygenOS or any ROM you want, then wiping internal storage again and proceeding. Some1 correct me if I'm wrong.
Do you know if I can do that with, the all in one tool kit?
I can get into the adb sideload parts of the phone not sure if I can do anything with that.
Whenever i try to flash something from my usb otg through twrp, I get ERROR: 7. "Failed to mount '/data' (invalid argument)"
So I can go into twrp >wipe > advanced wipe> select Data > repair or change file system.
Here it tells me that mount point: /data, file system: ext4, present: yes, removable: no, size:0mb, used:0mb, free:0mb, backup size: 0mb.
Should I repair file system, resize file system, or change file system?
I think i found the problem:
Whenever i try to flash something from my usb otg through twrp, I get ERROR: 7. "Failed to mount '/data' (invalid argument)"
So I can go into twrp >wipe > advanced wipe> select Data > repair or change file system.
Here it tells me that mount point: /data, file system: ext4, present: yes, removable: no, size:0mb, used:0mb, free:0mb, backup size: 0mb.
Should I repair file system, resize file system, or change file system?
You must:
1/ Connect your OP5 to your computer
2/ Make a backup of your data on your desktop (Pictures, DCIM, Download, etc)
3/ In TWRP > WIPE > "Format" Data partition, you will have a warning message (all your date will be erased), confirm with tape "yes"
4/ Reboot directly in TWRP (> Reboot > Recovery)
5/ Now wipe all partitions (Dalvik/Cache - Cache - System)
6/ Put your Rom on your internal storage and flash it !
Depend if you want a official stock rom or xXx (custom rom) you must flash Magisk for keep your Custom Recovery and allow root permissions
Just wipe internal storage, don't touch file system.
When i goto wipe the internal storage it says:
"Failed to mount '/data' (invalid argument)
Updating partition details....
Failed to mount '/data' (invalid argument)
...done"
and it says "Wipe complete: failed"
I don't think it can wipe /data because there's nothing in it.
My phone now shows up through the mtp protocol in recovery through the computer. The only file in the internal storage is the TWRP folder
Hello.
I did this, but skipped the first two steps (I already have my data backed up) and it gives me an error 7.
In bootloader my system reads out:
"Product Name: QC_reference phone
Variant: MSM UFS
Bootloader version:
Serial number: (my serial number)
Secure boot: ues
Device State: unlocked"
TWRP prints out:
"Installing zip file /usbstorage/oneplus5oxygen_23_OTA_028.1.zip
Checking for digest file....
Skipping digest check: no digest file found
Warning: No file_contexts
E3005: This devices is unlocked; bootstate: ""; sdk version "25".
Updater process ended with Error: 7
Error installing zip file '/usbstorage/oneplus5oxygen_23_OTA_028.1.zip'
Updating partition details....
...done"
Is there anything else I could try?
My phone now shows up through the mtp protocol in recovery through the computer. The only file in the internal storage is the TWRP folder
You don't understand:
1/ You have FORMAT data partion or just Wipe?
2/ Your rom is where? On internal storage or on a usb key?
3/ Verify your ROM file, your rom seem to be corrupted, check MD5? Where have you downloaded this rom, it's not the legit name
1) Ok. so i goto wipe > format Data > type in "yes", and then reboot directly into recovery.
2) I have my rom on an external usb drive. I can move it onto the phone through the twrp mtp.
3) I downloaded the file from here http://downloads.oneplus.net/oneplus-5/oneplus_5_oxygenos_5.0.1/
I just renamed it. I will download it again. My new file is named "OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip"
This gives me this error:
"E3005: This devices is unlocked; bootstate: ""; sdk version "25".
Updater process ended with Error: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip'
Updating partition details....
...done"
I found this thread which may solve my problem: https://forums.oneplus.net/threads/how-can-i-fix-this-twrp-update-process-ended-with-error-7.501934
My phone doesn't have a build.prop file on it, so it might not be able to read the ro.display.series causing it to abort?
Will this work?
3. The rom from oneplus MD5 matches exactly with my file's md5.
So the problem is caused by your external drive, YOU MUST PUT your rom directly on your internal storage.
TWRP sees the oxygen23OTA location as: /sdcard/OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip
I can use the twrp file manager to move it to the storage folder on the root. I currently have copies of the zip in /usbstorage, /sdcard, /storage. Is there a specific folder I should move it into? (my options are: acct, boot, cache, config, data, dev, etc, firmware, license, mnt, oem, proc, recovery, res, root, sbin, sdcard, sideload, storage, sys, system, tmp, twres, usbstorage, and vendor.
Installing off the sdcard, usbstorage, and storage folders. All give the following error:
E3005: This devices is unlocked; bootstate: ""; sdk version "25".
Updater process ended with Error: 7
Error installing zip file '/sdcard/OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip'
My computer see's the file in Oneplus A5000>Internal Storage> OnePlus5Oxygen_23_OTA_028_all_1801031502_109fde3709984ec8.zip
Could the problem be that that the bootloader shows the phone as QC_reference_phone?
I downloaded the xXx no limits rom, to check if it was an error with my download file from oneplus. The xXx no limits rom didn't give me any errors when installing, except for:
I rewiped again. Formatted my storage and flashed the xXx.
It worked.
Just flash the no Verity zip and you would be ready to go
I have the same problem as you do.. thanks for putting it out there...