This recovery & patch allow installation of AOSP based ROM (CyanogenMod/OpenDesire/DeFrost) with partition sizes set to match that of Nexus One.
No more need for Apps2SD hacks!
It is very easy to install, however requires security to be disabled on your device (S-OFF in FASTBOOT).
Steps to install:
1. Download AOSP Based ROM to your SD card.
2. Download nexified-boot-patch-v1.0.0-bravo.zip to your SD card.
3. Reboot in Fastboot
4. Fastboot flash recovery nexified-recovery-clockwork-2.5.0.7-bravo.img
5. Reboot into recovery
6. Wipe data/factory reset
7. Flash ROM
8. Flash nexified-boot-patch-v1.0.0-bravo.zip
9. Reboot & Enjoy
Both the recovery, and the boot patch, have kernel cmdline:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.
The patch also removes "dalvik.vm.dexopt-data-only=1" from build.prop which places dalvik-cache on the cache partition as per AOSP.
I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.
My current partitions are:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Warnings:
Do not flash radio via recovery, only via fastboot. You should not be flashing radio via recovery anyway, it is strongly discouraged.
Credits:
AlphaRev - for bringing S-OFF to HTC Desire
Firerat - for the original mtd patch which I learned a lot from.
Lbcoder - for the initial information on how to modify partitions via kernel commands, i learned a lot from him as well.
Skraw ( CM forums ) - for getting lbcoder interested
Koush - for AnyKernel
Cyanogen & Co - for giving us all such great ROMs to play with
Amon_RA and Koush - for giving us something to patch
Kali- for porting CM6 to Desire thanks a bunch
I am doing this to try and spark further interest in this, in the hopes that other developers may improve on it, as the default partition sizes on the desire are crap.
How to uninstall / set partitions back to normal:
Boot into Fastboot
Fastboot flash standard/unmodified clockwork recovery or amon_ra
Reboot into recovery
Wipe data/factory reset
Flash ROM & Reboot
Downloads:
nexified-recovery-clockwork-2.5.0.7-bravo.img
nexified-boot-patch-v1.0.0-bravo.zip
Should this work with OpenDesire 0.34,too?
And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?
nice work.....
back in a flash
xtcislove said:
Should this work with OpenDesire 0.34,too?
And do we need the recovery al the time? Or can we use an other one like PsfMod after flashing the update?
Click to expand...
Click to collapse
No, the partition sizes are passed as kernel parameters, so recovery & ROM must be patched to use the same parameters.
so what are the advantages of this?
i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?
thanks for your hard works
Well done!
Very brave of you to almost brick your device (twice?) and continue development nonetheless.
I don't need it, but many others will love this. Thanks a lot.
If I follow your procedure am I stuck on nightly-132, or once i've got the resized partitions can I continue to flash CM6 nighlites?
These kernel parameters:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Where exactly are they set? I assume it's somewhere inside the boot.img?
I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps?
great works on my Desire..Thanks daedelus82 and other persons...I see 197 Mb on available space..
Thank you very much daedelus, i was waiting for this since the day s-off was released
Could you upload a version of the stable CM6 too?
Great Work! I hope this becomes the norm, we need that /system space for apps.
Excellent! At last! Thank you very much!
aleksei87 said:
Thank you very much daedelus, i was waiting for this since the day s-off was released
Could you upload a version of the stable CM6 too?
Click to expand...
Click to collapse
Hello, yes I will patch CM6.0.2 stable as well. I have to go to work now but within a few hours. I will also try to answer other questions but have to run right now.
Please note, this WILL break 'fastboot flash' functionality.
But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
marinierb said:
These kernel parameters:
Code:
mtdparts=msm_nand:[email protected](misc),[email protected](recovery),[email protected](boot),[email protected](system),[email protected](cache),[email protected](userdata)
Where exactly are they set? I assume it's somewhere inside the boot.img?
Click to expand...
Click to collapse
Yes, boot.img for ROM, and recovery.img for recovery
djind said:
I am on CM602 with kernel update1 and psfmod unrevoked recovery. No chance of me getting the extra space for apps?
Click to expand...
Click to collapse
Sorry I have patched CM and Clockwork Recovery only.
ieftm said:
Please note, this WILL break 'fastboot flash' functionality.
But it's a nice intermediate way of doing things. There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
Click to expand...
Click to collapse
Only breaks fastboot flashing of system and/or userdata, as fastboot will flash it to different blocks than the kernel is using. All other partition locations/blocks are unmodified meaning flashing of recovery, boot, and radio will be fine.. Also if you flash userdata, system, and boot all at same time it will also work, as overwriting boot will remove the kernel cmdline.
Would love to see a HBOOT implementation of this that does not require kernel modifications.
cgrec92 said:
so what are the advantages of this?
i see data is 197mb, does this mean that there is about 70mb+ storage space for apps?
thanks for your hard works
Click to expand...
Click to collapse
Advantage is more space on DATA, whilst keeping phone as close to AOSP as possible. Nexus One is current developer phone, and it's partition sizes are 145MB for system, 197MB for data, 95MB for cache, same as what this patch achieves. Meaning your phone is as close to Android/AOSP as Google intended.
I have done this to my phone and am personally very happy with it, I have restored all my apps and still have 70MB free in data, and dalvik-cache resides in cache.
My current partitions are:
Code:
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 208092 0 208092 0% /dev
tmpfs 208092 0 208092 0% /mnt/asec
/dev/block/mtdblock3 148480 118376 30104 80% /system
/dev/block/mtdblock5 202368 130124 72244 64% /data
/dev/block/mtdblock4 97280 46536 50744 48% /cache
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/sdcard
/dev/block/vold/179:1
7431564 5484240 1947324 74% /mnt/secure/asec
/dev/block/dm-0 3124 1504 1620 48% /mnt/asec/com.google.android.stardroid-1
Thanks very much for this, I'll be flashing it shortly. I have two questions if you don't mind!
Why must radio be flashed using a different method?
Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.
Maybe something like 96 System, 64 Cache, and the rest for data? (just for the love of god make it a multiple of 16 or my OCD will break the universe)
Updated OP. Added CM6 stable v6.0.2
nawoa said:
Why must radio be flashed using a different method?
Is there a way for me to further shrink the system partition? From what I can see, I should be able to do with 100mb for system and still have 30+ mb free. I use a modified version of CM + GApps and I remove a ton of stuff.
Maybe something like 96 System, 64 Cache, and the rest for data?
Click to expand...
Click to collapse
You can patch system and cache to whatever sizes you want, it really depends on your ROM. If you have less than 96MB in your system partition then partitioning it to 96MB should be fine. I normally like to leave a few MB spare for good measure. See below for description on flashing radio from a re-partitioned recovery.
ezterry said:
Same steps as the rom, just ensure you *never* flash *any* spl or radio for any reason from a re-partitioned recovery with a cache partition that does not match the spl's actual cache start location. Or you will be in the market for a jtag adapter to fix your brick.
Click to expand...
Click to collapse
ieftm said:
There might be a HBOOT release with different partition tables (for example, one for Sense, one for AOSP roms).
That is currently under development.
Click to expand...
Click to collapse
Thx !! we are waiting for that ;-)
Hmm... Because of the radio flashing issue and because I use DT-A2SD anyway, I think I'm going to hold off on using this until there's the HBOOT solution you guys are talking about.
Crossing my fingers that all I need to do is install standard clockwork recovery then go to a standard CM build.
Related
This thread is reserve for nightly build of CyanogenMod Rom for HTC Desire
CyanogenMod is a free, community built distribution of Android 2.3 (Gingerbread) which greatly extends the capabilities of your phone.
Code:
** These CyanogenMod builds are highly experimental and unsupported.
**
** Please refrain from submitting bug reports for any issues
** you may encounter while running one of these builds.
**
** Submitting bug reports on nightly builds is the leading
** cause of male impotence.
What are Nightly build? Auto compiled build 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).
Warning : Not for new user, flash this build only if you know what you are doing !!!
INSTRUCTIONS:
- First time flashing CM 7 to your Desire (or coming from another ROM)?
1. Root your device and install Clockwork Recovery.
2. Do a Nandroid backup!
3. WIPE (wipe data/factory reset + wipe cache partition)
4. Install the ROM
5. Optionally install the Google Addon
- Upgrading from earlier CM7?
1. Do a Nandroid Backup!
2. Install the ROM (your Google apps will be backed up automatically)
There are no Google Apps bundled with CM ROMs, because Google asked Cyanogen to remove copyrighted apps, after flashing rom don't forget to flash Google Addon package if you want it.
Latest version: http://download.cyanogenmod.com/?device=bravo
before flash is recommended to check the md5sum
CyanogenMod Enhancement:
ChangeLog / Twitter
Device specific ChangeLog by igor.tonky
Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.
Thank you to EVERYONE involved in helping with testing, coding, debugging and documenting! Enjoy!
cm7 is in a development stage and for the first installation i recommend to:
1) install rom
2) reboot, skip setup wizard and setup your access point
3) reboot recovery and install gapps
4) start and follow setup wizard, when requested select desired gapps to be downloaded from market
Battery drain issue:
Set wifi sleep policy to never
settings -> wireless & networks -> wifi settings
press menu -> advanced and set wifi sleep policy to Never
press menu -> save
RIL issue:
Switching RIL is cause of know network problem:
* Unable to make a network scan
* Data connection die on asleep (only for some carrier)
CM7 HBOOT by Alpharev | xda thread
Change partition table size 130/5/302 (system/cache/size)
Require nightly #18 or newer
Upgrade instruction:
1) Nandroid backup in recovery.
2) Verify the MD5SUM of the file you downloaded against the one in the table.
3) Flash HBOOT with your phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl-cm7.img'
4) 'fastboot reboot-bootloader'
5) 'fastboot erase cache'
6) Boot recovery, wipe everything, advanced restore system & data, install CM7 again (same version or a newer one).
Legacy App2SD Addon:
CyanogenMod do not officially support a2sd, i'm working on it because desire (not only) desperatly need it (cutted down Firerat script)
Bootloop free: bind mount do not cause bootloop
Zero Maintenance: no maintenance required after ROM update
Other a2sd can be used, this is just the easiest way: use recovery to partition your SD then install cm7_legacy_a2sd_rX-signed.zip
By default only App will be moved on SD
Optionally Cache and Data can be moved to SD, but is not recommended (guide)
Require GB Nightly #7 or newer
It's recommended to set the install location to "Internal" under Settings -> CyanogenMod -> Application Settings -> Install location
Before install check if /sd-ext is mounted, "quick system info" under A2SD Storage should report Total and Free space, if it report "information not available" format sd-ext from recovery.
r3: improved installation process (i hope)
r2: added data2sd and cache2sd as options
r1: first release
General App2SD Q&A:
Q: A2SD is recommended?
A: Internal storage perform better than SD, install A2SD only when low disk space warning happen
Q: How to check if is working?
A: run:
adb shell
df -h | grep /dev/block/mmcblk0p2
output should be
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /sd-ext
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app
/dev/block/mmcblk0p2 751.9M 146.9M 566.8M 21% /data/app-private
Q: I have installed a2sd addon but now i get low space warning again, why?
A: by default a2sd addon move only app, this is fine for most user but some user with more application have to move also cache and/or data.
Cache2SD can be enabled with
adb shell
/sd-ext/userinit.d/10cache2sdext-binds enable
Data2SD
adb shell
/sd-ext/userinit.d/11data2sdext-binds enable
reboot when prompted
HBOOT
All alpharev's hboot are compatible except the oxygen version
CM7 version is recommended ~270MB for app (stock 110MB, N1 195MB)
HowTo
Perform automatic backups of files in /system/ while (re-)flashing CyanogenMod
useful link
http://goo-inside.me/google-apps/
md5:
18ef81c567398a93183aff65a41a1565 cm7_legacy_a2sd_r3-signed.zip
murdock's semi official nightly replacement drugs
update 31.05.2011: buildbot is down due to hdd crash. might take a few more days to return - so here is an interims nightly for you:
mirror1: cm_bravo_full_teamdesire-20110601-1925.zip size: 84M (88037737 bytes)
mirror2: cm_bravo_full_teamdesire-20110601-1925.zip md5sum: 38591bab5df5d8f57e714f7888567bdb
Kali- said:
CyanogenMod is a free, community built distribution of Android 2.3 (Froyo) which greatly extends the capabilities of your phone.
Click to expand...
Click to collapse
You mean Gingerbread not Froyo - pedantic I know!
Great work though by the way - excellent ROM!
sykomaniac said:
You mean Gingerbread not Froyo - pedantic I know!
Great wrok though by the way excellent ROM!
Click to expand...
Click to collapse
C&P fail
10 char
andQlimax said:
I was waiting for this thread lol
Any Radio / RIL recommended?
Click to expand...
Click to collapse
no
any 5.x should work
Nice looking forward to follow this thread
Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.
Niiiceee, great work team !
rover.prince said:
Well I am not superseeding the Great Kali's saying about A2sd but Dark Tremors App2SD works ok with CM7. Just installed it onto CM7. Working great on my CM7.
Click to expand...
Click to collapse
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report
before someone ask
Oxygen HBOOT do not work, system is too small (cm7 require other 20mb)
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested
not sure if this is a market issue or titanium backup but my apps don't appear as installed on the market after a restore. btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.
Kali- said:
we are working with alpharev for a CM7 specific partition layout but there are some thing concerning the /cache shrinking that requires to be developed and tested
Click to expand...
Click to collapse
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?
MrDevil said:
btw is the sd-ext issue fixed in cwm? read from the cwm thread of some people having issues about sd-ext not being backed up.
Click to expand...
Click to collapse
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review
Kali- said:
Never tested but for what i know DT need to be flash after any update and is not bootloop free
Thank's for report
Click to expand...
Click to collapse
I am using it personally, I have done the installation what I did.
1. Installed CM7.
2. Installed G.Apps
3. Started Phone, Installed All Apps
4. Restored Some Apps via Titanium Backup ==>Ended Up via Low Storage
5. Installed DT
6. Executed CacheSD
7. Phone Rebooted (Took Some Time to Boot)
Voilla I am happy.
cTrox said:
Great, looking forward to it! I'm using the N1 Layout atm and it my cache is under 50MB
Code:
Filesystem Size Used Available Use% Mounted on
/dev/block/mtdblock4 95.0M 48.4M 46.6M 51% /cache
I guess a bit above 50 would be good?
btw, what would happen if the cache is full? Would it just get really slow?
Click to expand...
Click to collapse
we are working for something like 5MB or less
the problem is about download and market.
for sure tmp file are stored on cache and if file size is bigger then free space download fail, not sure if there are other issue
rover.prince said:
Voilla I am happy.
Click to expand...
Click to collapse
this is the most important thing
Kali- said:
this is the most important thing
Click to expand...
Click to collapse
Kali I Love U and CM Team. Great Work with all thumbs UP.
Kali- said:
just tested and the one i posted do not backup/restore sd-ext
i will post a working one later, i just noticed that my patch is still under review
Click to expand...
Click to collapse
thanks for the info. looking forward to a rc.
will try to reflash later and restore apps with mybackup and see if it's a market or titanium issue.
How long will it take before CM7 is released in stable mod?
I'm getting tired of using Oxygen 2.0 and its bugs
If you want a lean mean Gingerbread rom for your new radio sapphire here it is!
Mixed results on 6.35.10.18 radio, radio 6.35.16.19 recomended. Upgrade your radio here
The source was originally from aosp and ezterry, it's quite deverged from that now.
The kernel is my 2.6.34 kernel from my other thread with all new updated usb for Gingerbread use. (turns out my kernel was fine,it was the roms that needed modifying)
As battery life goes it's ok as far as I can tell, unplugged last night at 12 am, used phone till 3 am, sat on table till 7 am, used it at work all day, when I got home at 6 it was at 58% still.
Not working:
HD youtube (has never worked for me)
Working:
cam
camcorder
usb mount
adb
usb tether (native* (wireless _settings)) < lol. been looking at code to long
charging
3d gallery
gps
wifi
cpu/memory info in about phone
usb debugging notify disable (toggle in development)
toggle for any app to sd (in applications/development)
openvpn added to vpn network types
long press back application kill (toggle in applications/development)
key backlights
Mms with full settings options (git://github.com/CyanogenMod/android_packages_apps_Mms.git)
voice search (update on market)
sync works (twitter, facebook, gmail,ect...)
updated apn list
openvpn
incoming and in-call touch UI
H for hspa enabled
CM Phone.apk
Androidterm (from cm)
Tmobile theme chooser (git://github.com/tmobile/themes-platform-vendor-tmobile-apps-ThemeChooser.git)
Notification powerwidget (thanks to ezterry)
Built in overclocking
Bluetooth pan
I shouldn't have to say wipe, yes do it, wipe all. (If coming from another rom)
If coming from any other rom I would suggest booting to the bootloader(hold back while pressing power on) and using fastboot to 'fastboot erase system -w'
Install instructions
Flash from recovery.
flash the gapps if you want them
I hope this works as good for you as it does for me!
I'm looking into a few things mentioned in this thread and adding new functionality, what would you guys like to see?
Older roms at end of post in Archive.
I'm not making a separate rom for mtd anymore, I made both DietGB and CM7 compatable with Firerats mtd boot flash and market works.
You must use fastboot and erase system "fastboot erase system -w" if you are new to DietGB or have any install or rebooting problems before posting here If you use the new recovery I compiled from cm7 clockworkmod you can just format in recovery.
I have been using this release for many weeks now, testing and modifing code, recompiling, and I think I finally have the most stable 6355 kernel and rom available, I also along the way added a few things.
New Sept 21
No wipe update to fix video recording force close
DietGB-v09.21.2011-6355sapphire
New Sept 16
Now 2.3.5 (has been for a bit now but I didn't release anything)
Many kernel updates (hope camera is good for everyone now)
added built in overclocking (in diet gingerbread settings)
bluetooth pan
new recovery
gapps backup if no wipe
3 days now, no reboots, no fc's
files are at Androidspin now, no more multiupload
DietGB-v09.16.2011-6355sapphire
July 19
Latest updates
added Notification PowerWidget
new recovery
Diet-GB-sapphire6355-07192011
carz-clockworkmod-v4.0.0.5-recovery
gapps_mdpi_gb_20110613_S
wipe if you have any issues, I didn't this time
June 19
Latest Aosp updates, new kernel, faster than ever in my testing and everything works, I would suggest a clean install.
Diet-GB-6355-v06-19-2011-signed.zip
Here is a new recovery v4.0.0.2 clockworkmod Carz-Clockworkmod-4.0.0.2-recovery.zip
reflash gapps after gapps_mdpi_gb_20110307_S.zip
New may 09
OK, everything is updated now and everything is working again, (cam and wifi) not that you knew it broke, so far after 2 days it seems more responsive and faster, I use set cpu @614 and 245
I did not wipe and it worked fine but after I did a wipe to test and it seemed faster so I don't know, you decide, I'm looking into adding compcache and swap also.
Diet-GB-6355-v05-09-2011-1-signed (usb mount fixed)(lowmemkiller fixed)
Here is a new kernel to try out, it's exactly the same as the stock kernel but has the 10mb ramhack. 10mb ramhack
New may 02
Updated to 2.3.4_r1
new Phone.apk
new Mms.apk
new Browser.apk
Diet-GB-6355-v05-01-2011
Also I have made a new recovery for our 6.35 radio sapphire phones based on Clockworkmod 3.0.2.8 get it here
New april 27
Updated kernel, no wipe from v04-23-2011, added back cm7 Mms, working on Phone.apk update
Here is link to just the kernel and modules package to flash on any version GB-v04-27-2011-signed.zip
Rom Diet-GB-6355-v04-27-2011
If you use a custom MTD flash this after DGB-boot-v1.5.8-custom-MTD_S.zip
April 23
Diet-GB-6355-04-23-2011
Updated kernel
Updated Rom 2.3.3
You need to wipe even from my rom, sorry
Diet-GB-6355-04232011
for Custom MTD flash this, DGB-boot-v1.5.8-custom-MTD_S.zip after flashing rom
v0.22.03.2011
volume/vib/silent option added
Failing at adding galaxy s style power widget, still working on it.
No wipe if coming from my roms, re install gapps
Diet Gingerbread v0.22.03.2011
Diet Gingerbread v0.22.03.2011-MTD
v0.20.03.2011
Tmobile theme chooser (tmo) (Androidian theme included)
AndroidTerm (cm)
H enabled
Diet Gingerbread v0.20.03.2011 non MTD
Diet Gingerbread v0.20.03.2011-MTD
No wipe if coming from my roms, re-install gapps (link below)
v0.16.03.2011
Updated Phone.apk
in-call and incoming call touch UI
kernel below included 528/245 max 710
No wipe needed, if coming from roms below, reflash gapps
Diet gingerbread v0.16.03.2011 non MTD
Diet gingerbread v0.16.03.2011-MTD
v0.13.03.2011
This is almost 2.3.3 I had some issues with cam with a few updates.
Facebook sync is fixed I believe
Soundrecorder with launcher shortcut added (I changed default to amr from 3gpp recording, I can post the 3gpp version if you want it)
Diet Gingerbread v0.13.03.2011 not for custom MTD
Diet Gingerbread v0.13.03.2011 w/MTD
I wiped this time, you should be able to just upgrade though, reinstall gapps
Google apps
Google apps( minimal package, get the rest from the market)
Full google apps (go to market and see if there are updates)
New kernel
I see some of you want a 710 kernel, well I did it for you, I added min and max at boot so it boots at 528/245 default, use setcpu to set to whatever you like, you can also select several different governors.
Flash over any of the roms here. Remember it's 528 default, so if you set to high and you reboot or lockup it will boot at 528 next time, once you find a stable frequency check set at boot in setcpu.
710 Diet Gingerbread kernel
Stand alone kernels (can be flashed back and forth without wipe)
528mhz kernel (if you have force closing try this please) also best battery life!
576mhz kernel (stock in rom)
614mhz kernel
Alternate gps.config files
Euro GPS config (flash this if you are having GPS issues in Europe)
Asia GPS config (flash this if you are having GPS issues in Asia)
Mixed results on 6.35.10.18 radio, radio 6.35.16.19 recomended. Upgrade your radio here
Custom MTD:
first before anything run this either in term or using adb (only "df" in term)
Code:
adb shell df
you should get something like this
Code:
[email protected]:~/android/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98100 32 98068 0% /dev
tmpfs 98100 0 98100 0% /mnt/asec
tmpfs 98100 0 98100 0% /mnt/obb
/dev/block/mtdblock3 174080 106820 67260 61% /system
/dev/block/mtdblock5 169728 114684 55044 68% /data
/dev/block/mtdblock4 133120 2048 131072 2% /cache
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 2816 2816 0 100% /system/fonts
/dev/block/mmcblk0p2 468331 8226 435120 2% /sd-ext
/dev/block/vold/179:1
7216340 5608896 1607444 78% /mnt/sdcard
/dev/block/vold/179:1
7216340 5608896 1607444 78% /mnt/secure/asec
K0HNKCLLUN"]
look at "/dev/block/mtdblock3 174080 106820 67260 61% /system" and "/dev/block/mtdblock4 133120 2048 131072 2% /cache"
I used "mtd 108 3" in my mtdpartmap.txt
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
These instructions are from firerats thread (recommended reading material) modified a little for my use.
Install Instructions:
Download DGB-recovery-v1.5.8-CustomMTD_S.zip
Download DGB-boot-v1.5.8-CustomMTD_S.zip
Create mtdpartmap.txt and put on /sdcard/ see configuration above or in Firerats thread < recomended
reboot to recovery
nandbackup
wipe cache + data
flash DGB-recovery-v1.5.8-CustomMTD_S.zip
reboot to recovery ( reboot and hold Home )
Flash Diet_GB_carz_v0.090-signed.zip
Flash gapps if you want them
Flash DGB-boot-v1.5.8-CustomMTD_S.zip
reboot
Click to expand...
Click to collapse
The above is what I did and I'm running fine right now,
Code:
[email protected]:~/android/system$ adb shell df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 98100 32 98068 0% /dev
tmpfs 98100 0 98100 0% /mnt/asec
tmpfs 98100 0 98100 0% /mnt/obb
/dev/block/mtdblock3 110592 106824 3768 97% /system
/dev/block/mtdblock5 363264 113212 250052 31% /data
/dev/block/loop0 1024 1024 0 100% /system/lib/modules
/dev/block/loop1 2816 2816 0 100% /system/fonts
/dev/block/mmcblk0p2 468331 8227 435119 2% /sd-ext
/dev/block/mmcblk0p2 468331 8227 435119 2% /cache
/dev/block/mtdblock4 3072 788 2284 26% /dev/cache
/dev/block/vold/179:1
7216340 5665644 1550696 79% /mnt/sdcard
/dev/block/vold/179:1
7216340 5665644 1550696 79% /mnt/secure/asec
55 > 250 on data
Thanks anyone who put effort into making Gingerbread for our old phone possible.
Archive:
v0.090
removed boot animation, push one to /system/media/ if you want one
now has custom MTD support (explained at bottom, scroll down) Thank you Firerat and Ibcoder
Dietgingerbread v0.090
coming from v0.081
I only wiped cache and data as explained below
If this is a first install wipe everything
v0.081
DietGingerbread v0.081
no wipe if coming from v0.03 up re-flash gapps
v0.080
no wipe if coming from v0.03 up re-flash gapps
DietGingerbread v0.080
Flash this to fix ext mount (also works on v0.070/1)
v0.071
no wipe if coming from v0.03 up re-flash gapps
DietGingerbread v0.071
v0.06
No wipe if coming from v0.03 up, flash gapps again.
DietGingerbread v0.06
v0.05
No wipe needed if you flash the full gapps after rom
DietGingerbread v0.05
v0.03
DietGingerbread v0.03
sorry you may need to wipe, I didn't but had to re install gapps after and everything else updated from the market on it's own.
v0.01
Gingerbread for sapphire 6355 (still v0.01 kernel, flash prefered kernel)
Wow, 6.35 radio Gingerbread ROM with working Cam actually happened. I thought that's impossible thing to do. Thanks OP for all hard work you put in this. Will test in next couple of days and report back. HTC Magic is still alive and kicking almost 2 years after being release.
Nice work carz !!!
You need to put a donate link.
I think you're the last dev dedicated to the 32a 6.35.
giant_rider said:
Nice work carz !!!
You need to put a donate link.
I think you're the last dev dedicated to the 32a 6.35.
Click to expand...
Click to collapse
I do have one, not sure it works, haha
If you post it, I will add it to my threads. I updated GB Cronos with your latest kernel. Hopefully I will have bug free USB.
carz, are you missing AudioPara4.csv?
giant_rider said:
carz, are you missing AudioPara4.csv?
Click to expand...
Click to collapse
not that I know of, it flashes when detecting 6.35 radio
its in system/etc/.audio it unzips as needed when installing the rom
I just noticed it gets extracted during execution of the any kernel script from ezterry.
I could have got rid of all that but its much easier to repo sync this way
great effort carz! 2 thumbs up for you. hehe...
anyway, does voice search worked with this rom?
one more thing, does button backlight glows in this rom? i mean, when we click/screen on because in Giant's cronos version doesnt worked (correct me if im wrong, sorry Giant im not to blame you, but i love to have it glows, if possible hee....)
anyway great job to both carz and giantrider...
I'm trying to see if I can pull some of your stuff out and flash over GB Cronos latest build.
Not sure why. At this point I should sleep. If it works I will end up with a faster GB Cronos, working USB (thx to you), but Youtube and Gmail will not work.
albert emmer said:
great effort carz! 2 thumbs up for you. hehe...
anyway, does voice search worked with this rom?
one more thing, does button backlight glows in this rom? i mean, when we click/screen on because in Giant's cronos version doesnt worked (correct me if im wrong, sorry Giant im not to blame you, but i love to have it glows, if possible hee....)
anyway great job to both carz and giantrider...
Click to expand...
Click to collapse
Sure they do
Just tested voice search. it worked fine.
No offense taken Albert....carz is actually compiling himself....I'm not
But thanks for the comment, I did not even notice the back light issue.
carz....maybe I should pack it in and we focus on one solid 32a 6.35 rom.....yours is currently the least buggy I think....if people confirm that then it only makes sense....
giant_rider said:
carz....maybe I should pack it in and we focus on one solid 32a 6.35 rom.....yours is currently the least buggy I think....if people confirm that then it only makes sense....
Click to expand...
Click to collapse
Hey I'm game, when you need something let me know.
Anyone flash it yet?
carz12 said:
Hey I'm game, when you need something let me know.
Click to expand...
Click to collapse
LOL, I meant I should retire my ports and focus on your build not the other way around
I guess we'll see what makes sense....
flashing now
just had to nandroid, change radio and spl, and hey-ho were going for a boot
F2FS for ACE
AOSP only!
S-ON USERS SEE ADDITIONAL INSTRUCTIONS BELOW
Should work on all current CM12 or most any of our LP-based AOSP ROMs around here that use a current CM based kernel/trees
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 link the current 2.8.1.1 TWRP built with the added F2FS support commits. When wiping a partition you will have the option to reformat in F2FS now as well.
Fstab conversion zip Fstab is the file used by the kernel to determine how to mount all partitions. CM default is all EXT4. To utilize F2FS we need to modify your fstab. This installer is 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 according to your current partitions 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 NOW HOSTED @ CODEFI.RE
http://downloads.codefi.re/jrior001/Ace
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 TWRP recovery img if you are not already on it.
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 "Repair or change filesystem". Convert to F2FS. Repeat for cache.
6. Flash the 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 ( manually, do not let OTA update flash on its own, you will not be given the chance to flash fstab zip and you WILL BOOTLOOP. Should this happen return to recovery and perform step 2)
2. Flash fstab conversion zip.
3. Reboot and profit.
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.
S-ON USERS
Code:
If someone has S-ON device, you still can use it like this:
After flashing ROM, reboot to bootloader and fastboot flash boot.IMG provided in ROM.zip as normal. This is required to get any new kernel updates. Return to recovery and make your desired f2fs changes and flash the f2fs script.
After you flashed this f2fs script, the modified boot image will be located at: /tmp/newboot.img
Now we need to download it by using adb in recovery: adb pull /tmp/newboot.img boot.img
After that, you can flash boot.img via fastboot and reboot as usual. (fastboot flash boot boot.img)
Code:
CHANGELOG
V1.0 - Initial release
V2 - switch to by-name fstab entries to go with cm12 nightlies after 1/9/15
V2.1 - typo fix
V3 - corrects fstab name after file name change introduced in 1/14 nightlies and beyond
Source:
Kernel: https://github.com/OpenDesireProject/android_kernel_htc_msm7x30/tree/cm-12.0
Device tree: https://github.com/OpenDesireProject/android_device_htc_ace
Fstab scripts: https://github.com/jrior001/f2fs_fstab_convert_script
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 a few other devs in the grouper forum whose scripts I adapted for my own work.
Contributors
jrior001 @Mustaavalkosta, @paulb-nl and any others that have helped keep msm7x30 alive
Kernel Special Features: f2fs support
Version Information
Status: Beta
Current Beta Version: 1.0
Beta Release Date: 2015-01-06
Created 2015-01-06
Last Updated 2015-01-06
Important to note, all issues related to f2fs need to stay here and out of the cm12 thread. This is a experimental tweak and mustaa has enough to deal with, without unsupported drama. Please be respectful of this. Thanks and enjoy!
Cant find Convert to F2FS in recovery
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
xdagee said:
hey thanks for your great effort.
I decided to do a test alongside today's [cm-12-20150107-UNOFFICIAL-ace] nightly but, unfortunately for me, I couldn't identify convert to f2fs after under change file system on the recovery [openrecovery-TWRP-ace-2.8.1.1-unofficial].
What will be the issue....
A few of you should test and let's see what happens.
Maybe am not doing something right.
am on TWRP v2.8.1.1 and S-FF with bootloader unlocked
Thanks :good:
Click to expand...
Click to collapse
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Mustaavalkosta said:
You need to go to Advanced Wipe and select data or cache partition and choose Repair or Change File System > Change File System > F2FS. This will format the partition so make sure you don't lose anything important.
Click to expand...
Click to collapse
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
xdagee said:
Thanks got it to work . I haven't done any major testing though but i believe i will do, will be back with my takes.
Click to expand...
Click to collapse
Very good, interested what your experience is. I ran a bunch of tests when I got this working on my One XL(Evita) and found f2fs to be slightly better for heavy read/write action things like installing apps(especially that initial Google restore of apps on first boot) and more less the same or slightly better in daily use.
First of all- every next restart is rom more responsive. (it has it's own limitations, of course ) I'm not testing very much, but using as usually. Second- Gallery app doesn't show pictures until i enabled root access.. this is new problem, ringtone was unknown too, 0103 release was fine with this. So..don't know where is problem, but i see that this is good step. Thank you!!!
edit: @Mustaavalkosta , @jrior001 : this is not very good that your threads are separated. Because I see new problems that i never seen before, so I think this is problem of F2FS. In my previous installed nightly (it was one of those "smaller", so no 0103 as I wrote before, but maybe 0101?) was calculator OK, media player too, gallery too and ringtones too. Now I have problem with all - direct after restart i see pictures in gallery but after (what?) again i can't see it. Ringtone - i set ringtone and it was ok, but later it changes to "unknown" - so no ringtone. Audio player has similar problem.
...on other side - it is really good. (Musta's ROMS and this too). Thanks for your work!
Updated OP with S-ON flashing instructions courtesy of @kib0rg
..bad evening... after trying to install app- it ends in reset, system no more started..
I've just uploaded a new v2 script to go with tomorrow's nightly. There are significant changes to the fstab that warranted this new version.
can i use this only in clean new installation? I have installed 0111 version.Can i use it with dirty flash of new nightly?
I don't know what i'm doing wrong. After flashing F2FS v2 phone stuck on black screen - no cm bootscreen appears..
Edit:
after flashing v1 phone normally booting. So there is problem with v2 or after (dirty) flashing new rom I use v2 instead of v1?
Phone stacked after flashing nightly.
As much testing hasn't be done on this; which we know the reason. being that if we are able to get a much more daily driver like ROM then more people will try testing f2fs. But for yesterday as I try to update my recovery, i found out that ace_f2fs_fstab_script_cm12_v2.zip has been uploaded. I downloaded flashed alongside 20150110's nightly. After flashing, phone get stacked just after boot screen appears.
@xdagee - what CM12 nightly do you use? I think last two has problem with dialer/phone. Do you use F2FS script v1?
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
jrior001 said:
For clarity, v1 should be used on night lies prior to 1/10, v2 should be used for 1/10 and beyond. 1/10 and beyond will also require the latest twrp update as well.
There was a major change to the fstab in mustaa's CM repos file that determines what partitions to mount that required everything be updated to match.
Click to expand...
Click to collapse
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
danvo01 said:
problem is that v2 isn't working. I have same problem as Xdagee. Of course new twrp.
Click to expand...
Click to collapse
Hmm...I tested before I uploaded but I'll check it out tonight.
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
working fine, thanks
jrior001 said:
Sorrys folks, there was a typo in one of the f2fs entries that was killing it, all fixed up now. I've uploaded a v2.1 zip that's corrected.
Click to expand...
Click to collapse
thats okay, we've got your back
CyanogenMod 13 by ivanichFeatures:
3.4 kernel with latest patches
USB-OTG
Stable enough to be daily driver
Fully working camera
In kernel mp-decision
Bugs:
Major:
None
Minor:
All CyanogenMod upstream bugs
Downloads:
CM13
GAPPS
Sources:
ivanich's GitHub
Changelog:
Kernel Changelog
ROM Changelog
TWRP Recovery:
Download
XDA:DevDB Information
CyanogenMod13 by ivanich, ROM for the HTC Sensation
Contributors
ivanich, shantur
Source Code: https://github.com/ivanich?tab=repositories
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.4.x
ROM Firmware Required: HBOOT 1.27/1.29
Based On: CyanogenMod
Version Information
Status: Stable
Created 2015-10-29
Last Updated 2016-09-07
FAQ
Q: I got Error 7 in recovery while flashing ROM
A: Reflash ROM one more time
Q: I flashed Opengapps and now my keyboard crashing
A: Read this and especially "Skip Google's Swype Library Setting".
If you are not smart enough to understand official Opengaps FAQ you have 2 options:
1. Create gapps-config.txt with skipswypelibs keyword inside it, and place it in the same folder as the Open GApps zip. Then flash gapps package.
2. Or remove /system/lib/libjni_latinimegoogle.so from recovery.
Q: I flashed Opengapps and now SetupWizard crashes
A: You must flash Opengapps just after ROM clean install and not after reboot.
Q: I have huge battery drain
A: Buy a new battery, stop using monster apps like skype, facebook and other crap.
Q: Where is FM radio?
A: Forget about it, support for our BCM4329 was dropped from AOSP a long time ago, or you can try SpiritFM(which is outdated and cause issues with audio)
Q: Booting stuck at the HTC logo
A: You are S-ON. Flash boot.img "fastboot flash boot.img" or even better perform S-OFF with rumrunner.
FIRST
Getting error binary in zip while flashing through twrp, and with adb sideload no os installed, do we have to flash newest twrp image? I have ext4(4gb) partition btw.
not working..... i think sd ext4 partition needed.
EDIT : not working with sd partitioned
Empty folder ?
Ok just installed cm-13-20151030-UNOFFICIAL-pyramid.zip, I had to use sideload to flash it. TRWP_r6 gave me status 7 error and rom wouldn't build dalvik.
With sideload, no issues but after bootanimation, screen was black except status bar, bout a minute later device soft reboots and welcome, cyanogenmod setup wizard. I also flashed my mod successfully too for more storage
ROM seems quick and looks good so far, I think sdcard might not be linked properly because when saving a screenshot and looking at it's details, it says Path: /storage/emulated/0/Pictures/Screenshots/...
Code:
[email protected]:/ # ls /data/media/0
Alarms
Android
DCIM
Download
Movies
Music
Notifications
Pictures
Podcasts
Ringtones
storage
My data partition is on sd-ext (4.5G) but storage setup is different
Code:
[email protected]:/ # df
Filesystem Size Used Free Blksize
/dev 303.3M 56.0K 303.3M 4096
/sys/fs/cgroup 303.3M 12.0K 303.3M 4096
/mnt 303.3M 0.0K 303.3M 4096
/firmware_radio 199.8M 21.5M 178.3M 4096
/firmware_q6 199.8M 5.8M 194.0M 4096
/devlog 19.7M 4.1M 15.6M 4096
/system 787.4M 452.9M 334.5M 4096
/cache 1.2G 280.8M 912.0M 4096
/data 4.5G 351.2M 4.2G 4096
/storage 303.3M 0.0K 303.3M 4096
/data/dalvik-cache 1.2G 280.8M 912.0M 4096
/mnt/runtime/default/emulated 4.5G 351.2M 4.2G 4096
/storage/emulated 4.5G 351.2M 4.2G 4096
/mnt/runtime/read/emulated 4.5G 351.2M 4.2G 4096
/mnt/runtime/write/emulated 4.5G 351.2M 4.2G 4096
/mnt/media_rw/06A6-765E 25.2G 15.2G 10.0G 16384
dowload
downloading
hinxnz said:
Ok just installed cm-13-20151030-UNOFFICIAL-pyramid.zip, I had to use sideload to flash it. TRWP_r6 gave me status 7 error and rom wouldn't build dalvik.
With sideload, no issues but after bootanimation, screen was black except status bar, bout a minute later device soft reboots and welcome, cyanogenmod setup wizard. I also flashed my mod successfully too for more storage
ROM seems quick and looks good so far, I think sdcard might not be linked properly because when saving a screenshot and looking at it's details, it says
Click to expand...
Click to collapse
I had similiar problems with all cm13 zips xD. You need to go into Storage and USB then internal, copy any file, than do this.., and sd card will show up.
Sent from my HTC One_M8 using Tapatalk
Its amazing,thanks !!!!
Aoudio bug
Imotep95 said:
I had similiar problems with all cm13 zips xD. You need to go into Storage and USB then internal, copy any file, than do this.., and sd card will show up. View attachment 3526043View attachment 3526044
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yeah I didn't test for long, bout half hr or so, cos kinda busy and main devices but yeah I found that some of the os reads the storage but with very limited permissions, apps like browser fc when trying to download because of storage location I guess, it kind of half set up like a nexus. That's how I posted the screenshots by copying the files from /data/media/0 to /mnt/media_rw/{sdcard no.?}. I couldn't install apks normally either and I also found that apks in system now have to be signed.
hinxnz said:
Yeah I didn't test for long, bout half hr or so, cos kinda busy and main devices but yeah I found that some of the os reads the storage but with very limited permissions, apps like browser fc when trying to download because of storage location I guess, it kind of half set up like a nexus. That's how I posted the screenshots by copying the files from /data/media/0 to /mnt/media_rw/{sdcard no.?}. I couldn't install apks normally either and I also found that apks in system now have to be signed.
Click to expand...
Click to collapse
What was your way of installing apk? and if you used gapps which one?
pbazw said:
What was your way of installing apk? and if you used gapps which one?
Click to expand...
Click to collapse
I just pushed some to system but you could try install with adb
Code:
adb install <path to apk>
Edit: I didn't try any gapps.
IIRC I think you can install playstore and then download google play services via playstore.
sideload
hinxnz said:
I just pushed some to system but you could try install with adb
Code:
adb install <path to apk>
Click to expand...
Click to collapse
Ths. one more sideload not starting any ideals?
pbazw said:
Ths. one more sideload fells to start any ideals?
Click to expand...
Click to collapse
Update to Android Debug Bridge version 1.0.32, connect device, start sideload on device first in recovery, I used latest TWRP r6, then enter adb command.
Code:
adb sideload <path to rom.zip>
[share] temporary fix for alpha update
File Explorer and Quickboot app flashable through recovery. (for people who are facing problem in alpha update).
First root your device and flash Beta SuperSU
EDIT: Everything is working fine now
Keyboard
Getting FC with ASOP keyboard
Moderator Information,
I have cleaned the thread. I have also checked the download link and it is there. If you have an issue, do not leave flaming messages on the thread, but report it to the moderators and let us deal with it.
Many thanks,
Stephen
First of thanks @ivanich for 20151101 build. Usb mass storage issue is fixed now I can transfer file through my pc.
Thanks @Khizar Ali for your flashable zip it saves my day. ES File explorer is now fully working (on 20151101 build not for 20151030) and also Quickboot because advance reboot option is no longer available .
2nd that
Usman Zen said:
First of thanks @ivanich for 20151101 build. Usb mass storage issue is fixed now I can transfer file through my pc.
Thanks @Khizar Ali for your flashable zip it saves my day. ES File explorer is now fully working (on 20151101 build not for 20151030) and also Quickboot because advance reboot option is no longer available .
Click to expand...
Click to collapse
This rom is excellent and thank you to those whom have had it so, It's only been a day but outside the Bluetooth bug with the rom and and a working google apps . I must say this can be used as is as a daily driver.:good::good:
My brother has got a POCO F1 and, he wanted to format his userdata and cache partitions like me (Mi 6 user here, AEX Pie + Vantom Kernel) to F2FS on his POCO.
What I've tried (and succeeded) is, adding the lines from my fstab file to his fstab.
Here's the steps we've followed:
- We've installed 9.1.24 Global Developer fastboot firmware by using the MiFlashTool (because AEX 6.3's flashable zip gave an error and told us to update to that version in the output).
- Then we've installed OrangeFox 9.0.1 as it also supports F2FS.
- Then I've got that fstab file, added the 2 lines for userdata and cache into it for F2FS, from my fstab (same android versions and kind of identical partition tables like my Mi 6 so, we tried - and succeeded, please follow).
- Then we've formatted the userdata and cache partitions to F2FS in the recovery.
- Then we've flashed AEX 6.3, Sphinx Kernel (looks nice, I may get some ideas from that) and the flashable* (see the attachments, alongside the original fstab from that version) "FSTAB-EXT4&F2FS-encryptable=footer-BERYLLIUM.zip" that I've made for the fstab.
- Then the GApps (particularly, OpenGapps Nano variant) and the other stuff like fonts etc (not important to specify but meh).
Then the system booted just fine, we've tried everything we could imagine to test and it seems working totally fine.
* Because of I was just lazy (lol) and used that old ass ZipMe app to create the flashables below, before flashing them you have to mount Vendor partition from the Mount screen of the OrangeFox/TWRP to get the the new fstab file written successfully.
> Also note that because of the POCO lacks a proper encryption method on F2FS (just like my Mi 6) your userdata partition will remain unencrypted by using this fstab file.
> For any reasons if you'd want to have your original fstab file back (even though this new one would work just fine for default EXT4 too), you can use the other flashable that I've attached below.
I hope this would be helpful for anybody so sharing the steps and ideas.
I think the same idea could be applicable to the combinations of other kernels that support F2FS and (I don't know, if anybody tries it please tell in the comments) even for MIUI (with a kernel that supports both F2FS and MIUI of course).
If you have any questions or suggestions, (preferably) tell in the comments or if you really want, you can also send pm for various reasons.
I hope that support for F2FS gets improved over time so everybody gets to use it on their devices lol, it's the healthy decision for the flash based storages (check the up to date documentations before starting a flame war or I'll ignore your ignorance - I'm just trying to help here and I feel bad for having to state this here explicitly, on my own behalf).
Note that, I'm not responsible for any possible damages/data losses to your phone (you know the drill here at XDA)/thermonuclear war or whatever; so please use your own brain and make your preliminary research and take precautions before trying anything that you aren't familiar with. Thanks.
Did you tried MIUI + Sphinx + F2FS?
Does official twrp support f2fs for poco
I'm on newest 9.2.18 firmware, can i use f2fs zip in this thread?
can i install this on stock miui 10.2.2.0 with custom extreme kernel???
It's working on Havoc 2.2 (19.2.11) and kernel eXtremeKernel_V9.1.
Thanks for sharing it.
Hello everyone, how to install FSTAB EXT4 file? I just can not. And you can throw this file into the firmware file?
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
Adriano-A3 said:
It's working on Havoc 2.2 (19.2.11) and kernel eXtremeKernel_V9.1.
Thanks for sharing it.
Click to expand...
Click to collapse
How did you establish FSTAB EXT4 that works for you?
IronRUS said:
Hello everyone, how to install FSTAB EXT4 file? I just can not. And you can throw this file into the firmware file?
---------- Post added at 12:12 PM ---------- Previous post was at 12:08 PM ----------
How did you establish FSTAB EXT4 that works for you?
Click to expand...
Click to collapse
mount | grep f2fs
Is it possible to modify system to boot f2fs also?? Thanks in advance
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
Well as i know ,you simply can't, every ROM installation will re-format /system to ext4 automatically
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
You can check the filesystem in Android by some apps like DiskInfo
The system cannot be f2fs since most roms target an ext4 /system partition when installing, so it would always format the system partition to ext4. Eventhough you can backup and restore all of its data once you convert, it would be formated back to ext4 the next time you flash anyway
Jole7 said:
Is it possible to modify system to boot f2fs also?? Thanks in advance
Click to expand...
Click to collapse
It's useless. F2FS is good to random write. /system is entirely read-only.
I will try to make it for system partition as an experiment
aside from /cache you shouldn't use f2fs on any other partition really. Maybe put it on /data for a few benchmark run to laugh at the score, but the performance degradation is too high and unpredictable
pipyakas said:
aside from /cache you shouldn't use f2fs on any other partition really. Maybe put it on /data for a few benchmark run to laugh at the score, but the performance degradation is too high and unpredictable
Click to expand...
Click to collapse
Performance "degradation" because of formatting data to F2FS? Nope.
MadMelman said:
Working on firmware 9.2.18, Havoc 2.2, Sphinx 2.5 & Micro Gapps.
Awesome
Is it all under the hood changes?
I don't see any particular increase in speed.
And can the system be f2fs too?
Thanks and keep up the great work. @Ccelik9
Click to expand...
Click to collapse
Well, your filesystem is itself is the one that's "under the hood". You may notice faster system bootups, app launches and also some in app responsiveness improvements if a particular app is constantly trying to access the storage to record "random" stuff into it's databases.
For system, nope as the others explained before me. I think that it's enough for cache and userdata partitions.
Rommco05 said:
Will attached files works also for Mi8?
Click to expand...
Click to collapse
I don't know, compare the mount points in your current fstab file. If they're similar to F1's then you may try what I've done here.
Dan_Jacques said:
Did you tried MIUI + Sphinx + F2FS?
Click to expand...
Click to collapse
Nope, we stay away from that crap xd but you can try if you wish.
thanhnvt194 said:
I'm on newest 9.2.18 firmware, can i use f2fs zip in this thread?
Click to expand...
Click to collapse
Yes. As long as the mount points stay the same, you can continue to use it.