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
[INTRODUCTION]
This ROM is based of the joined effort of a couple of devs (Ejtable, Scanno and Brucelee666) who are working on getting JellyBean working for our device. As soon as JellyBean is getting stable, my goal is also to put everything on github, just like i did with VegaCream. This way other devs can also work on this.
Please remember that I, ejtagle and brucelee666 are *NOT* professionals and do this in our spare time. We all have full time jobs and a family. So be happy that there is an Android ROM based on Android 4.1.1 / JellyBean for a device that was sold with Android 2.2 and never had an update.
We do our best to make this ROM as good as possible. With VegaCream we gave you a ROM that gave a new life to your tablet and unleashed its full potential. But we are not wizzards and there might be problems that we cannot solve or do not have time for.
[SPECIFICATIONS]
This ROM is based on AOSP 4.1.1 and the device config made by Ejtagle, brucelee666 and myself.
- INT2EXT+ (Needs a correctly partitioned SDCard)
- zRAM
- DPI is set at 120dpi
- Default JellyBean Launcher installed
- Apex Launcher installed
- Filemanager installed
- Terminal installed
- Google Apps is installed. This means that the Google base is installed and all the apps that are available in the Play Store are not installed (i.e. GMail, Maps)
- All languages that are available in AOSP are included
- Partition layout is the same as VegaCream / VegaICS beta1 / Modded stock
- /system/app, /system/lib, /system/fonts, /system/framework and /system/usr are Squashfs filesystems.
[INSTALLATION]
There are 2 methods of installation. There is a CWM recovery flashable ZIP and a NVFlash file.
I realy recommend flashing VegaBean the first time with the NVFlash version.
Before installing any version, you have to make sure that you have a SDCard that has the correct partition layout:
- First partition is a primary partition formatted as FAT32
- Second partition is a primary partition formatted as EXT4
EXT4 is a linux filesystem so you will need a program that can handle Linux filesystems when you are using Windows.
Before installing the ZIP file make sure that:
- You have the correct partition layout (if you have VegaCream installed, you have the correct layout, if not then use the NVFlash installer. This will repartition your internal memory))
- Copy the ZIP file to your SD-Card
- Boot into Recovery
- Do a FULL WIPE / FACTORY RESET
- Install the ZIP file from your SDCard
- After installing reboot the tablet.
[WORKING]
- WiFi
- Bluetooth (Tested with a A2DP headset)
- Camera
- HDMI including audio
- 3G (only fro the Huawei internal modem, usb modems may work)
- GPS not tested by me, but some say it kind of works.
[CREDITS]
- Ejtagle
- Brucelee666
- Scanno
- LeoP for his zRAM implementation
- Legionaire (for the VegaBean bootanimation)
[DOWNLOADS]
Please do *NOT* use Link2SD anymore. You do not need it. With the INT2EXT script, your apps will install on SDCard by default. Just make sure you have 2 primary partition. First partition *MUST* be a FAT32 partition. The second partition *SHOULD* be EXT4. When upgrading from a previous version, make sure your EXT partition is empty / reformatted. Also when using the NVflash version !!!
Downloads:
https://www.androidfilehost.com/?w=files&flid=118264
[Changelist]
[Beta 6]
- RIL updated to the latest version (3 october i think)
- updated to AOSP 4.1.2
- Added check to see if there is a second partition on the SDCard. If not INT2EXT is not excecuted (PLEASE TEST !!!)
- Updated GApps
[Beta 5]
Changes compared to Beta 3-1:
- New kernel with the following changes:
- Suspend problem solved. Tablet does not enter LP0 anymore
- Compiled with zRAM support
- zRAM modules added
- zRAM implementation from LeoP included
- RIL from ejtagle updated
[Beta 3-1]
- Included int2ext+
- Included bootanimation for legionnaire
[Beta 3]
- Latest RIL from EJTagle
- CM10 keyboard
- Stock browser with the option to set User Agent
- You can now just wipe cache and dalvik-cache when updating from a previous VegaBean version. Please remember that from other version you will have to do a full wipe / factory reset !!!
[Beta 2.2]
What has changed compared to Beta 2
- AOSP updated to JRO03L
- Latest update to the huaweigeneric RIL (from aug 27) by EJTagle
The stripped version has the following apps removed from /system/app compared to the original version:
- ApexLauncher.apk
- PlayMusic.apk
- Talk.apk
- YouTube.apk
The stripped version should give you around 10 MiB extra on /system. So if you have bad NAND problems and have problems booting (not able to) you can try this.
[Beta 2]
- HDMI audio working
- VegaBean bootanimation added by indigolemon
[Beta 1]
- Rotation really fixed and HW acceleration working
- Disable / Enable GPS would crash, fixed (thanks Eduardo)
Alpha 3:
- Rotation Fixed. Portrait mode is working correctly
- 3G files included... Sadly no 3G because of too old version of Huawei RIL. Need at least version 6 and we have version 4. So if anybody can get his / her hands on a newer version, please let us know.
Hey , very nice to see JellyBean here
I have ViewSonic 10s
I am using at this moment VegaICS , so i am thinking to upgrate it to JB. So my questions :
- kernel with hostdriver ?
- is system rewritable?? its Squashfs so i think its not (like VegaICS, no deletable apps...)
- can I update BusyBOX and Superuser ??? (always after i did it , WIFI was brocken and I lost root (VegaICS))
- is it possible to change DPI to normal 160 ??
............................
One more question about CWM
always after installing any Roms via CWM , it booted , but after first reboot/turnoff my device died... only what help is reflashing via NVflash....
So what should i flash first to use a stable-CWM (without killing device)
any suggestions
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
rpmccormick said:
If you are still using VegaICS, I suggest you switch to VegaCream RC2. It has an NVFlash installer, so you don't have to use CWM at all. It is by far the most stable and fast ROM ever built for our devices, and is 100% feature complete.
This ROM is a beta, and if you have not experienced VegaCream RC2 yet, you should try that first and wait on this for a later release.
Click to expand...
Click to collapse
ye but its 120 dpi... its horrible and all is toooo small .. can see pixels
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
2minuutes said:
What a great ROM, but I've got a problem where my Viewpad don't boot. Ok, it boots the first time after installing it, but not on 2nd boot. I've tried to install it over both VegaICS and VegaCream RC2. Does anybody have a solution? I really want this ROM. I had the same problem on VegaCream in the past, but it I think it works now, but not in VegaBean. I hope I get any help...
Sent from my HTC Sensation, Venom-infected with the ViperS ROM!
Click to expand...
Click to collapse
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Vlad87do said:
ye its the same problem , flashing with CWM kill your Pad at second boot
thats why i am flashing only via NVflash
Click to expand...
Click to collapse
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Nice, will test this out!
2minuutes said:
VegaCream works now after flashing it through NVFlash. Could the boot problem have something with an uncomplete CWM or something? Like it "destroys" the important partitions?Since both VegaCream and VegaICS use an unofficial build of CWM with Touch-interface? Mabye I'll try to flash an official version and install VegaBean through there! Will report back if it works!
Click to expand...
Click to collapse
I can now confirm that flashing VegaBean through official CWM works, and it boots and 2nd boot too... Just download the .zip file at the bottom and follow this guide by me: http://forum.xda-developers.com/showthread.php?t=1597556 or this guide by add.thebad: http://forum.xda-developers.com/showthread.php?t=1041036
Don't forget to hit the "Thanks" button if I helped you out
Link: https://dl.dropbox.com/u/85837377/recovery.zip
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Vlad87do said:
Thank you , i will do it then today !
Should i do it better via PC-adb and flash 3.0.2.8 with guide from add.thebad or better your method and recovery OR its just the same recovery 3.0.2.8 just deffirend flash method ???
...........................
Permission request to scanno: can I use his rom as base for Remics-Vega??
Click to expand...
Click to collapse
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
scanno said:
If you want to use this for a new rom go ahead. Just give the credits for the work done (also ejtagle and brucelee666)
Modifications to the standard AOSP source code can be found on my github. Also the kernel sources are there too.
They are not up-to-date yet.
If you find solutions to problems in the ROM, give them back to the community so they can also be used in other ROMS.
Click to expand...
Click to collapse
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Vlad87do said:
yes ofc i will.
Is there Host-Driver in the kernel included ?
I am searching developers for Advent Vega device : http://remics.bennz.eu
If you have interests to join Remics-Team pm me!
Click to expand...
Click to collapse
If you mean USB host... Yes it is... On my github there are the sources of the 3.1.10 kernel (based on the rel-15r7 version of nvidia) with the patches ejtagle made. But they are not up to date yet.
As soon as i have time i have to clean up the lunch target of beta1 and do a commit on github. Then you can fork from there and build a version for yourself. If you use the manifest file for vegabean you also get the modifications made to the framework, wpa_supplicant etc to make it all work.
See https://github.com/scanno
Again do not use it yet because they are not up to beta 1.
Thanks for the offer, but i do not have time to do a lot of work and join a development team. For the development of roms for the advent vega i would prefer and suggest that you and the Remics team go to the modaco forum and join the kernel development thread and join the efforts.
This way we have more changes of getting a very good base and from there make ROMS. The more roms to choose from, the better for the people using an advent vega.
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Vlad87do said:
Thx for answere, but i dont will compile it , i will use the ready zip file and edit it.
I am not a kernel-developer
thats why i asked you about team
Click to expand...
Click to collapse
Ok... but again all help is welcome, but you know that. Besides kernel development is done by EJtagle and not by me. He reversed engineerd most of the device specific vega stuff.
Also... /system/lib, /system/framework, /system/usr, /system/app are squashfs filesystems. To access the files in there you have to unsquash them.
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Vlad87do said:
do you can tell me programm on windows how to unsquash and again to squash after editing ?
Click to expand...
Click to collapse
Sorry... I am using Linux and it is available in the repository there. On windows I really do not know. You could Google to see if there are any hits on mksquashfs and unsquashfs. That are the tools used on Linux.
You will need to find a version that supports XZ ( LZMA2) compression. That is the compression algorithm used in vegabean.
This is needed because otherwise the ROM does not fit in the /system partition.
very nice!
7zip can do it under windows - unpack
******************* INFO&CREDITS *******************
I know i've been away from this forum for a lot of time (mostly my Nexus 5 fault ) but when i've seen that F2FS it's now possible on this device i decided to create an easier way to create&use this filesystem,so average users can try it and decide.The best part of XDA is that everyone can contribute in the best way he/she can.
Anyway all credit goes to: samsung (for the f2fs) , Alex Page <[email protected]>, @_that @Dees_Troy (TeamWin ), @dasunsrule32 (cyanogenmod), @Hundsbuah and to everyone who contributed to make this device better.Thank You all!
******************* About F2FS *******************
F2FS (Flash-Friendly File System) is a flash file system created by Kim Jaegeuk (Hangul: 김재극) at Samsung for the Linux operating system kernel.
The motive for F2FS was to build a file system that from the start takes into account the characteristics of NAND flash memory-based storage devices (such as solid-state disks, eMMC, and SD cards), which are widely used in computer systems ranging from mobile devices to servers.
Samsung chose a log-structured file system approach, which it adapted to newer forms of storage. F2FS also remedies some known issues of the older log structured file systems, such as the snowball effect of wandering trees and high cleaning overhead. Because a NAND-based storage device shows different characteristics according to its internal geometry or flash memory management scheme (such as the Flash Translation Layer or FTL), Samsung also added various parameters not only for configuring on-disk layout, but also for selecting allocation and cleaning algorithms. (source Wikipedia )
******************* WARNING *******************
* Please be aware that F2FS is still experimental and DATA LOSS or other issue may occur.
* You agree to use this MOD on you own risk and i don't take any responsability if you encounter any issue or if your personal data is lost
******************* Requirements *******************
Your tf700t device must be Unlocked
An external MicroSD card or a PC (for backup/restore )
A brain
******************* Preinstalling steps *******************
Backup of your personal data to an external card or PC (photo,music,ringtones,etc)
Create a backup from recovery and store it in a safe place (external sdcard or PC)
Download twrp_f2fs from the Download Section (second post )
Download a kernel from the Download Section (second post) - _that and Hundsbuah are for stock based roms only ; CM11 is for Cyanogenmod based.
Download your favorite rom
******************* Install Steps *******************
1) Install twrp_f2fs recovery using one of the methods bellow
Fastboot method
Code:
fastboot -i 0x0B05 flash recovery twrp_f2fs.blob
fastboot -i 0x0B05 reboot
Terminal/ADB
Save twrp_f2fs.blob to the root of your /sdcard directly (internal memory only).
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
Code:
su
dd if=/sdcard/twrp_f2fs.blob of=/dev/block/mmcblk0p4
and reboot your device
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
2) Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
3) Enter the WIPE menu and select Format DATA ( warning all your personal data will be lost )
4) Wait until the format is complete then reboot to recovery again (if previous step was succefull your DATA partition is now F2FS )
5) Wipe Cache (Wipe Menu --> Advanced --> select only Cache partition and go)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
6) ROM installation ( you can choose several methods to get your system back and running)
a) if you already have a System installed you can skip to step 7)
b) install your favorite ROM from external sdcard and Reboot to Recovery
c) restore your previous backup from an external sdcard (select only SYSTEM and DATA partitions) and Reboot to Recovery
7) Install one of the F2FS kernels (based on the ROM you have) and REBOOT SYSTEM
Remember that everytime you install a new ROM you have to Reboot to Recovery and install an F2FS kernel.
That's it,the system should boot with an F2FS data partition,start playing with it. :good: :laugh:
******************* Rom2SD_F2FS *******************
NOTE:
In order to use Rom2SD you need to have a running and rooted stock-based ROM with busybox and a kernel with preinit support (_that and hundbuah kernels are one of them
Also make sure there are no residual folders&files from an old Data2SD/Rom2SD setup ( basically delete the /boot folder in /system if there is one)
Partitioning your MicroSD -- > You can find a good tutorial (thx @sbdags) here
**** Install steps ****
Download all the files from Rom2SD section in the Download page ( post #2) and save them on MicroSD
Download a Kernel from the Download page ( choose the correct one depending on your favorite ROM base) and save it to MicroSD
Boot your device in Recovery
Install Rom2SD_F2fs.zip
Install Rom2SD1.zip
Go to Mount option and make sure Data partition is unchecked ,if not,uncheck it and press Home icon to go back to the Main menu (don't press back)
Go to Wipe and press Format Data (this will format your external data partition to F2FS) - if is failing check the Mount option again
Install your favorite ROM (don't reboot)
Install an F2FS Kernel (don't reboot)
Install Rom2SD2.zip
Reboot and enjoy Rom2SD_F2FS
**** Tips ****
If you have a Backup for the Rom installed on external then you can restore your data and avoid the waste of time needed to configure everything again
Boot to Recovery
Install Rom2SD1.zip
Go to Restore and select the desired backup and check only Data
Swipe to restore and then reboot to system
******************* Back2EXT4 Script *******************
Description: This script will help you format the Data partition to EXT4 without the need to change the recovery.
Instructions:
**** Internal Data ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk0p8) partition it's EXT4 but you can still use twrp_f2fs
**** External Data (Rom2SD/Data2SD setup) ***
Download Format Data to EXT4.zip from the download section and save it to MicroSD
Download Rom2SD1.zip from the download section and save it to MicroSD
Reboot to Recovery
Install Rom2SD1.zip
Install Format Data to EXT4.zip --> Warning,your personal data will be lost
Now your data (mmcblk1p2) partition it's EXT4 but you can still use twrp_f2fs
*********************************************************************************************************************************************************************************************************************
Note: As you can see there are several ways to get your system up and running after your Data partition was formated with F2FS.Also based on my tests you can use an "old" EXT4 backup to restore on F2FS and should work viceversa too.
I will also update this thread with info on how to go back to EXT4 without changing the recovery,and also i will try to modify the Data2SD/Rom2SD scripts and make them F2FS compatible.
And btw,please kick that THANKs button
Downloads
********************************************************* Downloads *********************************************************
++++++++ Kernels ++++++++
That_F2FS.zip --> MD5 Sum: 1165247d099f5dbd5f5a4d4a848ff186
Kernel_F2FS_Hund_v3.4.5 --> MD5 Sum: 888e71f5fade857ed7a062dc08b36d77
CM11_Kernel_F2FS.zip --> MD5 Sum: e9772d2b8a63a009d0499c43fb93a6db
Build by @sbdags F2FS kernels
++++++++ Recovery ++++++++
twrp_f2fs.blob --> MD5 Sum: 4391cdfac9bf9660f52b8b0081543ea0
++++++++ Rom2SD_F2FS++++++++
Rom2SD_F2fs.zip -- > MD5 Sum: f5629e4fc9c40cbb7590152001de8179
Rom2SD1.zip -- > MD5 Sum: f6a6b0e5f0260078782a86c2e60c664e
Rom2SD2.zip -- > MD5 Sum: e82008368cb8ee663a70e63c6cb10040
++++++++ Back2EXT4 Script ++++++++
Format Data to EXT4.zip -- > MD5 Sum: 7ddbbbbe5d7e3c546c46ab8c185b4a70
********************************************************* Sources *********************************************************
Recovery - build from the official sources available in Omnirom 4.4 tree (android_bootable_recovery)with @that kernel (kernel source ).
Hundsbuah kernel - original kernel from here + modified ramdisk
_that kernel - original kernel from here + modified ramdisk
CM11 kernel - Source + Patch
Pretoriano80 said:
Reboot to recovery (if the recovery was installed you will see the 4 linux penguins after pressing the RCK button)
Click to expand...
Click to collapse
Even if you hadn't told me before, I could guess which kernel your recovery is using.
Thanks for making this package available to all users!
A warning to all potential users of f2fs: There is still no program to repair a corrupted filesystem - fsck.f2fs can only detect corruption but not fix it. Don't store anything important on f2fs.
Do you run into any issue with this f2fs so far?
LetMeKnow said:
Do you run into any issue with this f2fs so far?
Click to expand...
Click to collapse
Nope, no issue so far. At some point i was afraid that internal storage will die on me with all the formatting, installing and erasing i've did during F2FS tests, but still no issues.
Sent from my Nexus 5
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
deadlocked007 said:
So does this zips the full internal storage or just the data part with apps and stuff?
Sent from my HTCONE using Tapatalk
Click to expand...
Click to collapse
Internal storage will be completely wiped,so /data/media too.
ariadnejro said:
Thank you for the new recovery with f2fs support.
I'm running latest crombikk with your own cm kernel and the system is running smoothly. Androbench shows that the random write speed gets doubled.
However, my system is not completely stable. Sometimes it freezes without rebooting, specially trying to copy very large files. And sometimes the internal storage gets unmounted. I suppose it's kernel related.
Are you planning to give the option to format also /system and /cache on f2fs? Or you think it's not worth it?
Click to expand...
Click to collapse
Didn't experienced issues so far but i 'm using CromiX here.
F2FS it's useful mostly for random write (or writing operations in general) ,there's no point using it for /system or /cache imo.
Sent from my Nexus 5 using Tapatalk
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
berndblb said:
I assume twrp_f2fs is compatible with the current .10 bootloader and all the current roms: CROMi-X 5.4, CROMBi-KK and CM 11?
Sent from my K00C using Tapatalk
Click to expand...
Click to collapse
twrp_f2fs it's based on official TWRP 2.7.0 and it should work fine with latest bootloader and all ROMs.
Basically i tested all those roms mentioned in your post and are working fine.
Sent from my Nexus 5
Seems to work well! I'm on the 3-19 build of CM11. Had really major IO issues with the device, nothing would make it even remotely usable, even on the performance CPU profile in both the cpu govenor and the asus cpu changer. It was always slow and laggy, it would not handle multiple things well, you basically had to single task. However, flashing this, doing my usual modifications, and it's making this baby fly again. I can open multiple apps and actually navigate without too much lag. Not sure if it's a placebo effect, but so far, it seems great, I'm able to install multiple things at once. I'll see how long this lasts (Wiping the SD can have some beneficial effects too) and I'll try to give an update later, it usually slows down after a few weeks. But this could be "settling" still, it's a fresh flash, even so, I'm happy it's usable again!
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
yew123 said:
Hey is there any method available yet for this to work with rom2sd? Just imagining F2FS, rom2d, cromix 5.4 and hunds ET
Click to expand...
Click to collapse
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Well as long as you only do the data partition it should be OK. I'll look into f2fs support this week.
_that said:
In theory it should work like any ROM2SD installation:
* install rom2sd1 to switch the device nodes to the external card
* format data to f2fs
* install your ROM and a kernel with f2fs-enabled fstab in the ramdisk, don't reboot
* install rom2sd2 to move the ramdisk files to the external /system and modify mount points
Disclaimer: Not tested, there may be issues with the CROMI-X installer trying to be too clever, ...
Click to expand...
Click to collapse
Thanks @_that, when i've got some free time i'll give it a go
CM10 kernel?
Have a request for you, guys. Can someone make f2fs kernel for CM10?
Because I really don't want update my TF700 to 4.4, and stock-based roms isn't my choice...
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
sbdags said:
I made 2 kernels for CM11 for data2sd setup with f2fs (sorry I know not CM10). But here they are if anyone wants to test them.
_thatv9 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 8c340aca96c50ed734b0c903b80d8312
Hunds 3.4.5 cm11 data2sd f2fs
DOWNLOAD
md5 sum : 92cbf93223c07410758feb9921694353
Click to expand...
Click to collapse
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Frostbiter said:
These Kernels will work on all CM based roms not just cromi-kk?
Sent from my SPH-L710 using Tapatalk
Click to expand...
Click to collapse
Should do.
delete please
sbdags said:
Should do.
Click to expand...
Click to collapse
I end up with encryption unsucessful error on boot using the _that/sbdags kernel then reboots and twrp runs an open recovery script, reformatting cache with the mk_ext4 (IIRC), then same error on boot.
The CM kernel runs smoothly for me, but cannot get the touchscreen to respond from a deep sleep. The screen will turn on / off with power button press, but unable to get past the reboot screen or slide to wake screen because there isn't a response with touch. Fully charged the screen reads 'connect your charger' and will not connect to adb so I could not get a log for you.
Vanilla-ish AOSP 5.1.1_r38 ROM (LMY9M) for WiFi Nexus 7 (2012) Grouper
This was created by building from LMY49M source and adding SuperSU/BusyBox
Featuring:
Vanilla AOSP 5.1.1_r38 (LMY49M) for WiFi Nexus 7 (2012)
3.1.10-Plain-Kernels-Tegra3-RC1 from @Snuzzo (reverted to this due to F2FS issue - starting in v1.9.8) with fastcharge!
NOT ALL-F2FS!!! EXT4 with NO JOURNAL MANDATORY on system partition - cache and data can be either filesystem. ROM manages system partition file system (and always has) - I don't notice a difference. Remember system partition is read-only f2fs makes little to no difference.
BusyBox v1.22.1 bionic (needed for Trickster MOD/AdAway) - ( @craigacgomez)
SuperSU 2.76 ( @Chainfire)
AdAway 3.1 compiled and packed to signed apk by me
MiXplorer 5.5.4.BETA-B1509183 @HootanParsa (http://forum.xda-developers.com/showthread.php?t=1523691)
OTG native support ( @craigacgomez) - use your favorite file manager (I now include MiXplorer)
Reboot Menu with submenu for Reboot, Recovery and Bootloader respectively (from Nexus 9 @craigacgomez and Nexus 5 forum THANKS @GROGG88)
Setup wizard crash fix (prefer Google WebView over AOSP fix from @craigacgomez)
Stock sounds/boot animation from stock ROM
AOSP keyboard reenabled
GApps GPS fix
AOSP is always Deodexed
MUST Flash GApps for a "close to stock" experience - EVEN IF UPDATING from prior version(s)
***NOTE download any additional Google apps you might need that are missing from the Google Play app!
Source:
https://github.com/bshiznit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Downloads
Before flashing scroll down and read NOTES!
ROM
MEGA https://mega.nz/#!mFNl3RZS!6hT9BCJPrfuMlBltXzqq18HIzax3eed3cOLRhcPQOYE https://mega.nz/#!PZEkDIjL!9_moD6HmLkfLaRmDrR8-SJFgeieOjUmNR7d5AZo2D3g
Dev-Host http://d-h.st/W2Chhttp://d-h.st/eIE6
md5 - a33f08c178c48e6579c173e03b313cab
Open GApps (closer to STOCK - choose ARM for Platform, 5.1 for Android then pick micro or nano or pico for Variant)) - http://opengapps.org/
I FLASHED: Can no longer mirror Open GApps...
NOTE takes a WHILE (5-10 minutes) to boot up on first boot! ART is optimizing applications. There is no more dalvik-vm!
If you like it hit thanks! Donations are appreciated but never expected
I do this for a hobby and to keep my tablet running like new
You need to wipe Data (if coming from 4.4.x or older or other non-5.x AOSP ROMs) or you see all sorts of Google Play services errors!
No need to wipe data over my prior BSZAospLp releases or other 5.1.x vanilla AOSP ROMs.
Coming soon (maybe):
Strict aliasing (maybe?)
Tilapia?
NOTES:
ALWAYS flash GApps even if updating from a prior AOSP 5.x release! ALL ROMs format the /system partition as part of the installation process and this is where the GApps are kept!
ALWAYS wipe both caches!
If stuck on black Google screen!!! Format and ALSO repair system (ext4), cache and data (ext4 OR f2fs) in TWRP Wipe --> advanced wipe --> repair or change button. Thanks @ffejy462 and @nickmv for this valuable info!
BACKUP using TWRP and Titanium - save those files off the device to a USB stick external HDD or whatnot! Not responsible for lost data!
WIPE Data in recovery unless coming from another Vanilla AOSP 5.x ROM!
Be sure you are at bootloader 4.23 http://forum.xda-developers.com/showthread.php?t=2150251
ONLY TESTED USING TWRP 2.8.7.0/3.0.2-0.
MUST FLASH GApps for Play Store, etc.
You may see a few FCs when it first boots and settles in but should go away given time.
If you like it consider donating! A nice big solid state hard drive will let me build faster and for more devices! (YAY my build box now has 411GB free even after all this developing - thanks to all who donated).
Thanks:
@dsixda for the Kitchen! (Consider donating to him work is paused on the kitchen he said due to health). I used this for all my initial development.
@Chainfire for SuperSU and keeping it updated!
@GROGG88 - for the power menu and GPS patches (even though it was from Nexus 5 it worked great)!!!!
@craigacgomez - used many commits from his Lollipopalooza for Nexus 9 (BusyBox in src tree and compiled with ROM, native OTG).
@scrosler - for also being a really cool dev and helping me (even though he's doing Nexus 5 things) and introducing me to @GROGG88
@adomol for the early f2fs ROM based on mine
@sykopompos for the sepolicy file and kernel instructions to allow root as well as the ART build.prop tweaks.
@scrosler for sharing his Nexus 7 (2013) ROM and updater-script - great dev and good resource
@Snuzzo for permission to use his kernel and for all of his guidance - great dev and awesome resource as well!
@drewwalton19216801 for Lollipop GApps!
@azoller1 for v4.23 bootloader thread and flashable zip
@MidnightNinja - for also posting a build
Google for Android
AOSP for source!
Goodies:
Google is phasing out the stock AOSP browser (https://android.googlesource.com/platform/build/+/4271a9b3ed5ffa40e4ef24801cab5690fe5ca56f) - so I compiled Chromium browser from source! Download it and install as you would any other .apk file:
https://mega.nz/#!GMMCEJJD!bgRdr_D346ZFEQeiYFaHCJ46tGDQXvy9dfRc4IkWWMY
Changelog:
LMY49M v1.9.9
AOSP 5.1.1_r38 LMY49M
SuperSU v2.76
LMY49J v1.9.8
AOSP 5.1.1_r37 LMY49J
LMY49H v1.9.7
AOSP 5.1.1_r35 LMY49H
SuperSU 2.65
LMY49G v1.9.6
AOSP 5.1.1_r34 LMY49G
LMY48Z v1.9.5
AOSP 5.1.1_r30 LMY48Z
Kernel from @Snuzzo now 3.1.10-Plain-Kernels-v0.1-Lawlly
LMY48X v1.9.4
AOSP 5.1.1_r25 LMY48X
AdAway 3.1
LMY48M v1.9.2
Updated to newer kernel from @Snuzzo (3.1.10-Plain-Kernels-Tegra3-RC1-00068-g09cd74e)
LMY48M v1.9.1
Now based on 5.1.1_r14 LMY48M - fixes yet another stagefright vulnerability!
See OP - included AdAway and MiXplorer
LMY48I v1.9
Now based on 5.1.1_r9 LMY48I
BusyBox in source tree (thanks @craigacgomez) and linked and working as usual
OTG supported in-ROM ( @craigacgomez vold and Settings commits)
Same kernel and fstab for F2FS OR EXT4 for data and cache partitions - so no separate downloads (borrowed the fstab logic from Nexus 9 stock)
FunkyKernel from @Snuzzo 1.7.0 going strong!
Reboot option in menu with sub-menu for Reboot, Recovery and Bootloader respectively (thanks @craigacgomez and @GROGG88)
SuperSU to latest PROD v2.46
LRX22C v1.5
Now based on 5.0.1_r1 LRX22C
F2FS for all partitions support - see OP
FunkyKernel from @Snuzzo in both ROMs
Advanced power menu (YTMND @GROGG88)
GApps GPS fix
Swipe enabled on keyboard (please flash GApps or errors)
SuperSU to latest PROD v2.37
LRX21T v1.1
Now based on 5.0.0_r6 LRX21T!
ART performance entries now baked in for build.prop file
fstrim as part of install for /system /cache and /data partitions for performance..
Borrowed some symbolic links from @scrosler's Nexus 7 (2013) ROM
Extras/Additional Info:
ART build.prop tweaks flashable zip (from Nexus 5 forum) - http://forum.xda-developers.com/showpost.php?p=56646559&postcount=220NOW INCLUDED DO NOT FLASH THIS on latest version(s)
Titanium Backup Twitter (currently supported) - https://twitter.com/TitaniumBackup
OLD Downloads
ROM LMY49J v1.9.8
ROM
MEGA https://mega.nz/#!PZEkDIjL!9_moD6HmL...UmNR7d5AZo2D3g
Dev-Host http://d-h.st/eIE6
md5 - 584bf8276748156ed7e5d3d948bc1ccc
ROM LMY49H v1.9.7
ROM
MEGA https://mega.nz/#!rMlx3QyB!fZHecDiS06DITzgK9uDsgdBmhdCcIpEZjfVhhc8gzwc
Dev-Host http://d-h.st/hz7o
md5 - 57690bafc228b6625aada3820d61cbb0
ROM LMY49G v1.9.6
ROM
MEGA https://mega.nz/#!jRcjCShL!f7tjngPgtyrErgvk_RylDPMrjpA_ySI3gVC5_c7Xxlw
Dev-Host http://d-h.st/jyPZ
md5 - 49537412b12fb6076788855ab8339db7
ROM LMY48Z v1.9.5
ROM
MEGA https://mega.nz/#!GRsjGArb!oQPOsvO8EaAG4EYkEy4MF2V63XVfI9fRCUSi8X7GIqY
Dev-Host http://d-h.st/ZR5l
md5 - 76afd2103e1cbad268eb5d349e84990c
ROM LMY48X v1.9.4
ROM
MEGA https://mega.nz/#!uYk1ELxA!mJoQv_JE0xWgbimRdvEfKJYZNqvSB79bRzecfaXurpw
Dev-Host http://d-h.st/KcD3
md5 - 99f6b8bff97e58cb3acb7657fe70423a
ROM LMY48M v1.9.2
ROM
MEGA https://mega.nz/#!jRESkRxZ!g5zGHBiT4Zp7ok461vFULT3lBZipnBd44hr45R8jyUw
Dev-Host http://d-h.st/sAHl
md5 - 9fd0fd2a52cb5f2b6a4e3734276d4e27
ROM LMY48M v1.9.1
ROM
MEGA https://mega.nz/#!PV8VEbxL!NaX59H7Kvo5AXKbjU42u9UqYlyuV0Btv2abDYWs0EAM
Dev-Host http://d-h.st/suBu
md5 - 784cf104b5532ac0ec27f8762cdae377
ROM LMY48I v1.9
ROM
MEGA https://mega.nz/#!jc8wWA7R!wEEi6dxopUnKnTtnT8VRtxMU4U1m3dNxF4e_62M-aYM
Dev-Host http://d-h.st/VDmU
md5 - aa4011eea486d4f9f9037338b0b24b28
ROM LRX22C v1.5
ROM - EXT4
MEGA https://mega.co.nz/#!PMNyRIiJ!VNHejQhKblluk2d7S9V4Wy5B-xapGYqWA-gAsQTyNIA
Dev-Host http://d-h.st/SNW
md5 - 37a19fcfb25794c7559e907d49d96688
ROM - ALL-F2FS (data and cache must be FORMATTED to f2fs!)
MEGA https://mega.co.nz/#!jJ0A3I5Y!rfFKIfi3qTDblyByNmwqFMBUmrvhk71YOjM6yX697Ps
Dev-Host http://d-h.st/ZukH
md5 - 0f0560f516daa992d8d4a4752556d88d
BETA PA GApps (at your own risk!)
THREAD http://forum.xda-developers.com/par...apps-official-to-date-pa-google-apps-t2943900
GApps (from http://forum.xda-developers.com/goo.../gapps-google-apps-flashable-package-t2930260)
BasketBuild https://s.basketbuild.com/filedl/gapps?dl=gapps-lp-20141109-signed.zip
md5 - 367ce76d6b7772c92810720b8b0c931e
ROM LRX21T v1.1
MEGA https://mega.co.nz/#!WZlEiKbT!ys1Walbq62qT5_VYl0GdDQEar8uGOddbw-kn0OnX-tI
Dev-Host http://d-h.st/Qkqn
md5 - 8473d155b0375adea5c9b254f73bee17
ROM LRX21M v1.0
MEGA https://mega.co.nz/#!HV801SxS!wpaRnPTXXGuVikPr6rHdS-5fmAqr2J4_YuE6j94uFNo
Dev-Host http://d-h.st/o8W
md5 - 11e661d8363c7a3ee98e736b3d66cba6
I'm going to give this a go.
Sent from my Nexus 7 using Tapatalk
bshiznit said:
Vanilla AOSP 5.0.0_r2 ROM (LRX21M) for WiFi Nexus 7 (2012) Grouper
Click to expand...
Click to collapse
Thanks for the ROM. However a tilapia(3g) version would be greatly appreciated!
wejgomi said:
Thanks for the ROM. However a tilapia(3g) version would be greatly appreciated!
Click to expand...
Click to collapse
I know sadly im outta space on my build box
I had a good feeling we'd see a flashible (rooted) rom today! Thanks! Apparently Google is working on a few bugs (wifi, battery drain...), and the official images probably won't be out until next week or so... In the meantime, this will work!
lg g2 xdabbeb's vs980 v2.2.0
the gapps is failing i done what was written
Ismail.A said:
the gapps is failing i done what was written
Click to expand...
Click to collapse
What recovery are you using? Any particular message? Could be a bad download...
If I'm flashing from an All F2Fs Ext4 rom, are there any special preparations I need to perform to ensure I don't brick? I would like to flash it but I want to ensure that there are few caveats first. Thanks.
keith.valdez said:
If I'm flashing from an All F2Fs Ext4 rom, are there any special preparations I need to perform to ensure I don't brick? I would like to flash it but I want to ensure that there are few caveats first. Thanks.
Click to expand...
Click to collapse
You are going to want to format everything back to ext4! My ROM will format your system partition the others are up to you :>
VERIFIED - just checked the fstab file in the kernel's ramdisk and it expects system, cache and data be ext4
Installed and boots fine, but I just see a screen saying "To start Android, enter your password".
Any ideas?
top_bunk said:
Installed and boots fine, but I just see a screen saying "To start Android, enter your password".
Any ideas?
Click to expand...
Click to collapse
Coming from F2FS right? You'll need to put cache and data back to ext4 in recovery...
You're right. Been so long since I've flashed anything on my N7 that I'd forgotten!
Will this work with Multirom? and is there any difference between this build from the first build made by another user? hope this is fine enough to flash right away on my device and not by breaking my recovery -_-
JovieBrett said:
Will this work with Multirom? and is there any difference between this build from the first build made by another user? hope this is fine enough to flash right away on my device and not by breaking my recovery -_-
Click to expand...
Click to collapse
Fixed the recovery thing! Added root and busybox!
The other ROM I think is a zip straight from the AOSP build environment (after you run "make" to compile it all - you can run "make otapackage" to generate a zip). That one will overwrite recovery on each boot and needs to be rooted by a manual process of editing some items in the kernel and then flashing SuperSU 2.19. I wanted a ROM where all that is done in advance
Also re: MultiROM no idea. But I don't think the stock kernel in this ROM is compatible with MultiROM...
Thanks for this ROM.
Had to re-format data back from F2FS to get rid of the encrypted password request - hope the ROM stays fast
Gapps failed. E: Error executing updater binary in zip '/sdcard/download/gapps-lp-20141106-signed.zip
Md5 checked out fine...
lg g2 xdabbeb's vs980 v2.2.0
Flashed it without any problems however I cant install Google+ from play store, haven't tried sideloading it. Despite that, everything seems fluid, can't decide if it's faster than kit kat right now as I have always run custom kernel on Kitkat and there is pure Google kernel.
For now good, bad is that mx player isn't working with lollipop right now, remember back in time there was the same problem with Kitkat then.
Good work ?
ffejy462 said:
Gapps failed. E: Error executing updater binary in zip '/sdcard/download/gapps-lp-20141106-signed.zip
Md5 checked out fine...
lg g2 xdabbeb's vs980 v2.2.0
Click to expand...
Click to collapse
I just reflashed with fresh downloads and it all worked OK. And using that version of TWRP. Maybe it copied over MTP bad?
Code:
#include
/*
* Your warranty is now void.
*
* I'm 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.
*
*/
Introduction
MultiROM is one-of-a-kind multi-boot mod for Galaxy ACE 3 LTE. It can boot any Android ROM as well as other systems like Ubuntu Touch, once they are ported to that device. Besides booting from device's internal memory, MultiROM can boot from external SD card. The main part of MultiROM is a boot manager, which appears every time your device starts and lets you choose ROM to boot. You can see how it looks on the image above. ROMs are installed and managed via modified TWRP recovery. You can use standard ZIP files to install secondary Android ROMs and MultiROM even has its own installer system, which can be used to ship other Linux-based systems.
Features:
* Multiboot any number of Android ROMs
* Restore nandroid backup as secondary ROM
* Boot from Internal memory and MicroSD Card (non tested)
Warning!
This whole thing is basically one giant hack - none of these systems are made with multibooting in mind. It is no longer messing with data partition or boot sector, but it is possible that something goes wrong (even if never happened until now) and you will have to flash stock firmware with Odin. Make backups. Always.
Installation, Note: Only manual installation is supported, because this mod is not officially supported.
MultiROM has 3 parts you need to install:
MultiROM
Modified recovery
Patched kernel
Now let's head to the installation. Note: Your primary ROM is recommended to be lollipop, because it doesn't act well as a secondary, due to enforcing selinux. Although you can use it as secondary, but change it's selinux status. My setup is Lollipop as primary, and KitKat as secondary. Stock ROM was not tested, because I hate it
I spent about 5 days working on this. My head will explode There is a tiny issue. MultiROM boot menu does not show up as it should. That's why we should use the MultiROM manager apk. and switch ROMs from the app.
Attention: The steps are if you use CM-12.1 as primary ROM
Kernel for Stock ROM with kexec-hardboot patch here
Step 1: Install this patched kernel over CM12.1. Or this, if you want OC.
Step 2: Install the modified Multirom Manager apk, I added support for our device
Step 3: Install Multirom
Step 4: Install MultiROM TWRP, via previous TWRP recovery, it can flash images
Step 5: Reboot into new recovery
Step 6: Install CM11, as secondary ROM!!
Step 7: Go to recovery-->Advanced-->MultiRom-->List ROM-->Choose CM11-->Flash Zip. Flash either stock kernel, or oc_kernel. Both include the necessary kexec-hardboot patch. Usually Multirom requires only primary ROM to have the kexec-hardboot patch, but in our case it does not work this way.
Now you are ready to switch ROMs. Ooh, almost forgot. MultiROM boot manager will show up if you connect the phone for offline charging, you will find out what happens on each case. This is the only bug that I can't resolve yet. Although multirom can be used, with this bug.
Code:
Update 20150829: Download everything from this [URL="https://androidfilehost.com/?w=files&flid=37974"]folder[/URL]
Kernel will be updated when ROM is built
Changelog: Re-implemented kexec hardboot and fixe last_kmsg creation
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
NOTE: If secondary ROM does not boot, select Restorecon under multirom
Click to expand...
Click to collapse
Switch ROMs from the MultiRom manager app
NOTICE: I can't guarantee it will work on other variants rather than "R"
To uninstall Multirom simply flash this
You current ROM will not be erased by the installation.
Adding ROMs
1. Android
Go to recovery, select Advanced -> MultiROM -> Add ROM. Select the ROM's zip file and confirm.
Using MicroSD Card
During installation, recovery lets you select install location. You just select the location (extX, NTFS and FAT32 partitions are supported) and proceed with the installation.
If you wanna use other than default FAT32 partition, just format it in PC. If you don't know how/don't know where to find out how, you probably should not try installing MultiROM.
If you are installing to NTFS or FAT32 partition, recovery asks you to set image size for all the partitions - this cannot be easilly changed afterward, so choose carefully. FAT32 is limited to maximum of 4095MB per image - it is limitation of the filesystem, I can do nothing about that.
Installation to MicroSD Card takes a bit more, because the external memory is (usually) slower and it needs to create the images. Also boot process is longer, highly depends on card's class. You can find ROMs installed on SD card in the "External" tab in boot menu.
Updating/changing ROMs
1. Primary ROM (Internal)
Flash ROM's ZIP file as usual, do factory reset if needed (it won't erase secondary ROMs)
Go to Advanced -> MultiROM in recovery and do Inject curr. boot sector.
2. Secondary Android ROMs
If you want to change the ROM, delete it and add new one. To update ROM, follow these steps:
Go to Advanced -> MultiROM -> List ROMs and select the ROM you want to update.
Select "Flash ZIP" and flash ROM's ZIP file.
Explanation of recovery menus
Main menu
- Add ROM - Add ROM to boot manager
- List ROMs - List installed ROMs and manage them
- Inject curr. boot sector - Use this option if MultiROM does not show up on boot, for example after kernel installation.
- Settings - Well, settings
Manage ROM
- Rename, delete - I believe these are obvious
- Flash ZIP (only Android ROMs) - Flash ZIP to the ROM, for example GApps
- Add/replace boot.img - Replaces boot.img used by the ROM, this is more like developer option.
Source Code
MultiROM - https://github.com/Tasssadar/multirom/tree/master (branch master)
Modified TWRP - https://github.com/Tasssadar/Team-Win-Recovery-Project (branch master)
CM12.1 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-12.1
CM11 stock kernel w/ kexec-hardboot patch- https://github.com/kostoulhs/android_kernel_samsung_msm8930-common/tree/cm-11.0
Stock kernel for stock rom w/ kexec-hardboot patch - https://github.com/kostoulhs/android_kernel_samsung_loganrelte/tree/master
MultiROM device tree - https://github.com/kostoulhs/android_device_samsung_loganreltexx/tree/multirom
Big thanks to Tasssadar for this awesome utility.
Also thanks @Grarak for the melius patch, i was based on it
Reserved
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Levivig said:
All the zip files listed above(steps 1 and 3) should be installed via TWRP, is that correct?
Click to expand...
Click to collapse
Exactly
Sent from my GT-S7275R
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
F. Dutch said:
This looks great, will defenatly try it. With 4,5 GB free internal memory do you recommend installing rom's on internal or SD ?
Click to expand...
Click to collapse
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
kotzir said:
Installing on internal works. I haven't tried to install on sdcard yet
My setup is Lollipop as primary and KitKat as secondary, installed on internal
Sent from my GT-S7275R
Click to expand...
Click to collapse
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
zh_eco said:
Can I Make My Setup Like This ? :
Stock ROM(4.2.2) as primary and Lollipop as secondary , Stock ROM installed on internal , Lollipop ROM installed on SD card .
And my sd card use ext4 partition , is this partition supported ?
This is amazing feature !
Thanks a lot for this great work !
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
kotzir said:
Multirom works on fat systems on sdcard as fas as I know, see more info about the limitations on the OP. To use stock ROM you need a stock kernel with kexec hardboot patch, I have already patched it, it is also available on my github. I just haven't built it. I can build it although
Edit: Due to the bug, that multirom does not show up on boot, we actually can't install ROMS on Sdcard, they are not visible by MultiRom manager app.
Edit2: stock kernel with kexec-hardboot patch download
Edit3: Trying to make it fully functional
Sent from my GT-S7275R
Click to expand...
Click to collapse
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Or just we will never can install ROMs on the SD card ?
Sent from my GT-S7275R using XDA Free mobile app
zh_eco said:
So I can't install any ROM on the SD card ..
until you fix the bug .. Right ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
kotzir said:
you can boot into multirom menu, if the phone is off and you connect it to the charger, so you can experiment a little
Click to expand...
Click to collapse
So we will stay do this , just if we install a ROM in the SD card .
Or what ?! :|
OK , after flashing the stock kernel with kexec-hardboot patch, I can't flash any other kernel like arasma kernel in my stock ROM(4.2.2) ?
If I can't .. Can you make a kexec-hardboot patch for arasma kernel ?
Here : http://d-h.st/aYr
Or .. Can you make the lollipop kernel (1.7GHz) work on the stock ROM ?
Sent from my GT-S7275R using XDA Free mobile app
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
zh_eco said:
Its not my problem if I'm always not understand.
Its my brain problem ..
Just answer me ..
Why you always Ignore me ?
I'm just asking you , you can tell me oh I'm sorry ! I can't .. Just like this and I will accept .
Click to expand...
Click to collapse
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
kotzir said:
Mate I want to answer you and I do the best I can. Now I am working to make multirom fully functional, what don't you understand? The same time I am studying. It is pretty hard for me. The thing you ask me requires fully functional multirom. Enjoy it as it is, if you can and wait for the fix. Thanks
*Also, I will modify the stock kernel, as the others
Click to expand...
Click to collapse
:good::good: Nice Work Man
zh_eco said:
Can I Make My Setup Like This ? :
...my sd card use ext4 partition , is this partition supported ?
Sent from my GT-S7275R using XDA Free mobile app
Click to expand...
Click to collapse
May I ask why you do this?
MTP practically destroys any real world benefit that EXT could possibly offer you, and if you use UMS et al you'll hit permissions issues with the media that completely ruin its ability to function as removable storage unless every single one of the systems it touches only has a single user or you carefully craft the system environment so that the user always has the same UID.
It's just weird to use a journalled filesystem with access permissions as removable storage. Either MTP destroys any gains you might possibly get, or UMS makes it impossible to access the contents of the volume on ~99% of all the systems you'll ever encounter in the wild. Ever wondered why you never see external storage volumes with permission based filesystems? This is why. It's largely silly.
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
F. Dutch said:
I tried to restore a backup of stock rom, i want to try if it works and maybe use it as 3rd rom but CWM says .android_secure.vfat.tar and .Android_secure.vfat.Tar.a are missing does anyone know what it means and how to fix it. Does CWM version matter? Can TWRP instal backups made by CWM?
Click to expand...
Click to collapse
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
kotzir said:
To use it with stock ROM, you need to install a stock kernel with hardboot patch, there is one in the OP. TWRP can't restore backups from CWM, different format of backup. I don't see any reason of using CWM, since there is TWRP.
Sent from my GT-S7275R
Click to expand...
Click to collapse
Thanks but the only backups i have of stock are made with CWM. When i try to restore it says .Android_secure.vfat.Tar and .Android_secure.vfat.Tar.a are missing so i can't restore and make a backup with TWRP. Found some info about it and trying tot make it work right now.
kotzir said:
Video on how to install
Video on how to flash updates
*Thanks Tech Tutorials channel for the videos
Click to expand...
Click to collapse
Thank U Very Much @kotzir For Adding My Videos To "OP"
Small update, check OP