Have you ever experience slow down, lag or even freeze on your Nexus 7 2012? Well there is a solution to this problem by changing your files system to F2FS, this solution will not revive your old and dying flash memory but it will greatly improve performance on any ROM, especially Android 5.1. There is many methods on XDA like ParrotMod by parrotgeek1. But F2FS is a more well known method for this.
REQUIREMENTS
1. TWRP recovery installed.
2. A ROM that support F2FS (search Google for this).
3. A kernel that support F2FS (most likely will be included in the ROM).
1. REBOOT INTO TWRP (duh)
2. BACKUP YOUR FILES (optional)
Step 1: Press "Backup"
Step 2: Select System, Data and Boot.
Step 3: Swipe to Backup
Step 4: Wait...
Step 5: Copy the backup files to your PC (copy the BACKUPS folder)(/sdcard/TWRP/BACKUPS/)
Congratulation, you have successfully backup your device.
3. FORMAT TO F2FS (the fun part )
Step 1: Press "Wipe".
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2: Press "Advanced Wipe".
Step 3: Select the partition you want to format to F2FS. The ROM you choose might not support /system F2FS so you have to be careful. After that, press "Repair or Change File System".
Step 4: Select "Change File System".
Step 5: Press "F2FS".
Step 6: Swipe to Change.
Step 7: Wait...
Step 8: (optional) Copy your BACKUPS file to your device and select "Restore" on your TWRP home screen.
Step 9: (optional) Select the folder you just copy to your device.
Step 10: (optional) Select the partition you want to restore.
Step 11 (optional) Swipe to Restore.
After its done, you can reboot your device.
Congratualtion, you have successfully format your files system to F2FS.
Note: If you want to change your device back to EXT4, follow the step above, press "EXT4" instead of "F2FS" at Step 5.
TROUBLESHOOTING
My device is stuck at the Android screen!
Power off your device and follow this guide:
https://forum.xda-developers.com/nexus-7/general/how-to-flash-stock-android-google-nexus-t3309881
That is! If you have any trouble, feel free to ask me
I have a 2012 nexus 7 that's so soow and unresponsive It used to be so awesome and snappy. Does this make the 2012 nexus 7's usable again
Sent from my SM-G955U using Tapatalk
Jeffdaddy said:
I have a 2012 nexus 7 that's so soow and unresponsive It used to be so awesome and snappy. Does this make the 2012 nexus 7's usable again
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Depend on the ROM you are using. I suggest you use the ParrotMod by parrotgeek (the link is in the post). F2FS need a compatible ROM to work, and sometimes will cause compatibility issues.
Yes, it will greatly improve your Nexus 7's eMMC performance.
Tried to follow your tutorial my TWRP didn't have a change to f2fs, am I doing something wrong?
Sent from my SM-G955U using Tapatalk
Jeffdaddy said:
Tried to follow your tutorial my TWRP didn't have a change to f2fs, am I doing something wrong?View attachment 5026845
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
You need to update your TWRP recovery to the lastest version. TWRP link: https://dl.twrp.me/grouper/
Select the lastest version (3.3.1-0) to download it. After that, just flash the .img file.
Well, it sounded good but everytime I convert to f2fs it has a boot screen asking me for the decrypt password and won't let me get past that, but when I convert back to ext4, no boot screen, ever deal with this? I only get the but screen in f2fsm
Sent from my SM-G955U using Tapatalk
Jeffdaddy said:
Well, it sounded good but everytime I convert to f2fs it has a boot screen asking me for the decrypt password and won't let me get past that, but when I convert back to ext4, no boot screen, ever deal with this? I only get the but screen in f2fsm
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
Try to boot it without restoring the backup.
Related
[SEP.21.2011][SPLASH]New HTC "Stock" Splash Screens for HD2 Gingerbread Sense ROMS
Been a while since I published anything here and figured today would be a good day to do just that!
Here you will find my custom made splash screens & boot animation for Gingerbread Sense builds. It should work on ALL Gingerbread Sense ROM's currently available and is compatible with all current Gingerbread Sense compatible kernels.
Without further adieu, I present you the newest HTC "Stock" splash screen
"HTC- Together with Google"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Installation instructions
***First and foremost, extract the zip file to a folder on your desktop. It is NOT a stand-alone CWM zip file!***
To install the first splash screen(displayed before MAGLDR):
1. Power off your HD2.
2. Holding the volume down key, press the power button and turn on the device. Continue to hold the volume down key until you see a rainbow screen. This is the bootloader screen.
3. Plug your HD2 into your PC and you should see it switch to "USB". Your PC may need to install drivers. If it does, wait for it to finish and then you should see "USB" on your device.
4. Once you are connected to your PC and your phone displays "USB", open the folder labeled "First (Before MAGLDR)" and run "CustomRUU.exe". Follow the on-screen prompts and instructions and you will soon see it flashing your device. Don't worry, this will not erase anything on your device. It will only change the first splash screen you see before MAGLDR and nothing else.
5. Once the update is complete, your phone will reboot itself.
6. Enjoy your new first splash screen!
To install the second splash screen(displayed after MAGLDR):
1. Copy "HTC_Splash_Screen.zip" to somewhere on your SD card that you will remember where it is.
2. Reboot your device and hold the power key until you boot into MAGLDR.
3. Select option 8 to boot into CWM Recovery.
4. Using install zip from SD Card option, browse to where you copied the zip file to and select it as the file you want to install.
5. After installation has finished, reboot recovery and your phone will boot back up again into Android.
6. Enjoy your new second splash screen!
To install the Boot Animation(displayed after 2nd Splash Screen):
1. Copy "HTC_Boot_Animation.zip" to somewhere on your SD card that you will remember where it is.
2. Reboot your device and hold the power key until you boot into MAGLDR.
3. Select option 8 to boot into CWM Recovery.
4. Using install zip from SD Card option, browse to where you copied the zip file to and select it as the file you want to install.
5. After installation has finished, reboot recovery and your phone will boot back up again into Android.
6. Enjoy your new Boot Animation!
You will find the download for this great new HTC "Stock" Splash Screen and Boot animation below.
Enjoy and don't forget to hit the Thanks button if you enjoy my work!
I never thought it was possible to flash roms from CWM, will give it a shot thanks !
Marvlesz said:
I never thought it was possible to flash splash1 roms from CWM, will give it a shot thanks !
Click to expand...
Click to collapse
Splash 1(before MAGLDR) is to be flashed from bootloader using CustomRUU. NOT CWM. If you try to use CWM it will just fail since it's not a CWM zip file.
Splash 2(after MAGLDR) is to be flashed from CWM.
Read the instructions I wrote up in the first post and it will walk you through every step of the process.
Enjoy!
Boot animation removed temporarily. Ironing out some bugs.
EDIT: Boot animation is fixed and back online! Enjoy folks!!
wow...so you actually edited the initrd.gz file? fantastic! have no idea what that file is but houses the image i would love to edit...
may i ask, how?
read this which is a bit beyond me....any other ways? likely not...
jsmccabe78 said:
wow...so you actually edited the initrd.gz file? fantastic! have no idea what that file is but houses the image i would love to edit...
may i ask, how?
read this which is a bit beyond me....any other ways? likely not...
Click to expand...
Click to collapse
It was a really time consuming process and I actually used several different threads.
This thread here will teach you how to extract and change the logo.rle correctly:
http://forum.xda-developers.com/showthread.php?t=1254686
This thread will teach you how to make your own logo.rle file:
http://forum.xda-developers.com/showthread.php?t=1140406
Good luck!!
just wanted to say a written thanks for the links. have replaced the image in the logo.lre...now to replace the initrd.gz. off to learn how to install virtualbox...thanks again!
Thx a lot !! Just what I needed.
How to revert back to Kitkat from MIUI lollipop in easiest way
Requirements :
MIUI 7.1 KK Rom
MiFlash
Important :
Before flashing it is advised to take the backup of data and make sure that your phone battery is charged enough.
Steps :
1. Download ROM from the above link and extract it to Desktop.
Note: - Some users get error while extracting onDesktop Because there is space in the username of PC or the folder as shown.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The users should put the ROM In C Drive in a folder without spaces. E,g C:/ROM/MIUI
The Error shown when using space between foldername.
2. Download flashing tool from the above link and install it.
3. Once installation is complete, Run MiFlash application.
4. Click on browse
5. Select ROM folder from Desktop(From the location where ROM is saved)
Note: -The path of the ROM folder Should be like "C:\Users\zeus\Desktop\MIUI" Not "C:\Users\zeus\Desktop\MIUI\images"
The MIUI Rom folder should Contain the following files
6. Turn off the phone, press and hold the Volume Down key and the Power button at the same time to enter Fastboot mode, then connect the phone to a computer.
7. Press Refresh button to see you device in flashing tool.
After pressing refresh button you will see connected device.
Here You have 3 options to select.
Choose the options carefully as per your need:-
1. Flash_all:- Clears all the data of the built-in storage, clear all user data, please be careful!(Clean Install)
2. Flash_all_except_storaget:- Will erase all user data does not clear the built-in storage data.
3. Flash_all_except_data_storage:- Does not clear the built-in storage data does not clear user data
8. Click on Flash and it will start process
Device Mismatch error ? Don't worry, click below.
Steps :
1. Dowload Notepad++ from here. Go to folder where you have extracted the Rom
2 .Right Click on any of 3 Batch Files ( .bat extension) you want to choose and open it with Notepad++
3. Delete those 2 lines ( line no. 10 and 11 ) and then Save it using ctrl+s or file menu.
4. Done , now you can flash fastboot rom on your device using Mi flash tool without having that error
9. Once flashing process completes Device will automatically reboot. Reboot might take upto 5 minutes.
Done !
its working 100% thanks for ur guide
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TWRP 3.4.0 & Root
Root and absolutely working TWRP 3.4.0 from nemo-nemo!
Oreo & Pie
Features
In the new TWRP and Root installation method described below, there is no need to format the Data partition to remove the encryption.
Thanks to TWRP's built-in FB Encryption (File Based Encryption), the contents of the Data partition are available with encryption preserved. The folders on the external memory have the correct names and structure.
- Forced DM-Verity removal
- Forcibly removing the protection of Motorola Hab
- Now there is no need to sew additional decoders when installing TWRP and receiving Root or when installing custom firmware!
- Full access to Oem partition modification directly from the running system using Root Explorer, which previously was only possible with Root obtained through SuperSu.
Installation Instruction
1. Download archive with files for installation TWRP and Magisk Google Drive
2. Extract files:
- twrp-3.4.0-nash-nemo-nemo.img to the folder adb with drivers adb & fastboot ;
- twrp-installer-3.4.0-nash-nemo-nemo.zip, Magisk-disable-dm-verity-v20.4.zip to the SD Card..
This is a special modification of Magisk for Motorola devices. You can read about it here Link
3. Boot the phone in fastboot mode, connect it to a PC and perform the following commands:
Code:
fastboot boot C:\adb\twrp-3.4.0-nash-nemo-nemo.img
4. The phone restart in to Recovery.
5. Go to the "Install" section. Click on "Select Storage" button, select Micro SD card, OK. Install twrp-installer-3.4.0-nash-nemo-nemo.zip and Magisk-disable-dm-verity-v20.4.zip.
6. Reboot into the system.
Attention! Backup creation after TWRP and Magisk installation should be done only after full booting into the system. Otherwise restoration of the Data partition backup will be interrupted with an Error 255.
Сredits:
nemo-nemo
TeamWin-TWRP
ilia3367
Thanks a lot, everything works fine. The only issue I had was the russian language on the first boot in TWRP, but it is easy change to english.
forgottennick said:
Thanks a lot, everything works fine. The only issue I had was the russian language on the first boot in TWRP, but it is easy change to english.
Click to expand...
Click to collapse
Well, this is understandable. This TWRP was created by 4PDA developers.
do I have to flash Magisk-disable-dm-verity whenever I want to install a custom rom?
If you need a Root then of course yes.
Very good, works, thanks!
Will this method work for the Verizon version of the Z2 Force?
ilia3367 said:
If you need a Root then of course yes.
Click to expand...
Click to collapse
Willi this work on the Verizon Z2 Force?
will4958 said:
Willi this work on the Verizon Z2 Force?
Click to expand...
Click to collapse
Verizon and Root concepts are not compatible.
hey, im getting a bootloop when trying this. no idea why?
***Mod Announcement: Thread has been locked and download links removed due to XDA GPL violations.***
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I would like to thank TeamWin for their amazing work!
I saw that the newer Samsung MediaTek phones were not getting any sort of love, so I bought one myself to kick start the development.
TWRP is the obvious choice as it is reliable and trustworthy with frequent updates and patches.
INSTALLATION:
Odin Method (Windows):
Step 0: Unlock Device Bootloader by toggling the OEM Unlock option in Developer Options. Device will reboot to Odin mode and will prompt you to long press volume up, device will then unlock bootloader and perform a complete factory reset so make sure to backup any data.
Step 1: Download the unofficial TWRP image from the link attached below.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Select the downloaded recovery.tar in AP slot and vbmeta_disabled_R.tar in USERDATA slot, connect the device to PC, go to options and untick "Auto-Reboot"
Step 4: Click START and the Device will get flashed, Odin will say SUCESS!.
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your M32 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
Heimdall Method (Linux):
Step 1: Install heimdall tool on linux , google it.
Step 2: Put the device in Odin download mode by holding VolumeUp+VolumeDown and inserting USB cable after the device is completely shut down.
Step 3: Open up terminal in the downloaded TWRP directory, extract twrp image from recovery.tar
Step 4: Enter the command "heimdall flash --RECOVERY recovery.img --no-reboot" where twrp.img is name of the downloaded image
Step 5. Exit Download mode by holding VolumeDown+PowerButton and then immediately boot
into Recovery mode by pressing VolumeUp+PowerButton.
Step 6: Congratulations, you have installed TWRP latest for your M32 4G, to access the system now, you need to perform some additional steps.
Step 7: Open up TWRP terminal and then type in "multidisabler" and then perform a full factory reset again by going into "Wipe" -> Format Data -> type "yes"
Step 8: Now stock ROM should work fine with TWRP!
COMPATIBILITY:
TWRP Recovery is compatible with latest Android 11-12 firmware
tested on:
M325FXXU3AUK1, M325FXXU4AVB1 ,M325FXXU4BVI2 as well
First time you boot into TWRP, don't forget to backup your EFS, Secondary EFS and NVRAM! Go into Backup and select "EFS,", "Secondary EFS" and "NVRAM" and backup to preferably MicroSDcard and copy it to your PC in case you need it if IMEI corrupts.
DON'T IGNORE THIS STEP!
DOWNLOADS:
VBMETA DISABLED FOR R: ***Link Removed***
TWRP TAR: ***Link Removed***
by [email protected] #PruhBootlooper
@cha0scl0wn
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As you can see, I accidentally erased all the partitions. I meant to just clear boot_a.
I tried recovering through these steps:
Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).
1. Open QFIL
2. Select Flat Build
3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.
4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.
5. Click download
6. Repeat steps for each lun folder
I kept getting this failure message in qfil:
I'm not sure if these are even the steps to fix it. Any Idea on what I need to do to resolve this?
nasedase said:
View attachment 5786719
As you can see, I accidentally erased all the partitions. I meant to just clear boot_a.
I tried recovering through these steps:
Download (https://drive.google.com/drive/folders/1WQaaM35SWiF_UbXAM8hiRB95D2CDkIEq) the backup. Unzip it to find 7 luns (0-6).
1. Open QFIL
2. Select Flat Build
3. Click load xml and select the rawprogram(#) XML that is in the lun(0-6) folder.
4. If it asks you for a patch xml, click cancel. It's not needed to flash this backup.
5. Click download
6. Repeat steps for each lun folder
I kept getting this failure message in qfil:
View attachment 5786723
I'm not sure if these are even the steps to fix it. Any Idea on what I need to do to resolve this?
Click to expand...
Click to collapse
Yes the best thing, or easiest rather, would be to determine which partitions are needed to get lgup to work, then flash a kdz with it.
Don't remember exactly which partitions are needed, google search for that. But flash those, from that backup, one by one, think there's only like 6 partitions needed.
That's the thing about qfil, if yer not sure what yer doing, don't do it
AsItLies said:
Yes the best thing, or easiest rather, would be to determine which partitions are needed to get lgup to work, then flash a kdz with it.
Don't remember exactly which partitions are needed, google search for that. But flash those, from that backup, one by one, think there's only like 6 partitions needed.
That's the thing about qfil, if yer not sure what yer doing, don't do it
Click to expand...
Click to collapse
The problem with the backup is that I wasn't able to get them to work through QFIL. Is there another method of flashing those partitions?
nasedase said:
The problem with the backup is that I wasn't able to get them to work through QFIL. Is there another method of flashing those partitions?
Click to expand...
Click to collapse
one by one. I've done it, it's time consuming, but it can be done. And be sure to pay attention so you don't flash the wrong one to the wrong partition. If you get a message about 'data overflow', immediately cancel, that means you are trying to flash to a partition too small for the image, and you'll overwrite the partition next to it, and probably end up with a brick.