This is a Nook HD CM10/CM10.1 sdcard installation initially based on verygreen Nook HD+ CM10 sdcard development.
This ROM is very much a work in progress.
For general and non-development topics about this ROM please see [Nook HD] CM10/CM10.1 General Discussion.
For Dual Boot/SDCARD/EMMC hybrid installation please see [Nook HD WIP]Dual Boot Stock and CM10.1 Hybrid
LATEST DOWNLOADS
CWM bootable image for pure SD install
uImage.20130613.sd.hd.zip - extract uImage (cyanobbot) from the zip file into the SD boot partition. *** latest ***
Screen artifacts now gone.
lg screen now working. Thanks leapinlar for testing.
update-20130224.zip - copy contents of zip file to /boot.
Provides serial number of Nook HD to android.
sdcard-cwm-hummingbirdv4.zip Posted: 1/21
Updates can now be installed from /emmc under the media folder.
From CWM menu select 'install zip from sdcard' -> 'choose zip from internal sdcard' -> <select the update file under the media folder>.
CM10/CM10.1 update file can now be downloaded using the stock B&N ROM and saved to the internal sdcard (emmc), which can later be picked up by CWM.
Removed critical partitions from being mounted and formatted. (Thanks to leapinlar for the suggestion)
ramdisk.cwm - for existing bootable sdcard, simply download this file and overwrite the old one to have the same functionality as above.CM10.1 CWM Flashable ROM: Upstream updates are merged regularly.
cm-10.1-20131230-UNOFFICIAL-hummingbird *** latest ***
cm-10.1-20131201-UNOFFICIAL-hummingbird
cm-10.1-20131108-UNOFFICIAL-hummingbird
cm-10.1-20131029-UNOFFICIAL-hummingbird
cm-10.1-20131021-UNOFFICIAL-hummingbird
cm-10.1-20131017-UNOFFICIAL-hummingbird
cm-10.1-20131006-UNOFFICIAL-hummingbird
cm-10.1-20130929-UNOFFICIAL-hummingbird
cm-10.1-20130924-UNOFFICIAL-hummingbird
cm-10.1-20130918-UNOFFICIAL-hummingbird
cm-10.1-20130915-UNOFFICIAL-hummingbird
cm-10.1-20130912-UNOFFICIAL-hummingbird
cm-10.1-20130903-UNOFFICIAL-hummingbird
cm-10.1-20130901-UNOFFICIAL-hummingbird
cm-10.1-20130829-UNOFFICIAL-hummingbird
cm-10.1-20130828-UNOFFICIAL-hummingbird
cm-10.1-20130826-UNOFFICIAL-hummingbird
cm-10.1-20130812-UNOFFICIAL-hummingbird
Increased audio levels
cm-10.1-20130807-UNOFFICIAL-hummingbird
Added USB host mode to Quick Settings
cm-10.1-20130804-UNOFFICIAL-hummingbird
Integrated new "Nook Tweaks" heading under Settings. Currently only Forced USB Host option is available (No need for verygreen's switcher anymore). Checking 'Set on boot' will restore setting after a reboot.
USB storage now automatically mounted.
cm-10.1-20130801-UNOFFICIAL-hummingbird
Added kernel support for verygreen's Forced USBHost Switcher.
cm-10.1-20130728-UNOFFICIAL-hummingbird
Download latest CM10.1 gapps here: http://goo.im/gapps/gapps-jb-20130301-signed.zipCM10 CWM Flashable ROMcm-10-20130101-UNOFFICIAL-hummingbird.zip
Headphone now working (Merged verygreen audio patch). :good:
Storage now default to MTP (Merged verygreen patch)
Uses dev-branch of omap4xxx and libhardware from omapzoom.
Download latest CM10 gapps here: http://goo.im/gapps/gapps-jb-20121011-signed.zipCM10 sdcard Installer (For CM10.1 installation additional step in the instructions should be followed) Due to many problems/issues encountered by users with regards to adb and sdcard not working in Windows, I have combined the two files below and written a short script to automate the installation process. Just insert the sdcard to your device and it will be installed with CM10 automatically. No user intervention is needed.
Instructions
Download the compressed image file cm10-sdcard-installer.img. Posted: 12/28
Unpack and write the image to your sdcard. For more info on how to do it, see this post.
(optional) To install CM10.1 instead of CM10, replace 'CM-10-hummingbird.zip' of the SD card boot folder with any CM10.1 image file you can download here in this page (you need to rename the file exactly as above).
Insert into the device and boot (cold)/reboot (warm).
Wait for it to finish installation.
Enjoy your HD with CM10 (CM10.1)
Note: This is very much a work in progress and not fully tested. Use it at your own risk!!!For manual installation, follow the instruction given in verygreen CM10 page and replace the following files appropriate for the Nook HD.
sdcard-cwm-early3.img.gz ---> sdcard-cwm-hummingbirdv4.zip
cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip ---> cm-10-XXXXXXXX-UNOFFICIAL-hummingbird.zip or cm-10.1-XXXXXXXX-UNOFFICIAL-hummingbird.zip
OLDER BUILDS
CWM bootable image for flashing CM10/CM10.1 ROM to sdcard
cm-10.1-20130723-UNOFFICIAL-hummingbird
cm-10.1-20130718-UNOFFICIAL-hummingbird
cm-10.1-20130716-UNOFFICIAL-hummingbird
cm-10.1-20130714-UNOFFICIAL-hummingbird
cm-10.1-20130711-UNOFFICIAL-hummingbird
cm-10.1-20130705-UNOFFICIAL-hummingbird
cm-10.1-20130702-UNOFFICIAL-hummingbird
cm-10.1-20130630-UNOFFICIAL-hummingbird
cm-10.1-20130628-UNOFFICIAL-hummingbird
cm-10.1-20130626-UNOFFICIAL-hummingbird
cm-10.1-20130625-UNOFFICIAL-hummingbird
cm-10.1-20130623-UNOFFICIAL-hummingbird
cm-10.1-20130621-UNOFFICIAL-hummingbird
cm-10.1-20130617-UNOFFICIAL-hummingbird
cm-10.1-20130615-UNOFFICIAL-hummingbird
Fixed: Missing menu icon
Working: Wi-Fi Direct (Tested with my HD+)
Tethering and hotspot
Working: Wi-Fi hotpsot
Not yet tested: USB Tethering
Not yet working: BT Tethering
Note for hybrid setup: Need to extract ramdisk.hybrid from update.20130616.ramdisk-hybrid.hd.zip into the SD card boot partition.
cm-10.1-20130609-UNOFFICIAL-hummingbird
Fixed: Boot screen artifact.
Additional note for hybrid setup: Please update uImage and ramdisk.hybrid noted below.
cm-10.1-20130608-UNOFFICIAL-hummingbird
Additional note for hybrid setup: Need to extract uImage from uImage-hybrid-6-8.zip into the SD card boot partition. (cyanoboot updated)
cm-10.1-20130607-UNOFFICIAL-hummingbird
Fixed: Intermittent boot problem.
Additional note for hybrid setup, Need to extract ramdisk.hybrid from update-6-8.zip into the SD card boot partition.
cm-10.1-20130602-UNOFFICIAL-hummingbird
Fixed: WIFI slowing down the AP where it is connected. (Thanks leapinlar for the head up)
cm-10.1-20130529-UNOFFICIAL-hummingbird
cm-10.1-20130528-UNOFFICIAL-hummingbird
cm-10.1-20130525-UNOFFICIAL-hummingbird
Closing lid will now put device to sleep (Tested with my new cover)
Merged with kernel from BN 2.1.0 (Please report any mmc issue)
cm-10.1-20130515-UNOFFICIAL-hummingbird
sdcard-cwm-hummingbirdv3.img.gz Posted: 12/27
Reverted mmc patch of kernel from B&N 2.0.5 to 2.0.2 - mmc write BUG discussed in HD+ thread.
Retained other B&N 2.0.5 patches - Device will not get hot even when the screen is on under cwm for a long time.
cwm updated with bigger and now using roboto font. Orientation has been corrected.
sdcard-cwm-hummingbirdv2.img.gz
There is something wrong with the initial cwm sd image sdcard-cwm-hummingbird.img.gz, partition 5 is not being formatted. Please redownload this updated version.
CWM Flashable CM10.1 ROM to sdcard
cm-10.1-20130512-UNOFFICIAL-hummingbird
cm-10.1-20130510-UNOFFICIAL-hummingbird
cm-10.1-20130508-UNOFFICIAL-hummingbird
cm-10.1-20130507-UNOFFICIAL-hummingbird
cm-10.1-20130505-UNOFFICIAL-hummingbird
cm-10.1-20130503-UNOFFICIAL-hummingbird
cm-10.1-20130502-UNOFFICIAL-hummingbird
cm-10.1-20130430-UNOFFICIAL-hummingbird
cm-10.1-20130425-UNOFFICIAL-hummingbird
cm-10.1-20130422-UNOFFICIAL-hummingbird
cm-10.1-20130420-UNOFFICIAL-hummingbird
cm-10.1-20130418-UNOFFICIAL-hummingbird
cm-10.1-20130415-UNOFFICIAL-hummingbird
cm-10.1-20130412-UNOFFICIAL-hummingbird
cm-10.1-20130409-UNOFFICIAL-hummingbird
Backported uhid to kernel 3.0 for BT keyboard to work.
cm-10.1-20130408-UNOFFICIAL-hummingbird
cm-10.1-20130407-UNOFFICIAL-hummingbird
cm-10.1-20130406-UNOFFICIAL-hummingbird
cm-10.1-20130405-UNOFFICIAL-hummingbird
cm-10.1-20130404-UNOFFICIAL-hummingbird
Major change: switch to sgt7 cm mod for tablet (frameworks/base, Settings & Trebuchet). See SGT7 - Making your Nexus 7 a true tablet. Thanks sgt7 team.
cm-10.1-20130331-UNOFFICIAL-hummingbird
Tablet UI now enabled again.
cm-10.1-20130326-UNOFFICIAL-hummingbird
Upstream change: Added basic pie control inspired by Paranoid Android.
Removed Tablet UI for the meantime (Will put it back in the next build).
cm-10.1-20130324-UNOFFICIAL-hummingbird
cm-10.1-20130320-UNOFFICIAL-hummingbird
cm-10.1-20130318-UNOFFICIAL-hummingbird
cm-10.1-20130317-UNOFFICIAL-hummingbird
cm-10.1-20130315-UNOFFICIAL-hummingbird
cm-10.1-20130313-UNOFFICIAL-hummingbird
cm-10.1-20130312-UNOFFICIAL-hummingbird
Upstream change: Added Quick Launch Shortcuts. To activate, press Home Button and slowly slide upward (or long press Home) until navigation ring is shown. To perform an action, continue sliding to one of the 3 target icons and release after the item is selected. To add/change actions, go to Settings->System->Quick launch shortcuts.
Switched to omapzoom frameworks/av and hardware/libhardware_legacy *** TEST ****
cm-10.1-20130310-UNOFFICIAL-hummingbird
cm-10.1-20130309-UNOFFICIAL-hummingbird
cm-10.1-20130307-UNOFFICIAL-hummingbird
cm-10.1-20130306-UNOFFICIAL-hummingbird
Upstream change: superuser now integrated with ROM settings.
cm-10.1-20130305-UNOFFICIAL-hummingbird
cm-10.1-20130304-UNOFFICIAL-hummingbird
cm-10.1-20130303-UNOFFICIAL-hummingbird
cm-10.1-20130302-UNOFFICIAL-hummingbird
cm-10.1-20130228-UNOFFICIAL-hummingbird
cm-10.1-20130227-UNOFFICIAL-hummingbird
cm-10.1-20130225-UNOFFICIAL-hummingbird
cm-10.1-20130223-UNOFFICIAL-hummingbird
cm-10.1-20130222-UNOFFICIAL-hummingbird
cm-10.1-20130221-UNOFFICIAL-hummingbird
cm-10.1-20130220-UNOFFICIAL-hummingbird
cm-10.1-20130219-UNOFFICIAL-hummingbird
Upstream change: reboot to recovery, bootloader, etc is hidden from power menu by default. To enable as before, go to Developer Options and enable Advanced Reboot. Also no longer shown in power menu while in lock screen.
cm-10.1-20130217-UNOFFICIAL-hummingbird
2D hardware blitter finally fully enabled (Updated Vivante GC320 2-D core driver to a more recent version). *** TESTING ***
Following upstream staging from Android 4.2.1 to 4.2.2. *** UNSTABLE ***
cm-10.1-20130213-UNOFFICIAL-hummingbird
cm-10.1-20130212-UNOFFICIAL-hummingbird
cm-10.1-20130210-UNOFFICIAL-hummingbird
cm-10.1-20130209-UNOFFICIAL-hummingbird
cm-10.1-20130208-UNOFFICIAL-hummingbird
cm-10.1-20130207-UNOFFICIAL-hummingbird
MTP showing wrong contents fixed.
cm-10.1-20130205-UNOFFICIAL-hummingbird
cm-10.1-20130204-UNOFFICIAL-hummingbird
cm-10.1-20130203-UNOFFICIAL-hummingbird
Added reboot to bootloader and bootmenu.
Replaced Reboot Menu with the following texts: Reboot, CWM Recovery, BN Stock ROM and Cyanoboot Menu.
Tweaked to increase audio volume.
cm-10.1-20130203-UNOFFICIAL-hummingbird
Minor fixes.
cm-10.1-20130202-UNOFFICIAL-hummingbird
Inverted tilt angle fixed.
Better screen rotation.
cm-10.1-20130130-UNOFFICIAL-hummingbird
vold patched to auto mount last vfat partition.
Also works with the new sdcard installation (dual boot/hybrid) posted in this thread.
cm-10.1-20130128-UNOFFICIAL-hummingbird
Tablet UI now reenabled and can be selected from settings. Thanks Team sgt7.
To switch: System->Status Bar->Tablet UI.
cm-10.1-20130127-UNOFFICIAL-hummingbird
Slower surfaceflinger but with better and 'well-behaved' UI.
cm-10.1-20130126-UNOFFICIAL-hummingbird
TESTING hwcomposer ver 1.1 - very fast UI and with better 3D performance.
Reverted all WIFI updates pre 1/14.
cm-10.1-20130121-UNOFFICIAL-hummingbird
Added tun.ko as suggested by robertchow.
cm-10.1-20130118-UNOFFICIAL-hummingbird
Recommit WIFI Auto connect option reverted by upstream.
cm-10.1-20130117-UNOFFICIAL-hummingbird
MAC Address fixed.
Revert WIFI commit by upstream to solve connection problem.
cm-10.1-20130114-UNOFFICIAL-hummingbird.zip
Updated hwcomposer to more recent version. Should be faster and have more butter smooth UI.
cm-10.1-20130113-UNOFFICIAL-hummingbird.zip
USB computer connection menu back in Storage setting.
Issue: Contents of Internal and SD card are swapped when shown using MTP.
cm-10.1-20130109-UNOFFICIAL-hummingbird.zip *** BETA ***
Wifi battery drain fixed.
It seems more deep sleep friendly.
cm-10.1-20130107-UNOFFICIAL-hummingbird.zip *** ALPHA ***
Microphone now working.
Still not working:
MTP
cm-10.1-20130106-UNOFFICIAL-hummingbird.zip *** ALPHA ***
Bluetooth (bluedroid) now functional.
Still not working:
Microphone
MTP
cm-10.1-20130105-UNOFFICIAL-hummingbird.zip *** ALPHA ***
Multiuser capabilities of JB 4.2.1 are now enabled. For more info read this article.
Still not working:
Bluetooth
Microphone
MTP
cm-10.1-20130104-UNOFFICIAL-hummingbird.zip *** ALPHA ***
Solved FC due to mounting problem in init.rc.
EMMC and SD Card are properly mounted now.
Reboot to recovery now working.
Initial Build: cm-10.1-20130103-UNOFFICIAL-hummingbird.zip *** ALPHA ***
Bluetooth and microphone not yet working.
For Performance and Development settings, go to 'About Tablet' and touch 'Build Number' many times to enable the missing options.
CWM Flashable CM10 ROM to sdcardcm-10-20121227-UNOFFICIAL-hummingbird.zip :good: *** STABLE ***
Merged with CM10 - lock screen can now be rotated.
Updated kernel - Reverted mmc patch to B&N 2.0.2 but retained other patches.
Updated SGX to DDK Release [email protected]
cm-10-20121225-UNOFFICIAL-hummingbird.zip
Merged verygreen audio lib patch
Updated kernel to B&N 2.0.5
Initial Build based on verygreen source: cm-10-20121224-UNOFFICIAL-hummingbird.zip
Linaro Build: cm-10-20121229-UNOFFICIAL-hummingbird-linaro.zip *** TEST BUILD ***
Same as the 20121227 build below except built using the Linaro 4.7 (12.12) toolchain.
*With bluetooth problems
Since this rom uses cyanoboot, you can use the menu to choose boot option (currently available options are SD normal and SD recovery)
Source Downloads: cyanoboot & kernel
See video here: CM10 in Nook HD
Notes/Issues:
If your HD boot directly to B&N rom upon turning it on (cold boot), do not press the shutdown button. Use adb and issue "adb reboot" or install app to reboot the stock. It should now boot from SD (warm boot).
For Windows users attempting to copy image file for an initial install or subsequent updates:
Under cwm, partition 5 (second vfat) will/can not be mounted by the OS when SD is inserted to your computer so either dual boot Linux or run in a VM (see post #45 of this thread by anthony062991) or use adb to transfer file.
When CM10 is already installed and running, enable MTP under USB storage setting. CM10SDCARD will be automatically mounted as media device where you can copy the zip file.
For working/non-working CM10 SD cards see this post.
For rooting the device see these threads by leapinlar: using adb and cwm recovery.
Thanks to verygreen, fattire, leapinlar and sgt7 team for their works.
mount error
I burned the image to a Sandisk sd card. The Nook cold booted into Cyanoboot and CWM. However, when I try mount /sdcard, I get an error. Has anyone encountered that?
Windsor1959 said:
I burned the image to a Sandisk sd card. The Nook cold booted into Cyanoboot and CWM. However, when I try mount /sdcard, I get an error. Has anyone encountered that?
Click to expand...
Click to collapse
You need to format that partition as fat32 in win or Linux.
Sent from my SGH-T989 using Tapatalk 2
---------- Post added at 07:18 PM ---------- Previous post was at 07:17 PM ----------
Works good for my team 16th class 10 card
Sent from my SGH-T989 using Tapatalk 2
angellsl said:
You need to format that partition as fat32 in win or Linux.
Sent from my SGH-T989 using Tapatalk 2
Do you mean the entire SD card before I burn the CWM image, or the unused partition after I burn it? Thanks!
sent from my Nook HD using xda premium
Click to expand...
Click to collapse
Windsor1959 said:
angellsl said:
You need to format that partition as fat32 in win or Linux.
Sent from my SGH-T989 using Tapatalk 2
Do you mean the entire SD card before I burn the CWM image, or the unused partition after I burn it? Thanks!
sent from my Nook HD using xda premium
Click to expand...
Click to collapse
After you cannot mount /sdcard within CWM, pop the card out of your nook, and plug it to your computer, identify the partition (usually the largest one not formatted), format it to fat32
Click to expand...
Click to collapse
I used EASEUS and formatted that partition. Now I have CM10! Thanks! It will be fun to play around with it and see how it does.
In app volume control does not work, e.g., Netflix
Sent from my Barnes & Noble Nook HD using Tapatalk 2
angellsl said:
In app volume control does not work, e.g., Netflix
Sent from my Barnes & Noble Nook HD using Tapatalk 2
Click to expand...
Click to collapse
Since this is based from verygreen CM10 source, anything not working in its big brother will also not work in our HD.
From verygreen thread it is stated:
Things that I know are not working:
- volume buttons don't produce any sound until some app does sound output first, even though volume is adjusted.
- there is no "Extended Desktop" possibility in Power Menu (this allows to hide taskbar)
bokbokan said:
Since this is based from verygreen CM10 source, anything not working in its big brother will also not work in our HD.
From verygreen thread it is stated:
Things that I know are not working:
- volume buttons don't produce any sound until some app does sound output first, even though volume is adjusted.
- there is no "Extended Desktop" possibility in Power Menu (this allows to hide taskbar)
Click to expand...
Click to collapse
Volume control is fixed in the latest by verygreen
Sent from my Barnes & Noble Nook HD using Tapatalk 2
I tried YouTube and a couple of games. Volume control seems fine. I'm impressed with the overall improvement in responsiveness over stock. After losing root thanks to the dreaded 2.0.5, this is a well-timed Christmas gift! Haven't found any bugs yet.
Sent from my Barnes & Noble Nook HD using xda premium
angellsl said:
Volume control is fixed in the latest by verygreen
Click to expand...
Click to collapse
note my source lib only knows about ovation (Nook HD+) ATM, as I only have that.
I need tinymix output from Nook HD to add support (on the rom that runs stock audio lib).
The tinymix output should be collected in these situations:
- right after boot
- with headphones plugged
- while doing a recording in voice recorder
Hey, this worked great! Took a little while to get the card partitioned right, thanks to human error, but once I got that down, works like a charm!
Any way to enable tablet UI for Nook HD?
angellsl said:
Any way to enable tablet UI for Nook HD?
Click to expand...
Click to collapse
Change ro.sf.lcd_density to 200 or below in /system/build.prop
verygreen said:
note my source lib only knows about ovation (Nook HD+) ATM, as I only have that.
I need tinymix output from Nook HD to add support (on the rom that runs stock audio lib).
The tinymix output should be collected in these situations:
- right after boot
- with headphones plugged
- while doing a recording in voice recorder
Click to expand...
Click to collapse
I'm merging your recent commits to my local tree. Will be checking tinymix and apply appropriate changes if needed.
Will consult with you regarding this matter if you wont mind.
Regards
Attached are the results from tinymix
I tried to mount /sdcard
"Go to "mounts and storage", choose "mount /sdcard"."
It says:
Error mounting /sdcard!
My sdcard is formatted as fat32 also with SDFormatter?
sdcard is 16GB class 10 if that matters?
anthony062991 said:
I tried to mount /sdcard
"Go to "mounts and storage", choose "mount /sdcard"."
It says:
Error mounting /sdcard!
My sdcard is formatted as fat32 also?
Click to expand...
Click to collapse
If you follow verygreen instruction, your sd card will have five partition, the 5th partition formatted as fat32.
You should be able to use adb while in recovery and check with fdisk. You should see something like this
Code:
/dev/block/mmcblk1p1 * 1 15 120456 c Win95 FAT32 (LBA)
/dev/block/mmcblk1p2 16 113 787185 83 Linux
/dev/block/mmcblk1p3 114 363 2008125 83 Linux
/dev/block/mmcblk1p4 364 3822 27784417+ 5 Extended
/dev/block/mmcblk1p5 364 3822 27784386 c Win95 FAT32 (LBA)
bokbokan said:
If you follow verygreen instruction, your sd card will have five partition, the 5th partition formatted as fat32.
You should be able to use adb while in recovery and check with fdisk. You should see something like this
Code:
/dev/block/mmcblk1p1 * 1 15 120456 c Win95 FAT32 (LBA)
/dev/block/mmcblk1p2 16 113 787185 83 Linux
/dev/block/mmcblk1p3 114 363 2008125 83 Linux
/dev/block/mmcblk1p4 364 3822 27784417+ 5 Extended
/dev/block/mmcblk1p5 364 3822 27784386 c Win95 FAT32 (LBA)
Click to expand...
Click to collapse
I am following his instruction step by step?
I can boot into CWM without any problems. I just can't mount sdcard or flash any zips?
As far as ADB it's not working in CWM at all? My device is not even listed?
EDIT:
How do you check with fdisk?
anthony062991 said:
I am following his instruction step by step?
I can boot into CWM without any problems. I just can't mount sdcard or flash any zips?
As far as ADB it's not working in CWM at all? My device is not even listed?
Click to expand...
Click to collapse
Can you pull out the card from the device and check the sd partitions in your computer.
Let me know
bokbokan said:
I'm merging your recent commits to my local tree. Will be checking tinymix and apply appropriate changes if needed.
Will consult with you regarding this matter if you wont mind.
Click to expand...
Click to collapse
Ok, routing seems to be totally same as hummingbird, so I added support to the lib ,should be in github now.
Related
So I created a new thread for this so I can edit the first post for release-info.
This is the old thread:
http://forum.xda-developers.com/showthread.php?t=1133866
Please note that the multiboot-feature will be removed if you update your real system.
The virtual systems will stay on the sdcard so just reinstall the mod and you can boot your virtual systems again
Changelog:
Code:
[B]v0.8:[/B]
- addon.d (Multiboot will be kept on ROM-Update)
- working reboot recovery inside multiboot-rom(will boot directly into the recovery for that rom)
- working reboot into bootmenu inside multiboot-rom
- security-fixes
- TLS-support
- fixed sdcard-problems for NAND-system
[B]v0.7:[/B]
- added integration in touchbootmenu. This is no compatibility-patch - since now multiboot can only be used in combination with touchbootmenu
[B]v0.6.1:[/B]
- fixed some memory-leaks in kernel-module
- fixed stupid bug which prevented creating backups on first start
[B]v0.6:[/B]
- new hook-method with kernel-side code which should be the solution to most rom-problems
- fixed a bug which prevented mounting cache-partition inside recovery
- fixed installer-bug when TouchBootmenu is used on NAND
- reboot to recovery/bootmenu does not work for now. will be fixed in future
[B]v0.5.5:[/B]
- support for Stock-roms with Greenbreadmod
- added version-file(for updater which comes soon)
[B]v0.5.4:[/B]
- fixed problem with install-script
[B]v0.5.3:[/B]
- support for TWRP recovery
- fixed problem with virtual systems with names longer than 9 chars
- don't change 2ndBoot-script for bootmenus with 2ndSystem-support
- show graphical error-message when error was detected and copy log to "/cache/multiboot/error.log"
- experimental support for booting stock-roms
[B]v0.5.2:[/B]
- more configurable(via config-file)
- fixed error-detection. On early errors you will get back to bootmenu
- fix boot-problems for some roms
[B]v0.5.1:[/B]
- fixed crash of GUI when choosing recovery
- fixed bug which prevented creating important images on first boot
- virtual systems now are using nand-backups with real data so you could install backups of virtual systems on NAND
- installer sets default bootmode to 2nd-boot
- added recovery-option for NAND
- patch background-image of virtual recovery so you see if you are flashing real or virtual system
- reboot system if you click "Go Back" in virtual recovery(until I found a solution for going back to multiboot-GUI)
[B]v0.5:[/B]
- better protection against unwanted changes on real partitions(thanks wizwin)
- fix Phone for for GB-kernel(thanks quarx)
- set props so apps can detect if phone started with multiboot or not(for future versions of multiboot-manager)
- reboot into bootmenu/recovery now works
ATTENTION: reboot into recovery will open recovery for REAL system!!!
- added GUI for choosing which (virtual) system you want to boot
[B]v0.4:[/B]
- replacing all references to real system with stub-image(will be automatically created at /sdcard/fsimage/stub.img).
Now the recovery for the virtual system should be completely abstracted and it shouldn't make any changes to the real system
- a PDS-backup will be created and injected because it's needed by android-system and above change removes the reference
[B]v0.3/v0.3.1:[/B]
- moving original system-partition to another location instead of lazy unmount so she will be accessible in 2ndBoot-system and will not be busy
- fixed recovery to improve installer-zip compatibility. MIUI works now
- internal script-changes
[B]v0.2:[/B]
- "Install zip from SDcard" works now
- changed hook-method so it works with more ROM's(including ICS)
[B]v0.1:[/B]
First release
Source:
https://github.com/M1cha/DefyMultiboot
Download:
http://forum.xda-developers.com/attachment.php?attachmentid=1289953&d=1346244428
Installation:
1. Download zip-file and copy to sdcard
2. create 3 filesystem-images in ext3-format and copy them to /sdcard/multiboot/NAME with the names system.img, data.img and cache.img.
Please replace NAME with the folder-name of your virtual system(you have to create this)
You can download ready-to-use images from here:
http://www.multiupload.com/VY3U4IXRO1
2. install zip-file in CWM
Some info:
- The menu-entry "Lastest Recovery" is no longer supported and will affect your real system!
- boot the System-Chooser with the 2ndBoot-option in bootmenu
Bugs:
- Data-Wipe deletes android_secure
Donate:
Developing Multiboot makes much fun and I really like the results but takes much time, so feel free to donate a beer.
Hey,
i have no "Lastest Recovery" but a "Custom Recovery"
Can i install your script or does it not work with this version of the Bootmenu?
Which rom do you have installed?
I will check if it's compatible.
Thanks for the fast answer
i installed the CM7.2 Nightly "cm72-111125.0850-NIGHTLY-Defy"
The nightlys should always have the newest version of bootmenu.
Where you downloaded the nightly? I only could find "cm72-111123.1710-NIGHTLY-Defy.zip".
But generally it would work if you install but the problem is that you will never be able to change your real system because recovery will only make changes to the virtual one.
That bootmenu has 2 recovery-entrys is a lucky thing which I use as trick so I don't need to modify bootmenu
But when bootmenu-integration is done and you have an old version you will have to update bootmenu.
updated to v0.4
See first post for more info
Gonna try this now. I downloaded your empty .img files but how do I create my own img's on Win7? And what do you think is the smallest size I can make them safely to use with MIUI or ICS?
I don't know how you can create the images on windows, sry.
Maybe I can write a little App which does this directly on Android.
I have to admit that the images I uploaded are a little bit oversized.
system needs max 200MB
cache and data depends on your usage.
I would choose a minimum of 100MB for data and cache. If you plan to install many Apps you should make the data-partition over 300-500MB
Doesn't matter, instructions for Linux would do too
Hmm..oversized but no prob downloading because they were empty, only transferring via USB takes time. 200 MB for system and data and 100 for cache sounds good I'll make them myself if you can give me the instructions, I have Ubuntu.
App to do this on the phone itself sounds good, makes it even faster, no transferring from PC Thanks for your work
The Problem is that I can't find a mkfs.ext3-binary for Android
Maybe I'll extract it from another phone which contains this.
But as of now, here are the instructions:
Code:
dd if=/dev/zero of=./system.img bs=1000000 count=200
mkfs.ext3 ./system.img
The number 200 specifies the size in MegaBytes. I hope this will help you so far
Sure does
But like the poster above said, CM7 latest nightiles contain Custom Recovery, Stable Recovery, and Stock Recovery in the Bootmenu option for recovery. So Custom Recovery = Latest Recovery for your tool? I remember it used to say Latest recovery a few months back, dunno when that changed.
Oh, now I unsterstand what he wants to say.
I thought there is ONLY "custom recovery".
But if there are two recovery's it's ok to install. So you can use "Custom Recovery" for your virtual filesystem.
I'm downloading the CM7-source so I can extend and compile bootmenu and everything will be easier.
But with a download-speed of 170KiB/s this will take a long time
How fast is the virtual system? Could it be laggy because it is loaded from the sd-card?
the time from bootmenu to the boot-process itself takes a little bit time sometimes if I'm debugging.
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
m11kkaa said:
But normally the booted system is in normal speed for me.
I think this depends on the speed of your sd-card and the usage of your apps.
Click to expand...
Click to collapse
What class brand capacity card do you use?
I'll be trying with miui and ics tonight
Sent from my MB525 using XDA App
I don't know which class my card is because there is no label. It's completely black
But I don't think I have the best one(maybe class 2 or something else?)
An APP for windows to create ext-3 partitions http://forum.xda-developers.com/showthread.php?t=824154
download link: http://www.multiupload.com/SV7SOY33MQ
I have a 8GB class 4 card. Will test it in a few minutes with CM7 as real system and ICS as virtual system. Do you know what happen if I restore a backup in the real system? As far as I know a backup will override the bootmenu, too. Or am I wrong?
Yes, that will override the bootmenu.
But your virtual system stays on the sdcard.
You just need to patch again bootmenu with the downloaded "defy_multiboot_vX".
I'm on CM7 latest nightly and got boot loop when i tried to install Galnet MIUI ICS on virtual system. Could you fix it?
After many sleepless nights and many wasted weekends we are proud to present
Android 4.0.3 / ICS for Toshiba Folio 100 - Alpha 4
The devlepment of this ROM has been discontinued in flavor for Jelly Bean:
http://forum.xda-developers.com/showthread.php?t=1864774
This is the current state of CyanogenMod 9 for the Toshiba Folio 100
DOWNLOAD:
When using a wrong recovery for the installation the device may not boot any more and will require manual fix. Please use the recovery provided by Nopy.
Alpha 5:
https://github.com/downloads/DerArt...0-2012.04.21-betelgeuse-UNOFFICIAL-signed.zip
MD5: cb59fe654e68762112d726e274e65de3
Bluetooth is broken in Alpha 5 - if you need it please use an older release.
Old versions:
Alpha 4:
https://github.com/downloads/DerArt...0.0-RC0-2012.03.04-betelgeuse-KANG-signed.zip
MD5: 01b8c1f1c8f7e836770601ce7923e739
Alpha 3:
https://rapidshare.com/files/1004577502/update-cm-9.0.0-RC0-2012.02.21-betelgeuse-KANG-signed.zip
https://github.com/downloads/DerArt...0.0-RC0-2012.02.21-betelgeuse-KANG-signed.zip
MD5: 181ee4399796c2891759f8377fce6e82
Alpha 2:
https://rapidshare.com/files/1100655268/update-cm-9.0.0-RC0-2012.02.19-betelgeuse-KANG-signed.zip
https://github.com/downloads/DerArt...0.0-RC0-2012.02.19-betelgeuse-KANG-signed.zip
MD5: 67ad6033ee965c10d5ab7c67a87b4ba2
Alpha 1:
https://rapidshare.com/files/2674919483/update-cm-9.0.0-RC0-2011.01.29-betelgeuse-KANG-signed.zip
https://github.com/downloads/DerArt...0.0-RC0-2011.01.29-betelgeuse-KANG-signed.zip
GOOGLE APPS:
http://goo-inside.me/gapps/gapps-ics-20120224-signed.zip
MD5: 11b5763810edb732379d39b6df9ccbcf
SOURCE CODE:
The git tree is here:
https://github.com/DerArtem/android_device_toshiba_betelgeuse
https://github.com/nopy/android_device_toshiba_betelgeuse
Kernel sources:
https://github.com/DerArtem/android-tegra-nv-2.6.39
Things that work:
Kernel 3.1
HQ Video acceleration
Audio over Speaker
Audio over Headset
Audio over HDMI
HDMI Video
Camera - reported as front and back camera
3D acceleration
Bluetooth
LP0 Suspend
Wakeup from LP0 Suspend
Internal USB
USB Host Port
Acceleration Sensor
Power Button
Volume Keys
Touch Screen
Wifi
Brighness regulation
Internal and external SD
3G using Huawei dongles (may need some improvements)
Vibrator
miniUSB Hotplug
Docking station
Audio jack switch
Internal microphone (sound is little quite yet)
A2DP Audio over Bluetooth
Things that don't work yet:
SCO Audio over Bluetooth
Digital Compass (Android lib not finished yet - Kernel part finished)
Touch Buttons (no interest to make them work as they are not required for ICS)
Remote control - initial support added - need more inventigation
Power cable plug detection can take up to 10 seconds
Some people report to have a bad HDMI audio
Audio may knocking sometimes
Installation:
Install the recovery provided by Nopy using fastboot.
Copy everything on the the SD card and install the ROM using the recovery.
You may have to reformat all your partitions using the recovery.
Do a full wipe before installing this ROM.
Credits:
DerArtem
Nopy
The Cyanogenmod Team
The other Tegra Dev Teams where we have borrowed code (Adam, GTab, Vega, AC100)
And everybody else who I might have forgotten
If you like this ROM please don't hesitate to hit the donate and thanks button.
Recovery
- IMG format : Flash this recovery using fastboot https://rapidshare.com/files/1261762467/cwm-recovery-5.5.0.4.img
Boot the device using the power + power + power + volume up key combo , then on the PC do in command line :
Code:
fastboot flash recovery cwm-recovery-5.5.0.4.img
- ZIP format : Flash using previous clockworkmod recovery https://rapidshare.com/files/2672749064/cwm-recovery-5.5.0.4.zip
- ZIP format for original recovery : put it in your sdcard, rename it to update.zip , and launch original recovery ( Power, vol+ , then vol+, vol-, vol+ ) https://rapidshare.com/files/1226631729/for-orig-recovery.zip
!!! WARNING !!! Don't reflash this update if your are already on 5.5.0.4
!!! WARNING !!! Don't flash another rom update with this recovery
This recovery use a new mapping, use power to select.
Changelog
A1 ( 29/01/2012 )
Initial alpha
A2 ( 19/02/2012 )
- Switched to audio lib from ventana ( may be better audio over HDMI )
- Better wifi suspend
- Switched to wpa supplicant 8
- Vibrator
- Fixed crazy power button
- Docking station detection
- Tablet identified as Galaxy tab
- 120 dpi by default
- Usb gadget
- Upstream changes
- USB 3G Huawai
A3 ( 21/02/2012 )
- Back to custom audio lib
- Wifi resume fixed
- Headset switch
- Microphone
- Resume in one click on power button
A4 ( 04/03/2012)
- Switch to 3.1 kernel
- Switch to xoom identity
- Folio device setting app ( only allow to choose density atm )
- cifs, ntfs, xbox controller modules
- External USB camera support , and if no usb camera is present , front camera reported twice
- folio does not turn off at 15% charge anymore
- A2DP audio
I just had to say thank u for all yours work thanks to you i have a tablet not a big and slow phone!
We have to wipe data to?
Are gapps inclued?
That's a nice rom. Al things that I use work on this rom. One thing I hope that will work soon is 3G using Huawei dongles.
Thanks for al your work.
anjo88 said:
I just had to say thank u for all yours work thanks to you i have a tablet not a big and slow phone!
We have to wipe data to?
Are gapps inclued?
Click to expand...
Click to collapse
It depends on what version you are comming from - but in generally: Yes a wipe is required or strange things may happen
I have attached google apps. It must be installed seperatly.
Thank you so much for your hard work on this!
I had a problem installing the rom - don't know why, I can't think what I could have done wrong, full wipe as usual. Now the internal sd partition E: seems to be broken, I cannot mount it through cwm and can't access to the recovery I made. I tried installing the last cm9 from the external sd, it boots but then an android notification pops up with the message "encryption unsuccessful", telling me to reset the tablet.
Any hints how could I fix this? Thank you very much!
-Nacho said:
Thank you so much for your hard work on this!
I had a problem installing the rom - don't know why, I can't think what I could have done wrong, full wipe as usual. Now the internal sd partition E: seems to be broken, I cannot mount it through cwm and can't access to the recovery I made. I tried installing the last cm9 from the external sd, it boots but then an android notification pops up with the message "encryption unsuccessful", telling me to reset the tablet.
Any hints how could I fix this? Thank you very much!
Click to expand...
Click to collapse
Same problem here. Looking for the solution.
DerArtem said:
It depends on what version you are comming from - but in generally: Yes a wipe is required or strange things may happen
I have attached google apps. It must be installed seperatly.
Click to expand...
Click to collapse
w
Wich cwm must we use?... need fastboot?.
THANX FOR U WORK
Edit: Using recovery from second post worked!
In case it helps a picture of the moment it starts hanging- sorry for the bad quality!
Thanks so much, but please make the touch buttons work because, even if they're not required for ICS, they're still a good add.
I hope it won't be hard to do so.
-Nacho said:
In case it helps a picture of the moment it starts hanging- sorry for the bad quality!
Click to expand...
Click to collapse
Looks like you have used a wrong/bad recovery. Nopy is currently working on a update.zip with the new recovery.
now I'm getting "Magic value mismatch" so I think I'm one of those that his folio doesn't run anymore, even when flashing other roms. Will the new recovery fix this? or flashing a rom via fastboot could fix it?
I managed to get my Folio back after wrong recovery error.
I just flashed CWM Recovery v3.0.2.8 (which apparently includes a MBR) using fastboot.
After that, I could flash CWM recovery v5.0.2.7 and CM9-r4 2.6.32 rom.
Now I am waiting for the new recovery from nopy to use 2.6.39 build, as CWM v3.0.2.8 can't flash it (assert failed on product.device folio 100)
huh I could fix it flashing foliomod via fastboot
This is simply awesome!!!! Thank you very much!
I own both remote and docking and I'll let you know how them works when this awesomeness will be available for the masses
DerArtem said:
Looks like you have used a wrong/bad recovery. Nopy is currently working on a update.zip with the new recovery.
Click to expand...
Click to collapse
Which recovery is supposed to work for flashing this one ?
new recovery is now on 2nd post by nopy!
@DerArtem and @nopy: do not forget to add the donate button.
roglio said:
@DerArtem and @nopy: do not forget to add the donate button.
Click to expand...
Click to collapse
It's already there in the .html version of xda
Hello,
Based off of Harsh 3.0.41 github
Changelog:
Version 0830 (MMDD)
OC/UV - 1.375GHz
Adjusted frequencies/voltages, if you have any suggestions...feel free to provide feedback...
Code:
750-250/800-438/850-625/900-813/950-1000/1035-1125/1120-1250/1205-1375
SetCPU users: I noticed that it kept the second core active...after I uninstalled, all was good Antutu CPU master is good alternative
Version 0821 (MMDD)
Commented out ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d (you may edit it to re-enable them if you wish)
EASY METHOD! - Will work for Temasek Kang – (cm7kang-G2x-133), CM 7.2 Stable (cm-7.2.0-p999), Eaglesblood 2.3.7 (EGB 02-13-12), HFP V2.2 (hellfirephoenixV2.2) and ROMs that have the GB vold.fstab that matches
ALL OTHER ROMs CANNOT use this version...for now...
Version 0820 (MMDD)
Linux 3.0.41
Compiled with Code Sourcery (CS) and Linaro (LIN) toolchains, choose your poison...
OC/UV - 1.4GHz p @ airnique23)
V(R) I/O Scheduler set as default (can be changed)
Includes ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d
Installation:
Recommended
CM 7.2 Stable...
CWM 5.0.2.0 (REQUIRED)
EASY METHOD
Will work for Temasek Kang – (cm7kang-G2x-133), CM 7.2 Stable (cm-7.2.0-p999), Eaglesblood 2.3.7 (EGB 02-13-12), HFP V2.2+ (hellfirephoenixV2.2 & 2.3) and ROMs that have the GB vold.fstab that matches
1. MAKE A BACKUP FIRST!!! Especially the internal memory (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Boot into CWM
4. Clear cache/dalvik cache
5. Install
6. Reboot (will take awhile to boot...be patient)
ALTERNATIVE (ALT) METHOD
1. MAKE A BACKUP FIRST!!! Especially the internal memory (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Please check /system/etc/vold.fstab and your internal sdcard (emmc) has an 8 instead of a 9 (change to 8 if its a 9 and make sure vold.fstab permissions are rw-r--r-- after saving)
4. Boot into CWM
5. Clear cache/dalvik cache
6. Install
7. Reboot (will take awhile to boot...be patient)
Known bugs:
Reboot/Reboot recovery work 90% of time. (same as Harsh's)
Button Panel LED backlights cannot be turned off (will cause phone to lag...BAD...still looking into it)
Wifi Calling app may get an Invalid Sim error after first installing the kernel (if you use it)...a restart fixes this
Titanium Backup might freeze when you run it after you flash this, go to the Applications > Force stop and clear data...should be good to go...it may affect other applications that reference partitions FYI...
Have slow GPS locks? try this
Important!
Be mindful when you OC/UV, all our phones are different, experiment to find your phones optimal setting...
Don't like the kernel?
Complete Steps 4 and 5, and reinstall your ROM you are using to avoid any issues...
What's the different between Code Sourcery and Linaro?
Code Sourcery and Linaro
Lagging after installing?
You probably already have a ROM or an app that runs tweaks...delete 95vrooom and reboot...may have to clear dalvik and cache and fix permissions if your are experiencing data drops...(thanks nycelitemaster & BigDog!)
Just be aware if you have disabled the LED button backlights...you will experience serious lagging...
Received "Damaged SD Card" message or stuck in recovery?
You will have to NVFlash back to stock...then NVFlash CWM 5.0.2.0...then you can restore your backup or reinstall your ROM...(thanks hypemanisus!)
I don't wanna NVFlash 5.0.2.0, what can I do?
CWM 5.0.2.8 will break recovery...I have not tested the other recoveries like CWM touch or TWRP...be warned...you MAY need to perform the "Damaged SD Card" steps...
Why do I have to edit the vold.fstab file? I never had this issue with ICS
ICS vold.fstab already has the 8...
Code:
#######################
## Regular device mount
##
## Format: dev_mount
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc 8 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
GB vold.fstab has a 9...
Code:
#######################
## Regular device mount
##
## Format: dev_mount
## label - Label for the volume
## mount_point - Where the volume will be mounted
## part - Partition # (1 based), or 'auto' for first usable partition.
## - List of sysfs paths to source devices
######################
dev_mount sdcard /mnt/sdcard auto /devices/platform/tegra-sdhci.2/mmc_host/mmc1
dev_mount emmc /mnt/emmc 9 /devices/platform/tegra-sdhci.3/mmc_host/mmc2
Compared to recovery.fstab...for GB and ICS...they're the same...
Code:
# mount pointfstypedevice[device2] fstype2
/recoveryemmc/dev/block/mmcblk0p5
/bootemmc/dev/block/mmcblk0p5
/cacheext4/dev/block/mmcblk0p2
/dataext4/dev/block/mmcblk0p7
/sdcardvfat/dev/block/mmcblk1p1
/emmcvfat/dev/block/mmcblk0p8
/systemext4/dev/block/mmcblk0p1
Still having issues?
Provide the ROM you are using and what the issue is...and a log if possible...
Credits:
Harsh (for allowing me to share)
TeamDouche
nycelitemaster (for testing...thanks sir!)
Everyone else who made 3.0 possible...
djvoleur said:
Hello,
Based off of Harsh 3.0.41 github
Changelog:
Version 0820 (MMDD)
Linux 3.0.41
Compiled with Code Sourcery (CS) and Linaro (LIN) toolchains, choose your poison...
OC/UV - 1.4GHz p @ airnique23)
V(R) I/O Scheduler set as default (can be changed)
Includes ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d (If you are experiencing lags, try deleting 95vrooom and reboot)
Installation:
Recommended but not required
CM 7.2 Stable
CWM 5.0.20
(If you are having an issue with the kernel, please provide what ROM and CWM version or other recovery version you are using)
1. MAKE A BACKUP FIRST!!! (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Please check /system/etc/vold.fstab and your internal sdcard (emmc) has an 8 instead of a 9 (change to 8 if its a 9 and make sure vold.fstab permissions are rw-r--r-- after saving), especially if this is your first time otherwise you will have to NVFlash back to stock...
4. Boot into CWM
5. Clear cache/dalvik cache
6. Install
7. Reboot (will take awhile to boot...be patient)
Known bugs:
Reboot/Reboot recovery work 90% of time. (same as Harsh's)
Button Panel LED backlights cannot be turned off (will cause phone to lag...BAD...still looking into it)
Wifi Calling app may get an Invalid Sim error (if you use it)...a restart fixes this
Titanium Backup might freeze when you run it after you flash this, go to the Applications > Force stop and clear data...should be good to go...it may affect other applications that reference partitions FYI...
Have slow GPS locks? try this
Important!
Be mindful when you OC/UV, all our phones are different, experiment to find your phones optimal setting...
Don't like the kernel?
Complete Steps 4 and 5, and reinstall your ROM you are using to avoid any issues...
Credits:
Harsh (for allowing me to share)
TeamDouche
nyelitemaster (for testing...thanks sir!)
Everyone else who made 3.0 possible...
Click to expand...
Click to collapse
Thanks, will try linaro build and report back with results.
*linaro working like a champ
Sent from my LG-P999 using xda app-developers app
HFP v2.2 and system boots fine. When it comes up I get a damaged SD Card message which is in fact untrue. Rebooted, cleared dalvik and cache, rebooted again all with no change. Flashed back the the backup I made prior to flashing this kernel and all is well.
Darkseider said:
HFP v2.2 and system boots fine. When it comes up I get a damaged SD Card message which is in fact untrue. Rebooted, cleared dalvik and cache, rebooted again all with no change. Flashed back the the backup I made prior to flashing this kernel and all is well.
Click to expand...
Click to collapse
This happens when you don't complete step 3...
I did that and it still showed Damaged SD card. Was able to restore from backup and all is well. Dunno maybe dumb luck?
Darkseider said:
I did that and it still showed Damaged SD card. Was able to restore from backup and all is well. Dunno maybe dumb luck?
Click to expand...
Click to collapse
What recovery are you using?
Sent from my LG-P999 using Tapatalk 2
Oh sh t.... will be trying it out...ty harsh and dj
Sent from my LG-P999 using xda app-developers app
Using linaro
Sent via G2X-SINGH-UI
nycelitemaster said:
Using linaro
Sent via G2X-SINGH-UI
Click to expand...
Click to collapse
Hehe
Sent from my LG-P999 using Tapatalk 2
I wanna try this out, but I hate the LED notifications
Sent from my LG-P999 using xda premium
Tried CS version, changed void.fstab (permissions verified), wiped dalvic and cache. Froze at boot screen of the ROM, pulled battery. It did it again. Flashed faux's current kernel, booted fine. Harsh's kernels don't seem to like me anyway. Oh well.
Sent from my Android powered coffee coaster.
sleepingturtle said:
Tried CS version, changed void.fstab (permissions verified), wiped dalvic and cache. Froze at boot screen of the ROM, pulled battery. It did it again. Flashed faux's current kernel, booted fine. Harsh's kernels don't seem to like me anyway. Oh well.
Sent from my Android powered coffee coaster.
Click to expand...
Click to collapse
What recovery do you have?
FatalityBoyZahy said:
I wanna try this out, but I hate the LED notifications
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
You can turn off the LED notifications...it's just when the phone is on...or there's a response to the screen...or when the screen shuts off...that i'm still looking into
djvoleur said:
What recovery are you using?
Sent from my LG-P999 using Tapatalk 2
Click to expand...
Click to collapse
CWM 5.0.2.8
Darkseider said:
I did that and it still showed Damaged SD card. Was able to restore from backup and all is well. Dunno maybe dumb luck?
Click to expand...
Click to collapse
Just unmount and mount it back from settings the message disappears
Sent from my -P999 using xda app-developers app
djvoleur said:
Hello,
Based off of Harsh 3.0.41 github
Changelog:
Version 0820 (MMDD)
Linux 3.0.41
Compiled with Code Sourcery (CS) and Linaro (LIN) toolchains, choose your poison...
OC/UV - 1.4GHz p @ airnique23)
V(R) I/O Scheduler set as default (can be changed)
Includes ZRAM and Morfics tweaks by way of 95vrooom in /system/etc/init.d (If you are experiencing lags, try deleting 95vrooom and reboot)
Installation:
Recommended but not required
CM 7.2 Stable
CWM 5.0.20
(If you are having an issue with the kernel AFTER installing, please provide what ROM and CWM version or other recovery version you are using)
1. MAKE A BACKUP FIRST!!! (Not responsible for any mishaps :victory
2. Choose which one you want to download/install, CS or LIN version, (please provide feedback) just compiled with a different toolchain
3. Please check /system/etc/vold.fstab and your internal sdcard (emmc) has an 8 instead of a 9 (change to 8 if its a 9 and make sure vold.fstab permissions are rw-r--r-- after saving), especially if this is your first time otherwise you will have to NVFlash back to stock...
4. Boot into CWM
5. Clear cache/dalvik cache
6. Install
7. Reboot (will take awhile to boot...be patient)
Known bugs:
Reboot/Reboot recovery work 90% of time. (same as Harsh's)
Button Panel LED backlights cannot be turned off (will cause phone to lag...BAD...still looking into it)
Wifi Calling app may get an Invalid Sim error (if you use it)...a restart fixes this
Titanium Backup might freeze when you run it after you flash this, go to the Applications > Force stop and clear data...should be good to go...it may affect other applications that reference partitions FYI...
Have slow GPS locks? try this
Important!
Be mindful when you OC/UV, all our phones are different, experiment to find your phones optimal setting...
Don't like the kernel?
Complete Steps 4 and 5, and reinstall your ROM you are using to avoid any issues...
Credits:
Harsh (for allowing me to share)
TeamDouche
nyelitemaster (for testing...thanks sir!)
Everyone else who made 3.0 possible...
Click to expand...
Click to collapse
SWEEET!!!!! :victory:
Thanks a million
Just flashed the Linaro version. So far, so good.
I have been running it hard through back-to-back benchmarking tools (Nenamark2, Antutu, Quadrant) trying to get the phone hot and unstable. No instability to report yet! My phone even seems to be staying cooler (and using less battery) than it would at 1400Mhz on Faux 052 stable. Gonna run this config for at least 2 days more before reporting back. Thanks mucho to Harsh and dj. Awesome job on the kernel and the dedication to this thread djvoleur!!!
Is it my imagination, or are landscape/portrait transitions faster than with other kernels? (I don't mean the smoothness of the animation, but the delay between when the device is rotated and the start of the screen transition)
Temasek build 130
CWM 5.0.2.0
Darkseider said:
CWM 5.0.2.8
Click to expand...
Click to collapse
I have no problems with Temasek Rom and CWM 5.0.2.0
5.0.2.0
Tried the Linaro build. Booted fine. I'll play with this for a few days.
I guess the CS build doesn't like me.
Sent from my Android powered coffee coaster.
5.0.2.8 is a port from the P990...I have a feeling that the ported version used the P990 recovery.fstab
Code:
# mount pointfstypedevice[device2] fstype2
/recoveryemmc/dev/block/mmcblk0p7
/bootemmc/dev/block/mmcblk0p5
/cacheext4/dev/block/mmcblk0p2 NULL ext3
/dataext4/dev/block/mmcblk0p8 NULL ext3
/sdcardvfat/dev/block/mmcblk1p1 /dev/block/mmcblk1
/emmcvfat/dev/block/mmcblk0p[B]9[/B]
/systemext4/dev/block/mmcblk0p1 NULL ext3
Once the vold.fstab is changed to 8 for the emmc, it would make the internal emmc not mount on boot, hence the Damaged SD Card message...that's my assumption...
So be weary of 5.0.2.8...and it looks like if you reboot into recovery you will need to NVFlash
Main thread + features + install instructions + dev support
http://forum.xda-developers.com/showthread.php?t=2201860
PhilZ Touch is a CWM Advanced Edition that adds all the features you could ever miss in CWM
It is a well proven recovery for many phones
It also adds a full touch interface a completely configurable GUI
Please give your feedback, what works, and any bug you could encounter
Read the features, and check if you are missing something
Also, do not forget to read about the powerful aroma file manager integration and double tap shortcut
Download links
Last version can be found here:
Galaxy Note 3 LTE International
Now: one common recovery for all: hlte
http://goo.im/devs/philz_touch/CWM_Advanced_Edition
The below specific variants are no more updated, use hlte common variant
- hltexx
For older bootloader, use versions before 6.13.0
Click to expand...
Click to collapse
Big thanks to @eybee1970 for the first flash
To @Chenglu for guide in dtbTool + support in fixing mount usb storage
To TeamWin for the primitive device tree
To @wanam for his help in compiling kernels
Reserved
Info:
Kernel compiled from sources update3
No sensors flashing: fast boot in recovery
Root allowed
Selinux enforced mode preserved
Built in NTFS/Exfat kernel module support for fast backups
Recovery: based on cm-11.0 kitkat branch
More info:
At worst, it would bootloop and you have to know how to get out of a bootloop, that's it
But you're still warned: Read Post 1
Credits to @Chenglu for parts of the ramdisk
Can you build a version for SM-N9005 hlte?
regards
Great your here! Best recovery option! Now can you get some of your buddies to push us an aosp rom??
Sent from my SM-N9005 using XDA Premium 4 mobile app
First, someone has to flash it so that we debug it
The risks are a boot hand so you need odin to flash another recovery
Either selinux missing permissions I will add later or needed graphics.c
Waiting for feedback
Yay \(^o^)/
I've been waiting for you Phil
Welcome
Sent from my Note 3 powered by Omega v4.0
Vocaloid fan? Check out this thread!
cool to see you here, mate
EDIT: ok, I flashed it
- CWM zip to flash Recovery does not work (at least for me...)
- ODIN flashable works
- CWM Touch Recovery works, no issues so far
Thx.
The warnings in post 1 are for noobs
So do not be do scared others
Phil3759 said:
The warnings in post 1 are for noobs
So do not be do scared others
Click to expand...
Click to collapse
post above yours
eybee1970 said:
cool to see you here, mate
EDIT: ok, I flashed it
- CWM zip to flash Recovery does not work (at least for me...)
- ODIN flashable works
- CWM Touch Recovery works, no issues so far
Thx.
Click to expand...
Click to collapse
Are you kidding?
It works?
LoL
Never thought on first release. This has no device tree. I built near from scratch, based on twrp broken device tree for cwm
Big thanks. I am removing noob warnings in op so that we start debugging where needed
:thumbup::thumbup:
Phil3759 said:
Are you kidding?
It works?
LoL
Never thought on first release. This has no device tree. I built near from scratch, based on twrp broken device tree for cwm
Big thanks. I am removing noob warnings in op so that we start debugging where needed
:thumbup::thumbup:
Click to expand...
Click to collapse
I have to thank you...I don't like TWRP, so I used CWM so far...but as I use Sammy Flip Cover, it is really hard to handle volume buttons....now I don't need them any more
EDIT: Thx for mentioning me in OP...but please correct my nick ...its a funny kind of my initials (A.B.) and the number behind is quite clear I guess
Phil3759 said:
Info:
Kernel compiled from sources update3
No sensors flashing: fast boot in recovery
Root allowed
Selinux enforced mode preserved
Built in NTFS/Exfat kernel module support for fast backups
Recovery: based on cm-11.0 kitkat branch
More info:
At worst, it would bootloop and you have to know how to get out of a bootloop, that's it
But you're still warned: Read Post 1
Credits to @Chenglu for parts of the ramdisk
Click to expand...
Click to collapse
Nice to see this ramping-up :good:
Obvious warning that should be added to the top post - like every single custom (non-Samsung) recovery so far, this is also tripping the Knox flag.
eybee1970 said:
I have to thank you...I don't like TWRP, so I used CWM so far...but as I use Sammy Flip Cover, it is really hard to handle volume buttons....now I don't need them any more
EDIT: Thx for mentioning me in OP...but please correct my nick ...its a funny kind of my initials (A.B.) and the number behind is quite clear I guess
Click to expand...
Click to collapse
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Phil3759 said:
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Click to expand...
Click to collapse
- will test backup...right now not enough free space on external sd
- usb storage mounting does not work
- won't test format
- boot in recovery is fast enough - same as before on regular CWM
- time/date not showing up correctly...for me it is 10.05 am now and it shows up 20.12 pm though I set the correct timezone
Phil3759 said:
Fixed with your correct nick
- is backup to exfat extrnal sd ok?
- mount usb storage and OTG USB?
- format usb otg in exfst/ntfs/ext4/ext2?
- boot into recovery is fast?
- time/date?
If all ok I will clean it and release other variants
Click to expand...
Click to collapse
Backup to extsdcard (fat) OK : Time 20min
Backup usb otg OK : Time 10 min
don't try format
boot in recovery speed time seem to be the same as normal cwm
time/date : in cwm I had 23h29 instead of 14h32 (I'm in france), in backup name the date is false (01_01_1970)
aromafm feature not working.
i have /aromafm/aromafm.zip in the clockworkmod folder on internal storage and sdcard...
Philz touch can´t found this folder...
"now clockworkmod/aromafm/aromafm.zip in storage paths"
i started aromafm.zip via install zip -> Choose zip from /sdcard -> clockworkmod -> aromafm -> aromafm.zip and this work it...
go in the sdcard folder ... -> empty! no data found on internal storage...
external storage is this problem too.
regards
Sakaschi
tr72 said:
Backup to extsdcard (fat) OK : Time 20min
Backup usb otg OK : Time 10 min
don't try format
boot in recovery speed time seem to be the same as normal cwm
time/date : in cwm I had 23h29 instead of 14h32 (I'm in france), in backup name the date is false (01_01_1970)
Click to expand...
Click to collapse
Many thanks
Can you verify mount usb storage on pc for external sd?
Sakaschi said:
aromafm feature not working.
i have /aromafm/aromafm.zip in the clockworkmod folder on internal storage and sdcard...
Philz touch can´t found this folder...
"now clockworkmod/aromafm/aromafm.zip in storage paths"
i started aromafm.zip via install zip -> Choose zip from /sdcard -> clockworkmod -> aromafm -> aromafm.zip and this work it...
go in the sdcard folder ... -> empty! no data found on internal storage...
external storage is this problem too.
regards
Sakaschi
Click to expand...
Click to collapse
Check data/media/0 stories in FAQ
storage set to /data/media/0 is selected....
Phil3759 said:
Many thanks
Can you verify mount usb storage on pc for external sd?
Check data/media/0 stories in FAQ
Click to expand...
Click to collapse
I can't check, I'm on mac. Try with virtual machine without success but it's not a good test.
Find an old flashdrive to try some format :
vfat : OK
extfat : OK on windows (VM), not on mac (ask to initialise the disc)
ntfs : OK
Don't have the driver to test the other.
******************* 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.