By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Follow this install guide substituting various filenames with filenames below if you don't understand the below instructions
Get nookhd-emmc-cwm.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost). (use dd under Linux and MacOS, use Win32DiskImager or similar tool under Windows, use 7zip under windows to unpack).
Download CWM recovery zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need it). As another option there's a graphical TWRP recovery available. (you can only have one recovery option)
Also download latest nightly from http://download.cyanogenmod.com/?device=hummingbird
You can write installation zips for recovery, cm binary + whatever else you need and transfer them to Nook user storage (if you have it activated and all), OR add all these files + whatever other packages you might need right away on to the sdcard.
Insert sdcard into Nook and reboot the Nook, next install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Use Install zip from sdcard, if you copied installation zips to sdcard, otherwise use "choose zip from internal sdcard" - both options are in "Unstall update from zip file".
Erase /data (only on initial install, this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there before you remove).
Remove the sdcard from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhd in build.prop) - This is because they specifically blacklist Nooks! For workaround #2, revert the value back to hummingbird when done installing, otherwise you'll lose sound.
- Certain sdcards still remain unstable.
- Google Earth crashes when you press "my location" button, but works fine otherwise.
Changelog:
13/08/09 - We are part of official CM and latest nightly from here is what you should get now: http://download.cyanogenmod.com/?device=hummingbird
13/08/01 - cm-10.1-20130801-UNOFFICIAL-hummingbird-emmc.zip
- Data usage statistics should now work
13/07/19 - cm-10.1-20130719-UNOFFICIAL-hummingbird-emmc.zip (backup link)
- Update wifi drivers to R5.SP3.06
- Kernel with initial charger control for the charger app to work
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
13/07/11 - cm-10.1-20130712-UNOFFICIAL-hummingbird-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-hummingbird-emmc.zip
- Rebased on cm-10.1.1 for security fixes.
13/07/08 - cm-10.1-20130708-UNOFFICIAL-hummingbird-emmc.zip
- ExFAT and NTFS support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-hummingbird-emmc.zip
- revert accidentally applies frequency bump patch that made it into 07/04
13/07/04 - cm-10.1-20130704-UNOFFICIAL-hummingbird-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-hummingbird-emmc.zip
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-hummingbird-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-hummingbird-emmc.zip
- Experimental kernel work
- enabled 1.5GHz freq by default
- in-kernel bluetooth
13/06/24 - cm-10.1-20130624-UNOFFICIAL-hummingbird-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-hummingbird-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-hummingbird-emmc.zip
- Boosted speaker and headset audio levels.
- gfx cash on startup fixed
- Zinio now works out of the box
13/06/12 - cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc.zip
- Fixed HDMI audio
- Fixed HDMI video upside-down picture
- Added usb audio support
- Enabled tabbed view in Settings app.
13/06/10 - cm-10.1-20130611-UNOFFICIAL-hummingbird-emmc.zip
- Initial release
This is unrelated development to bokbokan's sdcard/hybrid install, because he does not make his source code available, so don't ask me to pick features from his build.
oh my god
finally, :laugh:
Works great.
Sent from my Nook HD running CM10.1 on emmc.
Sweet!!!!!!
Will test it out.
I guess this means we will have access to a working repo soon so we all can start building from source.
dubidu said:
I guess this means we will have access to a working repo soon so we all can start building from source.
Click to expand...
Click to collapse
https://github.com/verygreen/android_device_bn_hummingbird
verygreen said:
https://github.com/verygreen/android_device_bn_hummingbird
Click to expand...
Click to collapse
Txs
Woohoo! Fantastic work! And thank you so much for posting source.
New binary release: cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc.zip
Changes:
- Fixed HDMI audio
- Fixed HDMI video upside-down picture
- Added usb audio support
- Enabled tabbed view in Settings app. (This seems to be looking ok, but if you find it's too bad, let me know and we certainly can try to roll it back or only have it for landscape or some other stuff).
Thank you!! :victory:
Running fantastic for me. Thanks.
AMAZING! I just wanted to cruise by the forums because I was bored with nothing new until I see this post! Awesome work is all I can say. Does this mean no more reboot restores with /system and complete control and customization of the device without the unlocked bootloader?
Haven't look at the code yet, but I believe if you change "ro.product.device" in "build.prop" you will loose all the sound.
Can someone test it?
Niiiiice! Thanks, been waiting on this.
Now, quick question: There is a stock ROM to flash, right? I just exchanged another HD & it was easy enough to just remove the SD card. I've only had this HD a week.
Thanks!
Oh yeah, I remember now: Yes, there is.
http://forum.xda-developers.com/showthread.php?t=2062613
LAYGO said:
Niiiiice! Thanks, been waiting on this.
Now, quick question: There is a stock ROM to flash, right? I just exchanged another HD & it was easy enough to just remove the SD card. I've only had this HD a week.
Thanks!
Click to expand...
Click to collapse
This is a ROM to replace the stock on emmc. You should back up your stock first. E.mote has an excellent tutorial that verygreen links in his OP here. Then you can restore that backup to get back to stock if you need to return it.
Edit: Guide is here. Just substitute the files from the OP instead of the ones listed in the guide:
http://forum.xda-developers.com/showthread.php?p=42399961
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
This is a ROM to replace the stock on emmc. You should back up your stock first. E.mote has an excellent tutorial that verygreen links in his OP here. Then you can restore that backup to get back to stock if you need to return it.
Edit: Guide is here. Just substitute the files from the OP instead of the ones listed in the guide:
http://forum.xda-developers.com/showthread.php?p=42399961
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I guess I wasn't clear in my question (too early). I just needed to know if there was a stock ROM to flash back to stock in case I had to return it. Of course, I could just Nandroid my stock install too (DUH, didn't think about that, just like you said).
Updating to latest ROM?
Folks,
I picked up a Nook HD+ 16Gb last night and followed the guide to install CM10.1. Everything went smoothly. A big THANK YOU to verygreen and lepinlar for all the work in creating this and the guides/instructions on how to install.
I've got a couple questions:
I installed the cm-10.1-20130608-UNOFFICIAL-ovation-emmc ROM and have made some changes on the tablet (added my daughters as Users, downloaded some apps, etc). How would I go about upgrading to the cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc ROM? Would I lose the changes I've already made? Is there way to install/upgrade to the new ROM and keep the changes I've already made? Thanks.
Shenandoah
shenandoah2 said:
Folks,
I picked up a Nook HD+ 16Gb last night and followed the guide to install CM10.1. Everything went smoothly. A big THANK YOU to verygreen and lepinlar for all the work in creating this and the guides/instructions on how to install.
I've got a couple questions:
I installed the cm-10.1-20130608-UNOFFICIAL-ovation-emmc ROM and have made some changes on the tablet (added my daughters as Users, downloaded some apps, etc). How would I go about upgrading to the cm-10.1-20130612-UNOFFICIAL-hummingbird-emmc ROM? Would I lose the changes I've already made? Is there way to install/upgrade to the new ROM and keep the changes I've already made? Thanks.
Shenandoah
Click to expand...
Click to collapse
First you do not want to flash that ROM to your HD+. If you look at the filenames you will see ovation (which means HD+) and hummingbird (which means HD). But if you want to upgrade to a newer ovation ROM, just flash the newer ROM over the top of your old ROM. It will keep all your changes you've made.
Sent from my Nook HD+ running CM10.1 on emmc.
Lepinlar,
Sorry about the post. I didn't read it close enough to realize it was for the HD (not the HD+). Should I delete my original post so it doesn't confuse anyone else?
Shenandoah
shenandoah2 said:
Lepinlar,
Sorry about the post. I didn't read it close enough to realize it was for the HD (not the HD+). Should I delete my original post so it doesn't confuse anyone else?
Shenandoah
Click to expand...
Click to collapse
No, it might actually help others users who are confused by the issue. Leave it there as originally posted.
Sent from my Nook HD+ running CM10.1 on emmc.
Awesome ROM, thanks for doing this. Battery life vs stock is amazing, UI looks much better, more customizable, great having root to back up apps and etc.
I had a small issue with the 06/08 build on my HD+ where the battery would not recharge. Power cycling (turning it off and then on again) seemed to fix it. Is anyone seeing this issue with this 06/12 build? Thanks!
Related
Cyanogenmod 7 for Motorola Milestone 2
This is an unofficial Milestone 2 port of CM7.
[ Downloads | Google apps ]
Known limitations
720P recording is not working
ALT lock does not work
Click to expand...
Click to collapse
Changelog:
08.09.2012 - Upgraded CM sources
01.09.2012 - Added OTA updater, upgraded CM sources
21.02.2012 - Upgraded CM sources (fixed blank screen after unlocking issue)
09.02.2012 - Upgraded CM sources
22.01.2012 - Backported ICS animations, UK 2.3.4 fingerprint, fixed Exchange FC for polish locale
04.01.2012 - Upgraded CM sources (e.g. T9 dialer)
29.11.2011:
Moved device specific settings to its own tree in the settings
Added lower backlight level
New multitouch module (no delay at startup)
Stock compass callibration app and audio effects
20.11.2011 - Hopefully fixed some wifi issues
18.11.2011 - Wifi tethering does not need DUN APN anymore
18.11.2011 - Fingerprint changed to UK 2.2 (fix Market from hiding some apps)
12.11.2011 - Tweaked CPU, camera, build.prop and recovery settings (Endless7);
settings for Droid2Bootstrap (will not destroy 2nd-init anymore)
11.11.2011 - Added keyboard switching, option to force PLMN display, more multitouch points
08.11.2011 - Fixed camera's photos
08.11.2011 - Initial release
Click to expand...
Click to collapse
Note:
If you have updated to stock gingerbread, you can't use this rom until you downgrade.
Instructions for upgrading from stock ROM:
1) Install Droid2 Bootstrap Recovery
2) Boot into recovery
3) Optionally: create a backup of your data
4) Choose Install zip from sdcard -> Choose zip from sdcard and select downloaded ZIP file.
5) Optionally: install Google Apps the same way
6) Wipe data/factory reset
7) Wipe cache partition
8) Reboot and enjoy
9) Optionally: use attached Baseband switcher app if you have troubles with phone signal.
Click to expand...
Click to collapse
Instructions for subsequent upgrades or upgrade from any CM7.x ROM:
1) Boot into recovery (long power off -> Reboot)
2) Choose "Install zip from sdcard" -> "Choose zip from sdcard" and select downloaded ZIP file.
3) Advanced -> Wipe battery stats
4) Advanced -> Wipe dalvik cache
5) Reboot and enjoy
Click to expand...
Click to collapse
As you can see, the update from the stock ROM requires a complete wipe, so be sure to backup your important data!
GIT sources:
repo init -u git://github.com/tezet/android.git -b gingerbread
Any collaborators are more than welcomed!
Click to expand...
Click to collapse
Donations
If you like and appreciate my work, and you may donate here (now in English).
Click to expand...
Click to collapse
Many thanks to Quarx for his Defy port and all folks involved in [email protected]
Looks very promising. Browsing your github right now.
Edit: Thanks for your effort. I was trying to start a similar project but some events IRL left me with NO free time at the moment. If there's any info you'd like to get from me just let me know.
What is the difference between this and the CM made by Endless7?
If this is really based on m2 files, that is a great progress
How is hardware video decoding working?
Edit: Difference is that there is no need to patch every build to make it work, and fixing things like video or 720 will be more easy to do.
And the really big difference, is that this way, we can get official cm7 support.
Yes, DSP decoding is working, including 720P.
I got lot of troubles with 720P encoding and gave up for now. Maybe I will come back to the topic, but for now I have already spent too much time on this...
Nice work, thanks!
Will I get anything extra in compare with Endless7 build? I mean, if I will now use your build instead CM7 from Endless7, will I get any perfomance boost or anything else than 720p decoding (can it hw decode same formats as stock firmware btw?).
Just asking.
Anyway thanks for this - official cm7 support would be nice.
I would say the most noticable difference is a better touch screen. Also the battery seems to be slightly better, but that may be very subjective opinion...
I'm not sure how about general DSP decoding, but at least h264 720P decoding didn't work in Defy build.
And I'm not sure what is the current state of Endless7's ROM, but this is the most noticable difference when I switched to this ROM.
From the APPs point of view, it is pure CM7.1, without any addons, so you may miss some Endless7's extra stuff...
Edit: I haven't verified lot of formats, just few 720P videos. If you notice anything missing in comparison to the stock rom, it may be probably fixed easily...
Forgot that, this roms uses another kernel
UK kernel should improve touch
Wonder if we can make it boot with a 2.3 kernel...
Another thing, phone will be listed as a953 on pc instead of 722, with uk kernel.
I guess I will wait for UK version of GB release before I will attempt to switch into GB kernel. I would like to use the same source of kernel and bpsw. There's no big gain in running GB kernel, really.
Yep, we are just a few days away from uk release.
2.3 kernel improve touch significantly from uk 2.2. Besides that not much more.
Is the multi touch working properly?
Yeap, the same as stock froyo.
I mean, the gingerbread roms here have 6 points multi-touch, is it the same here?
No, I haven't included that. You may add it by yourself, it's just a matter of module. Maybe I will include in the next builds, but it will be disabled by default. I'm not sure if it doesn't have any negative impact on touchscreen responsiveness...
Edit: why would you need that anyway? Is there any real-life use case other than keyboards?
As far as I see:
# use default multitouch configuration
ro.product.multi_touch_enabled=true
persist.sys.multitouch=2
You could change to 6 and you will get 6 points touch (maybe you have to add the module)
But, dont use anything higher than 4. It makes cpu consumption higher and laggy response in ALL roms.
Thank you for this great work !
A lot of people will be interested to know that it's possible to install your update.zip without data wipe when coming from Endless's CM7.
Forgot about it. It's perfectly OK to update from any CM7 rom without wipe. Just follow the usual upgrade procedure.
Could you consider adding a keyboard layout option in your nexts builds?
Also, alt-lock is not working at the moment. It's not critical though...
I also noticed bad 3d performance in Quadrant.
On the "planets" test, using Endless cm7 i get something like 60fps, but 10 with yours. Didn't notice any change when playing with n64oid/ogl-es though.
Edit : Scored 13.6 at Nenamark2, 21.6 at Nenamark1. Could somebody compare with Endless's CM7?
Edit2 : Concerning Quadrant, I remember getting 10fps too when on stock french 2.2.2 rom.
Thanks. Keyboard switch is on the top of todo list
I will look into 3D performance and compare it tomorrow with stock 2.2.2. Perhaps that's the UK's libs issue...
As for the ALT lock, that is on the very bottom of todo list I believe it does not work on Droid 2 either.
Edit: just confirmed the same result (10FPS) with stock 2.2.2 UK rom. Anybody could confirm it is really faster on Endless7's ROM?
I have a major bug with the camera : files created are 0byte large.
Video recording works fine.
Finally here it is, the long awaited CM10 for Nook HD+ (early snapshot, anyway).
This codebase is currently hardcoded to work from sdcard only.
How to build from source (you need to meet all the usual cm10 build prerequirements),
Get the source:
Code:
mkdir android/system
cd android/system
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/repo
chmod a+x ~/repo
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
wget -O .repo/local_manifest.xml https://github.com/verygreen/android_manifests/raw/master/ovation-jb/local_manifest.xml
repo sync -j16
(device repo on github)
(temp kludge for source kernel build: get my kernel from https://github.com/verygreen/green_kernel_omap and put it to kernel/bn/ovation (use ovation-3.0 branch for 3.0.31 kernel or ovation-aosp-kernel for 3.0.50), then put B&N source distro copies of wlan and wpan kernel dirs to external inside of kernel dir, and also desired version of sgx proprietary-open tar file into external/sgx)
Build:
Code:
. build/envsetup.sh
lunch cm_ovation-userdebug
. vendor/cm/get-prebuilts
mka bacon
In the out/target/product/ovation output dir you'll have the update file generated: cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip
If you do not want to build from source, here's my current (as of this post, see bottom for newer versions) binary snapshot: cm-10-20130511-UNOFFICIAL-ovation-sdcard.zip
(additionally there's emmc version, follow installation instructions here, but use this install file: cm-10-20130511-UNOFFICIAL-ovation-emmc.zip)
You will also need updated cwm image: sdcard-cwm-early4.img.gz
For first time install only (you will need 4G or bigger sdcard, smaller ones are not supported and not tested):
gunzip cwm image and write it to your sdcard (entire sdcard not just one partition of it), use either dd on Linux/MacOS or Win32 Image Writer for those impaired by Windows. Make sure to use sdcard rated for fast small IO for best results.
(Note: There is now experimental recovery image that does not require adb that's currently documented in this post)
Insert the card into the Nook and reboot the nook, CWM should start.
(This will also automatically repartition the card into a correct layout no matter the size (but no smaller than 4G).
In the CWM:
Go to "mounts and storage", choose "mount /sdcard".
Press power button to go back to the main menu.
Now do
Code:
adb push cm-10-XXXXXXXX-UNOFFICIAL-ovation.zip /sdcard
Also push whatever other zip files you want to install to /sdcard too.
(if you don't have operational adb, you can also just turn off the nook at this stage, put zip files to volume named "CM10SDCARD" (not "boot"), then put sdcard back into nook and start it again)
Next, choose "install zip from sdcard", and then "Choose zip from sdcard" and first cm-...zip, and then whatever other packages you have the need to install.
When done installing, press the power button to go one level up in the menu and then choose reboot.
This will reboot you into CM10.
If you ever need to get back to CWM later, use either "reboot to recovery" power menu, or reboot, and once B&N nook logo shows up, press and hold power and home keys together for about 4 seconds.
To reboot into stock nook software, just poweroff, remove sdcard, then poweron.
Caveats:
- Current sdcard layout is ~800M system and ~900M data for less than 16G and 2G data for 16G+ cards, the rest is a separate sdcard (because having sdcard to live on data is kind of dangerous). I am still taking feedback on these sizes better to change these early on while there are not a lot of users.
- This snapshot uses B&N binary kernel from 2.0, it happens to oops in mtp_open if you have mtp storage mode enabled and plug into a computer, so steer clear of it for now I guess, this will be fixed later. (if your nook reboots when plugged into computer or right on boot while plugged - this is it, likely to happen after first install).
- /cache is shared with stock ROM, helps for slower sdcards at the expense of slower boots when you switch your OS from stock to CM10 or back.
- Upgrade from 20121209 snapshot note: that snapshot had bad kernel that had problems with sdcards. Most advisable thing is to redo entire install (after downloading new, cwm-early3 image first). You might also be able to just install kernel from the update.zip and write it to the first partition on the sdcard, that shuld also fix all issues and will let your existing cwm to work to flash this new image.
Things that I know are not working:
- Coming out of sleep sometimes there's a crash (this is related to wifi, the workaround is to disable wifi while sleeping in the options).
- Rebooting to stock with sdcard still in causes stock to hang at 99% booting and sit there, simply pop out the sdcard and it will finish booting.
- on-headphones microphone is not currently used even if present (I now believe this is actually not a bug, and stock has the same behavior).
- Bluetooth signal strength is very low
- Hulu+ and other such things requiring DRM do not work.
This is now at feature-parity with stock B&N ROM, I believe (other than DRM).
Experimental versions:
Other than the stable version above, there are some experimental versions below that are tested before (hopefully) being promoted to the stable status.
01/07 version with a different kernel, otherwise same as 12/31
01/08 version with a recompiled B&N kernel, otherwise same as 12/31
01/19 version with a yet another different kernel, updated CM10 base and default dpi/screen size changes
02/12 Some CM10 changes from upstream and updated wifi drivers from B&N 2.0.6 code drop (hoping that it will fix the annoying coming out of suspend crash - nope, it did not.)
02/20 Don't reboot into emmc stock on crash, it does us no good. Revert Z-axis in accelerometer for hopefully better responsiveness.
wifi should no longer drain battery when sleeping, cover close will blank screen, gfx issues hopefully fixed
Enjoy.
Finally, a major step in the right direction. Thank you very much for your efforts.
Thanks for that.
One question before try it:
formating /sdcard from CWM will not format the internal "sdcard" directory of the Nook?
Thank you very much. Your work is always appreciated.
The ability to mount and use the internal storage would be great.
Many thanks for this, got it working for some reason the format sdcard step seemed to fail - but got it working by manual format under linux.
Now have gapps and everything else I need installed - so will play with it later but so far seems to run very smooth.
Agree that seeing nook internal storage would be good
Wow, fantastic, will try it tonight. Just checking, no problem using 64G card? Also, I'm assuming for the moment it leaves the complete data structure in tact on the B&N internal memory? Just mostly not mounted? Reason I ask is its a shortcut to get the apps that are already installed there, especially the B&N specific ones. Otherwise I could pull with ADB.
Thanks again!
verygreen said:
Caveats:
- Current sdcard layout is ~800M system and ~900M data, the rest is a separate sdcard (because having sdcard to live on data is kind of dangerous). I am taking feedback on these sizesm better to change these early on while there are not a lot of users.
- There's no access to "sdcard" on internal nook drive, though this could be organized if people think that's useful.
- This snapshot uses B&N binary kernel from 2.0, it happens to oops in mtp_open if you have mtp storage mode enabled and plug into a computer, so steer clear of it for now I guess, this will be fixed later. (if your nook reboots when plugged into computer or right on boot while plugged - this is it).
- /cache is shared with stock ROM, helps for slower sdcards at the expense of slower boots when you switch your OS from stock to CM10 or back.
Click to expand...
Click to collapse
Nice, just some quick questions here.
when you said build, I assume you means cross-compile, right? I know most people are not gonna compile stuff themself, and just use the binary. But so people know if they wanna learn since x86 and arm are different architecture. Just compiling from x86 isn't gonna work.
I agree the size is a bit bloated ATM. Even the gigantic Galaxy Note 2 is about that size also.
The access to internal SD can be useful. Assuming you brought 32GB version of Nook, then you have like 25GB+ worth of storage sitting there. If possible it should be mounted(only old /mnt/sdcard area), whether that be to /mnt/sdcard or /mnt/int_sdcard
I notice you build this based on JB version of android, which is what 4.1 or 4.2? But still using the B&N kernel which is 4.0.4? I'm sure some of the stuff works. I made that mistake as well when attempt to put Play market on the nook earlier.
Thanks for your hardwork.
someone0 said:
Nice, just some quick questions here.
when you said build, I assume you means cross-compile, right? I know most people are not gonna compile stuff themself, and just use the binary. But so people know if they wanna learn since x86 and arm are different architecture. Just compiling from x86 isn't gonna work.
Click to expand...
Click to collapse
Yes, it's cross-compiling, which is still building.
The cm repos provide necessay cross-compilers and all that stuff, though.
I agree the size is a bit bloated ATM. Even the gigantic Galaxy Note 2 is about that size also.
Click to expand...
Click to collapse
So the better sizes are?
I notice you build this based on JB version of android, which is what 4.1 or 4.2? But still using the B&N kernel which is 4.0.4? I'm sure some of the stuff works. I made that mistake as well when attempt to put Play market on the nook earlier.
Click to expand...
Click to collapse
build is based around 4.1.2.
B&N kernel is pretty much inline with JB (3.0.31), so it works pretty well (other than the mtp_open oops). I'll switch to building it from source anyway, but this will take some time.
dbh369 said:
Wow, fantastic, will try it tonight. Just checking, no problem using 64G card?
Click to expand...
Click to collapse
I don't have anything this big, so only tried 16G.
Also, I'm assuming for the moment it leaves the complete data structure in tact on the B&N internal memory? Just mostly not mounted?
Click to expand...
Click to collapse
Mostly. /cache is shared so this one is modified.
Also to get recovery we are reusing stuff in /bootdata (BCB and boot counter).
Reason I ask is its a shortcut to get the apps that are already installed there, especially the B&N specific ones. Otherwise I could pull with ADB.
Click to expand...
Click to collapse
You should not be sharing apps between the two, they might be different version too, anyway.
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Verygreen, thank you for all your continued hard work with the CM/NOOK bases.
Thanks for this.
A few things , you are maybe already thinking of implementing these:
1. It would be good if you could dual boot both systems with a menu or holding a volume button to boot to stock nook os, instead of having to take out the sd card, save a bit of time and ease (the slot is quite hard to open )
2. Access to internal storage would be good. I have 32gb nook, so not being able to use 25gb of free space on the internal storage is not great, but I'm sure its quite easy to fix. Is it just a matter of mounting it correctly ?
Everything seems great, with the tearing issue do you know what the problem is ?
jay_ntwr said:
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Verygreen, thank you for all your continued hard work with the CM/NOOK bases.
Click to expand...
Click to collapse
I could be proved wrong but I don't think it will work for you on a HD. It doesn't work on a HD for me....
With Nook HD, try rebooting a few times with card installed see if it goes to cwm,
tried on HD
CelticWebSolutions said:
I could be proved wrong but I don't think it will work for you on a HD. It doesn't work on a HD for me....
Click to expand...
Click to collapse
I tried the CWM card in my HD. I can concur that the HD doesn't boot from the card, it just goes to rooted stock.
ArcSmurf said:
Many thanks for this, got it working for some reason the format sdcard step seemed to fail - but got it working by manual format under linux.
Now have gapps and everything else I need installed - so will play with it later but so far seems to run very smooth.
Agree that seeing nook internal storage would be good
Click to expand...
Click to collapse
I got this problem too, format sdcard from cwm doesn't work.
It says Failed to mount /sdcard ... Skipping format ..
How did you fix ?
Really loving your efforts! Damn, thank you very much! I'll see if I can contribute soon, after I get my new computer. Can't wait for CM10 on HD+, it'll actually utilise the Nook HD+'s potential. It's dual-core, it can playback full HD, but it's limited by software.
Managed to get it to format sd card after I messed about formatting the sd card completely again and writing the cwm image
HiddenG said:
Really loving your efforts! Damn, thank you very much! I'll see if I can contribute soon, after I get my new computer. Can't wait for CM10 on HD+, it'll actually utilise the Nook HD+'s potential. It's dual-core, it can playback full HD, but it's limited by software.
Click to expand...
Click to collapse
quadcore.
jay_ntwr said:
Is there any reason to think this would not work on the NOOK HD as well? I understand that the reason it may have not been tested is that no one is willing to test it, but if it "should work" then I'd be willing to purchase the HD and test and report results.
Click to expand...
Click to collapse
Yes, this will not work on the nook HD directly, that has different uboot, different kernel and different SoC (not to mention different display).
I can't get /sdcard to mount or format no matter what I do. I'm using Windows, which seems to always be a hindrance in the root community.
Also, I'm fairly certain the the Nook HD+ processor (OMAP 4470) is a dual-core. Besides the main cores it has the two ARM Cortex-M3 cores, but it is still technically a dual-core processor.
PS- I'm running the Nook HD+ 16GB. Could the 16GB vs. 32GB cause any issues? Just wondering.
I decided to start a new thread for 10.1 development on Nook HD+.
Starting with 5/30 build there is a new sdcard layout, so you will need to redo your sdcard from scratch if you were running anything different. See at the bottom of the post for historic info on legacy sdcard builds.
Installation instructions:
- Grab cwm early7.1, gunzip and write to your sdcard using dd under Linux/MacOS or WinImage under Windows. Minimum supported size is 2G. Sandisk Class 4 is best recommended, Sandisk U1/Class10 (you can tell them by being red and gray in color) are NOT recommended,
- Download latest CM sdcard build you want to install, currently latest is: cm-10.1-20130904-UNOFFICIAL-ovation-sdcard.zip
- Download other files you might want to flash.
- Place the install files you downloaded onto the Nook (or you can do adb push later in cwm).
- Insert sdcard that you wrote cwm image to into your powered off Nook.
- Turn on the Nook. CWM interface should load.
- In cwm navigate to install zip from sdcard. -> install from internal storage. (use volume buttons to navigate, home button to select, power button to go one menu level up).
- Choose your files to install and install them.
- When done installing, press power button a couple of times to get to the initial menu and then select reboot option.
- Nook should now reboot into CM10.1 that you can enjoy.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up).
Known issues:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - this is because B&N blacklists ovation platform for the app. Revert back once done, as otherwise you'll lose sound.
- Certain sdcards still remain unstable.
- In Android File Transfer "Internal memory" refers to sdcard and "sdcard" refers to Internal nook storage. This is not a bug and is intentional.
Changelog:
13/09/04 - cm-10.1-20130904-UNOFFICIAL-ovation-sdcard.zip
- Adjustments to heap size to fix Kindle app problems.
13/09/01 - cm-10.1-20130901-UNOFFICIAL-ovation-sdcard.zip
- fixed filedescriptor leak in sensors HAL, hopefully making stop to soft reboots
13/08/30 - cm-10.1-20130830-UNOFFICIAL-ovation-sdcard.zip
- layer allocation changes to improve smoothness
13/08/16 - cm-10.1-20130816-UNOFFICIAL-ovation-sdcard.zip
- Improve stability of Sandisk Ultra 16G cards.
13/08/13 - cm-10.1-20130813-UNOFFICIAL-ovation-sdcard.zip
- Enabled volume rocker wakeup and home button wakeup options in Settings.
13/08/10 - cm-10.1-20130810-UNOFFICIAL-ovation-sdcard.zip
- Data usage display should work now
- Lifted davlik vm settings a bit.
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-sdcard.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
- Kernel capable of charger control (with the app).
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-sdcard.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-sdcard.zip
- redone touchscreen sensitivity changing mechanism, app to control it: NookTouchscreenSensitivityAdjuster-4.apk
- Rebased on cm-10.1.1 for the security fixes
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-sdcard.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-sdcard.zip
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-sdcard.zip
- in-kernel bluetooth
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-sdcard.zip
- WiFi Direct and BT tethering are now working
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-sdcard.zip
- Audio volume boost
- Zinio app now works out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-sdcard.zip
- Fixed HDMI audio
- Added USB audio support
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-sdcard.zip
- USBHost access is now conveniently located in QuickSettings.
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-sdcard.zip
- Forced usbHost support.
13/05/31 - cm-10.1-20130531-UNOFFICIAL-ovation-sdcard.zip
- Rebased to CM10.1-RC3
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-sdcard.zip
- Converted to new sdcard layout, old 4-partition layout is now deprecated. You should be able to return to stock with sdcard still plugged in without stock hanging at 99% forever.
- (original binary was lost due to operator error, so now this binary points to 5/31 release)
Legacy sdcard build info:
Anyway, installation instructions are basically the same as in CM10 thread, just need to use different installation binary.
You might want to use cwm early4 while you are at it too.
Installation on top of CM10 is not recommended.
Please report on whatever problems you happen to meet that I do not already know about.
Sound and video seem to be working.
Changelog:
13/05/29 - cm-10.1-20130529-UNOFFICIAL-ovation-legacysdcard.zip
- Fixed microphone input volume.
- Last legacy sdcard format release, consider upgrading to the new format.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-sdcard.zip
- Fixed BT audio and probably hdmi audio too.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-sdcard.zip
- Wifi battery drain should be gone now
- Should fix sgx crash on startup for those affected
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
Binary snapshot from 05/05
- DRM probably does not work.
- internal storage is presented in a strange way in mtp, reason is yet unknown.
- BT Audio does not work
Binary snapshot from 04/24:
- same as 4/22 with "phone mode" disabled.
Binary snapshot from 04/22:
- bt does not work
- probably many other problems that I did not get to see yet?
Binary snapshot from 01/07:
- Bluetooth does not work
- Mic input is very faint
- sleep/battery life is not great, but the system is doing memsleep, it's just seem to be waking out pretty frequently for things like wifi (like every couple minutes, overall I lost ~14% battery in 8 hours on battery overnight on the first test, so definitely nothing to brag about.
- Old familiar notification bar at the bottom does not really work either, so it's a phone-looking top notification bar for now (seems to be upstream problem so far).
- Initial boot animation is distorted - just ignore it.
- Sometimes (usually after update in cwm) boot fails due to a crash in hwc, manifests itself as dimmed bootloader splash or garbage on the screen - just reboot and it'll come back.
cm 10.1 on sd card
verygreen said:
I decided to start a new thread for 10.1 development on Nook HD+, because it's significantly less stable and so I do not want to cause confusion in CM10 thread.
Anyway, installation instructions are basically the same as in CM10 thread, just need to use different installation binary.
You might want to use cwm early4 while you are at it too.
Installation on top of CM10 is not recommended.
Please report on whatever problems you happen to meet that I do not already know about.
Sound and video seem to be working.
Known problems:
Binary snapshot from 01/07:
- Bluetooth does not work
- Mic input is very faint
- sleep/battery life is not great, but the system is doing memsleep, it's just seem to be waking out pretty frequently for things like wifi (like every couple minutes, overall I lost ~14% battery in 8 hours on battery overnight on the first test, so definitely nothing to brag about.
- Old familiar notification bar at the bottom does not really work either, so it's a phone-looking top notification bar for now (seems to be upstream problem so far).
- Initial boot animation is distorted - just ignore it.
- Sometimes (usually after update in cwm) boot fails due to a crash in hwc, manifests itself as dimmed bootloader splash or garbage on the screen - just reboot and it'll come back.
Click to expand...
Click to collapse
I installed it finally after several reinstalls of image on 2 different cards (Samsung 8GB class 10 and A data 8GB class10) finally succeeded on Samsung.Took very longtime to boot and after optimizing apps constant message "unfortunately setup wizard has stopped kept coming and could not proceed any further.Reinstalled image on sd card reinstalled the zip,same result.
Success after 2 reboots
Got it to boot finally!
Using the same 32gb SDcard as I was using for CM10. Had to wipe card and install the image (early 4 as suggested) and then adb push over the binary dated 01/07 and install it, on first boot was hanging on the Cyanoboot screen as mentioned by the OP, had to hold down power and shutdown and then power back on 2 times for it to actually start to boot, on 3rd boot it loaded fine, so my tip is to be patient and you shall persevere
Cheers verygreen, will get testing and give some feedback on your once again excellent work
Hi verygreen,
here is my feedback for the build 01/07.
The 2 first boot was hanging on the Cyanoboot screen but it boot correctly at the third.
Beside the bugs mentioned by the OP I also have freez of 1-2 second on every app how uses intensively internet (maps, firefox...)
3D games like Temple Run runs smooth
I have a FC for terminal emulator so I can't see dmesg command to analyse the freez bug with internet apps.
Thanks for your work
Usage review
Right I've been running this as my daily driver for 3 weeks now and gotta say other than a few little issues it works great
Issues are:
1. WiFi takes 3 goes to connect up most of the time, may be encryption specific (e.g. my work connection is WPA PSK and works most of the time first time but my home connection is WPA2 PSK encrypted and always requires me turning wifi on and off a few times before it gets past authenticating.
2. Random reboots, may well be sd card related as did have them before on CM10 too. Have found it happens fairly regularly when plugged in and charging (usually overnight) but can happen at any time, quite often in the stock browser, so most probably sd card i/o related.
I can try and grab logs if needed for the above?
Overall though works great and after having tweaked my build.prop to think it's a Nexus 7 I have even gotten Sky Go to work (UK based satellite tv broadcaster streaming app) so am super happy with it.
Great work Verygreen
Yeah, I'm suspecting that the reboots are because of i/o issues with writing to the sdcard. I never have the tablet connected to adb running logcat when it reboots. It tends to reboot when it's just been sitting there for a while, never in the middle of something. I had to just go back to the stock rooted B&N kernal for my wife's HD+ because she was complaining about the crashes.
On the other hand, my HD running CM10.1 has been pretty stable - one reboot per week. I just did the hybrid install yesterday, so I'm hoping that it's completely stable now. Only time will tell.
Hmm ... interesting "hybrid install". Can you guide?
Re: [Nook HD+] CM10.1 development
datas0ft said:
Hmm ... interesting "hybrid install". Can you guide?
Click to expand...
Click to collapse
Just prepare a new SD with his new image (from his hybrid thread) and install the same way as you normally do on SD. Just have to use his 1/30 or newer. It is all automatic. It leaves /boot and /system and /sdcard on SD and puts /data on internal memory (as a folder under internal data). That way stock can still boot without hanging with the SD in and data runs faster.
Edit: But this is only implemented on the HD, so it will not help you. You might look at his old hybrid, with that one you can take the card out once booted, which I think is what you wanted. If that got set up on the HD+ it would make it so the card gets taken out, and it stays on CM10 until rebooted.
Sent from my Galaxy Tab running Tapatalk
Thanks again leapinlar. I try this tomorrow when I again at work.
Have anyone idea or guide how to get never version CM10.1? On my Galaxy Tab 10.1 i use nightly build and it got many many great updates and fixes. For Galaxy i know git and can compile it itself, but for Nook no.
Re: [Nook HD+] CM10.1 development
datas0ft said:
Thanks again leapinlar. I try this tomorrow when I again at work.
Have anyone idea or guide how to get never version CM10.1? On my Galaxy Tab 10.1 i use nightly build and it got many many great updates and fixes. For Galaxy i know git and can compile it itself, but for Nook no.
Click to expand...
Click to collapse
See my edit. For HD only. Only source of CM10.1 is verygreen, and you have to wait for him to update.
Sent from my Galaxy Tab running Tapatalk
Re: [Nook HD+] CM10.1 development
Will updating to the latest Barnes and noble firmware stop SD from booting to jelly bean 2?
Sent from my Barnes & Noble Nook HD+ using xda app-developers app
Re: [Nook HD+] CM10.1 development
Zachinater said:
Will updating to the latest Barnes and noble firmware stop SD from booting to jelly bean 2?
Sent from my Barnes & Noble Nook HD+ using xda app-developers app
Click to expand...
Click to collapse
No. The only things different are improvements.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
Re: [Nook HD+] CM10.1 development
On my HD + the internal memory I'd not accessible while dual booting
Is there any fix for this
nook HD + dual booting cm10.1
Re: [Nook HD+] CM10.1 development
Zachinater said:
On my HD + the internal memory I'd not accessible while dual booting
Is there any fix for this
nook HD + dual booting cm10.1
Click to expand...
Click to collapse
I'm not sure what you mean, while dual booting. You mean while booted to CM10.1? If that is what you mean, it is under the /emmc folder.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
Re: [Nook HD+] CM10.1 development
But my emmc is not accessible while running cm10.1 I can view the files but they are not accessible
For instance the music from emmc does not show
And under storage it doesn't show
nook HD + dual booting cm10.1
Re: [Nook HD+] CM10.1 development
Zachinater said:
But my emmc is not accessible while running cm10.1 I can view the files but they are not accessible
For instance the music from emmc does not show
And under storage it doesn't show
nook HD + dual booting cm10.1
Click to expand...
Click to collapse
You are still not being clear. What do you mean accessible? Do you mean some specific program cannot load the files? And how can you view them, with a file manager? Do you mean seeing the files on your PC? You need to be more specific if you want help.
Sent from my Nook HD running CM10.1 on SD
Re: [Nook HD+] CM10.1 development
Is DRM working on this ROM?
nook HD + dual booting cm10.1
Re: [Nook HD+] CM10.1 development
Zachinater said:
Is DRM working on this ROM?
nook HD + dual booting cm10.1
Click to expand...
Click to collapse
I give up. If you are not going to answer, I won't help.
Sent with XDA Premium from my Nook HD+ running CM10 on SD
update needed
we really need an update
ive been waiting for an update for almost a month now please update this rom
and how do i get drm to work i have netflix but i cant use it cause of drm
Verygreen used to update every couple of days or so, but for the last month development has almost stopped whiich leads me to believe that there are RL issues involved in which case i would think that it is rude to ask for updates. If verygreen can't continue development (for whatever reason) we only have to hope that another dev will continue and build upon his work, there's not much else to do/happen, andvasking for updaters certainly doesn't really help...
Back on topic: this rom is by far the best I've used to my nook. Unstable as the others to be sure but noticeably smoother (maybe it only seems so due to the added animations from 4.2). Also I love the rest of 4.2 additions (notification bar, etc), it would be indeed great see this rom developed further, but as I wrote to my prologue, each to its own time...
By popular demand, I am bringing to you CM10.1 that you can install into Nook's internal ROM.
Note, this version totally overwrites your ROM, so back up everything important before proceeding. This is not a dual-boot solution as before, you do loose B&N ROM for good after installing this.
This is work in progress, yadda yadda.
Simplified instructions if instructions below don't work for you or you cannot follow them.
Get emmc-cwm-early2.1.img.gz, gunzip and write it to an sdcard of at least 1G in size (all content on that card will be lost).
Download CWM recovery (text) or TWRP recovery (gui) zip if you want internal recovery to be replaced with CM one (if you don't know what is it about, then you need ONE of these).
Also download latest binary zip from CM nightlies: http://download.cyanogenmod.com/?device=ovation
Add all these files + whatever other packages you might need right away on to the sdcard.
Boot from that sdcard, and install recovery (if desired) and the cm10.1 binary and whatever else you put there.
Erase /data (During initial install only. this is important to avoid crashes on bootup! Naturally, make sure you have copies of whatever important info from there).
unmount /sdcard and remove the card from the Nook. You might need to use this sdcard for your recovery needs in the future should EMMC content become badly damaged, so probably a good idea to have a copy of it somewhere.
Congrats, now on reboot you'll get into cm10.1 on your Nook HD+.
When you need to get into recovery, you can either do "reboot to recovery" in reboot menu (need to enable that in settings) or reboot the nook, and when you see original nook boot logo, press and hold power + home buttons for about 4 seconds.
If you plan to use USB Host feature, you will need a gender changer, as B&N decided not to release a special cable so far. The control to enable USBHost is in quick settings panel (slide down in the top right corner of the screen to bring it up). (QS controls are not available in CM nightly builds so you'll need to install the switcher app for now if you need it).
Known problems:
- Nook app reports incompatible in market (workaround1: just sideload it ; workaround2: change ro.product.device to nookhdplus in build.prop) - This is because they specifically blacklist Nooks! Note that workaround #2 will actually kill your sound, so revert back when you are done.
- Certain sdcards still remain unstable.
- Google Earth crashes when pressing "my location" button (but works fine otherwise).
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (not really needed, as you can use Quick Settings panel): USBHostSwitcher.apk
Changelog:
13/08/09 - We are official part of CM now, yay! Further updates will be at http://download.cyanogenmod.com/?device=ovation
13/08/01 - cm-10.1-20130801-UNOFFICIAL-ovation-emmc.zip
- Data usage display should work now
13/07/19 - cm-10.1-20130719-UNOFFICIAL-ovation-emmc.zip
- Picked some kernel fixes from omapzoom tree that I think would be useful for us too, this includes some voltage changes (decreases).
- Disabled hwui scissors optimization as it seems to be doing more harm than good.
- Reverted too greedy davlik vm settings
13/07/16 - cm-10.1-20130716-UNOFFICIAL-ovation-emmc.zip *Experimental*
- Update wifi drivers to R5.SP3.06
13/07/11 - cm-10.1-20130712-UNOFFICIAL-ovation-emmc.zip (backup link)
- Added Apple keyboard support
- Updated to CM-10.1.2 for security fixes
13/07/10 - cm-10.1-20130710-UNOFFICIAL-ovation-emmc.zip
- Updated to CM-10.1.1 for security fixes
13/07/08 - cm-10.1-20130708-UNOFFICIAL-ovation-emmc.zip
- NTFS and ExFAT support from upstream
13/07/06 - cm-10.1-20130706-UNOFFICIAL-ovation-emmc.zip
- redone touchscreen sensitivity changing mechanism. (app to control touchscreen sensitivity NookTouchscreenSensitivityAdjuster-4.apk)
13/07/04 - cm-10.1-20130704-UNOFFICIAL-ovation-emmc.zip
- upgraded to fixed SGX DDK [email protected] (this fixes Google Earth, and a bunch of games)
13/07/03 - cm-10.1-20130703-UNOFFICIAL-ovation-emmc.zip Experimental
- experimental touchscreen sensitivity change
- usb ids changed to match stock
- swap support enabled
13/06/30 - cm-10.1-20130630-UNOFFICIAL-ovation-emmc.zip
- Serial number is now visible in Android
- usb audio now actually works (only for output)
13/06/29 - cm-10.1-20130629-UNOFFICIAL-ovation-emmc.zip
- in-kernel bluetooth
13/06/26 - cm-10.1-20130626-UNOFFICIAL-ovation-emmc.zip Experimental
- cpu frequency changes for screen on scenario, new sgx binary blobs.
13/06/24 - cm-10.1-20130624-UNOFFICIAL-ovation-emmc.zip
- more kernel drivers for bt hid, usb 3g modems and gps devices
13/06/15 - cm-10.1-20130615-UNOFFICIAL-ovation-emmc.zip
- WiFi Direct and BT tethering are now working
- /sdcard now points to internal storage.
13/06/13 - cm-10.1-20130613-UNOFFICIAL-ovation-emmc.zip
- Boosted speaker volume. If you do not like new loud volume, flash this reversal zip after every ROM update: quietvolume-2.zip
- zinio now should work out of the box
13/06/11 - cm-10.1-20130612-UNOFFICIAL-ovation-emmc.zip
- Fixed HDMI audio
- Added USB audio support
13/06/08 - cm-10.1-20130608-UNOFFICIAL-ovation-emmc.zip
- Fixed nav bar settings crash
13/06/05 - cm-10.1-20130605-UNOFFICIAL-ovation-emmc.zip
- USBHost access is now conveniently located in QuickSettings. (IF you use some mod that disables quick settings, you still need my old ugly USBHost switcher app, just sideload it).
- now any (one at a time) usb storage should be automounted no matter how you plug it.
13/06/02 - cm-10.1-20130603-UNOFFICIAL-ovation-emmc.zip
- Forced USB Host support.
13/05/30 - cm-10.1-20130530-UNOFFICIAL-ovation-emmc.zip
- No Nook-specific changes, based on CM10.1-RC3
13/05/27 - cm-10.1-20130527-UNOFFICIAL-ovation-emmc.zip
- Fixed microphone input volume
- Kernel change to hopefully better work with some sdcards.
13/05/12 - cm-10.1-20130512-UNOFFICIAL-ovation-emmc.zip
- Fixed A2DP audio
- Fixed booting when not connected to PC/charger.
13/05/11 - cm-10.1-20130511-UNOFFICIAL-ovation-emmc.zip
- Should fix sgx crash on startup for those affected -- not.
- Cover close now should sleep the device (please test)
- Updated screen properties to highdpi (though that did not fix Nook app compatibility in market)
- Baselined on CM10.1-RC2
13/05/10 - cm-10.1-20130510-UNOFFICIAL-ovation-emmc.zip
- Wifi battery drain should be gone now.
13/05/05 - cm-10.1-20130505-UNOFFICIAL-ovation-emmc.zip
- Fixed mmc presentation, BT, sdcard mounting.
13/05/04 - cm-10.1-20130504-UNOFFICIAL-ovation-emmc.zip initial release.
Thanks for this though.
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Also I don't think cm10 is needed really.
I think its best to put the work into cm10.1 as its the latest platform and try bring that up to the same stage as cm10.
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
HiddenG said:
Wow, thank you once again verygreen! Thank you so much for your efforts!
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Regardless, appreciate your efforts once again!
Click to expand...
Click to collapse
Is the reboot to 99% problem solved ? This is the biggest issue to me.
sorrowuk said:
Verygreen, I am interested how this boots without sdcard as before the expliot worked because B&N left dev code to boot a kernel from sd card.
What exploit is used to boot from internal since sdcard isn't used.
Click to expand...
Click to collapse
Same method as Bauwks, B&N forgot to fix it, they fixed some other possible vectors only.
I was holding to this knowledge hoping that it would be useful on next B&N reader, but it does not look like they'll release another omap-based one, so no need to keep suffering anymore.
So here's hope whatever they release next, the debugging code will remain in place
HiddenG said:
I'm just wondering, does this overwrite the stock ROM, this no dual boot? Also, are there any performance differences?
Click to expand...
Click to collapse
Yes, this does overwrite stock ROM, so no dualboot.
While it's possible to perform some hair-splitting by putting multiple kernels into boot partition, that's quite a bit of hassle + all the /data splitting, so I decided to not go that way, at least yet.
There are performance differences. I did not perform any real studies, but I was shocked at how fast the install phase in cwm works compared to sdcard.
lchen5 said:
Is the reboot to 99% problem solved ? This is the biggest issue to me.
Click to expand...
Click to collapse
Yes, it is solved by removing the ROM, so nothing is left there that could complain about cards with too many partitions
Awesome
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
aszid said:
I've gotten this loaded up this morning, haven't done a whole lot with it as of yet, but it did boot right up
I have noticed one thing that is not working correctly, specifically the sd card. It's reported as not mounted.
Click to expand...
Click to collapse
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
Yes, I was just going to post that. Verygreen forgot to change the vold.fstab file from the sdcard version to emmc version.
Go to /system/etc/ and edit the vold.fstab file to say "/storage/sdcard1 auto" instead of "/storage/sdcard1 5". Just change the 5 to an auto. Then reboot and it should be ok.
Click to expand...
Click to collapse
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Follow up question
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
For restore (note, I did not really test any of these steps, but that's how it should unfold):
boot into recovery image from sdcard you made at the beginning.
Upload the backup boot image there (adb push mmcblk0p4 /tmp)
then do adb shell and in there write the image in place:
dd if=/tmp/mmcblk0p4 of=/dev/block/mmcblk0p4 bs=1048576
then do:
mount /bootdata ; rm /bootdata/BootCnt
The removal of BootCnt will tell stock u-boot to force factory restore.
now remove sdcard and reboot, the Nook will do factory restore and you are back to some sort of early 2.0.0 B&N release.
verygreen said:
It's always the small things that gets forgotten, sigh.
I knew I needed to update that, but did not find it at 4am. Now it's in my tree, so next version will have it fixed.
Also need a better way to write sdcard image, I guess, without uploading a whole gig or so of zeros which will get slow. I tried to put in some shortcuts to minimize the write area, but failed so far. Since everything is in the same partition, changing stuff on the fly is hard.
Perhaps a solution where we only use sdcard as means to do initial bootstrap and write correct recovery and use /data/media as the actual sdcard would be better after all.
Click to expand...
Click to collapse
I've been trying to examine what you have done here, and have most of it figured.
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
A suggestion on the CWM recovery.fstab. Change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
That CM zip is pretty straight forward where it just flashes the rom to emmc /system and replaces the boot.img.
Click to expand...
Click to collapse
Yes, it's pretty straight-forward, and that was one of the goals. Unlike Kindle where you need to jump through some crazy hoops due to Amazon design decisions, Nook is significantly more relaxed.
The CWM looks straight forward too, but you must use the empty file for something and I can't quite figure that. I thought maybe you were using it to mount something on emmc but I see no code to do that in the ramdisk. You might have the code in a customized init binary. Recovery looks like just a normal 6.0.3.2 recovery from CM.
Click to expand...
Click to collapse
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
The only difference between this CWM and sdcard cwm for sdcard installs are: removed repartitioning code in postboot script and updated fstab to point back at emmc.
A suggestion on the CWM recovery.fstab, change the boot partition fstype from vfat to emmc and backup/restore will handle it properly. And change the emmc to datamedia and /dev/null instead of vfat and 0p10. That way the emmc media partition will mount properly.
Click to expand...
Click to collapse
Aha, thanks. I'll try this and it'll probably solve the remaining CWM problems for me.
Also need to do twrp image, I guess.
verygreen said:
The recovery IS straighforward, there's no modified init or anything like that. I am not sure what empty file do you refer to.
Click to expand...
Click to collapse
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
And if you make those mods to the recovery.fstab, then users can use that CWM to reflash back to stock using the B&N zips.
leapinlar said:
I'm talking about the "file" in the recovery image. It is about 950MB and all zeros.
Click to expand...
Click to collapse
Whoops, forgot to remove.
This is how I zero out sdcard content so it better compresses before uploading it somewhere.
jentous said:
Could one of you guys explain a method of going back to stock from this? What I mean, is it possible to install Leapinlar's version 2.1 back to the emmc using the recovery used to install this emmc-based CM 10.1? If you suggest that we backup before installing this ROM does that mean that we can use that backup to restore the stock we have on emmc now back to emmc if this were not to work out well?
Click to expand...
Click to collapse
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Got it going
Thanks Verygreen and Leapinlar.
I got it installed and I saved the boot partition just in case. I hopefully will not be needing to restore, but it is nice to know that I can.
The installed ROM appears snappy and I will report back any issues I discover.
my sdcard is working great after updating the mount. Thanks!
leapinlar said:
Based on what verygreen said in the posts above, you should be able to use my stock CWM SD to both backup and restore his new setup. And you can restore an earlier backup of stock too. You can use my 2.1 zip on my thread to put the new stock on if you want replacing his CM10.1 on emmc.
Thanks verygreen, you are awesome!
EDIT: Yes! I just flashed verygreen's new CM10.1 emmc to my internal memory using my stock CWM SD. Worked perfectly.
Click to expand...
Click to collapse
verygreen said:
I just uploaded emmc-cwm-early2.img.gz with fixed recovery.fstab and a zero file removed as well.
Click to expand...
Click to collapse
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Thanks for all the great work!
aszid said:
Is there any effective difference between the 2 recoveries? That is.. is there any reason i should be bothering to keep 2 different recovery SD cards?
Click to expand...
Click to collapse
There's no great logic in my recovery, just an image I use to test-drive my installs for now.
So you can use whatever other recovery you like.
I see there's this new CM11 going, and thanks to @Hashcode who solved most of the complex problems already, here's my first stab at CM11 on our Nook HDs that installs into internal memory (EMMC).
The install is a lot similar to how it was done in CM10.2 days, but you will need a new recovery image (and a new sdcard image for those doing initial install):
So, For Nook HD+: Initial ovation sdcard image (cwm) | ovation recovery image (CWM)
For Nook HD: hummingbird Initial sdcard image | hummingbird recovery image (CWM)
I did some light testing and things seems to be working for whatever light loads I came up with, but still there are probably tons of problems that I have not yet noticed. Please write in the comments about what's broken and I'll try to fix it. Once it's good enough, I'll try to get official nightlies going for CM11 as well, I guess.
Latest CM11 EMMC images are now available as CM11 nightlies at:
For Nook HD+ get ovation builds
For Nook HD get hummingbird builds
There also might be experimental builds available referenced below in the history section.
(Also for completeness, For Nook HD+ sdcard image cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
For new Installs:
Download the initial sdcard image
ungzip and write to sdcard using dd (winimage or whatever for those stuck on Windows)
Instert the card into your nook and reboot
Flash the recovery image
Flash cm11 image
Flash whatever other extra things you need like gapps
remove the sdcard
reboot the nook
For upgrades from CM10.x (the only tested are 10.2 and 10.1). If you have any problems after upgrade - you'll need to do factory reset to clear /data:
Download recovery zip and CM11 install and place it on the nook
Reboot into recovery you already have installed
Flash the recovery zip you just downloaded
reboot into recovery again (This is important! Failure to do this will botch your upgrade and you'll need to wipe /data) so that the new recovery is started.
Install CM11, install other stuff you need like gapps
reboot
enjoy
Note: After upgrade you will need to reenter all of your wifi passwords.
Useful apps:
Overall loudness and volume control app: NookHDVolumeAdjuster-1.apk
Touch screen sensitivity control: NookTouchscreenSensitivityAdjuster-4.apk (backup link)
USB host control (usually only needed on official CM builds, as otherwise you can use Quick Settings panel): USBHostSwitcher.apk
Known problems:
- attempting to reformat external sdcard from android crashes volume manager - seems to be upstream problem of some sort. The sdcard is left in some strange state, so don't do it. (if you did, reformat the sdcard on your PC, all data will be lost either way)
Changelog:
2014/11/297 - Bring sdcard build to current source version:
* cm-11-20141129-UNOFFICIAL-ovation-sdcard.zip
2014/08/17 - Bring sdcard build to current source version:
* cm-11-20140817-UNOFFICIAL-ovation-sdcard.zip
2014/01/18 - Fixed 1080p movie playback on Nook HD+:
* cm-11-20140118-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140118-UNOFFICIAL-ovation-sdcard.zip
2014/01/17 - Fixed headset mic issue
* cm-11-20140117-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140117-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140117-UNOFFICIAL-ovation-sdcard.zip
2014/01/15 - Switched to TI wpa supplicant, should fix a bunch of wifi-related issues
* cm-11-20140115-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140115-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140115-UNOFFICIAL-ovation-sdcard.zip
2014/01/09 - Fixed inability to write to sdcards.
* cm-11-20140110-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140110-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140110-UNOFFICIAL-ovation-sdcard.zip
2014/01/08 - Misc updates: autodetect sdcard format, not just vfat. fuzzy touch patch courtesy of D Marble, bt-pan services that reportedly fix bt tethering for some people.
* cm-11-20140109-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140109-UNOFFICIAL-hummingbird-emmc.zip
2014/01/06 - Initial release
* cm-11-20140106-UNOFFICIAL-ovation-emmc.zip
* cm-11-20140106-UNOFFICIAL-hummingbird-emmc.zip
* cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip
The screen kept flickering like a tube light few times.
Thank you! Welcome back
Sent from my BN NookHD+ using xda app-developers app
Welcome back, you've been missed greatly. I kept telling everyone not to panic, you would be back.
Sent from my BN NookHD+ using XDA Premium HD app
Thanks dude. I was hoping you'd start building it. Downloading now!
Working well so far. Thanks for making it and glad to have you back.
for those who need gapps you could see below (Be sure to choose 4.4.2 gapps.)
Link for PA gapps : http://forum.xda-developers.com/showthread.php?t=2397942 <MINI MODULAR PACKAGE 121 MB>download link http://goo.im/devs/paranoidandroid/roms/gapps-mini/pa_gapps-modular-mini-4.4.2-20131230-signed.zip
My personal favorite is BaNK's gapps : http://forum.xda-developers.com/showthread.php?t=2012857 <core gapps only, 17MB>download link http://www.androidfilehost.com/?fid=23269279319195954
Thanks for starting the work again -- I can't wait for official nightlies. And welcome back.
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Nice to see this, I've used Bokbokan's eMMC build off his blog with TRIM support by default (MAG2GA ver06 10/2012), and I've used yours with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
It would be interesting to know if it presents visible differences from CM 10.2 regarding responsiveness, especially with ART enabled. It's the last fort to be conquered with our nooks (trim+art). Sadly my nook is not back yet so any reports would be welcome.
Awesome
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
jjjooonnn said:
Nice to see this, I've used Bokbokan's eMMC build (off his blog) with TRIM support enabled by default (MAG2GA ver06 10/2012), and I've used your CM10.2 with TRIM everything worked great.
Does this build come with TRIM enabled?
Will this be updatable via CM updates in settings?
Thank you for making my tablet a tablet again!
Click to expand...
Click to collapse
It should be updatable via the settings once it's an official built. Right now, all of the builds are unofficial ones, so they have to be fully downloaded and flashed.
verygreen is the official device maintainer for CM though, so once he "approves" of the build, it will be built nightly by the CM servers, and then it will be fully integrated into their update mechanism (or CyanDelta if you use that). Just like the 10.2 builds.
TeutonJon78 said:
Also, it seems that we have to use CWM. Is there a reason TWRP isn't supported, or is that on the to-do list?
Click to expand...
Click to collapse
It's on the todo list, but cwm was easier to make at first (as in, next to zero effort)
jjjooonnn said:
Does this build come with TRIM enabled?
Click to expand...
Click to collapse
Yes, this has TRIM-enabled kernel, though I have not decided if I should do it for the official releases.
Have there been any more bricks with the trim-fixed kernels in the past couple of months?
Will this be updatable via CM updates in settings?
Click to expand...
Click to collapse
I guess yes, once there are official nightlies again. But I want to make sure it's at least of adequate quality before enabling that.
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Good job!
I can't speak for anyone but didn't see anything from a quick search in the post: TRIM FAQ. I can attest that mine works and I believe it should be one of the bad eMMC (MAG2GA ver06 not ver05).
I did test TRIM (vdc fstrim dotrim) no issues, and found the CM11 under updates (after I updated to CM11) so I can attest to that much!
Thanks for the reply
Darrian said:
Just an advisory: I just flashed this over Succulent's rom with no problems, BUT I lost all my saved wifi profiles and had to reflash gapps. Not any big deal, but to anybody else who plans to do that and isn't coming from CM 10.1/2: be prepared. Relatively painless upgrade, though. Very glad to see TRIM enabled. Don't plan on enabling ART until xposed/gravitybox is compatible. This is much, much smoother than Succulent's build.
Click to expand...
Click to collapse
I would say they are about same smooth. Succulent's build has some nice framework and more option in performance settings. But just from system ui or user experience they are almost the same. Not could I tell the difference in app opening or transition.
Stock launcher Does lag when press the app drawer butter from home screen. But I use Nova launcher to solve the problem.
No find significant performance inprovememt over cm10.2 yet. Maybe Kitkat just does more job in UX polishing rather then performance.
Hopefully we could find some Performance MOD to use in KitKat.
It may very well be due to the fact that I upgraded from CM 10.2 and did not do a clean install, but for me Succulent's build was extremely laggy, many apps froze frequently, and when too many apps (more than like 3) were open it would reboot itself. I have none of those problems with this build, it's super smooth and fast and I haven't had any apps become laggy or crash or reboot my tablet. And this is upgrading from CM 10.2>Succulent's KK>Verygreen's KK; I still haven't done a factory reset and don't plan to unless it becomes necessary later. I use Nova as well. I'm not saying Succulent's build is bad, I thought it was bearable enough to use and was planning on using it long term, updating with each new build until it got to where I thought it should be, but then I installed this build and the difference is staggering. If I reflashed Succulent's build and wiped my data partition I might have a better experience, but now that I have this I don't see any need to.
this is great, glad to see you're back =)
my nook is currently being borrowed, i was wondering if anyone could quickly benchmark it?
thanks
Thank you Verygreen for this new build.
I will try it today.
I have 2 questions about CM11 and Nook HD+ hardware:
- did the HD+ have a bluetooth low energy (BT 4.0) chips?
- did the HD+ have a Low-power audio playback (kitkat new feature) capable chips?
If yes, is it included in this new CM11 build?
Thanks
Edit:
I found that Nook HD+ has wl1271l chip and uses wl12xx driver. That chip is BT 4.0 and BLE. See here http://www.rfm.com/products/data/wls1271l.pdf
But this thread show that BLE isn't activated in CM.
verygreen said:
久しぶりでした
(Also for completeness, For Nook HD+ sdcard image cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip, | initial sdcard image for ovation )
Click to expand...
Click to collapse
Thanks verygreen. Great to see your are back in action.
The SDCARD image link is downloading emmc image. Here is the correct like if any one is looking.
cm-11-20140106-UNOFFICIAL-ovation-sdcard.zip