Related
CyanogenMod is a free, community built, aftermarket firmware distribution of Android, which is designed to increase performance and reliability over stock Android for your device.
Code:
#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 ROM
* 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.
*/
CyanogenMod is based on the Android Open Source Project with extra contributions from many people within the Android community. It can be used without any need to have any Google application installed. Linked below is a package that has come from another Android project that restore the Google parts. CyanogenMod does still include various hardware-specific code, which is also slowly being open-sourced anyway.
All the source code for CyanogenMod is available in the CyanogenMod Github repo. And if you would like to contribute to CyanogenMod, please visit out Gerrit Code Review. You can also view the Changelog for a full list of changes & features.
What are Nightly builds? Auto compiled builds of the latest CyanogenMod source from github. This version change each night and aren't officialy supported. If you find bugs/issues you can/must discuss here (do not submit nightlies bug on CyanogenMod issue tracker).:good:
My builds uses all official CyanogenMod sources except the kernel. But I am merging it with all fixes/features from CM kernel repo, Google and kernel.org mainline too.
Downloads
Latest HumberOS
Installation
- First time flashing CyanogenMod to your device (or coming from another ROM)?
Root your device and install CwM Recovery* or TWRP.
Reboot into Recovery
Do a Nandroid backup!
WIPE (wipe data/factory reset + wipe cache partition)
Install the ROM from internal sdcard using CwM Recovery* or TWRP
* Check troubleshooting if you are using CwM Recovery.
FAQ
Please read before posting or reporting bugs!:good:
Reporting Bugs
Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
Please read the thread for known issues before reporting.
Grab a logcat right after the problem has occurred. (Please include at least a few pages of the log, not just the last few lines, unless you know what you're doing.)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Code:
What is your--
Tablet model:
Radio (baseband):
CM version:
CM Download url:
Gapps version:
----------------------------------------------------
Did you--
wipe:
restore with titanium backup:
reboot after having the issue:
----------------------------------------------------
Are you using--
a task killer:
a non-stock kernel:
CMSettings/Performance settings (other than stock):
other modifications:
----------------------------------------------------
Provide any additional information (observations/frequency of problem/last version it worked on/etc) as needed:
IRC
User channel
#teamhacksung-support
Developer channel
#teamhacksung
#cyanogenmod-dev
Development
HumberOS development thread
Changelog?
A rough changelog is available HERE
All Sources
HumberOS
CyanogenMod
______________________________________________________________
The CyanogenMod team would like to THANK everyone involved
in helping with testing, coding, debugging enting!
Enjoy!
Re: [ROM][JB][4.2.2][N80XX] CyanogenMod 10.1 - HumberOS - Q&A
Mmm been looking and thinking about flashing a rom might have to give this a try.
Thanks
Sent from my GT-N8013 using Tapatalk 2
Won't install.
Unable to get ROM installed on my GT-N8020
Latest version of rom tried.
Using CWM 6.0.2.8
Attempted correcting the assert failure but now aborts without error.
What am i doing wrong???
Also tried TWRP but it is unable to access the flash...
Re: [ROM][JB][4.2.2][N80XX] CyanogenMod 10.1 - HumberOS - Q&A
icuimp said:
Unable to get ROM installed on my GT-N8020
Latest version of rom tried.
Using CWM 6.0.2.8
Attempted correcting the assert failure but now aborts without error.
What am i doing wrong???
Also tried TWRP but it is unable to access the flash...
Click to expand...
Click to collapse
Hey!
I think the process is the same for all variants using CwM or TWRP.
Please, check the MD5 checksum.
Sent from my Galaxy Nexus using xda premium
TWRP is not supported on the N8020.
MD5 is fine.
Noticed when extracting the ZIP to modify the file it finds 24 files doubled up in the same place.
Is this an issue???
Is there anything i can provide to you that can help figure out why it won't install?
humberos said:
Hey!
I think the process is the same for all variants using CwM or TWRP.
Please, check the MD5 checksum.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
icuimp said:
Noticed when extracting the ZIP to modify the file it finds 24 files doubled up in the same place.
Click to expand...
Click to collapse
Which files?
Thanks!
N8020
Symlink: some symlinks failed
E:ERROR in /external_sd/cm10....
(status 7)
Installation aborted
Any advice against this ?
icuimp said:
Unable to get ROM installed on my GT-N8020
Latest version of rom tried.
Using CWM 6.0.2.8
Attempted correcting the assert failure but now aborts without error.
What am i doing wrong???
Also tried TWRP but it is unable to access the flash...
Click to expand...
Click to collapse
ttair said:
N8020
Symlink: some symlinks failed
E:ERROR in /external_sd/cm10....
(status 7)
Installation aborted
Any advice against this ?
Click to expand...
Click to collapse
Sorry guys!
My device is an N8013.
N8000, N8010 and N8013 have a similiar hardware.
But N8020 is LTE device and have some diferences between others.
I am still working on it.
Thanks!
N8013
i want to flash my rooted note 10.1 which is jellybean 4.1.1 deodexed version to this rom instead. my question is do i just straight away flash it or do i need to do something else since am on 4.1.1 ??
reddevilboyz said:
i want to flash my rooted note 10.1 which is jellybean 4.1.1 deodexed version to this rom instead. my question is do i just straight away flash it or do i need to do something else since am on 4.1.1 ??
Click to expand...
Click to collapse
Flash a recovery like this:
http://forum.xda-developers.com/showthread.php?t=2102677
Now download the ROM from here:
http://goo.im/devs/humberos/rom <-- you choose your device
and gapps from here:
http://goo.im/gapps/gapps-jb-20130301-signed.zip
Go into recovery by holding down the power button + volume up key (Release the power button when the device is turned on).
Now:
Wipe Factory Reset + Wipe Dalvin Cache + Wipe System + Wipe Preload
Install the ROM and gapps.
Wipe Cache + Wipe Dalvin Cache (optional)
Reboot
Screencast not working
Sorry for my bad english language but applying the inverse color after screencast recording screen capture solution thank you
I speak french
status update
I know that good things come to those who wait but would it be possible to have an update on when humberos for the n8020 would see the light of day? Ever since I bought my device I have been searching and reading on the internet every day and can not help but sadly left out of the possibilities to use an custom os on my device. I also have the impression to be alone in my search for answers as there is no real discussion going on on this subject and I wonder why this would be? For all I was able to find out is that the only work in progress going on specificly for the n8020 is being made by Humberto. Correct me if I am wrong. I also would like to ask as being new to Android if I can install a future release of humberos safely on my n8020 because its a t-mobile hungary branded. It's rooted however. I would like to thank anyone taking time to answer my questions.
Fuse
Cyanogenmod at this point for some reason seems to have serious issues with fused filesystems and so for one reason or another always messes up sd cards formatted with ntfs, ext4, or exfat. Most common of those being exfat as many people are using it on the large sd cards for obvious reasons. In this light after searching xda I found this and have been stably using it for weeks now in combination with your rom... http://forum.xda-developers.com/showthread.php?p=38182488#post38182488 ... its a flashable mod that supports mounting of exfat, ntfs, and ext4 formatted sd cards in CM 10.1 be it single partition or multi-partition. Till now I have encountered no errors or problems with it hence I was wondering if it might be possible for you, Humberto, to coordinate or work with that developer and include it in your rom or at least include a link on your page. Those of us using the n80xx love to use large sd cards as this is a tablet pc, samsung's recent stock firmware already takes care of exfat but cm 10.1 does not and without it... well there are several limitations and negative aspects of Fat32. Just something to consider and I know its not the most crucial part of the ROM but it would DEFINITELY be nice to be able to mount a wider variety of Filesystems without flashing 3rd party mods.
Thank you for your work
Hello Humberto,
you was a live saver for me and my N8010. I am running your rom now for a couple of weeks wirthout any big problems (beside a small installation problem since I have the N8010 version).
I have now noticed that cyanogenmod(dot)org have now nightly builds for the N80XX. My question is what are the main differences between "official" nightly builds and your rom?
If you or somebody else could answer my question I would be very happy
regards
nightly vs humberos
The main difference is in the kernel, I prefer humbertos kernel as , at least to me , it feels smoother and more stable along with providing additional options. Here are the Kernel tags for humberos so you can see the changes ...http://forum.xda-developers.com/showthread.php?p=37586691#post37586691
Aeolius said:
The main difference is in the kernel, I prefer humbertos kernel as , at least to me , it feels smoother and more stable along with providing additional options. Here are the Kernel tags for humberos so you can see the changes ...http://forum.xda-developers.com/showthread.php?p=37586691#post37586691
Click to expand...
Click to collapse
Hello Aeolius,
The Kernel Tags are to technical for me
Anyway if the hubertos kernel is more stable I will stay with it. Thanks.
goosefx said:
Hello Humberto,
you was a live saver for me and my N8010. I am running your rom now for a couple of weeks wirthout any big problems (beside a small installation problem since I have the N8010 version).
I have now noticed that cyanogenmod(dot)org have now nightly builds for the N80XX. My question is what are the main differences between "official" nightly builds and your rom?
If you or somebody else could answer my question I would be very happy
regards
Click to expand...
Click to collapse
My rom have minimal diferences between official CM builds.
Over ROM space we have some options in Settings like old Tablet UI as user option.
Over Kernel space we have a lot of diferences like OC, UV, memory management, kernel mainline sync (all security fixes), etc.
Enjoy it!
Aeolius said:
Cyanogenmod at this point for some reason seems to have serious issues with fused filesystems and so for one reason or another always messes up sd cards formatted with ntfs, ext4, or exfat. Most common of those being exfat as many people are using it on the large sd cards for obvious reasons. In this light after searching xda I found this and have been stably using it for weeks now in combination with your rom... http://forum.xda-developers.com/showthread.php?p=38182488#post38182488 ... its a flashable mod that supports mounting of exfat, ntfs, and ext4 formatted sd cards in CM 10.1 be it single partition or multi-partition. Till now I have encountered no errors or problems with it hence I was wondering if it might be possible for you, Humberto, to coordinate or work with that developer and include it in your rom or at least include a link on your page. Those of us using the n80xx love to use large sd cards as this is a tablet pc, samsung's recent stock firmware already takes care of exfat but cm 10.1 does not and without it... well there are several limitations and negative aspects of Fat32. Just something to consider and I know its not the most crucial part of the ROM but it would DEFINITELY be nice to be able to mount a wider variety of Filesystems without flashing 3rd party mods.
Click to expand...
Click to collapse
Hey dude!
I will check these features and if they are ok then I will let you know how we can include them in our project.
Thanks!
awesome
That's awesome, I hope you can get permission from the respective developers this would truly be a great feature, also I saw that you added 1700 and 1800 clock steps in the kernel tag is the only way to access those by editing the default steps in the text files myself or I'm misunderstanding the kernel tags ? Thanks for the great work!
Aeolius said:
That's awesome, I hope you can get permission from the respective developers this would truly be a great feature, also I saw that you added 1700 and 1800 clock steps in the kernel tag is the only way to access those by editing the default steps in the text files myself or I'm misunderstanding the kernel tags ? Thanks for the great work!
Click to expand...
Click to collapse
Actually both 1.7 and 1.8 Ghz are very unstable.
I removed them.
So, 1.6GHz is good for us.
Thanks!
Q&A for [KERNEL][AGNi][CM] 29-11-2014 AGNi pureCM v4.4 (ULTRA SMOOTH) [F2FS/EXT4]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][AGNi][CM] 29-11-2014 AGNi pureCM v4.4 (ULTRA SMOOTH) [F2FS/EXT4]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Just wanted to ask.. Sry i'm newbie to galaxy tab2
First, thank you for your great work.
I was using my Galaxy Tab2 just by flashing 'normal' roms like cm11, slimkat, etc...
I never had switched kernel, and I even don't know what kernel really does.
But I've read through your post, and figured out that this kernel will make my Galaxy Tab2 blazing fast
And I started to install this kernel.
Well, to be honest, to such newbies like me, installing kernel is very hard at the first time.. I knew nothing about how to format into F2FS, flashing recovery, etc... some unique steps (to me, it is haha)
Well I was using Philz Touch recovery which I flashed with Odin. After, I didn't know how to install recovery!
The answer was just flashing zip file of TWRP recovery through Philz... Embarassingly, it was so easy.
After, there was a problem. I had to format CACHE, PRELOAD, SYSTEM, DATA into F2FS (maybe not but there was 4 files that formats in a single shot). I recognized that if I format DATA, then I'll lose CACHE PRELOAD SYSTEM + CM11NEWEST UPDATE ZIP, GAPP TO FLASH which are saved at internal storage Sadly, I didn't have microSD to mount....
So what I did was,
1. Flash CACHE PRELOAD SYSTEM format tools
2. Install CM11 newest rom
3. Flash AGNi kernel aroma installer -----> installed AGNi kernel
4. Install GAPPS I prepared for my CM rom (this part, at the first time I flashed it before installing AGNi kernel, but it didn't work. After installing kernel, it got installed somehow.. lol)
5. Now, I formatted data with DATA format tools...
Step 5 was terrible at the first moment. Log at TWRP said E:error installing blah blah blah.. .formatting failed..
I just rebooted recovery as the first post said...
And data was formatted. LOL? It said error, but it was already done!
Anyways, installation is complete, successfully booted... now, it's time for me to try out the new kernel!
Well I guess I was writing this post to help ppl who get into the same trouble... I just did like that and it got successfully finished...
Thanks to developers.. I'll enjoy this wonderful kernel.
Ethernet connectivity possible?
Hello, is ethernet connectivity possible with this ROM? Please tell me the steps to take. What type of adapters/chipsets are supported?
Thanking you.
droped support for TAB2. Sorry....
[Q&A] [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F
Q&A for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [KERNEL][3.4.105][12/09/14] UBER-L | LINARO & SaberMod 4.10 -OFast Graphite F2FS. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Thanks
@Cl3Kener: Big thanks for your hard work. Installed your kernel yesterday, and can definately see some improvements.
@ramjet73: Big thanks to you too. I followed your posts/instructions and flashed rastapop+uber and am happy i finally took the plunge.
Now for my question: I have the tricksterMOD and I can't see any color profiles (except the default). How can I apply other profiles? I only see one.
Regards,
On LiquidSmooth LP 4.0 with UBER-L 3.4.105
Governer = optimax
Scheduler = zen
Read Ahead Buffer Size = 3072
Everything is running smooth and fast! Good battery life!
Low brightness after install
Hello, I gave a question... When I installed a last Uber kernel L v4.10 from 9 December of 2014... I have a very low brightness... How can I fix it...
Also I cannot make OC more than 2.7 or 2.8 ... Phone doesn't boot... And how I can fix it...
Thank you for a answer
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Are there any negative consequences for clocking the minimum frequency at 96MHz?
Usb-otg f2fs
I'm currently using the latest version of UBER-L kernel (01/01/15).
I have formatted my Micro USB to F2FS and would like to use it with my phone. TWRP recognises the USB and mounts it successfully, but the ROM (OptiPop) does not mount the USB. Both mount the USB fine when it is formatted to FAT32.
Is it possible for me to use F2FS using USB-OTG?
Thanks.
Edit: Got it working by using the 'Stickmount' app. ^_^
FloGatt said:
Hi,
is it advisable to disable filesystem trim in ubers cfg file while using f2fs?
Chet says, F2FS is auto-trimmed: https://plus.google.com/app/basic/stream/z13cxltwwqjcsx3ta22pyx5reobgudsiq04
Click to expand...
Click to collapse
I disabled trimming and I dont see a difference with f2fs. I would conclude that it isn't necessary with f2fs
Is there changelog of the new kernel version?
FloGatt said:
Is there changelog of the new kernel version?
Click to expand...
Click to collapse
Its all on github. The link is on the OP of the original thread. (The one with the download links)
GPU clock not going above 450MHz
Hey, I'm using this kernel (latest version as of now), on a clean flash of Optipop (also latest as of now - 11/01) with F2FS.
I set the max gpu clock to 650000000 in the uber_v1.3.cfg file in /etc
(also by terminal as in the 2nd post just to be sure) (echo "650000000" > the path and all)
Apps like System Monitor Lite and CPU-Z confirm that the max gpu clock is 650Mhz (Adreno 330 @ 650Mhz).
I have also set the performance governor (in the config file, and I tried via synapse + UKM 3.6.1 too) (I have set synapse not to apply settings on boot, so that should not be interfering with the init config of uber kernel until I set something in it.) I have no other kernel tweaking apps anyway.
However, the clock only goes up to 450MHz no matter what. It goes directly to 450 when touching the screen due to the performance governor, so I know settings are being applied.
However System Monitor, CPU-Z etc all show, current clock: 450MHz, Max Clock 650Mhz.
Even benchmarking with GFX bench gives results basically identical to the stock Nexus 5 with 450MHz, so there is no performance and FPS difference that should be there.
I searched the developer thread and found a few posts from many months ago that the gpu overclock was working properly for many people, with an appropriate improvement in FPS and benchmarks, with a couple of people also having my issue, that whatever of 650/533/450 max I apply, gpu doesn't go over 450MHz. However I couldn't find any solution.. it stopped working properly at some point between those builds when Chet introduced 533/650 and now?
I can't post in the dev thread (less than 10 posts).
This is reproducible, right after a clean boot, not a thermal issue (am not overclocking CPU, not running any CPU benchmarks, temp is less than 50C).
Hope someone can help. Thanks!
Installed Optipop back onto my N5 today. After a few hours of the phone being on the UI starts to act up then eventually needs a reboot to get back to being functional. I then flashed UberL kernel and now my screen is fuzzy and glitches out. Never had this problem in the past with Optipop or UberL. Please don't ask if I dirty flashed or deleted the android folder. I completely wipe my phone before I install a new ROM. I have been installing ROMs for a good minute now and have never seen this before. I have tried at least 5 other rom/kernel combos.....none have the same affect as UberL and Optipop. Yes I've tried F2FS ONLY Permissive Only and EXT4/F2FS Permissive and Enforcing with no luck.
Has the issue with the missing charging icon when the phone is turned off and plugged in reappeared? I have System, Data, and Cache formatted as F2FS and flashed F2FS-ONLY-Lollipop-Kernel-Cl3Kener-Kexec-Permissive.zip before flashing UBER, but I am still having this issue. Everything else appears to be running smoothly.
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
sirarduin said:
Is there anyway to know if I isntalled corectly this kernel ? I changed a setting in the cfg file and it seem to not change anything. For exemple,
10.2 : Double tap to wake
# -Double tap on screen to wake up the device.
# - option are:
# 0 - Diable
# 1- BOTTOM hald of screen
# 2- Full screen
DT2W=2
When i tried to doubletap the screen, nothing happened.
When i installed the kernel, i didn't cleared the cache and the ????? but it might be working Anyway. is there a way to know if its working ?
After a benchmarks i think that the kernel isn't realy doing someting. i added +50 in 3.CPU SETTINGS OVERVOLT... isn't realy doing someting.
Click to expand...
Click to collapse
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
JayR_L said:
Confirmed. I have the same problem. Nothing in the uber.cfg file works. Its as if it wasn't even there.
Click to expand...
Click to collapse
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
sirarduin said:
Format rom and then delete cache + tmp\mksh. Make sure to have a fresh ROM folder. Reinstall OptiPoP.ZIP, then flash the kernel before even boot. Now u can boot. install GA APP. Some time reinstalling work. Am lcuky...
Always do the following AFTER installing the kernel:
1. Clear cache
2. Clear dalvik
3. Fix Permissions
Click to expand...
Click to collapse
So you are saying that fixes the issue with the cfg file?
JayR_L said:
So you are saying that fixes the issue with the cfg file?
Click to expand...
Click to collapse
After 2 Benchmarks, i can say that doing this fixed MY problem. Uber/sabermod is now working realy well for the performance. Uses AnTuTU to check if its working. It upgraded a lot the performance for me.
Which governor gives me more performance?
[email protected] said:
Which governor gives me more performance?
Click to expand...
Click to collapse
performance ?! but it will drain your batterie a lot.
F2FS for VILLE
AOSP only!
Current CM or most any of our AOSP ROMs around here that use a current CM based kernel.
THIS IS EXPERIMENTAL AND HAS POTENTIAL FOR DATA LOSS IF DONE IMPROPERLY. IF YOU ARE NOT COMFORTABLE WITH THAT PLEASE DO NOT ATTEMPT. I CANNOT BE AVAILABLE FOR 24/7 SUPPORT ON THIS.
These mods will provide the ability to format /data and /cache in F2FS format instead of EXT4. Use extreme caution. The will erase your entire /data partition just like a clean flash. I cannot and will not be held responsible for your failure to keep backups handy. F2FS is still considered experimental by Samsung and should be by you the user as well.
What is F2FS?
F2FS wiki
Why F2FS?
F2FS put to the test vs EXT4
How to switch?
PLEASE READ INSTRUCTIONS CAREFULLY. IF NOT FOLLOWED YOU WILL LIKELY BOOTLOOP!!
F2FS capable TWRP Recovery This is the same as the Official TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Kernel+fstab conversion zip Flash this after converting partitions to F2FS to install a CM kernel with F2FS support built in. This zip uses an anykernel installer so it should be comparable with most current ROMS. The zip will extract your current boot.img, unpack and replace your current fstab with a new fstab to indicate you current partition types, replace kernel with F2FS capable kernel , then repack and replace the boot.img
Fstab conversion zip For use only when you are already running a F2FS kernel and only need to update fstab after switching to/from F2FS/EXT4. This installer will only unpack, edit the fstab, and repack the boot.img. This will not replace the kernel, you must already be using an F2FS kernel or be returning to EXT4 only to make use of this zip.
DOWNLOADS
Downloads
Procedure for fresh conversion including new Rom flashing:
1. Backup everthing you want to keep with titanium backup or whatever backup you choose.
2. Fastboot flash the new recovery img.
3. Run a twrp backup in case things get ugly!
4. Flash new ROM now if desired.
5. Still in recovery...Goto wipe -> hit Advanced wipe. Select data and hit change partition type. Convert to F2FS. Repeat for cache.
6. Flash the Kernel+fstab conversion zip.
7. Reboot and profit. Any partition app on market can confirm new format changes.
Procedure for nightly ROM updates after F2FS conversion:
1. Flaah nightly
2. Flash kernel+fstab conversion zip.
Procedure if you want to convert back and forth after initial conversion for testing purposes:
1. Change formats of data/cache as desired (only ext4 and f2fs supported).
2. Flash fstab conversion zip to update format types before attempting boot.
Code:
CHANGELOG
V1.0 - Initial release
Thanks To/Credits:
@jrior001 - For Op
@cannondaleV2000 [crazy right] - For The Idea/every thing
Devs, feel free to use or modify any of this for your own work just give thanks to where it came from. It was not all my original work, I must give thanks to Metallice and jrior00 a few other devs in the grouper forum whose scripts I adapted for my own work.
Source:
Kernel
Recovery tree
Fstab scripts
BUGs :
while converting to f2fs the sd card becomes wiped on hboot 2.16 and I'm just going to go on a whim and say 2.15 as well I don't run it so it has not been tested
You have been warned so no one complain "plz sir you wiped my sd y u no say dis" you will be laughed at
Flashalot said:
BUGs :
while converting to f2fs the sd card becomes wiped on hboot 2.16 and I'm just going to go on a whim and say 2.15 as well I don't run it so it has not been tested
You have been warned so no one complain "plz sir you wiped my sd y u no say dis" you will be laughed at
Click to expand...
Click to collapse
What about converting system to f2fs?
Is it possible to rebuild it based on TWRP 2.8.5.0 (latest)?
You have not mention anything about S-off.. Is it necessary? If yes, add this please in your how to .
Edit (to avoid extra post) i am taking about step 6
Sent from my MI 2S using Tapatalk
NightHeron said:
You have not mention anything about S-off.. Is it necessary? If yes, add this please in your how to
Sent from my MI 2S using Tapatalk
Click to expand...
Click to collapse
Flashing recovery through fastboot never needs s-off
also @Flashalot, will this work on my M7 if I replaced the zImage? We have an F2FS compatible TWRP but no F2FS compatible kernel
javelinanddart said:
What about converting system to f2fs?
Click to expand...
Click to collapse
If it's just system I believe your ok
Rapier said:
Is it possible to rebuild it based on TWRP 2.8.5.0 (latest)?
Click to expand...
Click to collapse
Yes it's just taking a while because I'm back to using separate recovery branch's as I believe this would be the cause as to why I am having the sd card wipe bug and I'm only one person [emoji6]
NightHeron said:
You have not mention anything about S-off.. Is it necessary? If yes, add this please in your how to .
Edit (to avoid extra post) i am taking about step 6
soff don't matter
Sent from my MI 2S using Tapatalk
Click to expand...
Click to collapse
Not needed
dd98 said:
Flashing recovery through fastboot never needs s-off
also @Flashalot, will this work on my M7 if I replaced the zImage? We have an F2FS compatible TWRP but no F2FS compatible kernel
Click to expand...
Click to collapse
Well to give you a insider tip f2fs is about to be released on m7 in a couple of days it's getting the final touches from @cannondaleV2000
Question: If I use a custom kernel (like IceCode or Void), I should first flash the kernel then the conversion zip right? And all the features and functionality of the custom kernel will be preserved just that it'll have added F2FS support. Right?
Question2: What happens if DATA?CACHE/SYSTEM are converted and I restore a nandroid backup made before while I didn't have F2FS? I remember that during restore, partitions are reformatted prior to restoring data on them. Will they be formatted with the new F2FS or they'll be formatted as they were before when I was making the backup (eg EXT4)?
EDIT: I've flashed the recovery and after flashing it sdcard shows only 2.5 GB total space...is this supposed to happen? Reading again your post with the BUG I assume you have a 2.16 hboot...could it be that the recovery is also made for 2.16 and this could be the case? Shouldn't be 2 different versions for 2.15 and 2.16? Also you might state this in the OP cause it is not saying anything about hboot requirement (or I couldn't find this)
It seems like the recovery is for 2.16 hboot only so it is not based on the official TWRP 2.8.1.0 (that's for hboot 2.15). Flashing it on a 2.15 hboot makes the storage showing wrong size. I flashed back the TWRP 2.8.5.0 official and everything is back to normal
Rapier said:
Question: If I use a custom kernel (like IceCode or Void), I should first flash the kernel then the conversion zip right? And all the features and functionality of the custom kernel will be preserved just that it'll have added F2FS support. Right?
Question2: What happens if DATA?CACHE/SYSTEM are converted and I restore a nandroid backup made before while I didn't have F2FS? I remember that during restore, partitions are reformatted prior to restoring data on them. Will they be formatted with the new F2FS or they'll be formatted as they were before when I was making the backup (eg EXT4)?
EDIT: I've flashed the recovery and after flashing it sdcard shows only 2.5 GB total space...is this supposed to happen?
Click to expand...
Click to collapse
since i believe those kernels use there own zImage then I believe the answer would be a no but for any of those who make custom kernels i have all the patches they need in the op
you would have to flash the kernel+fstab conversion because it was formated in EXT4
Rapier said:
EDIT: I've flashed the recovery and after flashing it sdcard shows only 2.5 GB total space...is this supposed to happen? Reading again your post with the BUG I assume you have a 2.16 hboot...could it be that the recovery is also made for 2.16 and this could be the case? Shouldn't be 2 different versions for 2.15 and 2.16? Also you might state this in the OP cause it is not saying anything about hboot requirement (or I couldn't find this)
It seems like the recovery is for 2.16 hboot only so it is not based on the official TWRP 2.8.1.0 (that's for hboot 2.15). Flashing it on a 2.15 hboot makes the storage showing wrong size. I flashed back the TWRP 2.8.5.0 official and everything is back to normal
Click to expand...
Click to collapse
it based on the unified recovery so there would be no need for a hboot requirement kinda already stated i have to make 2 diff ones ill make them in the morning should hit me up on hangouts instead of xda ya know lol
Flashalot said:
it based on the unified recovery so there would be no need for a hboot requirement kinda already stated i have to make 2 diff ones ill make them in the morning should hit me up on hangouts instead of xda ya know lol
Click to expand...
Click to collapse
Yes, I know we should talk on hangouts but I posted here cause I thought that the questions and answers will be of general interest and maybe others will want to know also
And if the recovery is for both hboots don't know why is showing incorrect size for sdcard...
Sent from nowhere over the air...
Rapier said:
Yes, I know we should talk on hangouts but I posted here cause I thought that the questions and answers will be of general interest and maybe others will want to know also
And if the recovery is for both hboots don't know why is showing incorrect size for sdcard...
Sent from nowhere over the air...
Click to expand...
Click to collapse
yea i guess so and i have no clue but im going to redo all the recovery edits and upgrade it to the latest twrp hopeful;y it wont take so long...
@Flashalot can you make tutorial how to compile TWRP from source with support for F2FS.
@Flashalot
Can you add the list of custom kernels that support F2FS to the OP?
My Void KitKat Kernel
My Frosted Kernel
@mikronac.ns's Stockie kernel (coming soon at least, I added the patches today, it needs to be released)
@rmbq's Bubba Kernel (old though, doesn't support ROM builds made after August 2014)
EDIT: Also I only see 640MB of Internal SD space on HBOOT 2.15. That's not right...
mikronac.ns said:
@Flashalot can you make tutorial how to compile TWRP from source with support for F2FS.
Click to expand...
Click to collapse
all my repos are up all you have to do is pull them and build like any other twrp recovery if you really want me to I guess
javelinanddart said:
@Flashalot
Can you add the list of custom kernels that support F2FS to the OP?
My Void KitKat Kernel
My Frosted Kernel
@mikronac.ns's Stockie kernel (coming soon at least, I added the patches today, it needs to be released)
@rmbq's Bubba Kernel (old though, doesn't support ROM builds made after August 2014)
EDIT: Also I only see 640MB of Internal SD space on HBOOT 2.15. That's not right...
Click to expand...
Click to collapse
Yea sure also don't worry that's from the messed up recovery sent the recovery to some cany5 testers today hopefully fix the problem if so I'll release it today
Flashalot said:
all my repos are up all you have to do is pull them and build like any other twrp recovery if you really want me to I guess
Yea sure also don't worry that's from the messed up recovery sent the recovery to some cany5 testers today hopefully fix the problem if so I'll release it today
Click to expand...
Click to collapse
OK. By the way, I have an updated installer. This requires us to maintain two installers because HBOOT 2.15 has a different FSTAB than HBOOT 2.16. I also deleted unnecessary junk to make the script smaller. And (being a grammer Nazi) I added some capatalizations to make it look nicer and corrected some grammar. I'll upload it when I'm done
EDIT: @Flashalot
https://github.com/javelinanddart/f2fs_fstab_convert is the installer (two seperate folders)
Zips are attached
javelinanddart said:
OK. By the way, I have an updated installer. This requires us to maintain two installers because HBOOT 2.15 has a different FSTAB than HBOOT 2.16. I also deleted unnecessary junk to make the script smaller. And (being a grammer Nazi) I added some capatalizations to make it look nicer and corrected some grammar. I'll upload it when I'm done
EDIT: @Flashalot
https://github.com/javelinanddart/f2fs_fstab_convert is the installer (two seperate folders)
Zips are attached
Click to expand...
Click to collapse
Ahhh nice also the grammar as well ill just pack this up in a aroma zip and call it a day lol probably redo that as well
Flashalot said:
Ahhh nice also the grammar as well ill just pack this up in a aroma zip and call it a day lol probably redo that as well
Click to expand...
Click to collapse
I can pack them as an AROMA Installer, don't worry, I just didn't know if you wanted it to be an AROMA installer. Is the test recovery working by the way?
EDIT: I pushed the AROMA installer commits. It is a unified installer now + has a check to make sure you don't screw anything up if you're on the wrong device or HBOOT
Question, I only lost my internal sd data if I convert that partition? If i convert system, data, cache. My photo wil be deleted too?
lorddavid said:
Question, I only lost my internal sd data if I convert that partition? If i convert system, data, cache. My photo wil be deleted too?
Click to expand...
Click to collapse
Backup your sdcard on your pc for safety. I couldn't try it to test for sure since the recovery didn't work properly on hboot 2.15. I'm waiting for a new one to test especially that are some new custom kernels with F2FS support
Sent from nowhere over the air...
This thread is a direct continuation of @Hashcode's work for porting to Lollipop. Because of his and @verygreen's heavy lifting, porting to CM12.1 happened almost painlessly, for which I'm grateful. Their contributions compelled me to share something back. Thus, I'm uploading personal builds of CM12.1 for HD and HD+ in this shared Box folder. While I do not own a hummingbird, sister builds are generated more or less concomitantly.
Some of the important device-specific changes from KitKat/CM11 are described in Hashcode's thread. The goal is to keep as close as possible to CM upstream, and integrate whatever fixes and enhancements we find over time. More progress information will be added here gradually, as I have time. A lot of useful discussion happened on the CM12.0 thread, and the status of things is available to anyone willing to search. Hunting for possible bug fixes, understanding how to actually boot a newer kernel are some of my current priorities. I am not a developer, and the usual disclaimers apply.
Recovery Information
Up to date eMMC TWRP images are included in the respective device folders. Personally, I've had a good experience with TWRP, and do not plan on looking at other recovery distributions. Now, there have been (very) sporadic reports of broken partition tables, soft-bricked devices, etc, blamed on recovery. Although recovery is usually not the actual culprit, here are some ways you can rescue a completely unresponsive device:
It's a good idea to keep a microSD card around, with verygreen's external recovery image from here.
Once booted off the external recovery, you can easily fix whatever is broken (ADB is your friend here). There's no need to re-install CM11, as re-flashing recovery and/or boot will most likely fix your issue.
Recovery partition: dd if=<path to recovery image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery
Boot partition: dd if=<path to boot/kernel image> of=/dev/block/platform/omap/omap_hsmmc.1/by-name/boot
Afterwards, you should at the very least have a working internal recovery. I don't recall any instance where /system and/or /data became corrupted because of recovery, but you can certainly fix them now.
I've never tested this part, but I believe that you may be able to install an eMMC CM12 ZIP with verygreen's external CWM, even if /data and /cache are F2FS (assuming you copied all ZIPs onto the external card). My understanding is that only /dev/block/platform/omap/omap_hsmmc.1/by-name/system (always ext4, mountable by any recovery) is touched during installation, so you may even bypass TWRP completely.
P.S. If you broke you bootloader by flashing the wrong recovery flavor, despite all images being clearly labeled as hummingbird or ovation, well, no sympathy for you… Still, you can bring your device back to life within minutes as described above.
Progress towards Official CM12 Nightlies
As of now, most things are ready for turning official nightlies on, including official TWRP images and SELinux Enforcing support, albeit with this proviso:
My HW composer changes described in post #3 and #602 are not included upstream, since the plan was to fix upstream for all devices using CyanogenMod/android_hardware_ti_omap4.
The stumbling block with SELinux Enforcing had been remounting /system upon each new install, to write the customized WLAN NVS BIN. I'm avoiding this step by modifying the scripts to store the Wi-Fi calibration data in /rom now, with the added benefit that it only needs to be generated once. These changes are also not captured upstream, and may never be. If someone figures out an upstream-approved way of writing to /system upon first boot under Enforcing, then we'll probably switch back to the old fix-mac script.
On a personal note, posting on my threads is pretty tricky business... My builds were never intended for general consumption, but rather a way to move porting and development forward, and I often debate only keeping the GitHub repositories for people to build themselves. Obviously, that would upset hundreds of people at this point, so I make an effort to upload reasonably bug-free builds, as well as help even with trivial non-problems whenever I can. Nevertheless, low quality, or badly written posts (and I don't mean bad English) are a sure way to get ignored, and my memory is pretty long term Basically, I won't police content here, but I also don't want to deal with the the kind of stupidity and entitlement so prevalent in real life.
In conclusion, no need to thank (unless you really want to), or ask about donating, etc, but do reassess the limits of your current understanding before making bold claims, as I do too. Nothing worse than having to fix a trail of misinformation... Also, comparisons to other people's work (unless constructive), complains about the state of things, or simply starting with "no offense" and such, will make your problem much less likely to be solved by me.
XDA:DevDB Information
UNOFFICIAL CM12.1, ROM for the Barnes & Noble Nook HD, HD
Contributors
amaces, Hashcode, verygreen, Jon Lee
Source Code: http://github.com/airend
ROM OS Version: 5.1.x Lollipop
ROM Kernel: Linux 3.0.x
Version Information
Status: Testing
Created 2015-04-16
Last Updated 2015-09-14
All Things Kernel
The information below (branch names, kernel progress, etc) is slowly becoming out of date (post #2 in the Marshmallow thread has more details). Although it feels pretty archaic at this point, I'm leaving this information here, mostly for historical reasons.
My primary focus has been and continues to be an even better kernel. Instead of opening a separate thread, I will be using this space for kernel updates and related information, in a sort of log format.
Since making any of the fancier OMAP-specific kernel trees work properly is a huge headache with limited benefits, I just merged the linux-3.0.101 patches, mainly for testing (the d-3.0 branch). These patches may help with the ARM core, not so much with OMAP parts, and certainly no change to any of the Nook-specific systems. Subjectively, the normal kernel still feels marginally more stable, but hey, everything still works.
It's mid May, and for the past couple of weeks, branch g-3.0 has slowly become my default kernel. It contains additional merges from the Google 3.0 OMAP kernel, the .101 commits, plus cherry-picked changes from various sources. Hopefully, all these make for a better kernel, although the holy grail remains K3.4…
I've been experimenting with improvements upon KSM; UKSM and PKSM are supposed to better recover duplicated/lost RAM (the former in the default g-3.0 branch, the latter in p-3.0). As with KSM, they need to be enabled (and optimally tuned) through the sysfs interface (echo 1 > /sys/kernel/mm/[up]ksm/run).
A significant number of patches were added for LZ4 support, and to make zram/zcache actually use it. I think it makes things snappier, but we'll have to wait and see. Also, it turns out that good old KSM is better after all; PKSM creates instability, and UKSM is a lot more CPU hungry, very much undesired on an already underpowered device.
Another exciting week for K3.0… @Hashcode uploaded a bunch of LMK/low RAM/etc optimizations for some AMZ/OMAP44xx variants, which I'm stealing for the HDs. As I'm better understanding the use of MFLAG/QOS for frame prioritization, I ported some of these changes from K3.4. The most exciting however, is the DMA-buffered K3.0 that I have working (branch dma-buf). It definitely feels better, although figuring out how to completely switch away from memory carveouts, fix the communication with OMX/Ducati for HW accelerated video, is complicated. This branch will remain an experimental project till K3.4 is up and running.
Just for testing, I'm rebasing most of my changes on top of the official CM12.1 kernel, and made the new iosched branch default for a while. This branch contains many changes to the block layer, cherry-picked from @faux123's tuna kernel. We now have newer I/O schedulers, such as FIOPS, ROW, and eventually BFQ. The current default elevator is ROW with 256 KB readahead. A few other interesting patches popped up, mainly related to unaligned access on ARM, and related optimizations.
Since July, all changes are grouped into feature branches on top of the upstream kernel, which are finally merged into the cm-12 branch, the default for the foreseeable future. This way of doing things is easier to maintain, and makes these changes easier to read, when deciding what to keep/discard for upstream.
HW Composer Issues & Fixes
The goal, and probably one of the base requirements to have these devices included in the CM12 nightlies, is to have a stable ROM with normal HW accelerated overlays. As of now, we achieved this by mostly reverting to the HW composer in CM11, although understanding why the newer code in hardware/ti/omap4 creates these underflows is equally important. Post #602 contains more information about this issue.
Starting with the July 14th builds, disabling HW overlays shouldn't be necessary any longer.
Before mid-July, we were using the upstream HWC in CyanogenMod/android_hardware_ti_omap4. As discussed ad nauseam, that combination of upstream K3.0/PVR modules/SGX DDK binaries/HWC runs into serious GFX buffer underflows. With five or more composer overlays, the panel attempts to reset constantly, which causes display flickers, followed by reboot (dumpsys SurfaceFlinger|grep -A 10 type will show how consistent this bug is).
In the meantime, a poor workaround was to disable HW overlays in Developer options. To make it stick across reboots, you could use this /data/local/userinit.sh:
Code:
#!/system/bin/sh
(while :
do
sf=$(service list | grep -c "SurfaceFlinger")
if [ $sf -eq 1 ]
then
service call SurfaceFlinger 1008 i32 1
break
else
sleep 2
fi
done
) &
First!!! Great to see you start your own thread. Thanks for all the great work
ac-t660 said:
If I have the 3/24 ROM already installed, should I dirty-flash the 4/8 version or do I need to reset and fresh install it in order to properly get the changes?
And like everybody else has said - thanks amaces and hashcode, incredible job!
Click to expand...
Click to collapse
Doh! I must have been typing my question as you were creating this new thread. Moving it since you and everyone using your builds are moving over here. Thanks again!
Based on this, I'd say that should be possible soon, if not already. However, that wasn't the case with the initial builds. I'd say no harm wiping just /system, and maybe /cache, flashing a CM12.1 ZIP, plus the proper GApps, and see how it goes.
Thanks!
I've flashed your 8 Apr build, and it (mostly) looks good. I still get the occasional forced reboots after some flickering. The flickering tends to occur when changing from portrait to landscape and pulling down the settings bar.
I very much look forward to see some progression.
Can you provide some instructions with installing TWRP on the HD+? I have Cyanoboot installed and flashed your build using CWM recovery.
Thanks.
In response to this post in the 12.0 thread.
amaces said:
The changelog would basically be the CM12.1 one
Click to expand...
Click to collapse
Great, so can you point to the latest CM12.1 commit that you've included when you make a release? Knowing the date doesn't pin it down completely.
amaces said:
About the ovation kernels, those images were for CM12.0, and while they may work with current builds (for reasons stated above), they don't provide any benefit anymore.
Click to expand...
Click to collapse
So we should use our original boot/kernel images?
Thanks!!
Hey amaces,
Thanks so much for the 12.1 builds. On the 4/4 build and will be testing out the 4/8 build over the weekend.
Thanks!!
shdware said:
Can you provide some instructions with installing TWRP on the HD+? I have Cyanoboot installed and flashed your build using CWM recovery.
Click to expand...
Click to collapse
Flashify can do that for you inside the ROM, or you could dd if=recovery.img of=/dev/block/platform/omap/omap_hsmmc.1/by-name/recovery inside adb shell or terminal. Also, current TWRP allows flashing of boot/recovery images directly.
MossyTC said:
Great, so can you point to the latest CM12.1 commit that you've included when you make a release? Knowing the date doesn't pin it down completely.
Click to expand...
Click to collapse
Sure, can do, although that kind of tagging needs to be thought out. I could simply append the CM review change number, but that's not very useful since most changes are in repositories that don't affect our devices. I'll look if anyone found a good way to do it (frankly, I don't recall seeing it done).
MossyTC said:
So we should use our original boot/kernel images?
Click to expand...
Click to collapse
The ROMs come with their own kernel. Those independent kernels were simply testing a few patches for the buffer underflow/flickering issues, and were meant for easy swapping within compatible CM12.0 builds.
Hi amaces,
I had done the 5.0 build, what do I need to do in order to pull in the 5.1?
TIA
andtron said:
Hi amaces,
I had done the 5.0 build, what do I need to do in order to pull in the 5.1?
TIA
Click to expand...
Click to collapse
I think it's better to backup your apps (I use titanium), do a full wipe and then install the 5.1 rom and gapps.
I am running the 04/08 and it is working fine except one major problem that is the bane of Android everywhere since kitkat...
It keeps telling me I have insufficient storage space to do anything, update apps or install new apps, and there are hardly any apps on the device.
When I go to Settings -> Storage it says total space 12.67GB but "Available" is only 700MB, which doesn't add up and doesn't agree with the graph.
I have:
Apps 0.92GB
Pictures, videos 5.62MB
Audio 296KB
Downloads 1.20GB
Cached data 1.24MB
Misc 1.65GB
Adding that up is just under 3.8GB total so I should have about 8.9GB free, but it only reports 700MB.
Something is wrong with the free space calculation. Any help here? This wasn't a problem on the previous CM12.
BTW I did a clean install (full system wipe) before installing the CM12.1.
Any help is appreciated. I am at my wit's end on this issue.
Thanks Tschumi.
My question is more on how to pull the sources and build the 5.1 myself.
mr72 said:
I am running the 04/08 and it is working fine except one major problem that is the bane of Android everywhere since kitkat...
It keeps telling me I have insufficient storage space to do anything, update apps or install new apps, and there are hardly any apps on the device.
When I go to Settings -> Storage it says total space 12.67GB but "Available" is only 700MB, which doesn't add up and doesn't agree with the graph.
[…] Adding that up is just under 3.8GB total so I should have about 8.9GB free, but it only reports 700MB.
Something is wrong with the free space calculation. Any help here? This wasn't a problem on the previous CM12.
BTW I did a clean install (full system wipe) before installing the CM12.1.
Any help is appreciated. I am at my wit's end on this issue.
Click to expand...
Click to collapse
That must be… frustrating. So, you're saying this happened on CM11, then CM12.0 was fine, and now the bug is back on CM12.1? There are a couple of unusual/puzzling issues that people report, including the reboot-instead-of-poweroff bug. Never having experienced these, it's hard to figure out the cause, but I'll keep it in mind.
andtron said:
My question is more on how to pull the sources and build the 5.1 myself.
Click to expand...
Click to collapse
These days, it's very easy; you simply upgrade your LP5.0/CM12.0 sources with: repo init -u git://github.com/CyanogenMod/android.git -b cm-12.1
mr72 said:
I am running the 04/08 and it is working fine except one major problem that is the bane of Android everywhere since kitkat...
It keeps telling me I have insufficient storage space to do anything, update apps or install new apps, and there are hardly any apps on the device.
BTW I did a clean install (full system wipe) before installing the CM12.1.
Any help is appreciated. I am at my wit's end on this issue.
Click to expand...
Click to collapse
I think it has something to do with updating from stock to cm. Go to 'terminal emulator' app, type 'su' then 'df'. Let us know what is the output.
Also, backup all your data. Do you mind clean install again? Which recovery are you using? If you convert your data partition to F2FS I'm sure it'll fix it. Not because F2FS will fix it, but because converting it to F2FS will format the entire /data partition (including the virtual /sdcard). There might be old files downloaded when you used stock rom.
extrem0 said:
...If you convert your data partition to F2FS...
Click to expand...
Click to collapse
Quick question, how does one go about converting the partition to f2fs on the ovation? I've done a couple searches but can't find anything definitive such as which recovery I should have installed and if it is a zip that I would need to flash.
Thanks!
J-Pod said:
Quick question, how does one go about converting the partition to f2fs on the ovation? I've done a couple searches but can't find anything definitive such as which recovery I should have installed and if it is a zip that I would need to flash.
Thanks!
Click to expand...
Click to collapse
I did it using twrp recovery 2.8.6.0 built by amaces. There's an option that allows you to convert some partitions to f2fs. Remember, it will erase all your files in your nook. Do a backup of your files before converting to f2fs.
J-Pod said:
Quick question, how does one go about converting the partition to f2fs on the ovation? I've done a couple searches but can't find anything definitive such as which recovery I should have installed and if it is a zip that I would need to flash.
Thanks!
Click to expand...
Click to collapse
Using @amaces TWRP, go to Wipe, check the data box, select "advanced wipe then it's something like " repair file system". I'm sure you can figure it from that.