Database Info

[NookHD+] CM10.1 native emmc install Now part of CM Nightlies - Nook HD, HD+ Android Development

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.

Related

First of all... Thanks Chainfire!!!! This is totally based on your work.... i made only some MOD....
Ok, the work is quite finished... the CF-ROOT for I9003 is ready!
I called this "beta version" (since i need your tests/opinions) but all might work.
IMPORTANT: This is only for KPH Firmware!!!
You can flash this over any other CWM or over the stock FW.
Many people will ask "Why i have to install this?"... because with this your phone will have:
- Root ( don't need to use SOC or any ZIP);
- Busybox 1.17.2;
- Sqlite3 v3.7.2;
- init.d support (you can put in the folder /system/etc/init.d all the script that you want to be loaded at the startup);
- New fixed CWM ( unyaffs issue has been fixed - offline charge fixed - USB storage mode while in CWM fixed);
- Add EXT4 support to the phone ( so you can convert the filesystem to ext4 to improve performance);
- full working CWM Manager (backup - restore - delete backup - install apk - flash update.zip - flash kernel - reboot to CWM);
- Tweaks Manager with various tweak ( Ram Min Free - SD Speed - I/O Scheduler - Kernel Scheduler - CPU Conservative Governor - Swappiness - Ram Script by Juwe11 - Media Stagefright)---> Many people asked for Juwe Ram Script ---> to enable it completely choose in the Tweaks Manager: Ram Script - Ram Min Free and Swappiness;
- Auto ZIP-Align on boot - You can choose it in the tweaks app(NEW)
- Reviewed tweaks values (some from darky's rom some from hardcore some from other post in XDA)( thanks to bigeyes0x0 and Misledz )(NEW)
- Custom Boot-Animation support (place your custom bootanimation in /system/media/ and call it sanim.zip)(NEW)
To do:
- other tweaks suggested by you...
- whatever can be added.
Let me know what you think
HERE you can find the original post.
HOW TO INSTALL:
1- Flash with Odin the .tar file
or...if you went from a previous version of CF-ROOT
2- Download the .zip file into the external SD the open CWM Manager --> flash Kernel --> select the file you have just downoaded
IMPORTANT:
If you cannot find the two apps on your app drawer maybe you haven't space left on /system so delete some unused apps like aldiko, delere /system/cfroot folder and reboot
IMPORTANT/2: after the flash the phone might take some time to boot. You might think that it freeze on Samsung Logo but it's normal cause the auto-zipalign proc need some time. Just Wait.
UPDATE: Added CF-ROOT with my custom kernel. This have Ext4 inside the kernel (no modules) and OC to 1.1 Ghz. I think that it is secure. I haven't test it very well so please report me the issues you will find.

!
Version 05.09.2011 Changelog:
- added Graphics Boost Tweak (thanks Gana)
- added acid tweaks (thanks to the people that worked on it .. specially Bigeyes0x0);
- reviewed 00tweaks file by Bigeyes0x0;
To disable journaling on ext4 partition apply the attached journaloff.zip in CWM (Not CWM Manager app - it must be fixed).
There're two version of the CF-ROOT, the version with **CWM_Manager** can be flashed with CWM Manager App (select flash kernel) the other with odin (like always)
UPDATE 20.10.2011:
CF-ROOT for XXKPM can be found HERE:
- Standard Version --> http://www.multiupload.com/S463K75UED
- Surprise version ( i suggest you this) --> http://www.multiupload.com/G20L6PL5WC
What's new ?
- I finally finished the custom bootanimation support.... now works like he have to works. Just copy your bootanimation into /system/media and rename it to sanim.zip.... i think that here you can find what you need http://forum.xda-developers.com/showthread.php?p=17322814#post17322814
IMPORTANT!!!
If you have installed the beta version you must know that the ext4 conversion for that doesn't work properly. Ok, system, cache and dbdata will be on ext4 but data not. This because the init binary check on boot if /data have rfs FS and, if not, it format the partition wiping all your data.
In the new version i modified the init binary so it cannot do it more
I must say that i became mad to discover this damn thing !

A few questions: Are you using the latest fixed version of CWM? Also you mentioned that you would be releasing another update soon regarding the Nandroid backup image corruption issue. Is it in this release?
Also: Is this an alternative to ROM manager, apart from the inclusion of the tweaker tool?
Regarding the enhancements, could you please elaborate on some of them and what is safe/not safe to use (particularly in the tweaks and what they do)?
What I understood, after looking over all the posts, was that you optimized the CF-Root by chainfire for the i9003, by using a compatible Root, CWM, and adding an ext4 kernel? Are you going to port the ext4 converter tool as well? Will we be able to use an external SD card with ext4 formatting (Could be used to store files larger than 4GB)?
Sorry about the ton of questions. Trying to learn, and what better way to learn than from the best!
I'm going to take it out for a test drive now on XXKPE with ext4! Will report back later!
Thanks for your valuable work, I'm a huge fan!!!
Cheers
Update: Confirming that the passive charging bug has been fixed! Thanks Skin1980!
I cannot find the CWM or Tweaks icons in the app drawer as indicated in your screenshots. I can access CWM recovery mode using the 3 button combo though.
I had installed the last version of CWM by Amit and formatted with ext4 and I just used ODIN to flash over that install. I tried flashing again, still not appearing in app drawer. Any solutions?

Great job skin.. Hoping for the early release of a stable one.. Will test it later
Sent from my GT-I9003 using XDA Premium App

it's great...>.<

Auguri! Ok wow, This is pure genius . I've always been wondering what our CWM were based off. I guess using this would fix most issues people get when flashing CWM, since it's based off the original firmware
Also I'm loving the tweaks, they seem to make the phone more smooth, Although I've seen a few bugs after applying this I can't seem to use the V6 charger script anymore I get an error, will be posting one shortly. There are some minor hiccups in between and I tend to get FC on some apps when I multitask.
Edit: Turns out It's busybox related, no shell access. I've tried launching Busybox by Stericsons to check and It says no root access was given and boots me out.

i happy that u r belong to this community
Is there any recovery module or tweak available, in which we can handle basic file operation like copy, move from sd card to system or any thing similar?

Erahgon said:
A few questions: Are you using the latest fixed version of CWM? Also you mentioned that you would be releasing another update soon regarding the Nandroid backup image corruption issue. Is it in this release?
Also: Is this an alternative to ROM manager, apart from the inclusion of the tweaker tool?
Regarding the enhancements, could you please elaborate on some of them and what is safe/not safe to use (particularly in the tweaks and what they do)?
What I understood, after looking over all the posts, was that you optimized the CF-Root by chainfire for the i9003, by using a compatible Root, CWM, and adding an ext4 kernel? Are you going to port the ext4 converter tool as well? Will we be able to use an external SD card with ext4 formatting (Could be used to store files larger than 4GB)?
Sorry about the ton of questions. Trying to learn, and what better way to learn than from the best!
I'm going to take it out for a test drive now on XXKPE with ext4! Will report back later!
Thanks for your valuable work, I'm a huge fan!!!
Cheers
Update: Confirming that the passive charging bug has been fixed! Thanks Skin1980!
I cannot find the CWM or Tweaks icons in the app drawer as indicated in your screenshots. I can access CWM recovery mode using the 3 button combo though.
I had installed the last version of CWM by Amit and formatted with ext4 and I just used ODIN to flash over that install. I tried flashing again, still not appearing in app drawer. Any solutions?
Click to expand...
Click to collapse
1- The CWM used is always the last... if i'll update the CWM i'll update the CF-ROOT;
2- The CWM fixed reguard nandroid backup is under test;
3- My CWM isn't ROM Manager compatible... with the CWM Manager from Chainfire you can do a lot of things without going into CWM
4 - to convert in EXT4 just follow the guide on the other thread;
5- Not sure if you can format in XT4 your external_sd... try ;
6- The tweak are all sure... now i haven't time to exlplain better... some don't work.... some other work.
7- If the icon don't appear in app drawer try to check into system/app if the two files are there... if not try to remove /system/cfroot folder and reboot. Maybe your system folder is full so you can install they manually, the original apk are inside /res/misc/ folder.
8- bye

for me wifi not working obtaining ip address,gps not lock can i flas normel bootimg.ur work is awesome thx

bala242 said:
for me wifi not working obtaining ip address,gps not lock can i flas normel bootimg.ur work is awesome thx
Click to expand...
Click to collapse
I'm sorry.. for me everything is working...Before my CF-ROOT all works?

ur a superhero man!!
great ;-)

Skin1980 said:
I'm sorry.. for me everything is working...Before my CF-ROOT all works?
Click to expand...
Click to collapse
ya everything work before,can i reflas ur ver cwm?any body get this error?

Is there any tweak for increasing the 2g speed ??
or getting 3g speed in 2g plans...
I need this very badly...

I am not getting exact idea that what exact cf root does??? Or how cf root is so special...?? Will this make our work easy to do changes in kernal (that would be great)...???
Please can anybody in simple language....!!!

anigr88 said:
Is there any tweak for increasing the 2g speed ??
or getting 3g speed in 2g plans...
I need this very badly...
Click to expand...
Click to collapse
What your asking for is impossible.

Update!
The problem I had turned out to be due to the lack of space in the "/system" folder - as you had predicted Skin1980! Once I deleted some unnecessary software, I was up and running fully within minutes!
The phone works great! The fixes are really good! Having no issues except for one so far. I can't seem to mound "sdcard" in CWM recovery mode and cannot do a restore, for the same reason, from the CF-ROOT menu.
I have a feeling it's something I did wrong earlier, so I'll reflash completely and try again ('cause I have a lotta time on my hands atm and I want the bestest possible phone I can get).
Note: This doesn't seem to be compatible with DDKB2. Assuming that this is mainly for GB firmwares? Can someone corroborate this?
As usual, thanks!

Erahgon said:
The problem I had turned out to be due to the lack of space in the "/system" folder - as you had predicted Skin1980! Once I deleted some unnecessary software, I was up and running fully within minutes!
The phone works great! The fixes are really good! Having no issues except for one so far. I can't seem to mound "sdcard" in CWM recovery mode and cannot do a restore, for the same reason, from the CF-ROOT menu.
I have a feeling it's something I did wrong earlier, so I'll reflash completely and try again ('cause I have a lotta time on my hands atm and I want the bestest possible phone I can get).
Note: This doesn't seem to be compatible with DDKB2. Assuming that this is mainly for GB firmwares? Can someone corroborate this?
As usual, thanks!
Click to expand...
Click to collapse
after a whole day of using it. The phone will tend to lag and build up after a while. You'll notice the phone becomes slow again. I don't know what's going on.

Misledz said:
What your asking for is impossible.
Click to expand...
Click to collapse
I just want a small boost in the speed ....

Misledz said:
after a whole day of using it. The phone will tend to lag and build up after a while. You'll notice the phone becomes slow again. I don't know what's going on.
Click to expand...
Click to collapse
I did notice that initially it was fast. But as I kept it going through the day to recalibrate the battery, it did slow down and start to lag. I thought it was something to do with that. Also I felt that I had done something wrong with the flashing.
Going to overhaul my phone completely: Format, re-partition, XXKPE install (flashing twice), flash fixed CWM from the other thread, root using SOP 2.1.1, install busybox requirements for deodexing (this failed for me the last few times), restore settings using Titanium Backup, Nandroid backup, ext4 this baby, restore, and then install CF-ROOT to monitor.
Wish me luck! See you guys on the other side... again!

anigr88 said:
I just want a small boost in the speed ....
Click to expand...
Click to collapse
You've got the wrong thread mate!
Your bandwidth is capped by you operator and is dependent on how much they allocate you. On top of that 2G is physically limited to certain speeds which, usually, cannot be surpassed by legal means, and the illegal ones give you too less of a boost vs complications and errors to even bother about (I mean big ass hardware)!

Team Win Recovery Project 2.x, or twrp2 for short, is a custom recovery built with ease of use and customization in mind. It’s a fully touch driven user interface – no more volume rocker or power buttons to mash. The GUI is also fully XML driven and completely theme-able. You can change just about every aspect of the look and feel.
Phone look:
Tablet look:
CHANGELOG for 2.6.3.0:
-Proper backup and restore of SELinux contexts (thanks to Tassadar)
-Pull in some ROM information for backup name generation
-Merge all recent patches from AOSP bringing TWRP up to date with Android 4.3
-Add 1200x1920 theme (thanks to Tassadar)
-A few other fixes and tweaks
CHANGELOG for 2.6.1.0:
-Initial SELinux support (only a few devices, need testers so come by IRC if your device doesn't have it and needs it)
-Initial support for f2fs file system formatting (Moto X)
-Update SuperSU install for 4.3 ROMs
-Fixed a permissions bug on files created during backup
-Fixed a bug that caused TWRP to not wait for compressed backups to finish causing 0 byte files and md5sums to not match
-Fixed decryption of encrypted data so that both TouchWiz and AOSP decryption are possible
-Ignore lost+found folder during backup and size calculations
-Various other minor bug fixes and tweaks
CHANGELOG for 2.6.0.0:
Special Note: If you are running a custom theme, you will likely need to remove that theme before updating to 2.6.0.0 as your custom theme will likely not have some of the new changes visible (e.g. you won't be able to encrypt a backup)!
-Can encrypt a backup to prevent theft of private data from your backup files
-Updated graphics / icon courtesy of shift
-Updated exFAT to latest commits
-Fixed a problem with Samsung TouchWiz decryption
-Update SuperSU binary
-Fixed saving of backup partitions list
-Fixed saving of last used zip install folder
-Fixed backup of datadata on devices that use a separate partition for datadata
-Fixed some issues with the advanced wipe list (android_secure, can now wipe internal storage on data/media deivces and wipe data on the advanced list no longer formats the entire data partition)
-Fixed some problems with partitioning a SD card
-Various other bug fixes and tweaks
Notes about encrypted backups:
Why encrypt your backups? -- Most people store their backups on the device. Any app that has permission to access storage could potentially read your backup files and try to harvest your data. Encrypted backups also provide an added layer of security if you move your backups to other storage devices or to the cloud. The encryption that we're using is probably not strong enough for enterprise level security, but should be strong enough to make it significantly difficult to get to your data.
Encryption is using OpenAES which uses AES 128-bit cbc encryption. If you happen to use a longer password (over 16 characters) then the encryption strength improves to 192 or 256 bits. Do not forget your password. If you forget your password you will be unable to restore your backup. We don't encrypt the entire backup. Encryption is very CPU intensive and can be fairly slow even when we spread the workload over multiple cores even on the latest high-end devices. To ensure that encrypted backups don't take forever, we don't encrypt any other partitions besides /data and in /data we don't encrypt /data/app (or other app related directories where apks are stored) and we don't encrypt dalvik cache.
DOWNLOAD:
The fastest and easiest way to install TWRP is to use the GooManager app:
Play Store Link
Direct Download
1) Install GooManager from the Play Store
2) Open GooManager and provide root permissions
3) Hit Menu (or the button with the 3 dots on your screen) and then Install OpenRecovery
OR:
You can find more information and download links on our website!
BUGS:
If you have found a bug, please consider posting it to our github issues log. It's pretty much impossible for us to keep up with the more than 40 threads that we have for the devices that we "directly" support. If you have a significant problem that cannot be answered in this thread, your best bet is to PM me directly, contact us via our website, or find us in our IRC channel below. If you see someone that's struggling, feel free to point it out to us. We need your help to help us keep track of all of our devices! Thanks!
SUPPORT:
Live support is available via #twrp on Freenode with your IRC client or just click this link.

Changelog: See our website!

FAQ:
Install as a Flashable Zip? [RECOMMENDED]
Download flashable zip from the OP and rename it "PG06IMG.zip" (without the quotes)
Place in the root of the sdcard
Power off phone (make sure you turn off hot boot or pull the battery when it's off)
Power on the phone holding power and volume down
Follow the prompts to flash it
Delete .zip (PG06IMG.zip) after booting
Enjoy
How to install with Fastboot:
Download the fastboot binary for your computer from HTC
Connect your phone and boot it into fastboot
Run fastboot with the command
Code:
fastboot flash recovery path/to/recovery-twrp-speedy-1.1.0.img
Does this back up Wimax partition?
That is an option if you chose. Recommended to make at least one backup of just wimax and store that somewhere safe.
The screen went black after doing [insert random function]. What is the issue?
When testing the recovery early on we noticed fastboot wasnt a stable way to flash the recovery. Random issues would arise after using the method. As a result and a solution, flashing the recovery via the PG06IMG.zip is recommended to avoid such issues. Please try this as a solution.
I found a bug! What do I do?
Well you're probably going to want to post here and see if other people are having the same issue. We're also going to start tracking bugs on Github along with our project. This will let you see what issues we are aware of. You can submit a bug here: https://github.com/TeamWin/Team-Win-Recovery-Project/issues Be sure to include how you came about the issue as well as list your device and how you installed twrp.
Have a great new feature idea for TWRP?
Submit it on our Github page! It'll help us track it and notify you of the progress. https://github.com/TeamWin/Team-Win-Recovery-Project/issues
Why should I use this over ClockworkMod?
While all three recoveries offer roughly the same abilities (backup, restore, flash) we feel like ours adds a bit more in addition to the basics as well as blend some of the more useful features. A few differences to hightlight:
USB Mass Storage mode (Not in CWM)
Re-organized menus with most commonly used features on top
Saveable settings for all preferences selected
Date and battery display (configurable timezones)
Ability to auto-reboot after flashing
Color themes
Capacitive button support
Go a head and give it a try! You've got nothing to lose. If you don't like it you can always roll back to whatever recovery you want. Of course, shift might go all Emo Pony on us, but he'll get over it.

Sweet! First post! Time to get rid of rom manager!
Teleported from my Shifty Speedy using Tapatalk

Nice! Congrats on the release on the evo shift!

Thank you for this amazing recovery teamwin! Way way better then anyone ever expected! CWM will prolly never be used again lol
Supremely Shifted

ZOMFG!!

yeah, i'm pretty sure this is wood i'm sporting

Yeah, been using this since last night, it is awesome. And clockwork did have USB storage mode, its in the advanced settings, not that it matters anymore.

Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk

thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Same thing here.. Had to do a battery pull.
Sent from my PG06100 using Tapatalk

Haha... You can still use RM to reboot to TWRP recovery and when I tried to backup my ROM (through RM) (just to see what would happen) it just sends me to TWRP recovery as well...
from the "CRACKED" Speedy EVO Engine...

thronnos said:
Found bug....
Rom: CM7 nightly 214(latest)
Kernel: PershootV9
Twrp install method: bootloader
Bug: whenever I go to fix permissions, the green progress bar will go all the way to them end and then freeze... I did it twice to make sure, but i needed to pull the battery both times
Teleported from my Shifty Speedy using Tapatalk
Click to expand...
Click to collapse
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.

good job man. . .thank you

jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
Not doubting you! But with CWM it took barely a minute.
Teleported from my Shifty Speedy using Tapatalk

jesusice said:
Are you sure you just didn't give it enough time? I've noticed that the progress bars actually bear no relation to the actual progress. I'm fixing permission in terminal now and I can tell you, it takes foreffingever. Haven't tried in recovery yet but I know not to believe the progress bar.
EDIT: In terminal it took 8min 24secs.
Click to expand...
Click to collapse
I waited a good 5 minutes after the "end" of the progress bar and finally did a battery pull. I was able to fix permissions through terminal, just didn't work through recovery.
Sent from my PG06100 using Tapatalk

noob question but will this also restore backups made from cwm?

hoesnaps said:
noob question but will this also restore backups made from cwm?
Click to expand...
Click to collapse
No. You'll need to make fresh backups
Sent from my PG06100 using Tapatalk

Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium

sparksco said:
Sweet new recovery. Does it support partitioning of sdcard yet? I think I'll wait for TWRP 2.x
Sent from my PG06100 using xda premium
Click to expand...
Click to collapse
It has the option to partition but I haven't tried it yet... anyone?
Sent from my PG06100 using Tapatalk

Hola peoples!!! Ok so I just thought I'd create my own thread on this matter. Mustangtim started one in apps and themes (and here is the link to that thread) but since I'm taking over this project it was brought to our attention that this should be in the dev section as its no longer just an app.. I am actually tearing .imgs apart trying to figure out what the deuce.
FIRST OFF THIS IS A WORK IN PROGRESS, WE ARE NOT YET FULLY SUPPORTED. HOWERVER I'M DOING MY BEST TO CHANGE THAT.
Secondly if you want to help get this started please visit the market and grab the app here. Its a $3 dollar app for unlimited amount of roms, based on your SD card storage capacity anyway. And speaking of which you need AT LEAST a class 4 or better SD card to make this run smoothly.
Also feel free to visit the forums at http://forum.init2winitapps.com/
Ok so here it is, Boot Manager Pro. Its been a long time coming for the g2x to dual boot. First off let me say long story short, I currently have a bootable SD Rom, known as ROM1. I have yet to be able to recreate my findings tho. But it works and it doesnt brick at all. However it is a bit laggy on my class 4 SD card. Luckily I've already done my research on this project as there are many threads of such awesome info so I'm just going to be lazy about it and quote the good people of xda versus re-writing it based off of their info.
ChrisDDD said:
So here's a very basic description of how it works... It doesn't partition your SD card, it just creates a folder of its own, and then sub-folders to hold the different roms you install. When you install a rom, it basically creates images of the usual Android partitions - system, data, cache, & boot. These are standard .img files, just like the ones Clockwork creates when you do a backup. After the images are created and wiped (formatted, which you should do initially) it installs your rom into these essentially the same way as Clockwork installs a rom to your phone's actual partitions. I assume it modifies the kernel that comes with each rom to mount the image files on the SD card instead of the phone's partitions.
When you want to boot a rom, it just replaces your current boot image with the modified one and restarts the phone. With the modified boot image, the system, data and cache images on the SD card are mounted to the correct locations and Android starts up none the wiser. The rom will initially run a little slow, because the SD card is slower than the internal memory, but after things get cached it speed up considerably.
When you want to reboot to another rom, or back to the phone's rom, Boot Manager again swaps boot images that mount the desired rom's partitions (in the case of the phone's rom) or files (in the case of an SD card installed rom).
When you first run Boot Manager, it makes a Clockwork flash able backup of your current boot image, which you can flash if a rom hangs or loops on startup. Alternatively, you can also simply boot into recovery and do an advanced restore, choosing just the boot image to restore from a backup. It accomplishes the exact same thing.
It can be a little hit or miss, with some roms just plain refusing to start through Boot Manager, but it does work and when it does, it's pretty amazing given what it's actually doing.
Click to expand...
Click to collapse
So basically upon installing the app you need to setup your phone so that way you can properly install a ROM, follow these steps:
1. Go into the supersu(or superuser app) and then go to settings then disable logging or click none.
2. Then go into the BMP app and press the menu button on your phone, not the app, and go to settings. Once in settings put a check mark in force large boot.img, screen on during install, and then go into variables, leave tegra alone but change the sdcard block to show mmcblk1p1. Then press finish and let the app restart. By the way I didnt change any of the sizes of the .imgs but feel free to do so. But be warned do not decrease the size of the system.img only increase it, if desired.
3.Then after you've done the above you need to setup the phone rom. Click on 'Setup Phone' under phone rom and follow that process to setup your phone rom.
4. Once your phone rom is setup you may begin to install a zip to rom1 or rom2 or whatever slot you want. This is the tricky part. I have done tons of reading and most people say that if your using CWM, which us g2x'ers do, then you will probably have a better chance of getting a bootable rom by restoring from a nandroid backup you did versus installing new.
5. So after you decide which path you will take, nandroid backup or fresh rom install, choose install. If you choose a fresh rom, wipe system, data, and cache right away. If nandroid, then wipe after the install.
6. Now once you have clicked install put your phone down, DONT MESS WITH YOUR PHONE AT ALL! PUT IT DOWN AND WALK AWAY OR SOMETHING! Don’t mess with it, text from it, xda from it, dont even use the screen as a mirror!!!! lol seriously the app is picky and while under the .img creation process you want nothing to mess that up or you will not get it booted. You may however drag down the notifications bar to follow the progress of the install.
7. Once its complete, tap the install complete notification in the notification bar and let the app do its thing to finalize the install and get you back to your rom selection screen. Now if you did a nandroid back up here is where you click 'manage slot' and then factory reset the backup you did. Just do it, dont ask why.
7.1 Also so if you desire to install gapps and/or possibly a different kernel, now would be the time to do so while your here. I have read mixed reviews of doing this process right after the rom installs. However when I set up my rom1, I booted into it first all happily then realized I had no gapps. So I had to reinstall BMP on rom1 then boot back to phone rom and then I installed GB gapps and had no issues booting back into rom1.
8. Once the above steps are done if your feelin lucky go ahead and tap on boot the rom you installed, and if all goes well it will boot up.
9. If it boots up you need to post confirmation here!!! Provided info such as phone rom and the info on the sd rom you used and slot number and such.
Hopefully it will just work for you. I have done all the above steps using HFP 2.1 as my phone rom and only been able to get 1 bootable rom. Being it was for testing I used HFP as my phone rom and as well as my rom1.
So if the above steps dont wortk out for you and your boot lopped or what ever, then turn your phone off and reboot into cwm. You have 2 options to resolve the boot issue you just created. 1, you may go to restore then advanced restore then restore your boot. Or 2. select install a zip and nav to the bootmanager folder then phone rom then flash the update zip there.. then reboot and you should be back at your phone rom.
Here is a basic run down of everything that I have done so far:
When I first started working on this project I wasn’t doing any dev'ing to change any of the stuff in the boot.img. I just changed settings in the app per all the research I did. So when all was said and done I restored HFP 2.1 to ROM1 and it actually booted!! And it works lovely btw.. I can still boot into this rom today. I then decided to pass the word and ways that I created the working rom1, well I nor anyone else I passed the info to was able to get it working. Only one other person was able to confirm that rom1 works but only after I copied all my rom1 info and sent it to him for testing.. and he was able to boot into my created rom1… As I see it, it was a blue moon event that I have yet to repeat. So I thought eff it lets do some dev'in so I unpacked the boot.img from rom1 then compared that to the unpacked boot.img from rom2 that I created in my trial and error experiences. So in doing so I noticed 4 differences; 1, the mount points obviously, 2, in the sbin folder had a ueventd file from the working rom1 was a text file viewable by gedit in ubuntu. In rom2 it was just a non-readable file. 3, in the init.rc file was also missing a chmod command for system, (the command is in rom1 but not rom2) and 4, there was a ueventd.tegra file that was in rom1 that wasn’t in rom2, but everything else is the same. So I decided to plug and play with the differences to see if she boots and no go. I don’t understand why its boot looping because I am using the same rom as phone rom as for rom1 and rom2. So it boot looped. So I had to restore my boot.img many times in cwm.
So then I said eff it lets do some more research, then I noticed in the .zips folder plus the individual rom folder there are .zips that will let you flash via cwm if you get boot loops and 'should' get you booting to your desired sdrom. I then tried that way and no go.. so then I opened up the zip and had a look at the internals.. first there is the moveboot.sh file that the app runs in cwm flash the given boot.img. I then checked out the meta-inf and opened up the updater-script thinking that the app wasn’t actually flashing the boot.img which is why it loops... Well I think im half way right. However the script itself is lil dodgy... first thing I noticed was at the end of the script they have a command to cp the log from /tmp to /sdcard/bootmanager well the command was wrong so it never copied the log. So I fixed that. I also saw that the assert command was pointing to ‘boot’ instead of mmcblk0p5, so I changed that too. Then I decided to do away with the assert command and the moveboot.sh file they have going on to utilize the same functions that the kernel zips use, which is a kernel folder that holds the boot.img and a run_program that dd's the boot.img to 0p5. plus I even updated the update-binary that the file uses. I used the one from the g2x nullifier as I know that one was made for our phone and should have no issues.. plus there was a noticeable difference in the sizes of the provided binary to that replaced binary. So with the updated.zip file I then rebooted into cwm to flash that being that I was using a different command to flash the boot.img as well as the other changed stuff and still it boot looped. So as of now the only thing I don’t think ive done was grab the boot.img from rom1 then change the mount points, only change that, and then use that for rom2 and see if it boots. I don’t think I’ve done that yet. But every dam process I do I get boot loops. So basically I have came to the conclusion that it’s now NOT a boot.img issue being that I have done everything to change the boot.img and to make sure it flashes, which it does indeed and now creates the log too… I think maybe it has issues with the system.img as that’s what comes next in the boot process. But that’s just my hypothesis. I won’t be able to confirm this till I liberate rom1’s boot.img then change the mount points to point to rom2 and then see if it boots.. if it don’t work then that would mean to me that there is an issue with system.img created. But that’s just my hypothesis…
What I don’t understand is why the eff when I didnt hack the app I got a working sd-rom, but when I do change some stuff with it still don’t work!!???!! I guess maybe ill just edit/hack the apk to see what’s up.. This is getting way more complicated than it needs to be, since it worked prior to all my major changes to the script its using for flashing and the boot.img and what not. Anyone have any ideas feel free to add them.
My next steps are to edit rom1 boot.img one last time to change the mount points to point to rom2 and then if that’s a no go then it’s got to be the system.img that’s getting created. By the way this whole process I have only been restoring my nandroid backup for HFP 2.1. I have not attempted to flash new as with thru my research more times than not people would get a bootable rom via restoring versus flashing new.. so if anyone wishes to experience an sd rom let me know, ill send you a link to download my rom1 to get it going. Mind you that its not perfect and you need a class 4 or better sdcard. Everything works but it just takes a bit longer to load things and get things cached as its on the sdcard and not nand. Also if you have any input or are wishing to help pm me I need more heads to get this sorted as I can’t be the only one who knows how to edit scripts and unpack imgs and such. Either way I will continue to do this until I get it right damit!!! Oh and I just ordered a class 10 sdcard to help with this process…
That was copied from the other thread that mustangtim started. Last night when I went home the first thing I did was change the mount points on rom1 to reflect rom2, I changed nada else, then I tried to boot it... it boot looped. So maybe its a permissions issue or the system.img.
So just as a proof of concept and before anyone calls bs on my work/findings Here is the link to my rom1 that boots and is HFP2.1. *Update, 'm just going to
leave it on my DB for now till I find something better I guess. xda wont let me attach the file since its 233MB. Oh well here is the link :
Code:
[URL="http://db.tt/eBZwrOrs"][U][B]Here it is, my Rom1 HFP 2.1[/B][/U][/URL].
I have also attached my updated script file to flash back to rom1, for now.
The boot.img points to rom1 instead of phone rom, ill add to phone rom
as well, just not the now. :) Feel free to flash this via cwm versus
restoring...
Also this is part of the this: the ‘.zips’ folder you need to replace the file in
that folder as well. It’s an update file for rom1 to flash the boot.img.
..
If you’re going to use this you need install a random rom to rom1 then replace those created files in rom1 with these files in the 7z file..
So I am doing this new thread to get the devs or people with know how to help me out with my findings. I have edited the boot.img so much I could pretty much re-write everything in there by now including using magic to create to my own kernel eff!! lol jk but seriously I need people with knowhow to provide confirmation of go or no go. Basically I have people whom have helped out but It seems that I'm the only one who has dug this far into this app(unless i've been misinformed) and I have no one on my level to talk with except the init2winit devs. Which are very helpful btw.
And lastly:
Conap said:
Guys if it's failing to make the boot.img first make sure your using the market version....others have released cracked versions of our app which they broke...if your using the actual market version just send me a pm or email [email protected] and send your log.txt from BootManager folder on sdcard and we'll get it straightened out. Thanks.
Click to expand...
Click to collapse
or post here or PM me, I'm always down to help out.
Also thanks go to the init2win team, Gflam and Conap as they started this app. and as well to Mustangtim as he brought me into the light of BMP.
So you got all that???!!!??? Now lets get this party started and get full support for dual booting. I will not rest until I get this working. Thanks for your time and possible assistance.

Ok so since I have a book above I thought this is a good place for links and such...
So just incase anyone is curious, here is the Official Boot Manager Manual
Here is a nice link for Tips and Tricks while Installing ROM's that so far has good info to help you watch via adb what the BMP is doing in its creation process.
Some FAQs:
When should I set up my phone ROM?
Set up your phone ROM EVERYTIME you install a new ROM to your phone so you can get back to your phone ROM and won't get stuck on your SD ROM.
My SD ROM seems to lag how can I fix this?
SD ROM lagging may be due to a few things which all have easy fixes. First fix is that most of you have class 2 cards which are what usually come with your phones. These have a much lower read/write then cards of a higher class, we recommend a class 6 card or above. Another easy solution is overclocking merely install a better kernel and use CPU Boost (or any other overclock app) to overclock your phone.
Can I nandroid my SD ROM slots?
Yes and no you can't nandroid them in the traditional sense of the word using recovery but this app works as a recovery for your SD ROM slots and you can back up your ROM slots within the app in the Manage Installed ROMs section which works as a nandroid for your slots by fully backing up your slots to your sdcard which can later be restored.
What if I want to change the sizes of my images, how may I determine the individual sizes easily?
Easiest way is to open up terminal emulator in your app drawer. Type 'su', then grant permissions if need be, then type 'df -h' and it will display such information. You may also use adb in the same fashion. Connect via usb, open up command prompt/terminal and get adb connected and then type 'df - h' again and the same info will show. I will say this again just because, do not decrease the size of your system.img ever! Unless you want mad issues!
Here is the changlog link and just for heck of it the info based on that link:
Code:
V3.2.6
Fixed DroidX/Droid2 Install issue
Fixed UI theme issues
Fixed issue with spaces in name of pic when selecting photo for screen shot
V3.2.5
Fix to allow continue of install if no boot.img is found.
V3.2.4
Added support for HTC Rezound
Added support for rom's with multiple boot.img's
Added support for rom's made for multiple phones
AutoDetect sdcard for usb mounting
Fix for installing ICS gapps
Optimized SDRom Install process
Added support for Motorola RAZR
Added install queue
V3.2.3
Fixed issues with rom's not showing when on emmc on Droid Incredible
Fixed issues with not showing correct booted rom in app
More improvements to sms sync(all rom's will need updated app for changes to apply)
Fix issues with loader
Fixed issue with switching to backup server when main server goes down
Fixed 1x1 widget to show unlimited rom slots
Added 2x2 widget that works with unlimited rom slots
V3.2.2
Fixed force close for img's over 1Gb when resizing
Fixed current booted rom displaying correctly on gnex
Fixed issue with wrong busybox downloading on gnex which should fix alot of install/boot issues
V3.2.1
Fix for errors causing installs to fail.
Fix for some of the licensing stuff.
Removed sdbooster prefs from Galaxy Nexus(Since they don't have sdcard).
V3.2
Changed 4 sd slots to infinite slots!
Galaxy Nexus Support
Sms and Call Log synced between ROMs (you choose what ones too also requries updating boot manager in all slots)
License Check extended to a week
ROMs do not need market installed for boot manager to run (requires updating boot manager in all slots)
Hide su toasts (superuser elite only)
Fix for force close when setting screen shot in MIUI rom's
Thunderbolt defaulted to force large boot.img
Fixed unsupported device using a key
Manually setting variables only accepts numbers
V3.1.1
Fix for various force closes in rom installs and Nand restores
V3.1
Added su binary check
User selectable colors for everything
Better navigation (press title for quick action)
Added compatability for new twrp backups
Better compatiblitlity with memory tweak scripts(i.e. supercharger script and liquids default scripts)
Fix for install process being killed by android
Fix for some themes erasing img's
Fix more force closes during install
Force smaller boot.img option in settings(Fix for some phone's who's boot.img won't fit on the phone after BootManager edit's it)
Improved gapps checker
Improved security
Boot Manager now accepts keys pay for by paypal (see http://init2winitapps.com/stories/BootManager.html)
Added Evo 3d GSM Support
Added notifcation sound/vibrate for finished install (turn on in settings)
Improved data check
V3.0.3
Fix some force closes
V3.0.2
Added backup server (Sorry our server dropped out)
Fixed some force closes
2nd init fixes for Liquid's ROMs
V3.0.1
Last minute UI fixes
V3.0
UI Completely redone
Includes screen shot of each slot
Custom Info
Custom Dialogs
Custom Animations
Custom everything!
Bug Fixes
Added Droid 2 Global support
Screen shot with long press of search
V2.2.1
Bug fixes in file browsers
File browsers only show relevent files
Kernel installer fix
Droid 2 bug fix
V2.2
New security (more advanced and requires data only once a day)
Installs no longer require data
Added Italian translation thanks Black-Ice
Droid X support
Droid 2 support
Fixed status bar notifications
Fixed phone rom rebooter if gapps aren't installed
Bug fixes
V2.1
Restore android_secure to sd from nandroids
Added TWRP nandroid support
Added CWM tar nandroid support
Added Spanish translation
Made widgets easier to use
SD Booster added (Change SD read cache for better preformance)
Added current settings to manually set variables.
Added option to keep screen on during install in settings
Fixed usb layout
Updated Security
Bug Fixes
V2.0
Install now runs from the foreground (status bar)
Restore Nandroids to slots also in the foreground
User can cancel installs as they run
4 new themes added including one by apophis9283
Some phones such as tb moved to new install code (Fix for some sense rom's)
V1.3
Added third theme to app (Red Theme)
Added 4x1 widget and new widget styling
Fixed in app messenger
Added support for Htc Evo 3D
Added support for Htc Sensation
Added Support for Htc Incredible 2
Added Support for Htc Incredible S
Added Support for Htc Desire S
Added support for LG Ally
V1.2
Added option to reboot to phone rom to install gapps in license check dialog
Better error checking and error logging
Automatically install's ext2 libs if not present
Moved Set Names to Manage rom's
Fix for add-on's not installing correctly
Better compatiblility for rom's that use data2ext or apps2sd(user must set larger img's in manual variables)
Trash cleaner added to extras
Better Fix for WiFi issues on Droid 1
Added display to show what rom you are booted into
Fix for updater-script not found errors
Added support for Htc NexusOne
Added support for Htc MyTouch4G
More compatiblity for ext4 support
V1.1
Fix WiFi issues on Droid 1
Fix bug in rom installer for setting permissions correctly
Fix bug for cache size not setting correctly in setting variables manually
Fix for decimals entered into partition sizes causing force close
Fix force close in widget
Fix force closes in installer
Added Wipe data/Factory reset to Manage Rom's section
Added code to show what file's are being unzipped in dialog
Added support for rom's that extract files to sdcard so the files actually end up on your sdcard
Added support for Htc Desire (apps2sd and data2sd rom's support is experimental. Please email if you test it and it works/doesn't work)
Added support for Htc Inspire4g
Added support for Htc DesireHD
Added option to use ext4 filesystem if rom's support it-Experimental Won't work with all rom's.
Added log.txt file to sdcard to log errors during install
V1.0
Initial Release

YEZZZ

glad to finally see this here!

jookdakang23 said:
glad to finally see this here!
Click to expand...
Click to collapse
indeed... hopefully it wont be before too long that I get this app fully supported for us!

This app will be extremely useful for G2X owners and makes the G2X more versatile and desirable.

da-pharoah said:
indeed... hopefully it wont be before too long that I get this app fully supported for us!
Click to expand...
Click to collapse
idk how you get it booted. lol i keep getting bootloops

jookdakang23 said:
idk how you get it booted. lol i keep getting bootloops
Click to expand...
Click to collapse
Are you using the files I supplied or the ones that BMP created for you?

Woo hoo good job bud
Sent from my LG-P999 using xda premium

x0xhellx0x said:
Woo hoo good job bud
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
LOL thanks bro.... Go Team Hellfire!!!!

da-pharoah said:
Are you using the files I supplied or the ones that BMP created for you?
Click to expand...
Click to collapse
i remember requesting the files but think you ever sent them

jookdakang23 said:
i remember requesting the files but think you ever sent them
Click to expand...
Click to collapse
no we had a miscommunication due to our avail times and GB's lacking ability to utilize two accounts on gtalk.... I have posted those files in the op however...

First, I want to thank everyone who has helped with us on this app. Second, I know I picked the right man for the job, did you see that OP! All kidding aside, a lot of you know I write for ACS under screen name artifintel. I just had too much on my plate to give this project the attention and direction it needs. The right guy is in charge, he's a stand up person and very knowledgeable with this app. Good luck everyone!
[email protected]

I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4

Rafase282 said:
I tried installing CM9, it didnt work, stuck on first boot screen after the LG logo.
I'm using rooted stock 2.3.4
Click to expand...
Click to collapse
what rom are using as phone rom? and you installed to rom1?

da-pharoah said:
what rom are using as phone rom? and you installed to rom1?
Click to expand...
Click to collapse
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel

Rafase282 said:
As phone rom i;m using rooted stock 2.3.4 v21y
The to rom1 I installed CM9 kang from oiwan with gapps and harsh kernel
Click to expand...
Click to collapse
and no bootloop you say?? well then it may be the stock rom your using... The app is very picky and if you get a bootloop, I feel that those can get booted with tweaks... but stuck on lg screen is just no bueno.. Try a different rom... maybe one that has its partitions at ext3 format just to try it.. I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..

hands down, a badass app...

SiL3nTKiLL said:
hands down, a badass app...
Click to expand...
Click to collapse
lol +1 for sure!

da-pharoah said:
I think owains rom uses ext4, but I could be wrong. I havent fully researched his rom yet..
Click to expand...
Click to collapse
positive on ext4

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.

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!