Related
I am now making post that there really shouldn't be any need for, because all that's in here is already covered elsewhere. 100% Apparently not easy enough to find for newcomers, so I'm making an attempt to help info collection.
NOTHING here is my work! All I’ve done is trying to make easy to follow instructions to other people’s hard work. Those people deserve your thanks, not me!
I’m a newbie myself and that’s why I can say that this really is very easy! If I can do it without problems, so can you! I try not to chat away too much in the instructions. Make regular searches, here or Google for more info. I found it, so surely you can too! Any questions? Well, being a noob myself I probably can't answer. Google is a very good friend of mine though...
Please do not ask questions through pm. It's better if people that know more than I do get a chance to answer them in the thread instead!
You need to know how to burn an sd image. Separate instructions to that after the other instructions if you don’t.
Step 1: Establish what it is you want to do! Choose A, B or C
A: You do not want to touch the internals of your NT but want to try CM10 anyway
B: You want to stay in the BN environment but would like to be able to install apps from elsewhere (for example Google Play Store)
C: You want to get rid of BN and install CM10 instead.
A: Run CM10 from sd card – no root required
This should work on 8GB Tablet as well as 16GB
When you boot into the card you’re running Android ICS. Remove the card and you’ll boot to internal BN operating system. (Or keep the card in, boot to Cyanoboot Menu and choose “internal boot”)
Ready-made card image download links to be found here: http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
It’s a large download (around 500 MB), but it is a ready-made sd card image. As it says in the instructions there, you’ll more than likely want to expand the user partition to take full advantage of the card, but that’s covered in his instructions.
There are other, more manual ways to make these cards as well. Also covered both in that blog and here at XDA! Go search!
B: Root the Tablet
This works on both 8GB and 16 GB Tablet.
“Rooting” is like unlocking your device, giving you access and control over it. You’re still running BN operating system though. Several excellent root guides here on XDA.
For example: http://forum.xda-developers.com/showthread.php?t=1488035
Or http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
The first one (Brian’s) require a 2 GB card the other one (Albert’s) just needs a very small card. (I think 128 MB would do, but I don’t have any that small to try)
Both give good instructions in their topics.
Both install gApps.
If you want to block OTA updates from BN, go to Play Store and find NT Hidden Settings. Even if it got installed with the root it’s probably not latest version and doesn’t have the Block OTA function.
C: Installing CM10 internally
***8GB owners must make sure to use ROM that works with their device!***
Since I’m a noob I look for easy way, and this is very easy and needs very little know-how!
***Warning! CWM is a very powerful tool. Do not "wander around" and "experiment" with stuff without doing proper research! Seriously! DON'T!***
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/showthread.php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
3. Boot into the sd-card and it should take you to CWM 5.x.x. environment.
I guess a backup of you current system would be a good thing (even though I admit to skipping that myself). To backup you'll probably need another card if you're using "The Albert Card" now, because I doubt it's enough room on that.
You navigate with the volume rocker, go back to previous menu with “power” and confirm choices with “n”
Choose “install zip from card” – “choose zip from card” – your CWM zip
See warning above!
4. Power off and prepare your sd card for ROM flashing. (If you’re working with just one card you will need to format it with SD Format or similar to get it back to full capacity.) Put your CM10 ROM zip and the appropriate gApps zip on the card.( It doesn’t matter if there’s other stuff on the card, so you don’t have to format it because of that!). I will not link to a specific ROM. Make your own choice but be sure it works for your model and also make sure you use the right gApps!
5. Reboot into Cyanoboot. This took me a couple of attempts to get right.
From powered down device, press power and right after that press and hold "n", You should boot into Cyanoboot and get the boot menu. Choose "Internal recovery" and you should get into new CWM
6. I don’t know how much clearing is needed, but I prefer to clear pretty much everything to make sure of a clean install. Cache and Dalvik I always clear.
***DO NOT format anything unless you knwo what you're doing! *** (See Satan's posts below)
7. Flash ROM and gApps same way as you flashed the CWM 6.x.x (install zip from card – choose zip from card) reboot and go!
How to burn an sd-image:
I use Win32Diskimager. Download link in Albert’s root topic (and numerous other places!!)
Unzip into a folder.
(I also copy my various img files to that folder to have them easily available)
No need to install, just run by doubleclicking the EXE in the folder.
Make sure the device letter really is your sd card.
Click on the blue folder and navigate to your img file, choose it and “write”.
It will take some time if it’s a large img, but that’s what the progress bar is there for, isn’t it?!
Nice work ,
But you should add 'do not format any partition ' warning. Android users coming from other devices might do this by default during flashing rom.
Almost every one with bricked tablets has tried formatting partitions.
Sent from my ST21a
Thanks Satan! I did not know that! Will do!
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
satan89 said:
but looks like some people missed it.
Click to expand...
Click to collapse
It looks like a lot of people miss a lot of things...
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
+1000
Do not format especially the rom partition and, most critically, the factory partition which respectively contain a set of small files with device-specific unique data (not only Serial No. but also MAC address, public/private key certificates, etc.) and the backup archive copy of the same data files (/factory/romdata.zip).
Unfortunately, I've seen some "unbricking" tools (including some that are very frequently cited/recommended on these NT forums) reformat/zero-out and flash over these 2 partitions. The end result being, even in the event the "bricked" NT gets "restored to stock", depending on the specific tool used it could be carrying device-specific data of someone else's (e.g., tool developer's) NT.
EXACTLY!
satan89 said:
Good
Veronica had made sticky thread to reduce number of bricked tablets, but looks like some people missed it.
To be more specific,
Do not format rom, boot, bootdata, and factory.
http://forum.xda-developers.com/showthread.php?t=1644862
Click to expand...
Click to collapse
I think this is exactly what happened to my NT. Took me weeks of researching (I don't have a lot of free time) to figure out how to restore my 16GB NT.
Help
Im trying to single boot CM10 from sd card without touching nook os. I am using guide (CM10.0 Jellybean SDCard IMG for Nook Tablet (12/31) FINAL)
I have tried for hours using different methods also and cant even get it to boot to CM, no CM logo at all. I have a BNTV250 NT on 1.4.3. I have tried multiple sd cards, I am using a Sandisk 8gb class 6.
In a nutshell all I should have to do is
-Format the card with SD formatter,
-Extract the (Extract cm10_xxxxxx_sd_hd.img from cm10_xxxxxx_sd_hd.7z/rar)
-Use Winimage to write the image to the SD card, correct??
The Nook still refuses to boot into Cyanogen, just boots up normal every time!
same with every procedure i have tried,
Any pointers????
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
asawi said:
Have you tried putting the sd-catd in the powered down Tablet and then insert the charger cable, connected to the charger?
Many Tablets have difficulties booting into sd other ways,
Click to expand...
Click to collapse
No, I have not, will try now.........ty
---------- Post added at 02:25 PM ---------- Previous post was at 02:23 PM ----------
HOLY ****!!!! I LOVE YYOU!!:laugh::laugh::laugh::laugh::highfive::victory:
That worked, I cant believe it. Why is this not written anywhere??
LOL! :laugh: Glad you got it working!! :good:
Any clue of how to get rid of booting that way? I'm not always with a USB cable witj me.
Enviado desde mi Nexus 4 usando Tapatalk 2
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
asawi said:
I've never had to do it that way myself so I really don't know. You could try pressing the "n" buttons right after the power button and holding it for a few seconds.
Actually not being able to boot into SD card easily is the reason some install internally instead.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Tried doping that with no luck. After 8 or 10 attempts magically boots todo cm. Thanks.
Enviado desde mi Nexus 4 usando Tapatalk 2
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
ThePhantom97 said:
Alright, just got cwm 6.x installed and now ready to install rom, just wanting to verify that I should still "wipe data/factory reset" and "wipe cache partition"? That is different from "formatting" correct? I don't wanna brick this thing without confirmation. Thanks for the awesome guide!
edit: Ignore the wipe question, found it, thank again for the guide, I will let you know how the install goes!
Click to expand...
Click to collapse
Thank you very much for putting this together, it was very helpful!
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
- I tried press Power and N button or 8 times fail reboots but it still boot into recovery
- I tried flash new ROM from sd card, and the status is shown Installing Update.... and then it shown Install from sd card completed!!! There was no any notification more (as usual). And after "completed" by this way, reboot and still went into recovery mode again
- I also tried flash new cwm version 6.0.x, wipe data, format system, data,.... and flash ROM again from sdcard but still didnt work.
- I also tried reset to factory default http://forum.xda-developers.com/showthread.php?t=1663836 but it still boot into CWM again and again.
- and follow many topics on google search but still no luck
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
I want to flash a new ROM, a fresh tablet to make a gift for my dad on father's day, but it is brick :crying::crying::crying:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
DavDoc said:
I think using ROM manager to flash recovery may not work with our device (I may be wrong) but we don't have an official build of CWM.
Regardless.... Do you have adb set up? If so, does it recognize your nt?
Sent with my Dinc4G
Click to expand...
Click to collapse
I have adb set up, but it doesn't recognize my NT , it always boot to recovery mode
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
DavDoc said:
Ok, no big deal yet. Lets try the following.
First you are going to need an extra SD card, one greater than 2G. Go to this thread http://forum.xda-developers.com/showpost.php?p=21895025&postcount=14 and follow the instructions. This will give you the files and show you how to make a CWM bootable SD card (ignore all the steps about rooting your device in this thread for now). Note that this will repartition your SD card, so you will not be able to use is for much else unless you re-repartition it yourself.
To tell if this is successful or not, note the version of CWM you are now booting into, I am guessing it will be 6.0.3.1 (newest version) since you tried getting this from Rom Manager. If it is booting from SD card it should show up as version 5.0.x.x (I don't remember the exact version but it is older).
If you got it to boot from SD card then lets pull an updated version of CWM from this site http://goo.im/devs/succulent/acclaim/recovery The older version of CWM may not work well with CM10.1. try CWM 6.0.2.9, make sure you download the flashable CWM zip and not the image file.
OK now you will need to put this zip file onto your SD card - there should be just enough room left for it, or you could put it onto a 2nd SD card (easier) Note: while in recovery you can take the bootable SD card out of your NT. Go ahead and flash the CWM zip. You should now have a working recovery. At this point try flashing a ROM of your choice.
Good Luck
Click to expand...
Click to collapse
Hello DavDic,
Thank you for your help,
I follow your link and I success to boot from SD card, and CWM version is 5.0.5, then I success install the update.zip too, unfortunately after removing the sd card and reboot, it still boot to CWM version 6.0.2.9 - this is the version that I flash from ROM Manager before my NT is bricked (I flashed wrong device when I choose Nook Color in Rom Manager)
So I try to reboot again from sdcard, cwm version 5.0.5, then flash new CM10.1 ROM, and reboot and still go to CWM 6.0.2.9
and again, I boot from sdcard, cwm version 5.0.5, flash to new cwm version 6.0.2.9, flash new ROM and still boot to CWM screen
So, I can create and boot from a Sdcard, But can not boot to OS, always go to cwm 6.0.2.9 screen (that I think the wrong file since I flash from Nook Color file ). Thank you!
h a l t said:
Hello,
I've searched many topics but still didn't work
My NT 16GB worked good till today. Today I want to flash a new ROM (CM10.1 rc5).
I though I made a mistake from here: from ROM Manager, I flashed the CWM to 6.0, but I might flash with Nook Color version :crying: and from this time, my NT is ALWAYS boot into recovery mode.
...
please anyone can give me a hint, let me see the way to escape the recovery screen :crying::crying: thank you so much!
...
Click to expand...
Click to collapse
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
digixmax said:
I think your problem most likely has to do with BCB/BootCnt not getting reset properly, as described at http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1.
If so, the easiest way of resetting these files is to flash Succulent's flashable_fix_bootloop.zip at his repo http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
Thank you, I did but no luck still boot to recovery mode
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
DavDoc said:
You need to try and get an adb connection. I assume you are running Windows, if not............
But, what happens when you plug your NT into your computer. Do either of your drives (Internal/external SD) show up in my computer?
Click to expand...
Click to collapse
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
h a l t said:
Both drives show up in my windows computer, but I can't read, "please insert a disk" error when I double click on drive,
I am trying this thread http://forum.xda-developers.com/showthread.php?t=1470910 and hope...
Click to expand...
Click to collapse
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
DavDoc said:
You should have an adb connection then. Before you jump into the total wipe attempt, try getting an adb connection. Use this first and see if it works http://forum.xda-developers.com/showpost.php?p=36650082&postcount=171
You will need the driver files for this though, let me know if you don't have them.
Click to expand...
Click to collapse
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
h a l t said:
Yes I have the driver files, on device manager it shown Android Phone ADB interface, something like this, and what is the next step please...
Click to expand...
Click to collapse
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
DavDoc said:
You should have adb access given what you just said.
Are you familiar with command prompts and adb commands?
Click to expand...
Click to collapse
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
h a l t said:
yes I have adb access from Dos, but don't know which command to fix my problem. Thanks so much for your patience, still googling
Click to expand...
Click to collapse
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
F5, F5, ..... I see the light at the end of the tunnel,... God, what is the adb, shell command to help me escape this trouble :angel::angel:
DavDoc said:
Well this is a start at least.
I think Digixmax may be on to something though.
@digixmax, I am at work and don't have an NT in front of me, do you remember which partition the recovery is in. I wanted OP to see if those two files were even there. He may have gotten rid of them completely inadvertently.
Click to expand...
Click to collapse
These two files are in the /bootdata partition (see http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 for a list of the NT partitions and their content).
But if OP's flashing Succulent's flashable_fix_bootloop.zip (which basically re-install a fresh copy of these two files) didn't fix the problem then he might have wiped out some other critical components of the system.
I follow Adam's guide, unbrick my NT, and then flash new CM10.1 ROM perfectly.
Thank you again DavDoc and digixmax for helping me so much! :good:
Glad you got it working again
Sent with my Dinc4G
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
naveen_reloaded said:
I am currently on 4.1.2 10-20121209-UNOFFICAL-acclaim ROM
I want to move to CM 11.
My current recovery is CWM - Recovery v6.0.1.9
ON all CM 11 page , it says to update my recovery to new one through fastboot.
I am not sure how to do this on nook tablet. Can anyone help me ?
Also does repartitioning of 16Gb needs to done with each rom install or once done , it stays the same through out ?
Click to expand...
Click to collapse
Hi, repartitioning doesnt need to be done with a new rom install.
IF THIS IS A CLEAN INSTALL
you dont HAVE to install it through flashing a new recovery using fastboot
you just need a working newer CWM , or a working TWRP that you can boot
if you can boot to an older Clockwordmod recovery in any form, you can flash a newer version of CWM to the internal by using a zip file , this user has a couple of the newest ones hosted here:
newbtrigger69 said:
https://www.mediafire.com/folder/3j4kxa3bwkrs1/CLOCKWORKMODS <--------------------------------------------- my compilation of a few important CWM versions in case u dont like twrp (like me).
Click to expand...
Click to collapse
after you flash the new recovery, remove the SDcard, power completely down,
press and hold the "N" NOOK button, and hold the power button for just a second or 2 after you see the tablet boot, and you should be prompted for the new recovery that you just flashed.
---
the newer recoveries have an option on the boot menu to start fastboot. So, if you really wanted to follow the instructions to the letter, get or make a working sd card of a newer CWM recovery, boot to it, then as long as your adb/utilities folder on your PC has fastboot in it, you can fastboot the recovery-0.2.img as is in the cm11 thread.
I found I never had to use fastboot before this cm11 install , so I didnt even have the fastboot on my pc side and had to hunt it down.
my first several installs of CM11 were done using an older boot sdcard that had TWRP recovery on it and it works fine.
----
it will probably be a lot easier it you have a working tablet, to have the copied the zips for cm11 and the gapps you want to install to the tablets
internal memory first, before flashing the new recovery internally
---------- (I completely forgot this other possibility, I'm always just doing clean installs)
IF YOU WANT CM to automatically upgrade though the CM updater process on a running CM10
then , yes you need the newer recovery, and it probably is best if it is the recovery-0.2.img the developer posted in the CM11 thread.
I've never tried it so I dont know how well it migrates your "stuff" from CM10 to CM11
theres a lot of changes to the way storage is mounted in CM11 , and the CM updating process is an important thing they are trying to make as seamless as possible.
If theres stuff on the tablet you really need, I'd save it first before doing any kind of major upgrade like this.
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
naveen_reloaded said:
Thanks. I might do a clean install itself. I dont have much stuff.
Actually i am moving to CM 11 in hope that it would be faster. Currently i cant rad the PDF on thios tablet. The scrolling is very stuttery.. gives me headache. If that too doesnt solve that issue , i might simply sell this one and get some nexus tablet.
I just need a tablet to read my study books.
Click to expand...
Click to collapse
the latest nightlies of CM11 on a 16GB tablet (has 1GB RAM) are fantastic. best thing ever, especially if you replace the kernel with one that user:demetris has supplied.
I havent run the CM11 on an 8GB (512MB RAM) tablet yet, but it really is a good package.
Its kinda like when Windows 7 came out, its what should have been released instead of XP or Windows 98, its really, really good.
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
naveen_reloaded said:
Just tell me .. is flashing recovery via fastboot is same for all devices or for nook tablet its different. Also i need a SD card to do this ?
Can you help me how to flash recovery via fastboot for our nook tablet ?
Click to expand...
Click to collapse
hmmm...
Ive seen fastboot on other devices, Kindle Fires, which I think have a motherboard thats a close match to the NOOK tablet.
on the Kindle, you can force fastboot by using a special cable.
if you need fastboot on the NOOK, the recovery program that you execute at boot has to have the option to start fastboot.
you can boot a recovery that has that option from an internal recovery (CWM newer versions have it, I dont remember about older versions)
or you can boot from an SD card you make that boots a CWM recovery
in any scenario, for fastboot to work, you need a working ADB setup and the fastboot program on your PC
------
you can completely install CM11 without replacing the internal recovery partition of your NOOK which is what that fastboot instruction is trying to get you to do.
the special internal recovery, as I understand it, is only for compatability with the automated CM updating process.
you can boot from an SD card that has CWM 6.0.4.x , or TWRP , and as long as the CM 11 nightly is on the SDcard too, or in the NOOK internal memory, you can flash it.
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
naveen_reloaded said:
I am more confused
can you take me step by step or link me to a relevant thread ?
I am sorry if i am taking your time ..
Click to expand...
Click to collapse
--------- assuming you want to update your NOOK's INTERNAL software, and not run CM11 from an SDcard
I apologize had wrong file linked first post
this zip file should be flashable through your current CWM (6MB)
http://www.mediafire.com/download/0f5fjkjvxp1hga0/flashable_CWM_6.0.4.5(2).zip
http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2
it should update your internal recovery to cwm 6.0.4.5
then you should be able to flash the CM11 nightly and gapps without error
--------------------------
a different (I think slightly more dangerous) way to load the newer recovey to your internal was posted here:
http://forum.xda-developers.com/showpost.php?p=48317620&postcount=15
get the newest recovery image file -
File: http://goo.im/devs/chrmhoffmann/cm-11.0/acclaim/recovery-0.2.img
md5sum: e2a87c433171b3d97d852d27aea1ff49
-------
You can install it from a terminal emulator, if you want to.
1. Download the cwm-recovery.img file referenced in the first post of the thread.
2. Copy this file to the internal memory of your Nook Tablet. Rename this file to cwm.img.
3. On your Nook Tablet, launch Android Terminal Emulator (ATE).
4. In ATE, type in 'su' [ENTER]. Grant it access when prompted.
5. In ATE, type in 'cd /emmc' [ENTER]. This will change your file system current directory to /emmc, which corresponds to the internal storage drive.
6. In ATE, type in 'ls' [ENTER]. This will list the contents of the /emmc directory. You should see the cwm.img file you copied over and renamed earlier (step 2).
7. In ATE, type in 'dd if=/emmc/cwm.img of=/dev/block/mmcblk0p3' [ENTER]. This will write the contents of the cwm.img file to partition 3 of device mmcblk0 (internal memory).
You should now be able to reboot and use cwm. CAREFUL, as you could brick your device if you get step 7 wrong.
nvm
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
naveen_reloaded said:
@mikeataol
It worked perfectly. Just flashed it and it udpated to lastest CWM.
Installed CM 11 and got GApps and installed them too. Now downloading some PDF apps to see if they work smoothly and no stuttering is there.
In CM 11 , there is no option for "reboot to recovery" , why so ? I had to use cnyaboot option to enter into recovery.
Click to expand...
Click to collapse
Great!
re: reboot recovery
you have to unlock developer options first by going into
Settings/ About Tablet / Build Number
and tapping the "build number" field 7 times.
then you see a new settings group "developer options",
and in there is advanced reboot and other things.
---------- Post added at 04:24 AM ---------- Previous post was at 04:21 AM ----------
are you on an 8GB / 512 MB ram, or a 16GB 1GB RAM Nook tablet?
Lol , just found that reboot to recovery , came here to say i found , you already replied.
Installing bexus kernel.
Thanks a lot for your help.
One thing though. The scroll stuttering issue is there . Its as if the screen refresh rate or frames per second is not upto the mark , scrolling is very stuttering.
Is there any way to increase or solve this issue ? Please
this is killing the whole tablet and the purpose i want to use this tablet .. ie to read books.
I use 16Gb/1GB tablet
ok ran into issue
After flashing gapps and installing kernel , i am stuck with andoid.phone stopped working error as soon as the tablet boots.
What is the gapps to be used for CM 11 on tablet and is bexus interfering with the gapps ?
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
naveen_reloaded said:
how to enable multi touch ?
Also i think there is a serious problem with the screen/display. There is considerable lag and its not smooth scrolling. Its very stuttery...
Click to expand...
Click to collapse
I would not enable the multi touch, thats just asking for even more trouble.
I think you should consider a total re wipe , and start over
on a 16GB Nook Tablet, the nightly just by itself should run fine
i just downloaded and opened a 71mb pdf file with no issues whatsoever
opens in Adobe reader just fine, scrolling and zooming and searching is perfectly acceptable, nothing I would describe as a stutter
----
if you HAD enabled the multi touch while you were on CM10, I'd consider reflashing the stock LCD firmware before you put CM11 back on it
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
naveen_reloaded said:
yeah flashed thrice and i have witheld flashing bexus kernel for time being.
Stutter in the way , the refresh rate is not upto the mark
To best see this issue , dont swipe a text/pdf fast , do it slowly then you will see the jerkiness and also a lag between your swiping and actual screen change.
LCD firmware ? where to get it ?
Click to expand...
Click to collapse
to me, seeing a white page while adobe pdf loads the next buffer of pages several pagesahead is normal
I dont see anything abnormal while swiping slowly
re: LCD firmware
if you were on CM10, and fashed the 10 point LCD firmware, then I think you would need to rebuild the unit back to CM10, and reflash the stock LCD firmware.
I dont know how to explain , but look carefully when scrolling (slowly) , you will see tests stuttering as its been scrolled .
I am on CM 11 , do you want me to go to CM 10 ? and flash that firmware?
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
Which PDF reader are you using?
I don't have any stuttering issue on the Mantano Reader.
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"?
Hi everyone,
Just bought a used NT and I flashed cm10.1 and TWRP 2.8.4.0. After a reboot, my NT shows a pixel glitch screen after the N logo then stucks at it. I tried to press power button to hard reboot, but it doesn't change. A recovery sdcard doesn't work to it too.
So I'm here to ask if there's any way can rescue my NT. Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
CherryRook said:
Hi everyone,
Just bought a used NT and I flashed cm10.1 and TWRP 2.8.4.0. After a reboot, my NT shows a pixel glitch screen after the N logo then stucks at it. I tried to press power button to hard reboot, but it doesn't change. A recovery sdcard doesn't work to it too.
So I'm here to ask if there's any way can rescue my NT. Thanks.
View attachment 5713397
Click to expand...
Click to collapse
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?)
nmyshkin said:
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?)
Click to expand...
Click to collapse
Thank you for your reply.
Maybe it's not clear that I explained about the reboot (sorry for my bad English, not a native speaker), I can press the power button to shut it down, or hard reboot it. The problem is that the glitch screen shows every time and stucks every time.
May I ask that how to use the sd recovery card you provide? Shut down, insert the sd card, boot up and follow the instructions, is that right?
About the TWRP, I was tried to flash lineage 14.1 to my NT but the latest version of TWRP (3.1.1.0) doesn't work on my tablet, it's just black and blank after I flashed the recovery, so I have to use the older version. Besides that, some versions of TWRP has the famous error that both internal storage and micro sd card are 0 mb size. That's strange. Because I download them all from the official site.
nmyshkin said:
You need to find a way to either power down or at least reboot (after that you need to remake your flashing file sdcard because there is clearly something wrong there).
Of course, you could let the battery die on its own, then boot up an sd recovery card. That will return your device to FW 1.4.2 and fix any partition issues.
So unless you can force a shutdown or reboot with the power button, you may not have many options other than to drain the battery (or open the device and disconnect the battery for a minute).
Edit: Also, that TWRP version looks way out of range for CM 10.1 Should be more something like 2.2.2. A newer TWRP version may not work at all with an older ROM like 10.1 (why 10.1, and not 11, or 12.1, or....?
Click to expand...
Click to collapse
P.S. my NT is 16GB version. Is your file work to my device?
CherryRook said:
Thank you for your reply.
Maybe it's not clear that I explained about the reboot (sorry for my bad English, not a native speaker), I can press the power button to shut it down, or hard reboot it. The problem is that the glitch screen shows every time and stucks every time.
May I ask that how to use the sd recovery card you provide? Shut down, insert the sd card, boot up and follow the instructions, is that right?
About the TWRP, I was tried to flash lineage 14.1 to my NT but the latest version of TWRP (3.1.1.0) doesn't work on my tablet, it's just black and blank after I flashed the recovery, so I have to use the older version. Besides that, some versions of TWRP has the famous error that both internal storage and micro sd card are 0 mb size. That's strange. Because I download them all from the official site.
Click to expand...
Click to collapse
First, yes, you insert the recovery card, boot the tablet and follow the screen instructions, mostly "are you sure?", etc. This will restore your tablet to factory condition, FW 1.4.2. Should work for either 8 or 16 GB models.
Secondly, I hope you do not really mean CM 14.1. That would be a mistake, I think. That ROM requires repartitioning and there are newer (possibly better) options that do not.
If you are set on Android 7, then I suggest either AOSP 7.0 (which is what I run on my tablet) or LNOS 14.1 (which I have only tested on an 8 GB model, so I can't give a fair assessment:
nmyshkin said:
Lineage 14.1
https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/folder/3262390066
(there are many versions of this ROM. The link takes you to the "obsolete" folder where you need to hunt down lnos_acclaim-ota-NJH47F.180211.zip. This seems to be the only version without the shut-down bug)
Flashed with emmc-based TWRP 3.0.2-0
Click to expand...
Click to collapse
For either of those ROMs you can use the sdcard version of TWRP:
nmyshkin said:
TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
Click to expand...
Click to collapse
in order to flash the higher version of TWRP to the emmc which is what you will need for flashing the ROM:
nmyshkin said:
the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
Click to expand...
Click to collapse
If you have trouble with the TWRP from the actual website, let me know and I'll post a copy of my file. The emmc TWRP 3.0.2-0 is a little squirrely. The touch interface is shaky and you have to look carefully at what you have selected (or deselected) before going on to another step or you can end up in trouble. Not my favorite version.
Root, etc. for each of the ROMs is achieved a little differently, so when you get to that point, ask.
I don't recommend adding GApps to these unless you absolutely must have it. I do have GApps installed on my AOSP 7.0 install and it's "OK", but it would be more responsive without it. If you must have Google access then microG is probably the better way to go. You can read more about in my post on the 8 GB tablet. Everything there is applicable to the 16 GB tablet, except the ROMs I reviewed would all be expected to perform much better on the 16 GB version.
nmyshkin said:
First, yes, you insert the recovery card, boot the tablet and follow the screen instructions, mostly "are you sure?", etc. This will restore your tablet to factory condition, FW 1.4.2. Should work for either 8 or 16 GB models.
Secondly, I hope you do not really mean CM 14.1. That would be a mistake, I think. That ROM requires repartitioning and there are newer (possibly better) options that do not.
If you are set on Android 7, then I suggest either AOSP 7.0 (which is what I run on my tablet) or LNOS 14.1 (which I have only tested on an 8 GB model, so I can't give a fair assessment:
For either of those ROMs you can use the sdcard version of TWRP:
in order to flash the higher version of TWRP to the emmc which is what you will need for flashing the ROM:
If you have trouble with the TWRP from the actual website, let me know and I'll post a copy of my file. The emmc TWRP 3.0.2-0 is a little squirrely. The touch interface is shaky and you have to look carefully at what you have selected (or deselected) before going on to another step or you can end up in trouble. Not my favorite version.
Root, etc. for each of the ROMs is achieved a little differently, so when you get to that point, ask.
I don't recommend adding GApps to these unless you absolutely must have it. I do have GApps installed on my AOSP 7.0 install and it's "OK", but it would be more responsive without it. If you must have Google access then microG is probably the better way to go. You can read more about in my post on the 8 GB tablet. Everything there is applicable to the 16 GB tablet, except the ROMs I reviewed would all be expected to perform much better on the 16 GB version.
Click to expand...
Click to collapse
Thank you for these detailed instructions. Unfortunately, I write the factory reset file to a 16gb sd card, insert my NT and boot it, nothing change.
CherryRook said:
Thank you for these detailed instructions. Unfortunately, I write the factory reset file to a 16gb sd card, insert my NT and boot it, nothing change.
Click to expand...
Click to collapse
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
nmyshkin said:
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
I hate to say this but it doesn't work, still can't boot from sd card. The interesting thing is, my NT will automatically reboot after stuck at glitch screen for a while.
CherryRook said:
I hate to say this but it doesn't work, still can't boot from sd card. The interesting thing is, my NT will automatically reboot after stuck at glitch screen for a while.
Click to expand...
Click to collapse
You may need to try another card, if you can get one. This is often the problem when the tablet won't boot (did you try booting by inserting the power cord?). It may take some trial and error, and as they say in the instructions, you may need to remake the card (reformat, re-write the image) to get it all to work.
I can't think of any other approach for where you are now. The device clearly can't get to either a recovery or an OS.
With no SD card in, does it show up as some sort of USB device? Maybe 0451/d00f?
"doof" is German for stupid.
Renate said:
With no SD card in, does it show up as some sort of USB device? Maybe 0451/d00f?
"doof" is German for stupid.
Click to expand...
Click to collapse
Unfortunately no. It has no reaction on mac and when I plug it to PC, windows shows me a announcement that there's a device which doesn't work properly
nmyshkin said:
Some tablets will not boot from the sdcard unless they are plugged in to external power (either the power pack or USB from your PC). Try shutting down, then insert the power cord to make the tablet boot (it should come on by itself when power is applied). See if that helps.
OK, I should have given a lot more instructions with that file but I have never used it myself and forgot about all the stuff. Here is a link (messy...the important stuff runs down the left side of the screen) that describes how to use that zip file to restore your tablet: https://web.archive.org/web/2018082...06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That's weird. I followed the instructions on that page but still doesn't work. everytime I boot up, I got a quick N logo show screen then the familiar pixel glitch one.
Also I tried to change the partition ID to 0x0E FAT 16 LBA according from a thread in Chinese forum, but nothing changes
I was wondering if it's any kind of hardware issues?
CherryRook said:
Windows shows me a announcement that there's a device which doesn't work properly
Click to expand...
Click to collapse
Well, that means that there is *something* there.
Go to Device Manager and look for something with an exclamation.
Go to Details and look for Instance path.
I'm not sure even with an external SD card whether it still relies on the loader in eMMC.
OTOH, it could be a case of your regular system working well enough to start (and not go to SD) but too screwed up to run.
Renate said:
Well, that means that there is *something* there.
Go to Device Manager and look for something with an exclamation.
Go to Details and look for Instance path.
I'm not sure even with an external SD card whether it still relies on the loader in eMMC.
OTOH, it could be a case of your regular system working well enough to start (and not go to SD) but too screwed up to run.
Click to expand...
Click to collapse
I checked the device manager and found nothing. Literally, nothing there even after the weird announcement popped up.
I agree with your idea: maybe my emmc and system work fine, but something of bootloader or hardware has some problem so I got a pixel glitch screen. In my observation, the pixel glitch scrolls out from the right margin of the screen and covers the n logo and adobe claim. I still can recognize the text and images from those pixel snows, so I highly doubt that something about rendering must be wrong.
CherryRook said:
the pixel glitch scrolls out from the right margin of the screen and covers the n logo and adobe claim. I still can recognize the text and images from those pixel snows, so I highly doubt that something about rendering must be wrong.
Click to expand...
Click to collapse
What you describe is "normal" for a NT booting Cyanoboot--up to a point. With a properly functioning card, first boot copies over the cyanobootloader so that subsequent boots are from the emmc (assuming the system is intact). On the 16 GB NT every boot from the powered-down state flashes the pixelated screen briefly, and all at once. On the 8 GB NT, the pixelated effect moves from one side of the screen to the center and then from there to the other side until the entire screen is covered, then boot continues. and the pixelated effect disappears.
The problem seems to be getting a boot from the sdcard. If you read through the now crippled forum, you will see that's not so uncommon. The most common solution is a different card or at least a complete re-write of the offending card.
It has been reported often that some NTs cannot boot from the sdcard unless they are connected to a power source (either the charging pack or the USB connection to a PC). I have not seen this with my two tablets, but it would not surprise me.
Even making the original cyanoboot sdcard is filled with traps. Everything has to be done just right or the card will fail to boot or--worse--wreak havoc on the system.
It occurs to me that one other approach to this situation is to prepare such a card as if you were going to flash a custom recovery and a ROM. These instruction shepherd you through the card preparation:
nmyshkin said:
1. Using a disk partition tool (such as MiniTool Partition Wizard Home Edition) create on the SD card a Primary FAT32 partition, 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
2. Obtain and copy to the SD card the following files:
a. first MLO, then next u-boot.bin, and finally flashing_boot.img in succulent_boot.zip obtained from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
b. TWRP (TeamWin Recovery Project) version 2.8.6.0, e.g. twrp-2.8.6.0-acclaim-sdcard.img from https://dl.twrp.me/acclaim/twrp-2.8.6.0-acclaim-sdcard.img.html, rename it to recovery.img before copying to SD card. Be sure to use the sdcard.img file and not the one for internal emmc
c. the flashable_TWRP_3.0.2-0.zip zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet
Click to expand...
Click to collapse
Every single step is important, especially step 1. In step 2a the order in which the files are placed on the card seems to be important according to some guides. So every detail is important. No shortcuts. If you can prepare such a card and get your device to boot from it (try with the power cord), into the Cyanoboot menu, you should be able to flash a good emmc recovery and then......a ROM. But if the card won't boot, you can't do any of that.
Edit: Does this work on your tablet, or is it too far gone?
Perform Factory Reset of the Nook Tablet:
PWR off the Nook Tablet.
Hold "PWR" & "∩" & "VOL+" & "VOL-" buttons simultaneously to reboot.
After reboot, release only the "PWR" & "∩" buttons after 2-3 seconds upon receiving the "∩ - Contains Reader® Mobile technology by Adobe Systems Incorporated." screen while still maintaining to hold the "VOL+" & "VOL-" buttons.
The screen may blink a couple seconds later and then you will be presented with the Factory Reset screen with the following options:
Do you want to reset your device to the factory default?
Press POWER key to exit
Press HOME key to continue
Are you sure?
This will delete all your content and restore the device to the factory default settings.
Press POWER key to exit
Press HOME key to continue
I even accidentally let go of the "VOL+" & "VOL-" buttons once while testing this a few times but quickly pushed them back down again and was still given the factory reset screen so this method works even with a little goof like that. This worked since holding down the "VOL+" & "VOL-" buttons was found to be unnecessary.
nmyshkin said:
What you describe is "normal" for a NT booting Cyanoboot--up to a point. With a properly functioning card, first boot copies over the cyanobootloader so that subsequent boots are from the emmc (assuming the system is intact). On the 16 GB NT every boot from the powered-down state flashes the pixelated screen briefly, and all at once. On the 8 GB NT, the pixelated effect moves from one side of the screen to the center and then from there to the other side until the entire screen is covered, then boot continues. and the pixelated effect disappears....
Click to expand...
Click to collapse
It's just so weird.... I booted it successfully and my NT works well again.
I made a new recovery card, here's what I did:
1. Format a 8GB Kingston card to FAT32, set partition ID type to 0x0C FAT32 LBA, then set it to main active partition;
2. Copy everything for the card (MLO, u-boot.bin, flashing-boot.img, renamed TWRP 2.8.6.0-sdcard, flashable_TWRP_3.0.2-0.zip) to the card;
3. Plug my NT to PC, insert the card, boot;
4. Pixelated screen disappears and it boots normally to the sd card cyanoboot;
5. I entered to the sd recovery and flash the 3.0.2.0 TWRP, reboot.
Now it's running but I still have some problems.
First, when I try to perform a factory reset in the sd recovery, I noticed it has a caution that "Unable to mount /bootdata/," I'm not familiar with the system structure but I think ihat where the boot files save and maybe it caused the pixel glitch;
Second, when I check the partition status in new flashed TWRP 3.0.2.0 on emmc, It doesn't show any partition except ART / Davlik Cahce in Advanced Wipe page. I'm not sure what's going here. Then I rebooted to system, which works fine, and reboot again to recovery, and all partitons come back.
I'm so confused by all these things but at least I can use it now. May I ask, if I want to flash the AOSP 7 ROM, whcih version of TWRP I need? Should I flash it with sd recovery or emmc one?
CherryRook said:
It's just so weird.... I booted it successfully and my NT works well again.
I made a new recovery card, here's what I did:
1. Format a 8GB Kingston card to FAT32, set partition ID type to 0x0C FAT32 LBA, then set it to main active partition;
2. Copy everything for the card (MLO, u-boot.bin, flashing-boot.img, renamed TWRP 2.8.6.0-sdcard, flashable_TWRP_3.0.2-0.zip) to the card;
3. Plug my NT to PC, insert the card, boot;
4. Pixelated screen disappears and it boots normally to the sd card cyanoboot;
5. I entered to the sd recovery and flash the 3.0.2.0 TWRP, reboot.
Click to expand...
Click to collapse
So it was the card. Ta-da!
CherryRook said:
Now it's running but I still have some problems.
First, when I try to perform a factory reset in the sd recovery, I noticed it has a caution that "Unable to mount /bootdata/," I'm not familiar with the system structure but I think ihat where the boot files save and maybe it caused the pixel glitch;
Click to expand...
Click to collapse
The emmc version of TWRP (3.0.2.0) is full of little goofy "error" messages. Just ignore the bootdata messages. In general, TWRP is not going to wipe out /bootdata/ unless you try really hard. That's to prevent you from ending up with a brick.
CherryRook said:
Second, when I check the partition status in new flashed TWRP 3.0.2.0 on emmc, It doesn't show any partition except ART / Davlik Cahce in Advanced Wipe page. I'm not sure what's going here. Then I rebooted to system, which works fine, and reboot again to recovery, and all partitons come back.
Click to expand...
Click to collapse
This I cannot explain, but I hope that things will settle down as you begin flashing a ROM. Just bear in mind that the emmc TWRP has a poor touch interface. Always be sure items you have checked (or unchecked) are really that way. There should be no highlighting around a checked or unchecked item. If there is, it's not really what it looks like and you need to select (or deselect) again until you have a normal checkbox.
CherryRook said:
I'm so confused by all these things but at least I can use it now. May I ask, if I want to flash the AOSP 7 ROM, whcih version of TWRP I need? Should I flash it with sd recovery or emmc one?
Click to expand...
Click to collapse
The emmc TWRP you have is the correct one for AOSP 7. Continue here: https://forum.xda-developers.com/t/...-internally-on-the-16-gb-nook-tablet.3578665/ with step 2d. I do not recommend GApps, but it's in the instructions. If you want it, here is a link to the package I used. All the packages at OpenGApps seem to auto-expand with time until they are too large for our devices. If you don't want GApps, just skip any steps that refer to it.
Then proceed to step 3d since you have already flashed the emmc TWRP.
If you want full root access you'll need the superuser control apk. Here is a link.
I know the instructions are very tedious, with a lot of rebooting, but they are what worked for me reliably, over and over again. Detail counts in this kind of thing (and luck!).
nmyshkin said:
So it was the card. Ta-da!
Click to expand...
Click to collapse
It was the card, yes.
A brand new new questions here:
When sd card is inserted, I can't reboot or reboot normally or to the recovery. I did it from the power menu then it gives me a black and blank screen until I hold the power button to force it shut. If I try to boot it from the shutdown status. I have to remove the sdcard otherwise it can't be booted.
CherryRook said:
It was the card, yes.
A brand new new questions here:
When sd card is inserted, I can't reboot or reboot normally or to the recovery. I did it from the power menu then it gives me a black and blank screen until I hold the power button to force it shut. If I try to boot it from the shutdown status. I have to remove the sdcard otherwise it can't be booted.
Click to expand...
Click to collapse
I'm not sure I understand, but the sdcard you have made is not something that you would normally leave in the device. It is for flashing purposes only or for accessing the sd-recovery for some reason (like the emmc recovery gets messed up somehow or you need to flash something that is too new/too old for the emmc recovery).
If you completed the initial cyanoboot installation corrrectly, the device should boot into cyanoboot and then to the ROM (if installed) when turned on (without the card). If you leave the sdcard in and power up without selecting the "n" button to get to the boot menu, you will get an error about "boot magic", etc., and the device will just sit there on the cyanoboot screen.
So, yes (?) you need to remove the card to boot "normally" (i.e., into the ROM), although even there if you are quick you can intercept the boot with the "n" button and go into emmc recovery (from one of the boot menu options).
Is the problem that you don't have any OS? I wasn't clear whether that survived your first attempts with the bad card.
Edit: if you want to use an sdcard with the NT for storage it will have to be a different one than the one you prepared specially for flashing cyanoboot, etc.
nmyshkin said:
I'm not sure I understand, but the sdcard you have made is not something that you would normally leave in the device. It is for flashing purposes only or for accessing the sd-recovery for some reason (like the emmc recovery gets messed up somehow or you need to flash something that is too new/too old for the emmc recovery).
Click to expand...
Click to collapse
I restored the ID type of the sd card and now my NT can boot normally with the card inserted.
Tried the AOSP 7 you recommend and it's very good, thank you for it - but I think it would be better to have more custom settings, but Xposed and something like that are too heavy to NT with AOSP 7.
I tried to flash the lineage os 14.1 in your notredame folder but it can't boot. Looped at booting animation. Also, I tried a rom from AndroidFileHost, DrM-14.1-acclaim-Root-OC, but I got the status 7 error when flashing it, nomatter I use 3.0.2.0 TWRP on emmc or 2.8.4.0 one on the sd card. Any suggestion?