[Q] Trying to make bootable CM7 card....what did I do wrong? - Nook Color Q&A, Help & Troubleshooting

I'm trying to create a bootable SD card with CM7. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1000957.
I've put the CM7 file on the card, but when I put in in my nook and boot it just goes to the nook software. Can anyone help me with what I did wrong? When I look at the SD card, I see these files:
cm_encore_full-253.zip
u-boot.bin
uRamdisk
uImage
MLO​And it looks like the nook put some stuff on it when it booted, folders called:
My Files
B&N Downloads
LOST .DIR
.android_secure​
Any help would be vastly appreciated!

Girevik said:
I'm trying to create a bootable SD card with CM7. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1000957.
I've put the CM7 file on the card, but when I put in in my nook and boot it just goes to the nook software. Can anyone help me with what I did wrong? When I look at the SD card, I see these files:
cm_encore_full-253.zip
u-boot.bin
uRamdisk
uImage
MLO​And it looks like the nook put some stuff on it when it booted, folders called:
My Files
B&N Downloads
LOST .DIR
.android_secure​
Any help would be vastly appreciated!
Click to expand...
Click to collapse
If you are still booting into the stock ROM I would say you have a bad image and to do it again.....

As I think back through the process, the only thing I was a bit confused on was the generic image. After downloading it, I expanded it out using winrar before writting it to the SD card with winimage. Was that the right thing to do?

Girevik said:
As I think back through the process, the only thing I was a bit confused on was the generic image. After downloading it, I expanded it out using winrar before writting it to the SD card with winimage. Was that the right thing to do?
Click to expand...
Click to collapse
Try again with Win32DiskImager

votinh said:
Try again with Win32DiskImager
Click to expand...
Click to collapse
Do I need to expand the image out first with winrar, or will the Win32DiskImager handle that?

Girevik said:
I'm trying to create a bootable SD card with CM7. I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1000957.
I've put the CM7 file on the card, but when I put in in my nook and boot it just goes to the nook software. Can anyone help me with what I did wrong? When I look at the SD card, I see these files:
cm_encore_full-253.zip
u-boot.bin
uRamdisk
uImage
MLO​And it looks like the nook put some stuff on it when it booted, folders called:
My Files
B&N Downloads
LOST .DIR
.android_secure​
Any help would be vastly appreciated!
Click to expand...
Click to collapse
You have to preface the ROM zip files with "update-", so change the name of the zip file to update-cm_encore_full-253.zip. Additionally, you're missing some files that would allow the ROM to be written to the sd, specifically uRecRam and uRecImg. You should probably go back and review the instructions and start from the beginning.

Girevik said:
As I think back through the process, the only thing I was a bit confused on was the generic image. After downloading it, I expanded it out using winrar before writting it to the SD card with winimage. Was that the right thing to do?
Click to expand...
Click to collapse
You should have wound up with an .img file that you write to SD with WinImage. From that linked page:
[...] Grab the installer image here:
http://crimea.edu/~green/nook/generi...rd-v1.3.img.gz
it's a ~9M image that would unpack into ~130M disk image.
Click to expand...
Click to collapse
Did you wind up with a ~130M .img file?
From what you've written, sounds like the write wasn't good and it doesn't even start to boot.
Also, when it does boot, watch the process as CM is extracted when you boot that disk. Per the top part of that guide, some cards work better than others.

shumash said:
You have to preface the ROM zip files with "update-", so change the name of the zip file to update-cm_encore_full-253.zip. Additionally, you're missing some files that would allow the ROM to be written to the sd, specifically uRecRam and uRecImg. You should probably go back and review the instructions and start from the beginning.
Click to expand...
Click to collapse
Will try that, but would it skip the boot from the SD card all together because of that?

bobstro said:
You should have wound up with an .img file that you write to SD with WinImage. From that linked pageid you wind up with a ~130M .img file?
From what you've written, sounds like the write wasn't good and it doesn't even start to boot.
Also, when it does boot, watch the process as CM is extracted when you boot that disk. Per the top part of that guide, some cards work better than others.
Click to expand...
Click to collapse
Looks like my image, after I expanded it with WirRar, is more like 117MB (123,379,200 bytes). Do I need to bring down the image and expand it again?

Creating a bootable CM7 uSD using winimage and verygreen installer:
1.Download winimage, verygreen boot image, CM7 zip or Mirage zip, gapps zip...
2.Unpack the verygreen .gz to get the .img file inside
3.Put your SD card in your card reader
4.Open winimage....
5.Disk->Use disk (whatever your sd card is)
6.Disk->Restore virtual hard disk image on physical drive (select the verygreen .img file-change .vhd to .* if you don't see it)
7.Click ok on the warning and you should have a boot disk
8.Right click the CM7 zip and "send to" your new boot disk
9.Pop out the SD card, put it in the Nook
10.Boot the Nook, let it install and turn off
11.Put the SD card back in your PC, transfer the gapps zip to it, put back in Nook
12.Turn on the nook, let it boot to CM7
13.Connect to wifi (saves a little hassle later when google wants you to log in)
14.Press the power button, restart, to recovery
15.Let gapps install then turn off
16.Restart the nook
17.Touch the android
18.Log in to your google account
19.Install whatever google apps you want (don't worry if you don't get them all now, the market will still have them later)
20.Enjoy
I recommend using DizzyDen's patch after step 1 if you want better market support. I make the IMEI from my Nook's serial # and use these build.prop edits.

Girevik said:
Do I need to expand the image out first with winrar, or will the Win32DiskImager handle that?
Click to expand...
Click to collapse
The more answer you get, the more confusion.
Anyway, follow this carefully.
Assuming you running Windows on PC.
1. Download (or redownload) the file from your link. It is .gz file, it is a zip file, so you need to unzip it. After unzip, you will get the .img file, and that's the one you need to write off your uSD card.
2. Execute Win32DiskImager (assuming you already downloaded), prefer an old version, r0.15 or something like that.
3. Create a bootable uSD. After this step, your PC should see the uSD as "boot" and inside, it should have only 4 files as you listed above.
4. Copy the ROM into the boot directory (like you listed above) and properly eject the uSD off the PC.
5. Insert the uSD into the NC and power it up. You don't have to do anything else, it will FULLY AUTOMATICALLY detects the zip file (the ROM file), install, then delete and then shut down. Note: you don't touch anything.
6. Now, you have to power it up.
7. Repeat step 4 to get the GApp installed by trying to boot into recovery (this step needs your skill, read the how-to from the link you posted)

gallahad2000 said:
Creating a bootable CM7 uSD using winimage:
Click to expand...
Click to collapse
1.Download winimage, verygreen boot image, CM7 zip, gapps zip...
2.Unpack the verygreen image to a .img file
3.Put your SD card in your card reader
4.Open winimage....
5.Disk->Use disk (whatever your sd card is)
6.Disk->Restore virtual hard disk image on physical drive (select the verygreen .img file-change .vhd to .* if you don't see it)
7.Click ok on the warning and you should have a boot disk
8.Right click the CM7 zip RENAME IT WITH THE PREFIX "update-" and "send to" your new boot disk
9.Pop out the SD card, put it in the Nook
10.Boot the Nook, let it install and turn off
11.Put the SD card back in your PC, transfer the gapps zip to it, put back in Nook
12.Turn on the nook, let it boot to CM7
13.Connect to wifi (saves a little hassle later when google wants you to log in)
14.Press the power button, restart, to recovery
15.Let gapps install then turn off
16.Restart the nook
17.Touch the android
18.Log in to your google account
19.Install whatever google apps you want (don't worry if you don't get them all now, the market will still have them later)
20.Enjoy
I recommend using DizzyDen's patch after step 1 if you want better market support. I make the IMEI from my Nook's serial # and use these build.prop edits.[/QUOTE]

shumash said:
6.Disk->Restore virtual hard disk image on physical drive (select the verygreen .img file-change .vhd to .* if you don't see it)
Click to expand...
Click to collapse
It appears this was my problem. I was using "write disk" rather than the restore option. I now appear to have CM7 on the card (althought it's been on the bootup screen for a while, and I now need to get the gapps installed.

Girevik said:
It appears this was my problem. I was using "write disk" rather than the restore option. I now appear to have CM7 on the card (althought it's been on the bootup screen for a while, and I now need to get the gapps installed.
Click to expand...
Click to collapse
I made the same mistake, it's not really explained in any of the guides.
shumash said:
8.Right click the CM7 zip RENAME IT WITH THE PREFIX "update-" and "send to" your new boot disk
Click to expand...
Click to collapse
That's an unnecessary step. The verygreen installer will flash it even without the prefix.

shumash said:
You have to preface the ROM zip files with "update-", so change the name of the zip file to update-cm_encore_full-253.zip. Additionally, you're missing some files that would allow the ROM to be written to the sd, specifically uRecRam and uRecImg. You should probably go back and review the instructions and start from the beginning.
Click to expand...
Click to collapse
No, you don't... the recovery script is setup to find "update-*" "cm_encore_full*" and gapps-gb*" files. So, as long as your file begins with everything up to the * it will work.
uRec* won't be present until the script actually runs once. The script creates the uRecRam and uRecImg files to use on further boots into recovery mode.

DizzyDen said:
No, you don't... the recovery script is setup to find "update-*" "cm_encore_full*" and gapps-gb*" files. So, as long as your file begins with everything up to the * it will work.
uRec* won't be present until the script actually runs once. The script creates the uRecRam and uRecImg files to use on further boots into recovery mode.
Click to expand...
Click to collapse
Thanks for the clarification, I just knew he was wrong.

DizzyDen said:
No, you don't... the recovery script is setup to find "update-*" "cm_encore_full*" and gapps-gb*" files. So, as long as your file begins with everything up to the * it will work.
uRec* won't be present until the script actually runs once. The script creates the uRecRam and uRecImg files to use on further boots into recovery mode.
Click to expand...
Click to collapse
Thanks for clarifying my misconceptions. At one time, a standard "cm_encore_full*" file didn't take and did when I added the "update-" to it.
That's why we come here, to learn at the feet of the masters.

Related

CM7 sd card install troubles

Following verygreen's directions, I got his installer image onto the sd card (but had to rename it to end in ".img". I removed the card and put it back in the PC, and when I try to put the CM7 file on it, it says card needs to be formatted to use it. I think if I format, it will remove the installer image. Should I have formatted it first? I'm sorry if this sounds really basic (and stupid), but, please help.
So I formatted the card, and put verygreen's image installer back on, removed the card and inserted it again and again get formatting message. It's a sandisk 8gb, new.
According to the directions, I need the image installer on the card and then the CM7 file? I've read and re-read directions and searched links for information on what to do next ???
I think you messed up on the very first step. The file ending .gz is a zip file. I used WinRar to unzip it. There is a .img file inside that you flash to your card.
SonicClang said:
I think you messed up on the very first step. The file ending .gz is a zip file. I used WinRar to unzip it. There is a .img file inside that you flash to your card.
Click to expand...
Click to collapse
Thank you, and you're absolutely right, I messed up from the git go. I did finally learn I needed to unzip it, and things went well from there. Quite amazing! Now I need to do a search for the Netflix fast forward (chipmunks) fix.
There's plenty out there on the Netflix thing

[Q] Root Nook Color 1.2 with OS X Lion?

I just bought a new Nook Color that's got the latest 1.2.0 Firmware. I've already registered it and I'd like to install the latest version of CM7 on it.
I've got a newer iMac with OS X Lion installed. What's the best way for me to Root this and install CM7? What's the latest version of CM7?
I've got a 4 GB MicroSD card and reader for my Mac. I think that I've got all the correct tools, just not sure what would be the easiest method to do this. Thanks for any advice!
It really depends on what you want to do. Do you want to install on emmc? SD? Do you want to run the 7.1RC or the nightly releases?
I recommend reading through the two guides linked below and seeing exactly what you want to do with the device.
As far as using OSX, I believe you can use the *nix commands the same to set up the cards however you need.
http://forum.xda-developers.com/showthread.php?t=1030227 - Emmc
http://forum.xda-developers.com/showthread.php?t=1000957 - SD
Thank you for the links. I was able to get CM7 installed using the second link. I'm going to play around with it now and see how well things work. Thanks!
If you're interested in going eMMC, it's pretty simple from OSX. I got it done in about 15 minutes, and most of that was waiting for the clockwork image to burn. What I did:
Download clockworkmod, repartition zip, reformat zip, cm7 zip, gapps, and oc kernel zip (though if you use the latest nightly you don't need to install the kernel seperately)
Extract the CWR .img file, insert blank sd card into Mac
Open terminal and run the command "diskutil list". Figure out which disk is the SD card. Your HD will probably be /dev/disk0 and your sdcard /dev/disk2, but double check to make sure. You don't want to reformat your HD by accident.
Now run the following commands- assuming your SD card is /dev/disk2, otherwise substitute the appropriate location:
diskutil unmount /dev/disk2
dd if=<drag CWR image here to auto fill in the location> of=/dev/disk2
Now wait. There's no progress bar but the SD card is being burned. Allow about 10 minutes, it's done when the next command prompt line shows up. When it's done, pop the card out then reinsert to mount it. Drag all your zip's onto the card, then eject and put it in your Nook.
Reboot the Nook and it'll boot into clockwork. If you're repartitioning, do those zips now then wipe data and reboot, because you'll probably need to re-register the Nook. Then go back to clockwork and wipe cache, dalvik, data, and flash CM7, gapps & kernel. Don't reboot yet!
Take the SD card out and put it back into your Mac. Open Disk Utility and reformat the card to MS-DOS (FAT32). Then take the card out and put it back into the Nook. Now you can reboot.
That's it! Super easy. At this point I would recommend opening ROM Manager and using it to flash clockwork to the internal memory, makes it easier to upgrade in the future.

SD card install says: "Looking for install images"

Ok I wrote the generic image file to sd card through winimage or whatever its called. Then I went here: http://download.cyanogenmod.com/?device=encore. I downloaded the first one dated 7/8/12 and put it on the sd card also. I installed sd card in nook and turned on. It went through a bunch of installing but the last few sentences say:
"Looking for the install images...
Initial install files not found.
Please download it from nook.linuxhacker.ru
and put on first partition of this SD Card
the name should start with updatei-cm and end with .zip"
What does this mean and what am I doing wrong? Right now looking at the SD card file on my computer i see files: MLO, u-boot, uImage, URamdsk, and a zip folder that says: cm-7-20120701-NIGHTLY-encore. I did not unzip the file, all I did was download it right to the computer and dragged to SD card and I even tried downloading straight to to SD Card and no luck.
You can download CM7 RC 3 from the same source and try to add itfirst. If it loads,then rename your other zip with an update_ prefix, put it on your boot partition, boot into recovery and you should be where you want to be. (You'll prolly need to install GAPPS zip after first load of RC3 to get google apps, too).
Follow advice on lepanlar's tip site and you won't go wrong.
TheKid1 said:
Ok I wrote the generic image file to sd card through winimage or whatever its called. Then I went here: http://download.cyanogenmod.com/?device=encore. I downloaded the first one dated 7/8/12 and put it on the sd card also. I installed sd card in nook and turned on. It went through a bunch of installing but the last few sentences say:
"Looking for the install images...
Initial install files not found.
Please download it from nook.linuxhacker.ru
and put on first partition of this SD Card
the name should start with updatei-cm and end with .zip"
What does this mean and what am I doing wrong? Right now looking at the SD card file on my computer i see files: MLO, u-boot, uImage, URamdsk, and a zip folder that says: cm-7-20120701-NIGHTLY-encore. I did not unzip the file, all I did was download it right to the computer and dragged to SD card and I even tried downloading straight to to SD Card and no luck.
Click to expand...
Click to collapse
Just make sure the file name starts with update- instead of cm- and all will be well.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
leapinlar said:
Just make sure the file name starts with update- instead of cm- and all will be well.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
Thank you so much, that worked. Yay!!!
leapinlar said:
Just make sure the file name starts with update- instead of cm- and all will be well.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
I couldn't believe this was such an easy solution to such a frustrating problem. All I had to do was change a file name from "cm" to "updat". Thank you!
Hi, i am an absolute noob! I tried updating to CM10 from CM7 on my Nook Color. I got the same error message and did also try update instead of cm. But I keep getting the same message. Additionally the message also says "Please put on first partition of this SD card." I tried this with an 8 GB class 4 Strontium card. After I first burnt the image onto the SD card, after that the SD card reads as "boot" with 297 mb of 297 mb remaining. By the time I burn the image again and then load the update/cm.zip and gapps-jb.zip there is only 50.1 mb remaining. What could be the problem?
Also, I note that after an unsuccessful attempt only the image remains when I view the SD card on the computer. I have to then again copy the update/cm.zip and gapps.zip file. Any assistance would be much appreciated! Cheers,,
leapinlar said:
Just make sure the file name starts with update- instead of cm- and all will be well.
Sent from my Nook Color running ParanoidAndroid and Tapatalk
Click to expand...
Click to collapse
akn2102 said:
Hi, i am an absolute noob! I tried updating to CM10 from CM7 on my Nook Color. I got the same error message and did also try update instead of cm. But I keep getting the same message. Additionally the message also says "Please put on first partition of this SD card." I tried this with an 8 GB class 4 Strontium card. After I first burnt the image onto the SD card, after that the SD card reads as "boot" with 297 mb of 297 mb remaining. By the time I burn the image again and then load the update/cm.zip and gapps-jb.zip there is only 50.1 mb remaining. What could be the problem?
Also, I note that after an unsuccessful attempt only the image remains when I view the SD card on the computer. I have to then again copy the update/cm.zip and gapps.zip file. Any assistance would be much appreciated! Cheers,,
Click to expand...
Click to collapse
It needs to be update-, with the dash.
Also, if going to CM10 from CM7, you need to reburn your SD with the new image from my updated instruction thread linked in my signature. The old image will not work properly with CM10.
Sent from my Galaxy Tab running Tapatalk
Thanks for the quick response. I did use update- . Also, the thread you mentioned was the one I used to attempt the upgrade. Somehow it isn't working. This is the full message
"it appears that the sd card is already properly formatted initial install files not found"
leapinlar said:
It needs to be update-, with the dash.
Also, if going to CM10 from CM7, you need to reburn your SD with the new image from my updated instruction thread linked in my signature. The old image will not work properly with CM10.
Sent from my Galaxy Tab running Tapatalk
Click to expand...
Click to collapse
akn2102 said:
Thanks for the quick response. I did use update- . Also, the thread you mentioned was the one I used to attempt the upgrade. Somehow it isn't working. This is the full message
"it appears that the sd card is already properly formatted initial install files not found"
Click to expand...
Click to collapse
And when you put the SD in the PC, you can see the cm- zip? It needs to be named just right, beginning with cm- or update- and ending in .zip
You have gotten past the hard part, getting it to boot in the first place. You just are not getting the files right. If it is on the card and named right it would try to install. And since you put both the cm zip and the gapps zip there, one or both should try to install. They must not be on the card right.
Sent from my Nook HD+ Running CM10 on SD
The strange thing is that after I put back the SD after an unsuccessful install, I can no longer seem the cm-.zip and gapps-,zip files. I can see that they are successfully copied onto the SD card after first burning the image and taking out the SD card and then copying those two files like you mention in your post.
After I first burned the image onto the SD card and then deleted it after the first unsuccessful attempt, the SD card shows up as a boot drive and only shows 297 MB space available and after the image and the two files are copied as above then only 50.1 MB space is left available.
Can't figure out where it's going wrong.
leapinlar said:
And when you put the SD in the PC, you can see the cm- zip? It needs to be named just right, beginning with cm- or update- and ending in .zip
You have gotten past the hard part, getting it to boot in the first place. You just are not getting the files right. If it is on the card and named right it would try to install. And since you put both the cm zip and the gapps zip there, one or both should try to install. They must not be on the card right.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
---------- Post added at 08:22 AM ---------- Previous post was at 08:01 AM ----------
"lost page write due to i/o error on mmcblkp1" this also shows up before the program does the "inflating" and finally boots
also during this process, an error something along "unzip: write no space left on drive" also appears
akn2102 said:
The strange thing is that after I put back the SD after an unsuccessful install, I can no longer seem the cm-.zip and gapps-,zip files. I can see that they are successfully copied onto the SD card after first burning the image and taking out the SD card and then copying those two files like you mention in your post.
After I first burned the image onto the SD card and then deleted it after the first unsuccessful attempt, the SD card shows up as a boot drive and only shows 297 MB space available and after the image and the two files are copied as above then only 50.1 MB space is left available.
Can't figure out where it's going wrong.
Click to expand...
Click to collapse
akn2102 said:
The strange thing is that after I put back the SD after an unsuccessful install, I can no longer seem the cm-.zip and gapps-,zip files. I can see that they are successfully copied onto the SD card after first burning the image and taking out the SD card and then copying those two files like you mention in your post.
After I first burned the image onto the SD card and then deleted it after the first unsuccessful attempt, the SD card shows up as a boot drive and only shows 297 MB space available and after the image and the two files are copied as above then only 50.1 MB space is left available.
Can't figure out where it's going wrong.
---------- Post added at 08:22 AM ---------- Previous post was at 08:01 AM ----------
"lost page write due to i/o error on mmcblkp1" this also shows up before the program does the "inflating" and finally boots
also during this process, an error something along "unzip: write no space left on drive" also appears
Click to expand...
Click to collapse
Alright, I know what is wrong. It is that strontium card. You need to use a SanDisk class 4 card. You are getting read/write errors on that card. I had that happen to me when I used a cheap card. Find a quality SanDisk.
And those file sizes are correct. That is what it is supposed to say.
Sent from my Nook HD+ using XDA Premium
Thanks. Will try that and update.
leapinlar said:
Alright, I know what is wrong. It is that strontium card. You need to use a SanDisk class 4 card. You are getting read/write errors on that card. I had that happen to me when I used a cheap card. Find a quality SanDisk.
And those file sizes are correct. That is what it is supposed to say.
Sent from my Nook HD+ using XDA Premium
Click to expand...
Click to collapse
Similar problems here. I'll explain step by step what I did and maybe someone can tell me where I went wrong.
I'm using a MacBook Air running 10.8.3 (not that it makes a difference, but I am using Terminal and DiskUtility for some of these operations).
I'm trying to install Cyanogenmod on a Nook Color 1.4.3 following the directions given here.
1. Downloaded generic-sdcard-v1.3.img and cm-10.1-20130521-NIGHTLY-encore.zip
2. Installed the .img on a SanDisk 4GB microSD card. Ejected it, remounted it, it mounts as a single partition named "boot" that's 121 MB in size with 112 MB available. The files on "boot" are MLO, u-boot.bin, uImage, uRamdisk.
3. Tried to copy cm-10.1-20130521-NIGHTLY-encore.zip to "boot" but there is not enough space.
In a previous attempt, I forgot to copy the cm-10 file to "boot" and was able to get the linux sdcard image to temporarily mount on my Nook, but then received the error mentioned earlier by someone else:
Initial install files not found.
Please download it from nook.linuxhacker.ru
and put on first partition of this SD Card
the name should start with updatei-cm and end with .zip
Click to expand...
Click to collapse
Then, when I ejected "boot" and mounted it on the Airbook, I saw two partitions: "boot" and "CM7 SDCARD." The latter partition had plenty of room for the cm-10.1-20130521-NIGHTLY-encore.zip file, so I put it on there. But it didn't matter if I leave the filename as "cm-" or change it to either "updatei-cm-" or "update-cm" or whatever; the same error occurs.
What am I doing wrong? I assume there is a way to force the sdcard image to create a "boot" with plenty of room for the cm-10 zip file. But how? And do I rename the cm-10 to updatei-cm-10 or what?
Thanks in advance.
jjjmills said:
Similar problems here. I'll explain step by step what I did and maybe someone can tell me where I went wrong.
I'm using a MacBook Air running 10.8.3 (not that it makes a difference, but I am using Terminal and DiskUtility for some of these operations).
I'm trying to install Cyanogenmod on a Nook Color 1.4.3 following the directions given here.
1. Downloaded generic-sdcard-v1.3.img and cm-10.1-20130521-NIGHTLY-encore.zip
2. Installed the .img on a SanDisk 4GB microSD card. Ejected it, remounted it, it mounts as a single partition named "boot" that's 121 MB in size with 112 MB available. The files on "boot" are MLO, u-boot.bin, uImage, uRamdisk.
3. Tried to copy cm-10.1-20130521-NIGHTLY-encore.zip to "boot" but there is not enough space.
In a previous attempt, I forgot to copy the cm-10 file to "boot" and was able to get the linux sdcard image to temporarily mount on my Nook, but then received the error mentioned earlier by someone else:
Then, when I ejected "boot" and mounted it on the Airbook, I saw two partitions: "boot" and "CM7 SDCARD." The latter partition had plenty of room for the cm-10.1-20130521-NIGHTLY-encore.zip file, so I put it on there. But it didn't matter if I leave the filename as "cm-" or change it to either "updatei-cm-" or "update-cm" or whatever; the same error occurs.
What am I doing wrong? I assume there is a way to force the sdcard image to create a "boot" with plenty of room for the cm-10 zip file. But how? And do I rename the cm-10 to updatei-cm-10 or what?
Thanks in advance.
Click to expand...
Click to collapse
The problem is you are using an old image zip that was made for CM7. You need to get my image updated for CM10 from my NC updated SD install instruction thread linked in my signature. Follow the directions there.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
The problem is you are using an old image zip that was made for CM7. You need to get my image updated for CM10 from my NC updated SD install instruction thread linked in my signature. Follow the directions there.
Click to expand...
Click to collapse
Thank you, this was very helpful. I'm not sure how I overlooked the CM7/CM10 issue -- another pair of eyes is always useful.

[GUIDE/TOOLS - NOW OBSOLETE] HDplus CM10/10.1 Easy Install Guide for Legacy SD

UPDATE 05/28/13 - Now that verygreen has changed his SD scheme to his new version, this guide should not be used on his ROMs dated 5/27 or newer. Use his new image and follow his new instructions. If you want to see the old instructions click on the Show Content button below.
Click to expand...
Click to collapse
Many users have had difficulty installing the HD+ CM10/10.1 ROMs using the Original/Legacy (verygreen) SD setup (especially Windows users). I have written this guide and have made some tools that should make it easier. No need for ADB or Linux. I have upgraded the CWM (clockworkmod) recovery to version 6.0.2.8 which includes larger fonts, a brighter screen and the ability to use the internal storage for installing zips and performing backups. It also uses verygreen's process from his early4 zip that aligns partitions at 2M. This guide and tools are for the Original/Legacy SD setup by verygreen, not the Hybrid. If you want the Hybrid, go here.
Setting up the SD
Begin by downloading the files you need either with stock or your PC. You will need my updated SD image file, attached below (do not use the early4 image from the verygreen thread), the CM ROM zip you want to install and the gapps zip to match it. Put the last two zips on your internal media sdcard built into the HD+. You can get the HD+ CM10 ROMs here and the HD+ CM10.1 ROMs here. You can get the gapps zips here, 20121011 for CM10 and 20130301 for CM10.1.
Extract the SD image zip and you will have a 117MB .img file. Burn that to your SD with Win32DiskImager in Windows or the dd command in Linux or OSX. The SD needs to be at least 4GB and preferably a SanDisk Class 4.
To use Win32DiskImager, find it on the web (here, it's free) and install it on your Windows PC. Open it (be sure to run it as administrator) and select the drive (device) that has your card reader with your SD inserted. Then in the image file box put the location where you have the extracted img file. Then when everything is set right, click on the write button. A warning will pop up asking if you want to proceed. When you have verified that you are going to write to the correct device, click on Yes. (One user overwrote their external USB hard drive by not verifying first.) If you get an error message about access denied, it means you are looking at the drive with Windows Explorer. Close Windows Explorer and try again. In fact, it is a good idea to close all unnecessary windows when burning, even your browser.
When burning is complete, insert the SD into the Nook and boot. It should boot to the cyanoboot logo and sit there for a little while while it creates the other partitions on the SD and formats CM10SDCARD. Then it will end up in CWM for HD+ Original SD. If it does not leave the cyanoboot logo within a reasonable time (it hangs sometimes), just touch the power key and CWM should come up. To use CWM, press the volume up/down keys to move the cursor and the n key to select an item. The power key is the back button.
Installing ROMs
You can use the "install zip from SD/choose zip from internal memory" option to flash the CM ROM you downloaded earlier to your internal memory sdcard. Then you can flash the right version of gapps to match your ROM.
When you reboot (you need to leave the SD in the slot), the CM ROM should start. You will need to register with Google to set up Play Store.
If you later want to upgrade your ROM to another build, download it to your CM10SDCARD partition using CM. Then boot to CWM and flash it.
Backing Up
This version of CWM lets you back up and restore your setup. You can even back up to internal memory. It does not back up /boot, but does back up /system, /data and /cache.
Swapping EMMC and SDCARD
Some users have installed CM to a small SD card and want their apps to use the large internal media storage to store their data. I have developed a couple of zips to swap EMMC and SDCARD when booted to CM so that internal memory is available to your apps to store their files. One zip will add the swap and one will remove it. Get them attached below.
These zips can be flashed with CWM but will only install to the Original SD with CM. I just fixed a bug in the rev0 and rev1 zips. If you already flashed rev0 or rev1, you need to flash the remove zip before you flash the rev2 fixed version. No need to boot in between.
With rev2, both SDCARD and EMMC will show internal media storage, as will both MTP folders. A new folder, ext_sdcard, will show the external SD media partition.
Updating earlier versions of CWM
Updating prior installs of the Original SD installation to this new version of CWM is easy. Just download the ramdisk zip file attached below and extract the file. Put your old SD setup in your PC and rename the ramdisk.cwm to ramdisk.cwm.bak. Then copy the new ramdisk.cwm you just extracted to the card, replacing the version that was there. Next time you boot to CWM, the 6.0.2.8 version for HD+ Original SD will be there.
Change Log
Change Log
05/28/13 - guide is obsolete starting with the 5/27/13 ROM
05/15/13 - removed warning, resolved
04/10/13 - added warning running CM10.1.
03/09/13 - added rev2 of the swap zip, as it failed on CM10.1
03/08/13 - added rev1 of the swap zip to fix a permissions bug.
03/07/13 - retitled thread
03/03/13 - added CM10/10.1 SDswap zips
02/27/13 - Initial posting
OP Updated
Re: [GUIDE/TOOLS] HDplus CM10/10.1 Easy Install Guide and Tools for Original SD
For hd plus only?
Sent from my BNTV400 using xda app-developers app
Re: [GUIDE/TOOLS] HDplus CM10/10.1 Easy Install Guide and Tools for Original SD
mrDAXpax said:
For hd plus only?
Sent from my BNTV400 using xda app-developers app
Click to expand...
Click to collapse
Yes, you can use bokbokan's hybrid image to do it the same way for the HD. And I think his standard image does it too.
Sent from my Nook HD+ running CM10 on Hybrid SD
question...
Sorry if this has been answered somewhere else but, I did this using a 32gb card and everything I running smooth. I have a 64gb card that I want to switch it out for. I know it won't be a problem doing the root and all of that again, but I was wondering if anybody knows how to change the 32gb SD card back to normal? When I stick it in my computer all it shows is the boot partition and when I try to format it, it only formats that's partition. Meaning that my 32gb card turns into a worthless 116 mb card. I've tried on windows and Ubuntu and get the same results...
So does anybody have any suggestion?
Re: [GUIDE/TOOLS] HDplus CM10/10.1 Easy Install Guide and Tools for Original SD
startoxic said:
Sorry if this has been answered somewhere else but, I did this using a 32gb card and everything I running smooth. I have a 64gb card that I want to switch it out for. I know it won't be a problem doing the root and all of that again, but I was wondering if anybody knows how to change the 32gb SD card back to normal? When I stick it in my computer all it shows is the boot partition and when I try to format it, it only formats that's partition. Meaning that my 32gb card turns into a worthless 116 mb card. I've tried on windows and Ubuntu and get the same results...
So does anybody have any suggestion?
Click to expand...
Click to collapse
Yes, use SDFormatter free from the web. It will do it.
Sent from my Nook HD+ running CM10 on Hybrid SD
Thank you, I will try that and let you know how it works
This is probably a stupid question, but once I've got the SD card set up properly, can I then go ahead and delete the ZIP files that I've installed? Or do I need to keep them kicking around? Figure if I can free up some space, I should.
Re: [GUIDE/TOOLS] HDplus CM10/10.1 Easy Install Guide and Tools for Original SD
stormerider said:
This is probably a stupid question, but once I've got the SD card set up properly, can I then go ahead and delete the ZIP files that I've installed? Or do I need to keep them kicking around? Figure if I can free up some space, I should.
Click to expand...
Click to collapse
You can delete them if you want, but I usually always keep them somewhere so I don't have to redownload them if I need to reflash, which very oftern I have to for various reasons. I can always delete them later if space becomes an issue.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
You can delete them if you want, but I usually always keep them somewhere so I don't have to redownload them if I need to reflash, which very oftern I have to for various reasons. I can always delete them later if space becomes an issue.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
*nod* I meant deleting them off the SD card (should have specified). I'd be keeping them on my fileserver to ensure that I can reflash the sdcard to the same version I started with if I need to.
leapinlar said:
Setting up the SD
Begin by downloading the files you need either with stock or your PC. You will need my updated SD image file, attached below, the CM ROM zip you want to install and the gapps zip to match it. Put the last two zips on your internal media sdcard.
Click to expand...
Click to collapse
I'm confused by this, what are you referring to as "internal media sdcard"? I used win32 to burn the .img file, then booted into CWM...I'm clearly doing this wrong, because after that, the sdcard only has 117mb and no room to put ROMs on
Re: [GUIDE/TOOLS] HDplus CM10/10.1 Easy Install Guide and Tools for Original SD
KamikazeChris said:
I'm confused by this, what are you referring to as "internal media sdcard"? I used win32 to burn the .img file, then booted into CWM...I'm clearly doing this wrong, because after that, the sdcard only has 117mb and no room to put ROMs on
Click to expand...
Click to collapse
You are doing it right. 117MB is what it is supposed to have. You do not put the files on that card. You put them on the HD+ (on the internal sdcard).
If you could see that it only had 117 MB, you were not booted to CWM, you were looking at the SD while it was still inserted in the PC. Booted to CWM means it is in the Nook.
When you insert the burned SD into the powered off HD+, then turn it on, it boots to CWM. That is what I mean by booting to CWM.
The internal sdcard means the storage that is built into the HD+ (that is why I call it internal). Boot to stock and download the files with it. They get put on the internal sdcard or "sdcard" as it is called. After you insert the burned card into the HD+ and boot to it, CWM has the ability to flash the zips by reading them from the internal sdcard built into the HD+.
Edit: I just clarified that in the OP. It is hard to anticipate how users will interpret your words in advance.
Sent from my Nook HD+ running CM10 on Hybrid SD
i dont seem to understand what file is supposed to amount to about 120mb. i extract "cm-10-20121231-UNOFFICIAL-ovation" and amounts to more than 200mb's but it also replaces other files.
Re: [GUIDE/TOOLS] HDplus CM10/10.1 Easy Install Guide and Tools for Original SD
droidbot1337 said:
i dont seem to understand what file is supposed to amount to about 120mb. i extract "cm-10-20121231-UNOFFICIAL-ovation" and amounts to more than 200mb's but it also replaces other files.
Click to expand...
Click to collapse
You do not extract the cm zip. You extract the image zip which is attached to the post. It is the one that is 120 MB and is the one you burn to the SD with win32diskimager.
Sent from my Nook HD+ running CM10 on Hybrid SD
leapinlar said:
You do not extract the cm zip. You extract the image zip which is attached to the post. It is the one that is 120 MB and is the one you burn to the SD with win32diskimager.
Sent from my Nook HD+ running CM10 on Hybrid SD
Click to expand...
Click to collapse
thank you for the help. i appreciate it! i can now use my new HD+ (bought it last night) to its full potential.
I just wanted to say that I was suffering from the dreaded "Nook refuses to boot from the SD card" syndrome. I tried three different SD cards burned using four different computers, to no avail. Tried this patch? Worked perfectly. Thanks! :laugh:
SDXC cards viable for this use?
Well, that registration video was a real interesting bit compared to most forums I've ever used. Somebody put a lot of work into that.
I'm noticing a lot of emphasis on Class 4 cards. Impetuous sort that I am, I already obtained a Sandisk Ultra 64 GB microSDXC (Class 10/UHS 1) card for this project. Best Buy had a good deal and I was hoping to have a lot of room to work with and it wasn't clear what access to the internal storage would be available or best left alone. Has anyone had success or great problems with this card?
Other than that issue before attempting to execute the install, this is a very helpful thread. Much clearer than verygreen's original. That shouldn't be taken as an insult to verygreen as technical writing for those outside a project is not a skill everyone has or should have. Asking those deep within a project to shift mental gears to operate at the outsider's level can be a waste of resources and is often better delegated to a specialist. And we should be thankful for those specialists when they volunteer like this.
Epobirs said:
I'm noticing a lot of emphasis on Class 4 cards. Impetuous sort that I am, I already obtained a Sandisk Ultra 64 GB microSDXC (Class 10/UHS 1) card for this project. Best Buy had a good deal and I was hoping to have a lot of room to work with and it wasn't clear what access to the internal storage would be available or best left alone. Has anyone had success or great problems with this card?
Click to expand...
Click to collapse
Some have had good success with that card, especially if they use my Hybrid setup which uses less of the SD to operate from.
leapinlar said:
Some have had good success with that card, especially if they use my Hybrid setup which uses less of the SD to operate from.
Click to expand...
Click to collapse
It appears to be working on the first try. I'm currently syncing my app set from the Play store. It looks like this will be a huge value add for the Nook. I wouldn't have bought it if the full Android option weren't there. I just hope enough of us still buy books from B&N to keep them going.
Thanks.

[HOW TO] Installing LN14.1 Internally on Nook HD+

Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to install amaces' LN14.1 (ref: https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269) internally on a Nook HD+ :
Download sdcard-reco-ovation.img.xz from amaces' repo https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778, unzip it (using e.g. 7-zip) and use win32diskimager to write the unzipped content sdcard-reco-ovation.img to a SD card.
Download and copy to the same SD card:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of Gapps' corresponding pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Turn off the Nook, insert the SD card, and boot the Nook from its power-off state.
[Optional] Make a backup of your stock ROM & Apps: to backup onto the Bootable Recovery SD card you'd need to make the boot partition on the SD card large enough to hold the backup of your stock ROM and its Apps -- see my post #7 below.
Select "wipe data & factory reset".
Select "install zip from SD card" and install TWRP recovery zip file.
Select "install zip from SD card" and install LN14.1 zip file.
Select "install zip from SD card" and install Gapps zip file.
Remove SD card and select reboot.
Once the HD+ completes boot-up (be patient as the post-installation initial boot would take 3-5 min), set up the wifi connectivity and your google account info.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 5, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
- This procedure can also be used to install amaces' AOSP7.1 ROM (instead of his LN14.1 ROM).
- If your HD+ is currently running CM11/12/13, see https://forum.xda-developers.com/nook-hd/general/how-to-updating-nook-hd-internal-emmc-t3562818 for an alternate procedure which does not require use of a SD card.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I used these steps and can confirm that it works. I came from stock ROM. I understand that there's a risk since I did not do a original ROM backup.
So far, I am impressed by the work that have gone in to make it happened from so many volunteers.
wiismhour said:
...
I understand that there's a risk since I did not do a original ROM backup.
...
Click to expand...
Click to collapse
If you ever need/want to re-install stock ROM, see #6 of https://forum.xda-developers.com/showthread.php?t=2062613.
digixmax said:
If you ever need/want to re-install stock ROM, see #6 of https://forum.xda-developers.com/showthread.php?t=2062613.
Click to expand...
Click to collapse
Good point! Thx
I did this on my Nook HD yesterday. Everything seemed to go correct, however my tablet will not power off. If I power off it immediately restarts. I saw a similar problem mentioned with another build but can't seem to find the thread that was referenced.
edit: I found this thread https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269/page166 which implies this is a known problem.
Holding the power button beyond the shutdown screen worked! The tablet powered off and stays off. Phew.
Can I take a moment to say thank you. I have owned a Nook HD and Nook HD+ for almost four years. I am not very technical but did do some modding of them to enable unknown sources, the very basic you could do. The tablets were really sluggish with the original OS but we muddled through. Last week the Nook HD froze at the boot screen and the only way to resolve was a factory reset. I figured the time was right to do something more permanent and followed your instructions.
The only issue I had was I was not able to do a backup. I used an 8 GB SD card. When I used win32diskimager to write the unzipped content sdcard-reco-ovation.img to the SD card for some reason the size of the card changed to ~900 MB. So the SD card didn't have enough space for the OS backup. I redid the card several times but it kept happening. Not sure if you know what I did wrong, but I hope its moot since I hope to never to have to go back to the Nook OS.
Very sorry for the long message, but I am excited with the prospect of having a tablet we can actually use. I plan to do this to my HD+ but that one is still working and has a ton of content that I know will be lost. But I think I have to do it.
bru20 said:
...
Can I take a moment to say thank you.
...
Click to expand...
Click to collapse
You're quite welcome (you can thank me by just hitting the "Thanks" button on my post).
...
The only issue I had was I was not able to do a backup. I used an 8 GB SD card. When I used win32diskimager to write the unzipped content sdcard-reco-ovation.img to the SD card for some reason the size of the card changed to ~900 MB. So the SD card didn't have enough space for the OS backup. I redid the card several times but it kept happening. Not sure if you know what I did wrong, but I hope its moot since I hope to never to have to go back to the Nook OS.
...
Click to expand...
Click to collapse
Bootable Recovery SD card images (such as Amaces' image in this case) are usually intentionally made just large enough for users to add necessary flashable zip files for ROM/GApps/Recovery yet small enough to fit in the smaller size cards a user might happen to have laying around. It's possible but more tedious (and thus potentially error-prone) to create a Bootable Recovery SD card with custom size of up to 16GB for the boot-partition -- I'll post a short guide for this.
Process for Creating a Bootable Recovery SD card for Nook HD+
[Caveat emptor: adopt/follow this guide at your own risk].
Below is the process for creating a Bootable Recovery SD card for flashing ROM/GApps/Recovery on a Nook HD+:
Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on a SD card a Primary FAT32 partition of size no larger than 16GB, and set the partition ID type for the partition to 0x0C FAT32 LBA and set its Active flag. Once this is done, the partition should appear as a (read/write accessible) drive under Windows.
Use an archive file manager such as 7-zip and extract the .img file from amaces' sdcard-reco-ovation.img.xz ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778 )
Use the archive file manager to extract the files from the .img file and copy them to the SD card: first MLO, then the rest of the files u-boot.bin, uImage, kernel, ramdisk, ramdisk.cwm, ramdisk.stock, and the folder OLD.
Copy to the SD card the flashable zip files for the ROM/GApps/Recovery/etc. that you'd want to install.
Notes
The most common symptoms of failed SD boot and their likely causes are:
The HD+ boots straight to stock -- most likely the boot partition's type and/or flag are not correctly set, or the NT cannot find the MLO in the boot partition (make sure that MLO is the very first file to be copied to the freshly made /boot partition).
If the HD+ consistently boots straight to stock in spite of a valid /boot partition and boot files, it's possible that the tablet is one of those HD+ units that have difficulty booting of SD cards, see http://forum.xda-developers.com/showthread.php?t=2288688 for more info and potential remedies.
The HD+ screen stays dark for seemingly a long time then eventually boots to stock -- most likely the MLO or u-boot.bin are corrupted. I have had this happen to me a few times in the process of extracting them from archive zip files.
The boot partition size is too large -- for some reason the HD+ cannot boot on boot partition of size larger than 16GB.
Fantastic write up.
Everything went flawlessly.
I notice that my device is no longer rooted. Is there a relatively quick way to re-root now that I've completed all the steps in your original post?
Thanks for such a well written guide!!
bozzchem said:
...
I notice that my device is no longer rooted. Is there a relatively quick way to re-root now that I've completed all the steps in your original post?
...
Click to expand...
Click to collapse
Root is built into this ROM and can be enabled in Settings->"Developer Options", but because of a current bug you'd need to enable it, then disable it, then re-enable it again.
digixmax said:
Root is built into this ROM and can be enabled in Settings->"Developer Options", but because of a current bug you'd need to enable it, then disable it, then re-enable it again.
Click to expand...
Click to collapse
Let's just say that you effin rock!!
:highfive:
Problem solved.
Sorry, double post........
After getting root access as described above in post #9, I installed SuperSU and SuperSU Pro from Play.
Once the binary updated and I rebooted, I was stuck in a bootloop. I had to reflash the entire process to get the HD+ operational again.
Is this normal? Did I miss something? Does SuperSU not work with this ROM?
I see that the ROM has "Privacy Guard" which looks to be a form of superuser. Ti backup isn't happy with the stock SU and would prefer I install SuperSU. I would love to install SuperSU but don't want to reflash from scratch again.
Any tips/help would be greatly appreciated!
bozzchem said:
After getting root access as described above in post #9, I installed SuperSU and SuperSU Pro from Play.
Once the binary updated and I rebooted, I was stuck in a bootloop. I had to reflash the entire process to get the HD+ operational again.
Is this normal? Did I miss something? Does SuperSU not work with this ROM?
...
Any tips/help would be greatly appreciated!
Click to expand...
Click to collapse
I believe the "Manage root access" menu in Settings->"Developer options" is meant to eliminate the need for root-access-management apps.
digixmax said:
Root is built into this ROM and can be enabled in Settings->"Developer Options", but because of a current bug you'd need to enable it, then disable it, then re-enable it again.
Click to expand...
Click to collapse
I don't see that option after flashing aosp_ovation-ota-NOF26W.170226.zip
Do I need to reflash, and let CWM fix for root?
michealm1979 said:
I don't see that option after flashing aosp_ovation-ota-NOF26W.170226.zip
Do I need to reflash, and let CWM fix for root?
Click to expand...
Click to collapse
Did you not see "Manage root access" under Settings->"Developer options", or not see "Developer options" itself?
digixmax said:
Did you not see "Manage root access" under Settings->"Developer options", or not see "Developer options" itself?
Click to expand...
Click to collapse
I don't see Manage Root Access.
michealm1979 said:
I don't see Manage Root Access.
Click to expand...
Click to collapse
Apparently "Manage root access" is only available on LN ROM.
For AOSP ROM it looks like you still need to install SuperSU, see https://forum.xda-developers.com/showpost.php?p=71063379&postcount=1647.
Thank you for the work on this. Mine is HD Plus.. Only problem I'm having after upgrade is the unit ignores "Power off" and seems to turn itself on after about 30 seconds of black screen and boots back up. Battery is at 100%, and I disconnected the USB cable, nothing is connected. Anyone else seen this?
RoundSparrow said:
Thank you for the work on this. Mine is HD Plus.. Only problem I'm having after upgrade is the unit ignores "Power off" and seems to turn itself on after about 30 seconds of black screen and boots back up. Battery is at 100%, and I disconnected the USB cable, nothing is connected. Anyone else seen this?
Click to expand...
Click to collapse
I am running lnos_ovation-ota-NOF26W.170226 and have not seen this problem with this build as well as the previous build.
Did you do a "wipe /data & factory reset" before flashing the ROM/GApps zip files?
Also, this thread which has a much larger set of reader might be a better place to post and get help with questions like yours.
digixmax said:
I am running lnos_ovation-ota-NOF26W.170226 and have not seen this problem with this build as well as the previous build.
Did you do a "wipe /data & factory reset" before flashing the ROM/GApps zip files?
Also, this thread which has a much larger set of reader might be a better place to post and get help with questions like yours.
Click to expand...
Click to collapse
I did it on two systems, one is 16GB the other 32GB. The one that keeps turning back on was one was upgraded from CM11 (32GB), the other was virgin Nook OS . Yes, I did wipe /data and factory reset, formatted cache, etc.

Categories

Resources