Related
This issue was resolved by Meghd00t's new REPART.IMG file. See this post on that thread: http://forum.xda-developers.com/showpost.php?p=26060323&postcount=151cool:
I have the 8gb model Nook Tablet and (mistakenly) tried to flash CWM & CM7a to the EMMC of my tablet. At that time, there were no warnings about how the internal flash version would brick the NT8.
Now, my tablet will not boot to ANYTHING on the internal memory. I do NOT get the stock "reset" warnings - or even a flash of light. No matter how I try to boot it (with or without cable, with or without the Nook button) or how long I hold the buttons down, it still remains with a BLACK SCREEN.
However, the SDCard will boot properly.
I followed the instructions on this thread ( http://forum.xda-developers.com/showthread.php?t=1515788) precisely to reset the BootData. I did NOT receive any errors. However, it still will not boot internally.
I then tried sigmabeta's process to flash CM9 (http://forum.xda-developers.com/showthread.php?p=25661314) to the internal emmc (which is supposed to work on NT8). The flash process (via SD/CWM) went properly and I did not receive any errors. However, I still cannot get anything to boot (except my SDCards).
If I put my CM7a (bootable) SDCard (http://forum.xda-developers.com/showthread.php?t=1481826) into the NT8, it boots and runs great! Likewise meghd00t's recovery/CWM sdcard boots and runs properly.
I can do ADB & FASTBOOT and I have even done the dd to download my partitions (for backup) and then dd copies from online onto the device's partitions. Still no joy.
However, even after dd'ing a downloaded copy of p5 to the device, ADB still reports my TRUE serial number? It seems that the dd to part5 did not take?
The only other thing that I have found, that seems significant, is the fact that when I am in CWM, I cannot mount the EMMC. I can ADB/shell into the device but that did not allow me to mount the emmc either.
Any ideas how I can get this thing to boot internally? How can I force the device to mount the emmc?
Click to expand...
Click to collapse
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Final "fix"
lavero.burgos said:
If you have tried all the unbrick methods out there with no luck, then throw it to the wall and see it is fixes .
~ Veronica
Click to expand...
Click to collapse
Not sure that I have tried ALL of them, that is why I am still searching. Also, people come up with new ideas that have not previously been published.
Thanks for all YOUR help. Especially the dd to fix bootdata.
Sure wish someone would come up with a solution for this problem. There seems to be quite a few of us who are looking for answers.
Sent from my Nook Tablet using XDA
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Existing solutions
succulent said:
I have been reading for a while and I didn’t want to the answer because the answers are already in the Dev. area. I rather have people do some research and learn to solve their own problem rather than listen to someone else that might misled to do something even worse.
NT already has a recovery in place; factory restores (eight failed boot method). Most people do not know this and try something in an environment that they are not familiar with, Ubuntu. If you are using Windows, then you can resolve it in Windows. You do not need to repartition, format, or delete partitions. I have learned that many people like to format things apparently.
The most common problem seems to be; my NT does not turn on or my nook only boot with sdcard. It is not technically true; your NT actually turns on. The backlight just doesn’t turn on because you format/replace the x-loader/bootloader. X-loader loads the bootloader. You know the bootloader work if you see the “n” logo screen. If your NT restart after the "n" logo screen, it mean bad recovery.img/boot.img.
How did this happen? You flash the wrong MLO file to your x-loader, you used an old CWM (experimental one) and formatted your sdcard or you like to format things.
How do I resolve this? First thing is to make a proper CWM sdcard, one with proper partition table. You can compile your own CWM recovery when you compile CM7. Second, flash stock 1.4.2 rom, which contain the latest x-loader, bootloader, boot, and recovery files that works on both 8GB/16GB NT. This will restore your NT to stock android gingerbread.
If you happen to format the rom partition, you need to restore it with a backup and perform the eight failed boot method. This will restore your proper rom partition data along with the stock android. It is all in my thread in the Dev. area.
If you happen to screw up your partition table, obviously this will not help you until you fix your partition table.
Click to expand...
Click to collapse
Thanks for the info. I do appreciate it and I will be trying some of your suggestions later today when I get home.
One problem (that seems to be easing up a bit) is the fact that few posters distinguish WHICH version of the NT that they are working with. The NT16 "solutions" became the NT8 "problems." It would be great if everyone posted WHICH version they have.
The other issue is (as you stated) when you follow a guide to fix an issue, it CAN mess up your device even worse that it was. Then, you have TWO issues to deal with - rather than just one as before. I am afraid that is where I am now.
One question: You mention "compiling" CWM. Are you referring to the technical term of compiling code into an executible? Or, are you simply referring to the process of putting a working image onto an SDCard? I can do the latter without issue but I have never compiled code.
I do use Ubuntu Linux so many of the Windows driver issues are moot for me. However, I do have a dual boot with XP in on the other side - just in case I need to do some Windows-only stuff.
I really appreciate the help. I am no novice but I am not a developer either. I can usually search, read, try, and work out the problems that I (and other less technical users) experience. That is what my website is all about - translating the really "tech" jargon into everyday language for non-techies to follow. But this one has stumped me (and at least a few others) for the past couple of months.
succulent said:
I have learned that many people like to format things apparently.
Click to expand...
Click to collapse
Sent from my NookTablet using Tapatalk
I've noticed this as well. People really need to do more reading before randomly selecting/flashing things.
So I have tried everything getting this thing (Nook 16GB Tablet) to work (boot off SD [class 4 8gb Sandisk] card into CM10.X+)
I have followed the directions to a T (several several times) and everytime I turn on my Nook it goes to the cyanoboot screen and goes to (SDC) LOADING BOOT and is stuck there, or if I hold the N before it get to it it will allow me to choose my boot option (I've tried the SDC recovery to use automatic partition zip provided on iamafanof's wordpress site; please note I have tried it with manually partitioning, and just leaving image as is and same results).
I have did a complete factory restore via the repart.img method, tried different SDC image versions, bought a new SD card just to make sure it wasn't the card.
The weird thing is I can create a CM7 SD card and it loads fine (so I don't think its the SD Card).
I am at witts end with this; I work in technology as a career (on a bit diff side) and this thing is driving me nuts not working.
I have tried booting tethered as well; the only thing that may be different is that I bought this used and it has an aftermarked (Griffin) charger.
What really sucks was I was originally thought I bought a NC b/c I heard it was easier to create a bootable SDC and found out I had a microphone
Can someone recommend a next approach? The only other thing I could think of was to try the alt boot files on "iamafanof" wordpress site but the links are dead.
I don't care if its 10.1 or 10; just really interested in Android 4.0 period.
Also this Nook was 1.4.3 when I first tried to boot from SD; since then I went through process above and now is 1.4.0 factory reset.
I have looked through the forums EVERYWHERE and I decided to join here to get help - thanks in advance!
I hdon't know why this happens, but just to be clear, have you tried Iamafanof's ready-made CM10 bootbale sd? http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
If you decide to install CM10 internally this image can be used as a bootable CWM card even if you don't want to run CM10 from it.
And FWIW, why does it suck that you got a Tablet instead of a NC? The Tablet is so much better, and certainly not any harder to mod.
asawi said:
I hdon't know why this happens, but just to be clear, have you tried Iamafanof's ready-made CM10 bootbale sd? Removed link per 10 post policy
If you decide to install CM10 internally this image can be used as a bootable CWM card even if you don't want to run CM10 from it.
And FWIW, why does it suck that you got a Tablet instead of a NC? The Tablet is so much better, and certainly not any harder to mod.
Click to expand...
Click to collapse
Well guess it doesn't suck considering I payed 50 for a better tablet, I am just annoyed with it at this point. Yes I did, I formatted a SDC and burned that image to it after unzipping ( cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar ) as well as other versions and they don't work even if I don't mess with partition tables. My only guess is that the boot files in the boot 1st partition of the image aren't compatible with my device which could be explained since I'm sure mine is a late model ( but why does CW7 work ? )
At this point I wonder if its possible to use the CW7 SDC and just copy gapps and the 10.1 Rom over. I'm extremely new at this so hopefully that isn't a stupid idea.
I do want to stay away from rooting internal for various reasons.
Any ideas ?
xXErebuS said:
So I have tried everything getting this thing (Nook 16GB Tablet) to work (boot off SD [class 4 8gb Sandisk] card into CM10.X+)
I have followed the directions to a T (several several times) and everytime I turn on my Nook it goes to the cyanoboot screen and goes to (SDC) LOADING BOOT and is stuck there,
...
I have looked through the forums EVERYWHERE and I decided to join here to get help - thanks in advance!
Click to expand...
Click to collapse
Which direction and which ROM zip file did you try to use?
xXErebuS said:
...
Yes I did, I formatted a SDC and burned that image to it after unzipping ( cm-10-20121231-NOOKTABLET-acclaim-HD-SDC-img.rar ) as well as other versions and they don't work even if I don't mess with partition tables. My only guess is that the boot files in the boot 1st partition of the image aren't compatible with my device which could be explained since I'm sure mine is a late model ( but why does CW7 work ? )
At this point I wonder if its possible to use the CW7 SDC and just copy gapps and the 10.1 Rom over. I'm extremely new at this so hopefully that isn't a stupid idea.
I do want to stay away from rooting internal for various reasons.
Any ideas ?
Click to expand...
Click to collapse
I'd suggest you try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip at http://iamafanof.wordpress.com/2013/02/18/cm10-1-jellybean-android-4-2-2-for-nook-tablet-0218/ (under heading "Flash this if your NT doesn’t boot newer kernel" in SDC section).
digixmax said:
I'd suggest you try flashing flash_kernel_acclaim_30MAR2013_HD_SDC.zip at [(under heading "Flash this if your NT doesn’t boot newer kernel" in SDC section).
Click to expand...
Click to collapse
That's for if your doing the internal root though right ? I don't want to do that. I listed above one of the exact zip files I tried, I've tried several of them ( the pre done SDC images). And none of them will boot past cynogenmod .
xXErebuS said:
That's for if your doing the internal root though right ? I don't want to do that. I listed above one of the exact zip files I tried, I've tried several of them ( the pre done SDC images). And none of them will boot past cynogenmod .
Click to expand...
Click to collapse
The version of the kernel fix that I referenced is for SD-based ROM (the file name contains the "SDC" string).
Sent from my Barnes & Noble Nook HD+ using XDA Premium HD app
digixmax said:
The version of the kernel fix that I referenced is for SD-based ROM (the file name contains the "SDC" string).
Sent from my Barnes & Noble Nook HD+ using XDA Premium HD app
Click to expand...
Click to collapse
Ok I now see it (flash_kernel_acclaim_30MAR2013_HD_SDC.zip) but how do I flash it if I can't boot into SDC Recovery from the Cynogenmod screen? Does it modify internal ROM - can I put it on a blank SD Card or on the CM7 and go into recovery?
Sorry if this is a noob question.
Well I've now tried it manually > forum.xda-developers.com/showthread.php?t=2098419
and I get stuck at the same place (booting into SDC Recovery in steps).
I have ruled out it being the SD card (unless I some how managed to get two bad ones that still boot into CM7).
xXErebuS said:
Well I've now tried it manually > forum.xda-developers.com/showthread.php?t=2098419
and I get stuck at the same place (booting into SDC Recovery in steps).
I have ruled out it being the SD card (unless I some how managed to get two bad ones that still boot into CM7).
Click to expand...
Click to collapse
Did you extract and copy to SD the two files boot.img and recovery.img as prescribed in step #6 of http://forum.xda-developers.com/showpost.php?p=36685310&postcount=1?
digixmax said:
Did you extract and copy to SD the two files boot.img and recovery.img as prescribed in step #6 of ]
Click to expand...
Click to collapse
Yes I did. I have another larger flash drive coming in the mail, I do not think its the flash drive though. No one else has ever had this issue? CM7 works fine, I may try to boot into CM9 later this weekend.
Just to clarify I have done manual method and burned image, they boot to the cynogenmod boot menu and if I pick SDC anything it just hangs there.
I almost want to say I don't think it's cynogenmod bc I can choose internal boot from it and it boots into nook fine
xXErebuS said:
I almost want to say I don't think it's cynogenmod bc I can choose internal boot from it and it boots into nook fine
Click to expand...
Click to collapse
This so odd! It seams like there is something wrong woth the boot section on your sd, but I don't see how that could be the problem if indeed you have tried ready-made images that we know work for "everyone else"!
Clutching at straws here, but have you tried Iamafanof's readymade CM10.1 image as well? http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (I'm guessing you have, but like I said, clutching at straws...)
xXErebuS said:
Yes I did. I have another larger flash drive coming in the mail, I do not think its the flash drive though. No one else has ever had this issue? CM7 works fine, I may try to boot into CM9 later this weekend.
Just to clarify I have done manual method and burned image, they boot to the cynogenmod boot menu and if I pick SDC anything it just hangs there.
I almost want to say I don't think it's cynogenmod bc I can choose internal boot from it and it boots into nook fine
Click to expand...
Click to collapse
If you pick SDC Recovery from Cyanoboot menu it should say "loading SDC recovery" but it will take some time (up to between 1-2 min) before the CWM menu appears. Same thing with SDC Boot: it will take a bit of time before you see its boot animation. But neither should not take more than a couple of minutes to appear.
Also, for the manual method I'd suggest checking to make sure that boot.img and recovery.img on the SDcard /boot partition are not corrupted in the process of copying them to SDcard.
asawi said:
This so odd! It seams like there is something wrong woth the boot section on your sd, but I don't see how that could be the problem if indeed you have tried ready-made images that we know work for "everyone else"!
Clutching at straws here, but have you tried Iamafanof's readymade CM10.1 image as well? http://iamafanof.wordpress.com/2013...-1-jellybean-sdcard-img-for-nook-tablet-0110/ (I'm guessing you have, but like I said, clutching at straws...)
Click to expand...
Click to collapse
I am about 95% sure I have; I will try it again just to make sure; I tried several different versions of the image for 10.0 and 10.1 as well as the manual methods for both thinking it may be the build.
I will try to boot CM9.X and see if it works since 7 works. Really strange that no one else seems to have the issue.
In addition, I have left it well over 1-2 minutes at the cynogenmod screen and it never boots into CWM or the image (depending on boot option I pick).
So quick update.
I tried building a CM9 card and I got Cynogenmod to boot into SDC recovery (maybe I can use the same boot.img file?) However when trying to boot into SDC (after installing gapps.zip / ROM.zip) it reboots and boots into the normal INT nook.
Granite I may have messed something up with the process since I only did it once; but atleast I got past Cynogenmod screen.
Followed these directions and used these files:
http://iamafanof.wordpress.com/2012/11/11/how-to-guide-bootable-cm7cm9cm10-sdcard-for-nook-tablet/
ive had similar issues , one thing that hit me was that my downloads were incomplete . when you download the images of cm 10.X verify the file size vs the download page stated size and make sure that your downloads are complete. also i would try re downloading them all over again thats what i had to do , and follow the instructions to the dot but give us a link so we can see which ones your reading too , ive learned alot in the past three weeks of non stop hacking and modding on my tablet, its bricked itself three times so far and ive been forced to un brick it ,
the reason why i said that is , sometimes i get so worked up and over whelmed, take a five minuet break and go to the fridge and grab a drink and dont think about this for five minuets , clear your head and calm down then look back at the work you have already completed and examine it step by step fresh , you prob just missed one little detail ,
"it reboots and boots into the normal INT nook. "
if upon reboot it goes to nook , hold power button until its off , then hit power to turn it on , once N shows up hit the N button on the tablet if you have CWM installed to internal , this is like a short cut key to force it to boot to sdc , OR with tablet completely powered off plug in charger cable , it should turn tablet on ,and with cable inserted it should boot to sd card first , if it takes a while then goes to nook OS your sd card is incorrect ,
checked your link this isnt the one i used , i used this link
http://forum.xda-developers.com/showthread.php?t=2056626 yes its for 10.0 but once its installed internally you can connect to wifi and update to 10.1.2 4.2.2 in software on device , just remember to get the right Gapps before hand
forwarning , dont play with the touch screen firmware editor without reading , if you do pm me ill tell you how i crash coursed through that and how to fix it once you break that too lols 10 point is nice though
SD card version works nice too
http://forum.xda-developers.com/showthread.php?t=2098419
I POSTED EARLIER BUT IT NEVER SHOWED UP SO IM REPOSTING. sry for caps.
rooted my nook color and everything was fine. then i tried to root my nook tablet. searched all over the net for comprehensive instructions to do so and i found this
The first thing you need to do is extract the contents of file #1 and write the extracted img file to a Micro SD. If you are using Microsoft Windows then click the file named Win32DiskImager.exe, select the NT16or8gbV47SDimagefile.img, select your drive letter for your SD card.
If you are using Linux, then open up the terminal and CD into the directory where NT16or8gbV47SDimagefile.img is located. Once in the correct directory issue this command to write the .img to the Micro SD:
sudo dd if=NT16or8gbV47SDimagefile.img of=/dev/sdX
You must replace the X in sdX with the appropriate letter for your SD slot. There are many ways to get the correct letter but I use the program Gparted.
Ok, so now you have an SD card that will root your Nook Tablet. Let's boot into Recovey. Turn off your Nook if it is on, and connect the USB wire to your computer. Your Nook will now turn on and enter into ClockwordMod Recovery. Using the Volume Keys to move up and down and the N key to select, click on Install zip from SD. You will now see a zip file called Root_8gb-or-16gb-NTV4_7.zip. Highlight that file and press the N.
If all goes well, the operation will complete. You are now rooted. Press the Power button to go back to main Recovery menus and select Reboot and press the N key. Your Nook will appear normal. It is not. Press the N key and you will see a new option for Home screen. Clicking the new Home icon will take you to an Android looking desktop. Yay! We are not done yet.
Now, install ES File Explorer from the Play Store. Open the app and browse your Micro SD card. Look for a folder called Apps. In this folder you will see a file named Nook Recovery Flasher.apk. Click this file to install it. Once installed, click on Flash CWM Recovery. Now you do not need the SD card you made earlier to boot into Recovery. It is now part of the system.
Remove the SD card and connect it your computer and format it so that it is empty.
Copy the files #2, #3, and #4 that you downloaded from above to the SD card and insert it back into the Nook Tablet.
Remember how to boot your Nook into Recovery mode? Do it.
Select Install zip from SD again and install ONLY CWM_v6.2.7_emmc.zip. This will upgrade your recovery. Without upgrading, you will not be able to flash CyanogenMod. Once the operation is complete, use the power button go back to reboot the Nook. Boot it to Recovery one more time.
Now you can select the latest CyanogenMod file you downloaded to install it. After that, select the latest Gapps you downloaded. Reboot the Nook and you are good to go!!!
. i folowed all the instructions to the dot. but when i got the this step, "Remember how to boot your Nook into Recovery mode? Do it." and i did it. but when i rebooted it immediately tried to boot into recovery but got stuck on the cardboard box screen and it flickered none stop and would not proceed to recovery (CWM) menu. I tried everything i could think of and i found that if i reformatted my sd card with the CWM sd root img and put sd card into NT and boot up it successfully brings up CWM. from this i tried both normal cache wipe and advanced menu cache wipe and also tried wipe to factory settings and wipe battery stats, rebooted and it still gets stuck on the flickering cardboard box screen..........anyone have any ideas? i cant seem to boot it up at all past this screen. maybe i shud format system through sd-card cwm? but then i would have no OS, so how would i proceed with this. is it totally broke or wut? god i hope not:crying::crying::crying::crying::crying::crying:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
wut ive got so far
digixmax said:
If you aim to run rooted stock ROM, see http://forum.xda-developers.com/showpost.php?p=31271965&postcount=240.
If you aim to install custom ROM such as CM10.x internally on emmc, see http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
See also http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for more background info on rooting & flashing custom ROMs.
Click to expand...
Click to collapse
well i think wut u gave me is exactly wut i need. followed the custom rom tutorial and it worked fine to the point to where i first get to cyanoboot menu where i would have proceded to install cm10 and gapps. but i accidentally put the wrong cwm on the sd card and it said bad boot. (note it also said it disabled charging) so i go the right cwm boot img for it. but the fact that it disabled my charger i cannot get back into the cyanboot menu. anyone kno how i can reactivate charging? if not then im completely screwed because once it dies i wont be able to charge it again and it will be flippin useless. even worse than before.........sigh fml someone shoot me in the dome
The "charging disabled" message on the Cyanoboot screen does not mean what you think it means (i.e., charging is turned off on for good until you somehow turn it on again). If you're stuck on that boot screen, just hold down power button for 20-30 sec to turn it off and start over with the SD card with the right CWM.
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
YAY!
Temetka said:
Yeah, I always wondered about why it says charging disabled when you are in the cyanoboot loader.
That being said, you should be just fine. I recently had to restore, then reflash, then restore my 16GB Nook Tablet. I saw that message in the upper left hand corner and all I really thought was, huh I wander why they do that.
As the poster above me said, just burn the correct version of CWM (you need v6 or higher), load your CM10 and Gapps .ZIP files onto the card.
When you see the Cyanoboot loader hold down the "n" button for the menu.
Select internal recovery.
Select install file from zip.
Select your CM10 .ZIP file.
Wait a few minutes while it does it's thing.
Repeat the same procedure from the install menu for the gapps.zip file.
Once it is done, you can safely remove the SD card. Sometimes this will make the Nook reboot. But that's fine. You want it to reboot anyway. It should boot into CM10. Sometimes the first boot can take a while as it set's itself up. Once it comes up you should be good to go.
Post back if you have any questions.
A piece of advice. If you ever for any reason may need to restore the Stock OS/ROM ***DO NOT*** run any 5point or 10point multitouch installer. If you do and you forget to reflash the multitouch firmware, you will be unable to use the touch screen with the stock OS. Then you will have to reload CM10, reflash the screen firmware, then reload the stock OS. I was running CM10 for months and totally forgot that I did the 10point flash. Screwed me over for a bit. Learn from my pain, don't do that. 99% of all Android users I know (and I know a lot, I work in IT) use 1 finger most of the time and sometimes 2 for pinch to zoom. So in my opinion, you don't gain very much functionality from it and if you forget to reflash the 2 point touch firmware, you could end up with a headache. Just thought i'd throw that out there.
Click to expand...
Click to collapse
YAY! i figured out how to get past the bad boot part. just be sure to be vigilant and press "n" asap when the screen boots up in cyanoboot......and i mean like THE second it pops up. that solved all my problems.......
but i dont understand the piece of advice part with the 5 point/ 10 point touch installer deal. ill do alil research on it to see wut it is and wut i got to do. if you care to send a link explaining it that would be super flippin awesome. and btw thx sooooooooooooooooo much. this forum has been the most helpful place. quick responses and accurate information. everyone i talk to rocks. i appreciate it so much. :victory:
The 5point and 10point touch is just that.
So you know how your screen responds to your touch input? And let's say you use to fingers to zoom in on a picture. That would be an example of 2 touch. Expand from there for more finger interaction.
Here's an XDA thread on the topic:
http://forum.xda-developers.com/showthread.php?t=769932
and nice Wikipedia article on how multi-touch works:
http://en.wikipedia.org/wiki/Multi-touch
Glad you are up and running.
Hi all!
My Lenovo S6000L entered on a bootloop more than one week ago, apparently with no cause (no modifications made). The first thing I tried was entering recovery mode and wipe data and cache. Both were apparently successful. Then I reboot again and it continues with the bootloop (done this about 99 times).
Since then i have been reading as much as I could about what to do, but unsuccessfully. I decided to wipe dalvik-cache and see what happens, but the only way it came to my mind was using a update.zip file on the SD-card (because the SD-card is the only one place I can access). Here the problems became more annoying: haven't been able to run till the end any of the update.zip files I downloaded or made according with the tutorials I found. The message is always:
-- Install /sdcard ...
Installation aborted.
I have tried removing everything from the updater-script excepting the ui_print('Whatever') commands, hoping to see something else on my screen (and being afraid of errors being caused by eMMC access error), but message is the same.
Things I have tried:
Signed and unsigned zips
Unix and Windows line breaks on the script file (I'm using Sublime Text)
Writing all the commands in one line (anyways leaving one empty line at the end of the file)
No changes on the output of the screen. One of the downloaded zip files I have tried is a CWM ZIP, hoping to enter in a recovery mode that could let me delete de dalvik-cache (even if not sure yet about how much that could help).
In bootloop is quite difficult to use dba. I haven't been able to access the tablet using the computer yet. It' also quite challenging to get a stock ROM for this model.
Any help? I feel quite desperate.
Thanks for your time.
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
BornReady_ said:
Hey! I am trying to get Cyanogenmod 12.1 on my stock Nook Tablet. I no longer use the Nook Tablet as often and would like to give it a new life by making it an Android. After reading a ton of articles and forums, I have tried a ton of them, but none of them seem to work successfully. One of them I tried was, Install CM for acclaim on the wiki.cyanogenmod.org website , the process went successfully until I rebooted and it continued to boot me to the regular Nook setup. I think it is because the Clockworkmod Recovery is outdated. I also see that Cyanogenmod's latest recovery is also available, but how do I put it on my SD card successfully. Please provide a step to step guide for me. Thank you!
Click to expand...
Click to collapse
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
nmyshkin said:
I just did this about a week ago (finally) and there are no better instructions for getting started than those provided by digixmax here. Just ignore the statements about CM 11 and forge ahead. Later in that thread there are a variety of recommendations for file substitutions in the method if you are aiming for CM 12 instead of 11. I followed the ones here. These also work.
My own discovery was that you should ignore the TWRP error messages about being unable to mount '/bootdata'. I finally came across that somewhere and it proved to be true for me.
Take it slow. Gather together all the files you will need first. Then prep the SD card (don't forget to set the flag). Then copy the files over in the order specified. It matters. Then go for it! (don't neglect to backup the stock system before wiping things--you may be glad you did).
My start-up with CM 12.1 was really rough and I thought I might abandon it but after a few days and quite a number of reboots things settled down. Maybe that has something to do with coming from CM 10.2.1, maybe not. Anyway, the system is no worse than CM 10.2.1 and I don't have trouble with cold or warm boots hanging like I used to with CM 10.2.1.
My pet peeves are listed here and/or here but may be idiosynchratic to my device or particular flash.
Click to expand...
Click to collapse
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
BornReady_ said:
I literally just finished sending a message to digixmax when you posted this. I remember seeing you in the other forum, trying to get CM12.1 to install. I did all this instructions over and over for hours, but I keep getting stuck at the CyanoBoot section. I get the Boot Menu, but then the SDC Recovery option isn't available, I see it, but it isn't clickable.
Click to expand...
Click to collapse
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
nmyshkin said:
OK, so as soon as the cyanoboot screen appears you hold down the N button, right?
Also, did you boot with the power cable connected?
Click to expand...
Click to collapse
Yes, I booted with the power cable connected, I tried on being connected to the laptop and power wall as well. I also held down the N button, which is why I got to the Boot Menu.
Bear with me
Are you sure you got the SD card version of TWRP?
Yes, 100% sure.
BornReady_ said:
Yes, 100% sure.
Click to expand...
Click to collapse
Well that was interesting! We're "live" apparently
I want to help but I'm not digixmax... I'll bet he has an idea. Wait for him to get back to you while I rummage around.
Lol, thanks for the help anyways though. I will have to wait for digixmax.
Wow, everytime you mention digixmax, he replies. He just privated messaged me in return.
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
I'm sorry, I should have been more precise. I don't know if it will help, but this is the TWRP recovery image I used successfully when I tried this process. That's v. 2.8.6.0
digixmax said:
If you can get to the CyanoBoot menu but its menu entry for "SDC recovery" is greyed out then it's because CyanoBoot (flashing_boot.img) cannot find a recovery.img file on your bootable SDcard.
Which version of SD-based recovery did you download and use?
You might want to wait for and check against the answer to my inquiry post at http://forum.xda-developers.com/showpost.php?p=65016892&postcount=41 (I no longer have a NT and as such cannot vouch for any specific recent recovery versions).
Click to expand...
Click to collapse
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
nmyshkin said:
Don't give up. If you're using a Windows machine to prepare the card then whether the .IMG is displayed or not depends on your settings. It does not show on mine but a look at the file properties shows it is an .IMG file.
So that's the wrong tree. SDCards have been known to be problematic so if you have another around you might want to give it a try. You also might do a slow (complete) format on it before preparing it from scratch.
The other thing, of course, is the integrity of the individual files. Checking the MD5 values is a pain but sometimes reveals a bad download.
Click to expand...
Click to collapse
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
BornReady_ said:
I have tried everything. It doesn't seem to work. I'm also sure there aren't issues with downloading because I have redownloaded the files over 7 times. Is there a way I can download the folder of files that you used to install cyanogenmod?
Click to expand...
Click to collapse
I've already shut down my computer for the night. I'll have a look at the size that an image of the card would be. Maybe that's the easiest way if there's room in my dropbox. If you've read through the CM11/12 thread you know I ran into problems and if you were to look at the CM10 thread you'd find me floundering around there also, so I know how frustrating it can be. And then suddenly it just works.
I'll let you know tomorrow.
BornReady_ said:
I have seen everyone else's folders and they seem to include "flashing_boot.img" However, the file I downloaded from your page only has "flashing_boot" When I try to rename the file, the Nook Tablet won't even turn on anymore at all. Matter of fact, I can't even get to the Boot Menu now, it keeps having that red line that states, "booti: bad boot image magic (in memory)" I'm losing hope...
Click to expand...
Click to collapse
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
digixmax said:
As @nmyshkin pointed out, it's most likely because your Windows Explorer is configured not to display the file-name extension, so when you try to rename "flashing_boot" to "flashing_boot.img" you in effect end up with a file with name "flashing_boot.img.img".
This is likely also the root cause of your original problem: if you now just rename the TWRP recovery file you had downloaded (which already has the hidden .img extension) to "recovery" (and not "recovery.img" lest you end up with a file named "recovery.img.img") then CyanoBoot will see the recovery file.
For avoidance of doubt, just set your Windows Explorer to display file-name extension.
Click to expand...
Click to collapse
You are totally correct. I enabled Windows Explorer to display file-name extension and the TWRP recovery file turned out as "recovery.img.img" I am going to try it out now and reply with if it works or not.
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
BornReady_ said:
Alright, I have been trying and following the instructions clearly, but it keeps giving me the red line stating, "booti: bad boot image magic (in memory)" now. I have gotten to the Boot Menu before, but now it won't even let me get there. What does this message mean?
Click to expand...
Click to collapse
Is flashing_boot file on your SD card correctly named "flashing_boot.img", and not "flashing_boot.img.img"?