Hi all,
please help me on this, please.
I think my hd+ was messed up. I remember at first I had CWM boot environment. but when I was flashing NookHDplus-factory-2.20-plain-stock.zip, it crashed. I didn't realize the emmc structure might be lost, I restart and flashed the twrp_recovery_ovation_4.zip into the machine(I heard from somewhere else it might be helpful). but now it is even worse.
I have tried 3 bootable microSD card(1. pny 4G, class4, 2. kingston 8G, class4, 3. sandisk 4G, class2) 1. is imaged with emmc-cwm-early3.1.img; 2. is imaged with nookHDplus-bootable-cWM-6028-for-stock-4GB-rev4-(05.11.13).zip. and 3 is formatted with SDformat & actived and with files from NookHDplus-bootable-CWM-6028-for stock-BOOTFILES-r4-(05.15.13).rar.
1)so without microSD card in slot, the hd+ did as follows(the power supplier is plugged in for indication):
green light turn on 4 second-->nook icon(with adobe reader statement) 2 second-->white cyanoboot(and blue universal bootloader) icon 4 second
2) with class 4 microSD card.-->loop
green light turn on 4 second-->nook icon(with adobe reader statement) 2 second-->white cyanoboot(and blue universal bootloader) icon 15 second.-->loop
3 with class 2 card.
green light turn on 4 second-->nook icon(with adobe reader statement) 2 second-->white cyanoboot(and blue universal bootloader) icon 30 second-->loop.
So it looks hd+ saw the microSD card, but still cannot enter the correct procedure.
Does anyone has any idea what I can do now? I was so frustrated...
Thank you so much in advance!
It might be that your emmc is bricked. All of the cards require that at least some of emmc is working. Verygreen made a noemmc CWM and ROM somewhere that I don't have a link for. Try searching the forum. Others have reported success with that in booting to CWM and getting a ROM working on SD.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
It might be that your emmc is bricked. All of the cards require that at least some of emmc is working. Verygreen made a noemmc CWM and ROM somewhere that I don't have a link for. Try searching the forum. Others have reported success with that in booting to CWM and getting a ROM working on SD.
Click to expand...
Click to collapse
Thank you very much! I would like to try it in the weekend. But I noticed in the discussions, that the OS on sdcard will also use some part of emmc, so if the emmc has errors in those part, the OS will not operate successfully, right?
By the way, is there any possibilities that you professionals make a kind of 'tool' microSD, that can automatically format and rebuild the file structures on a messed emmc and then copy/restore the stock OS to it without any manual input. Or even better, since the space of SD card is usually big enough, people can copy different OS zips into it, so that the tool card can let people to choose which OS to be installed after it automatically format and rebuild the file system structure on emmc.
Thanks again.
peanuto said:
Thank you very much! I would like to try it in the weekend. But I noticed in the discussions, that the OS on sdcard will also use some part of emmc, so if the emmc has errors in those part, the OS will not operate successfully, right?
By the way, is there any possibilities that you professionals make a kind of 'tool' microSD, that can automatically format and rebuild the file structures on a messed emmc and then copy/restore the stock OS to it without any manual input. Or even better, since the space of SD card is usually big enough, people can copy different OS zips into it, so that the tool card can let people to choose which OS to be installed after it automatically format and rebuild the file system structure on emmc.
Thanks again.
Click to expand...
Click to collapse
Not me. It is too complex on the HD/HD+.
And you are right, the status of emmc can effect SD installs.
Sent from my BN NookHD+ using XDA Premium HD app
Related
Hi All,
I have a Nook HD, recently purchased and then updated to BN 2.0.6 firmware during the BN registration process. I used the sdcard-cwm-early5.img.gz as referenced in Verygreen's post here to create a bootable CWM SD. I then installed the CM 10.1 build posted in thread by Bokbokban here. Finally, I installed latest gapps from goo.im. All seems to be pretty good, excepting that sometimes, seemingly randomly, the device will reboot itself, at which time it bypasses the SD during boot and goes straight for the stock BN rom on the emmc.
Any ideas on how to proceed? I haven't seen a pattern in the reboots yet, so I am not sure what may or may not be causing them. While I'm not exactly a newb with all that is involved with rooting/flashing various android devices (I own 5 of them), I could use some guidance on how to troubleshoot or diagnose problems like this.
I am confused. You used an HD+ image from verygreen and an HD ROM from bokbokan. How did you make that work? They should not have worked.
But if you really only used HD files, the reboot problem is probably the brand and class of the SD you used. It needs to be SanDisk class 4. We have that problem a lot on the HD+. It is cause by a kernel panic when trying to write to SD.
The solution is to get a better SD or use bokbokan's new Hybrid SD setup that puts /data on internal memory so SD speed does not matter.
Sent from my Nook HD running CM10.1 on Hybrid SD
leapinlar said:
I am confused. You used an HD+ image from verygreen and an HD ROM from bokbokan. How did you make that work? They should not have worked.
But if you really only used HD files, the reboot problem is probably the brand and class of the SD you used. It needs to be SanDisk class 4. We have that problem a lot on the HD+. It is cause by a kernel panic when trying to write to SD.
The solution is to get a better SD or use bokbokan's new Hybrid SD setup that puts /data on internal memory so SD speed does not matter.
Sent from my Nook HD running CM10.1 on Hybrid SD
Click to expand...
Click to collapse
Thanks for your prompt reply. To be clearer, I did not use the HD+ image, but I did use the CWM image Verygreen posted, 'sdcard-cwm-early5.img.gz', as that version supported using CWM to read .zip's from /emmc (in other words, those that were downloaded via BN stock browser).
At the risk of sounding like I am second-guessing you, I think it's worth noting that I had no trouble with many things related to writing to the SD card: writing the CWM image, booting into CWM from the SD, writing the CM10.1 image onto the card, booting from the 10.1 rom, etc... So if it is, as you say, the card having write issues and causing a kernel panic, I'm wondering how I can prove that. I will check the kernel logs when I get home.
I'm using a Sandisk 'ultra' class 10 16gb... I get that 'class 10' generally means 'crappy for small random write requests', but I've had good luck with this particular card on other platforms that are sensitive to consistency of write speeds (G2, Nook Color). However, I'll try a class-4 Sandisk per your suggestion.
Follow-up question: I can't seem to find a solid guide that shows how to install to emmc... is that a new frontier for this device? Is it just that nobody has bothered, or is there a problem with original bootloader supporting that?
redfriar said:
Follow-up question: I can't seem to find a solid guide that shows how to install to emmc... is that a new frontier for this device? Is it just that nobody has bothered, or is there a problem with original bootloader supporting that?
Click to expand...
Click to collapse
The internal bootloader is locked down pretty good. Some day someone will be able to break it, but for now no one has.
Sent from my Nook HD+ running CM10 on Hybrid SD
Btw, I have had really bad results with my San disk CL 10. You may find other cars will work better.
Sent from my Barnes & Noble Nook HD+ using xda app-developers app
Hello,
First off, thanks to e.mote for the CyanogenMod 10.1 for Dummies guide and to the work put in by verygreen, leapinlar and bokbokan. The guide was simple and straightforward, I installed CM10.1 and CWM (seemingly) without a hitch.
However, when attempting to do a baseline backup, I'm running into some problems. I've searched the forum overall and gone through pages and pages in the Nook sections and not found any real solution. On my 8GB HD, when rebooting to recovery and attempting to backup to an SD card, I'm having the following issues:
When CWM loads, I get a "warning: no file_contexts" message. I've read mixed things about whether this is significant or not and what to do to correct it.
When I go to backup and restore>backup it seems to backup to the SD card without a hitch (although it has shown differing amounts of free space on the cards whenever I've attempted this). But when I insert the card into my computer to copy the backup, the only thing on the card is a folder called "LOST.DIR" and all the space but 3.1MB is free. I've done this 3-4 times so far, with two different microSD cards (one 4GB, one 32GB). I've both checked it and formatted the card (in FAT32) on a computer running Windows XP and one running OSX. Same results on both every time.
At some point when attempting to do the backup, the screen of the Nook begins to flash/flicker and doesn't stop until I restart it.
The first time I tried to do the backup, after I tried to restart, it didn't boot back up and the power button was unresponsive. Possibly this was due to overheating? I plugged it into the charger and it started up on its own after about 10 minutes.
Anyone else encounter this? Any solutions. Obviously I want to be able to back things up. I just rooted the device this evening, so I'd rather to not have to go through the install process all over again rather than have a proper backup.
Thanks!
You need to tell us which version of CWM you are running. And is installed to internal memory or SD?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You need to tell us which version of CWM you are running. And is installed to internal memory or SD?
Click to expand...
Click to collapse
Ah, of course! Sorry, that's what I get for doing this so late. Okay, so it's installed to the internal memory. The files I downloaded were this and this. When I reboot into recovery is says "EMMC CWM-based recovery v6.0.3.6".
Thanks
elcapitansmirk said:
Ah, of course! Sorry, that's what I get for doing this so late. Okay, so it's installed to the internal memory. The files I downloaded were this and this. When I reboot into recovery is says "EMMC CWM-based recovery v6.0.3.6".
Thanks
Click to expand...
Click to collapse
Ah, ok. That means you have the newest version which puts the backup on internal memory. If you look at the menu choices closely, you will see it says to internal sdcard and the other choice is to external sdcard. So you will not find the backup on your external card.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Ah, ok. That means you have the newest version which puts the backup on internal memory. If you look at the menu choices closely, you will see it says to internal sdcard and the other choice is to external sdcard. So you will not find the backup on your external card.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks! That'll teach me to just blindly follow instructions rather than looking around and exploring on my own - I didn't even notice the "Backup to External SD" option. So, thanks for your patience, your work on this and your speedy replies. Seems like all is well now.
Here is my problem description:-
I was using CM10.1.3 emmc with CWM latest version as suggested in the respective thread. I have installed a SD formatter app from Google Play and tried to format my 32GB Class 10 Samsung MicroSD card inside the device. After that, the sd card was non writable. So I tried to restart the device, but alas, it got stuck in the 1st Black screen with the big Nook. Not even able to boot into CWM. Even the CyanogenMod logo didn't come.
I have a bootable CWM (6.0.28) recovery MicroSD card (8GB Class 4) and used it to boot into recovery, cleared Cache/ Factory reset, Dalvik Cache and then again flashed Carbon unofficial 4.3 JB rom and Gapps for JB 4.3. But it still getting stuck in the 1st Nook screen.
After reading a lots of thread here, it looks like that during the format of SD card, it somehow destroyed the proper partitions of the emmc. But unlike others mentioned in different Bricked Nook HD thread, I am able to access each components of emmc when booted from CWM Bootable card, able to mount internal storage etc.
So, is there a solution to restore the emmc partitioning properly? I tried to connect it to PC for connecting it through adb but didn't have the proper usb driver for it. The driver I got, needs the hardware id of the product to modify the inf file which sadly I can't access in the device.
I also tried to restore it to stock 2.2 rom from the CWM backup created earlier before installing CM10.1.3. It got restored but didn't solve the problem, it still getting stuck into Black screen with Nook written to it, the one comes before CM logo.
Please help.
Anyone? Please guys help me here.
Suryasis said:
Here is my problem description:-
I was using CM10.1.3 emmc with CWM latest version as suggested in the respective thread. I have installed a SD formatter app from Google Play and tried to format my 32GB Class 10 Samsung MicroSD card inside the device. After that, the sd card was non writable. So I tried to restart the device, but alas, it got stuck in the 1st Black screen with the big Nook. Not even able to boot into CWM. Even the CyanogenMod logo didn't come.
I have a bootable CWM (6.0.28) recovery MicroSD card (8GB Class 4) and used it to boot into recovery, cleared Cache/ Factory reset, Dalvik Cache and then again flashed Carbon unofficial 4.3 JB rom and Gapps for JB 4.3. But it still getting stuck in the 1st Nook screen.
After reading a lots of thread here, it looks like that during the format of SD card, it somehow destroyed the proper partitions of the emmc. But unlike others mentioned in different Bricked Nook HD thread, I am able to access each components of emmc when booted from CWM Bootable card, able to mount internal storage etc.
So, is there a solution to restore the emmc partitioning properly? I tried to connect it to PC for connecting it through adb but didn't have the proper usb driver for it. The driver I got, needs the hardware id of the product to modify the inf file which sadly I can't access in the device.
I also tried to restore it to stock 2.2 rom from the CWM backup created earlier before installing CM10.1.3. It got restored but didn't solve the problem, it still getting stuck into Black screen with Nook written to it, the one comes before CM logo.
Please help.
Click to expand...
Click to collapse
What SD formatter app program from Play Store are you talking about? I need to know that so I can determine what you did?
Sent from my SCH-i705 using XDA Premium HD app
I have used the tool AParted (https://play.google.com/store/apps/details?id=com.sylkat.AParted) and tried to format my 32GB Samsung Class 10 MicroSD card.
BTW, in the mean time, I did little bit of digging and got the Serial of the Tab and if you want can share with you. I have also tried to install the CM10.2 SD card version with CWM 6.027 Bootable SD card. I was able to push the Zip files to the SD card using QtADB tool by mounting the SD card in the CWM menu, installed the CM rom to SD card and then installed the Gapps for JB 4.3. Still unable to boot into CM, it is going to CWM in every restart. Used this guide http://forum.xda-developers.com/showthread.php?t=2032364 for installation.
Suryasis said:
I have used the tool AParted (https://play.google.com/store/apps/details?id=com.sylkat.AParted) and tried to format my 32GB Samsung Class 10 MicroSD card.
BTW, in the mean time, I did little bit of digging and got the Serial of the Tab and if you want can share with you. I have also tried to install the CM10.2 SD card version with CWM 6.027 Bootable SD card. I was able to push the Zip files to the SD card using QtADB tool by mounting the SD card in the CWM menu, installed the CM rom to SD card and then installed the Gapps for JB 4.3. Still unable to boot into CM, it is going to CWM in every restart. Used this guide http://forum.xda-developers.com/showthread.php?t=2032364 for installation.
Click to expand...
Click to collapse
You are using some strange and outdated tools. That AParted probably really messed up you internal memory.
That guide is an old one for putting CM10 on an SD install. And you do not install the SD version of CM10.2 with that 6027 bootable CWM SD. Pick a newer guide and start again.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You are using some strange and outdated tools. That AParted probably really messed up you internal memory.
That guide is an old one for putting CM10 on an SD install. And you do not install the SD version of CM10.2 with that 6027 bootable CWM SD. Pick a newer guide and start again.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Actually I realised that and used the new guide for for installation of latest CM10.2 build by using the latest guide here: http://forum.xda-developers.com/showthread.php?p=36421852#post36421852. But whenever I am trying to boot into CM10.2, it is getting booted into CWM recovery.
I have checked in another thread where you had made a ZIP file to fix the internal storage structure, is it possible for my case.? Should I use this guide: http://iamafanof.wordpress.com/2013/09/17/cm10-2-jellybean-android-4-3-for-nook-hd-18sep2013/
I have used the method in http://iamafanof.wordpress.com/2013/09/17/cm10-2-jellybean-android-4-3-for-nook-hd-18sep2013/ and installed 10.2. But during restart, it is showing the message that /Bootdata/BCB missing and probably that is the reason, it is always rebooting into recovery mode. I have checked in one thread where you have made a flashable Zip file to restore the system partitions. Can it be done for my case?
Waiting for your answer.
Suryasis said:
I have used the method in http://iamafanof.wordpress.com/2013/09/17/cm10-2-jellybean-android-4-3-for-nook-hd-18sep2013/ and installed 10.2. But during restart, it is showing the message that /Bootdata/BCB missing and probably that is the reason, it is always rebooting into recovery mode. I have checked in one thread where you have made a flashable Zip file to restore the system partitions. Can it be done for my case?
Waiting for your answer.
Click to expand...
Click to collapse
Start over and use this thread:
http://forum.xda-developers.com/showthread.php?t=2317500
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Start over and use this thread:
http://forum.xda-developers.com/showthread.php?t=2317500
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Will that fix the emmc partitions in HD+? Initially I have installed CM10.1.3 by using this method and after the issue occurred, I tried to install the Carbon 4.3 ROM through CWM recovery after performing FActory reset, cache cleaning and Dalvik Cache cleanup. But that didn't solve the issue. I have even tried to restore the stock Nook 2.2 firmware from the CWM recovery which I created earlier before installing the CM10.3. But the issue didn't get resolved.
Suryasis said:
Will that fix the emmc partitions in HD+? Initially I have installed CM10.1.3 by using this method and after the issue occurred, I tried to install the Carbon 4.3 ROM through CWM recovery after performing FActory reset, cache cleaning and Dalvik Cache cleanup. But that didn't solve the issue. I have even tried to restore the stock Nook 2.2 firmware from the CWM recovery which I created earlier before installing the CM10.3. But the issue didn't get resolved.
Click to expand...
Click to collapse
If you used the CWM from that thread and flashed the plain stock 2.2.0, it should have fixed it.
Sent from my BN NookHD+ using XDA Premium HD app
I have tried the following steps:-
Downloaded the TWRP emmc 2.6 Bootfiles, copied them to a 64GB Class 10 sd card by formatting it to FAT32, setting it to active and then copied the Files (MLO file 1st) into it.
Also copied Nook stock 2.2 zip in the sd card.
With the card installed, Nook HD+ booted into TWRP recovery.
Performed a factory reset and wipe data.
Installed the stock rom.
After that, I checked the Bootfile partition and it was having the BCB file.
I am also able to access 27GB Emmc and copied all the zip files to Internal store using TWRP file manager.
Now I took out the SD card and tried to boot the Tab but it was again stuck into 1st Boot screen with Nook logo.
When I inserted the card 2nd time and checked the Boot Data partition using the TWRP's integrated file manager, there was nothing inside of the /BootData folder.
Is there a way to build the /Bootfiles/BCB for Nook HD plus?
Suryasis said:
I have tried the following steps:-
Downloaded the TWRP emmc 2.6 Bootfiles, copied them to a 64GB Class 10 sd card by formatting it to FAT32, setting it to active and then copied the Files (MLO file 1st) into it.
Also copied Nook stock 2.2 zip in the sd card.
With the card installed, Nook HD+ booted into TWRP recovery.
Performed a factory reset and wipe data.
Installed the stock rom.
After that, I checked the Bootfile partition and it was having the BCB file.
I am also able to access 27GB Emmc and copied all the zip files to Internal store using TWRP file manager.
Now I took out the SD card and tried to boot the Tab but it was again stuck into 1st Boot screen with Nook logo.
When I inserted the card 2nd time and checked the Boot Data partition using the TWRP's integrated file manager, there was nothing inside of the /BootData folder.
Is there a way to build the /Bootfiles/BCB for Nook HD plus?
Click to expand...
Click to collapse
it will do no good to build that file since you already had it and the boot to emmc wiped it out. TWRP puts it back when it exits, but your normal boot seems to remove it.
Sent from my SCH-i705 using XDA Premium HD app
Please suggest me a solution for it. I read here that there is a special type of SD installation possible with no access to the emmc and the OS will threat the SD card like it treats the emmc. Could you link me to a proper guide to do that?
Also, in my case, what might be the main problem of deletion of the Bootdata partition during emmc boot? Is there any possible solution for it?
Also, if possible, provide me the Zip file for the fix, just wanted to try it out as nothing is working till now.
Anybody? please let me know how to fix the emmc partitions. I still has hope as I am completely able to access my EMMC via SD card boot.While using TWRP recovery, I can even copy files from my SD card to internal memory of the device. Also able to flash Roms too.
So please provide me a flashable Zip file which can reconstruct the EMMC file structure for proper boot.
Suryasis said:
Anybody? please let me know how to fix the emmc partitions. I still has hope as I am completely able to access my EMMC via SD card boot.While using TWRP recovery, I can even copy files from my SD card to internal memory of the device. Also able to flash Roms too.
So please provide me a flashable Zip file which can reconstruct the EMMC file structure for proper boot.
Click to expand...
Click to collapse
I'm also in need of the same thing. I believe SD card manager or some such program fubared my partitions so now my Nook HD+ just hangs at the nook logo when booting from EMMC. I can boot off SD just fine though.
Suryasis said:
Please suggest me a solution for it. I read here that there is a special type of SD installation possible with no access to the emmc and the OS will threat the SD card like it treats the emmc. Could you link me to a proper guide to do that?
Also, in my case, what might be the main problem of deletion of the Bootdata partition during emmc boot? Is there any possible solution for it?
Click to expand...
Click to collapse
I was also in a similar situation in that I was stuck at the nook screen and not able to go beyond. I thought it was due to a discharged battery and leaving the Nook in my car in -20 F weather. However, I was not able to enter recovery. I found a thread by Verygreen detailing an SD card only installation for bad emmc units. I dd'd the image to the sd card and booted to cwm on the card. Then shut down, pulled the sd card and copied the rom to the card. Rebooted and the install went through correctly. I now have a working Nook HD+ although I don't have emmc access. But at least it works now. I found the thread in one of the other "Stuck on Nook screen" threads. Hope this helps you.
I have an issue that seems to be similar to those suffered by a number of people. I'm just having difficulty understanding the cause of it, and the solution. I have a nook hd+ that no longer boots as a result of trying CM11 on an SD card.
I installed CM11 to an SD card (as I was nervous of altering my nook) using bokbokan's excellent instructions. Initially it seemed fine but this morning it was unexpectedly out of battery and will no longer boot.
The symptoms are similar to this: http://forum.xda-developers.com/showthread.php?t=2611769, this: http://forum.xda-developers.com/showthread.php?t=2736347 and this: http://forum.xda-developers.com/showthread.php?t=2649061&page=2 except that the posters there had previously replaced the stock software and overwritten the emmc.
When the SD is in, it locks up on the Cyanoboot screen, when the SD card is out I only get to the black screen with 'Nook' on it and no further. It looks like the SD install has messed something up on the internal emmc. Hard resets and multiple failed boots don't appear to help.
I can occasionally (but not always) get it to reboot to CWM recovery by reinserting the card and holding down N and lock, but I get a lot of errors such as "E:Can't open /cache/recovery/last_log", "W:failed to mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache on /cache failed:No such file or directory" and "I:Can't partition non-vfat: /emmc (ext4)". When I go to 'Mounts and Storage' in CWM, I cannot mount anything (e.g. "Error mounting /boot!").
I chose to go down the SD card install route (using ) in order to avoid touching the stock install on the emmc, but now the whole thing is dead.
Reading other threads, it sounds like either:
1. The emmc is bricked due to some firmware bug. The impression I get from reading around is that CM11 was supposed to incorporate a workaround for the issue. If the emmc is the problem, I have to return the Nook and hope to get a working one.
2. The emmc has (somehow) become corrupted, I have to put a different version of CWM on my SDcard (so it will install to the EMMC rather than the SDcard, and because CM11 uses a different version), using the instructions here: http://forum.xda-developers.com/showthread.php?p=35811322 and then reinstall a stock rom to my emmc. I then have to reregister the Nook (not sure if this is essential) before being able to use my CM11 SDcard install again.
If it is the first problem, I would like to know how I can check to see if the emmc is indeed broken.
If it is the second, I would be grateful for any help in understanding how and why the SD install has messed up the emmc, and whether the steps above are likely to bring it back to life.
It sounds like your emmc is indeed bricked. I would go for the warranty exchange now. Just because you installed CM11 to SD does not mean it does not use emmc partitions. It still accesses and uses many of them (cache, rom, bootdata, /data/media, etc.). So there is opportunity for a brick. I would exchange it now while the cyanoboot logo does not show when booting without the SD.
Sent from my BN NookHD+ using XDA Premium HD app
Mf123 said:
I would like to know how I can check to see if the emmc is indeed broken.
Click to expand...
Click to collapse
You may find links and info in this post helpful http://forum.xda-developers.com/showthread.php?p=44810400
Thanks to both for replying. I feared that was the case.
I'm a bit disappointed that the SD card install (generally the option for those who want to leave the nook untouched) can in fact ruin the machine.
I've contacted the Nook website and will see what happens.
Mf123 said:
Thanks to both for replying. I feared that was the case.
I'm a bit disappointed that the SD card install (generally the option for those who want to leave the nook untouched) can in fact ruin the machine.
I've contacted the Nook website and will see what happens.
Click to expand...
Click to collapse
Just take your device to a store. They will exchange on the spot once they verify your registration on their computer. Of course don't tell them you were running CM, even on SD.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Just take your device to a store. They will exchange on the spot once they verify your registration on their computer. Of course don't tell them you were running CM, even on SD.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks, but there are no BN stores in the UK. They don't even sell the Nook directly from their uk website anymore. I have to post it to the Netherlands and see what happens.
So, after 2 months, and a lot of arguing with customer services, I have finally got a replacement Nook through the post.
I am still keen to try CM, but want to be really sure that my Nook doesn't get bricked again. Is there any way of checking whether an sd card install is likely to trigger an emmc failure on my new Nook?
Mf123 said:
So, after 2 months, and a lot of arguing with customer services, I have finally got a replacement Nook through the post.
I am still keen to try CM, but want to be really sure that my Nook doesn't get bricked again. Is there any way of checking whether an sd card install is likely to trigger an emmc failure on my new Nook?
Click to expand...
Click to collapse
The best way to avoid bricking by CM11 is to not try CM11. I run CM 10.1.3 and have heard of no one bricking when running that.
Sent from my BN NookHD+ using XDA Premium HD app
I want to install CM11 onto my external SDcard, not touching the B&N stock OS or rooting it in any way , so as not to void the warranty. #1 is this possible?
I built the SDcard, creating partitions: BOOT (0x0c FAT32 LBA & set Active),SYSTEM, DATA partitions.
I downloaded Succulent's "cm_ovation_11.0_02JUL2014_HD_SDC" file, unzipped it and copied the 6 files from it (MLO first)
Booted the HD+ but it didn't boot to sd,-- only did the normal Nook boot and hung at 99% loading the nook OS.
I then saw something about needing to install CWM Recovery first and boot that, so I located a download for CWM, but found it contains the same files as Succulent's "cm_ovation......" file (MLO, etc.). So if I were to extract that to the BOOT partition, I'd overwrite what I extracted from his zip.
So I'm missing some pieces to the trick....
Try using bokbokan's version and instructions here:
http://forum.xda-developers.com/showthread.php?t=2583952
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Try using bokbokan's version and instructions here:
http://forum.xda-developers.com/showthread.php?t=2583952
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thank you, but I had customized my partitions, and was hoping to stay with them, versus overwriting them with an image someone made that has pre-picked partitions. That is, unless somehow I can resize the partitions he made (and at which point in the process?) On mine I had 4 partitions. the last one was just an NTFS one, 6GB, I was hoping to keep available for just general storage, not necessarily for KitKat's use.
See http://forum.xda-developers.com/showpost.php?p=49007593&postcount=84 for pointers on creating CM11 SDcard with customized partition sizing. You should be able to create and maintain a 4th partition (but you'd need to figure out how to mount the partition so as to make it accessible to Android and/or your PC OS).
cm11 boot to sd
Ok, I must be missing some simple step.
In that link Digimax sent me, I believe I followed all steps. I ended up with these files on the BOOT partition (as seen in windows):
The 6 files extracted from sdcard-ovation-cm11.0-v1.img
pa_gapps-modular-mini-4.4.4-20141121-signed
cm-11-20140804-UNOFFICIAL-bok-ovation
a folder called LOST.DIR (not sure what that's from)
I choose "Boot to CWM Recovery" and I first did a backup. Then I selected "Install ZIP" then "Choose zip from sdcard" & I see
/sdcard/
- 0/
- clockworkmod/
That's it. Nothing else. Selecting either one of these displays no zip files. What am I doing wrong? In that post, step 4 it mentions "pair" of zip files. I assume though the 2nd item in the "pair" is the Gapps zip. Cuz for HD+ all I see is one file: cm-11-20140804-UNOFFICIAL-bok-ovation. (it doesn't have "sgt7" in the name anymore.) I assume I don't need the one for the regular HD model.
baytee said:
Ok, I must be missing some simple step.
In that link Digimax sent me, I believe I followed all steps. I ended up with these files on the BOOT partition (as seen in windows):
The 6 files extracted from sdcard-ovation-cm11.0-v1.img
pa_gapps-modular-mini-4.4.4-20141121-signed
cm-11-20140804-UNOFFICIAL-bok-ovation
a folder called LOST.DIR (not sure what that's from)
I choose "Boot to CWM Recovery" and I first did a backup. Then I selected "Install ZIP" then "Choose zip from sdcard" & I see
/sdcard/
- 0/
- clockworkmod/
That's it. Nothing else. Selecting either one of these displays no zip files. What am I doing wrong?
Click to expand...
Click to collapse
It does not appear that you've made any mistake. It's possible that bokbokan's CWM recovery has changed since I wrote up that guide nearly a year ago (and shortly thereafter have gone onto flashing/running CM11 on emmc and thus would have missed any such change).
One possible solution you might consider trying is to download or copy the ROM and Gapps zip files to your HD+ user-media partition, then while in CWM recovery menu select "... zip files from emmc" and browse to where the ROM/Gapps zip files are located.
In that post, step 4 it mentions "pair" of zip files. I assume though the 2nd item in the "pair" is the Gapps zip.
...
Click to expand...
Click to collapse
Yes, that's correct.
bok build install behaves super flaky for me
One possible solution you might consider trying is to download or copy the ROM and Gapps zip files to your HD+ user-media partition, then while in CWM recovery menu select "... zip files from emmc" and browse to where the ROM/Gapps zip files are located.
I got the sdcard to boot after many reboots and had to keep hard powering off (cutting it off) if the NOOK name displayed too long, (where I knew it was going to boot Nook OS) It booted to CWM, I did a backup, then installed the zips (had to put on internal memory as you said, but even this wasn't easy, It gave some weird error I don't recall,maybe about something "has stopped", so I ended up having to copy it from ES File Explorer after booting to Nook OS) Then I repeated the boot trick as mentioned, backed it up, then installed the 2 zips. I rebooted, got walkthrough of 1st time setup. This is where it got weird. Screens would advance on their own, be shifted halfway off the screen, had a long delay or else wouldn't respond to my clicks, would power off (and wouldn't power on until MANY presses of the power button) or reboot on it's own during the setup. I finally got thru setup and then after booting to Android, it would still be very sluggish, and still powering off on it's own and being difficult to turn on. And it continued to be unreliable to boot to Android, sometimes booting to Nook OS still (even though some in forums say once they got it to boot to Android it would forever after.)
Maybe I need to try a different build. Who else has a well-known, reliable? build besides Succulent? (even though with his it wouldn't boot to CWM but hang at 99% forever on Nook OS loading). If there's no others, maybe I'll give his another try since I had some luck getting CWM to boot with the above trick.
baytee said:
...
This is where it got weird. Screens would advance on their own, be shifted halfway off the screen, had a long delay or else wouldn't respond to my clicks, would power off (and wouldn't power on until MANY presses of the power button) or reboot on it's own during the setup. I finally got thru setup and then after booting to Android, it would still be very sluggish, and still powering off on it's own and being difficult to turn on. And it continued to be unreliable to boot to Android, sometimes booting to Nook OS still (even though some in forums say once they got it to boot to Android it would forever after.)
Click to expand...
Click to collapse
What brand and class of SD card are you using to run CM?
...
even though with his it wouldn't boot to CWM but hang at 99% forever on Nook OS loading
...
Click to expand...
Click to collapse
FWIW, every time that I have had the problem of stock ROM boot-up stuck at 99% it was always because the stock ROM got corrupted due to some unexpected errors in the creation/update of the SD-based CM ROM image, and the only way I was able to recover was to restore stock ROM from backup copy.
I have a PNY 16gb class4 (C16G china 1308PW3599P)
The problem of it hanging at 99% only happened with Succulents, not Bokbokans. As far as the Nook OS being corrupt , I have doubts of that since without the SDcard it ALWAYS boots fine to the nook OS.
baytee said:
I have a PNY 16gb class4 (C16G china 1308PW3599P)
The problem of it hanging at 99% only happened with Succulents, not Bokbokans. As far as the Nook OS being corrupt , I have doubts of that since without the SDcard it ALWAYS boots fine to the nook OS.
Click to expand...
Click to collapse
The problem of stock booting to 99% and hanging with an SD inserted has to do with the properties of the SD, not corruption of stock. Stock will always hang if the SD has more than 3 partitions. Most of Bokbokan's SDs are set up to only have 3 just for that reason. I don't know how many the succulent SD has, I would bet more than 3.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
...
Stock will always hang if the SD has more than 3 partitions. Most of Bokbokan's SDs are set up to only have 3 just for that reason. I don't know how many the succulent SD has, I would bet more than 3.
Click to expand...
Click to collapse
Succulent's CM SD image for the HD+ only has 3 partitions.
I WAS creating a 4th partition & was unaware it was an issue so thanks. I was doing customized partition (not using their premade sd image). But my whole goal is booting to sdcard, not to nook os.....and the 99% Id assumed was after it failed to boot to sdcard & instead had gone on to boot nook os. But Just in case it helps me boot CM11 on sdcard, I'll try it with 3. Thanks for that tip.
actually I WAS creating a 4th partition & was unaware it was an issue so thanks. I was doing customized partitions (not using their premade sd image). But my whole goal is booting to sdcard, not to nook os.....and the 99% Id assumed was after it failed to boot to sdcard & instead had gone on to boot nook os. But just in case it helps me boot CM11 on sdcard, I'll try it with 3. Thanks for that tip
baytee said:
actually I WAS creating a 4th partition & was unaware it was an issue so thanks.
Click to expand...
Click to collapse
FWIW, I took succulent's pre-made SD image for CM11 (https://goo.im/devs/succulent/ovation/cyanogenmod/image/cm_ovation_11.0_24DEC2013_HD_SDC_IMG.7z), burned it to a (Sandisk class 4) 8GB SD card. The image has 3 partitions which succulent had sized to fit a 2GB SD card; I added a 4th partition (type: FAT32, name: /media) to fill the leftover space of my 8GB card (and reset the boot (1st) partition's type/flag to ensure that it's still bootable). The resulted CM11 card with the extra 4th partition booted up just fine on my HD+.
So, having an extra 4th partition (or, in general, more than 3 partitions) does not prevent a SD-based CM image for the HD+ from booting successfully -- just as one by virtue of logics would have expected.
digixmax said:
FWIW, I took succulent's pre-made SD image for CM11 (https://goo.im/devs/succulent/ovation/cyanogenmod/image/cm_ovation_11.0_24DEC2013_HD_SDC_IMG.7z), burned it to a (Sandisk class 4) 8GB SD card. The image has 3 partitions which succulent had sized to fit a 2GB SD card; I added a 4th partition (type: FAT32, name: /media) to fill the leftover space of my 8GB card (and reset the boot (1st) partition's type/flag to ensure that it's still bootable). The resulted CM11 card with the extra 4th partition booted up just fine on my HD+.
So, having an extra 4th partition (or, in general, more than 3 partitions) does not prevent a SD-based CM image for the HD+ from booting successfully -- just as one by virtue of logics would have expected.
Click to expand...
Click to collapse
No it does not prevent it from booting to the SD, but it does prevent stock from booting successfully if the SD is inserted in the slot. It will hang at 99%.
Sent from my BN NookHD+ using XDA Premium HD app
Verygreen's CM 11 SD build of 11/29/2014 for the HD+ works very well for me. First boot does take awhile so don't give up too fast.
Sent from my BN NookHD+ using Tapatalk