Related
First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this. (You need to goto this thread to install the sdcard version and follow instructions.
First of all, make sure your drivers are setup properly as this is a windows script to fix everything since you can only fix it from a computer. (I CANNOT EMPHASIZE THAT ENOUGH!)
Then you just download this zip, it check's md5 sum on the image before flashing so no worries, and then it flashes. It will reboot when it's finished.
I am in NO way responsible should anything happen, it was your fault for not checking the app's md5 in the first place so if this works for you, openly admit that you could have been better with handling the app's flashing. <-- Required.
I'm having a seperate thread so I can actively update this with anything that may arise since it would make my app's thread cluttered.
Read the whole thread or enjoy a broken Ntab, it's your choice.
Just wanted to say thanks for the dedication to those of us not smart enough to figure things out on our own.
Sent from my BNTV250 using Tapatalk
is this for those nt cannot use sd card recovery or 8 times boot break to restore the originally rom?
Dumb Question
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Benblanko81 said:
Total noob question. What do you mean by drivers set up properly? I want to try this, but I do not want to screw up again, and I just want to be totally sure I understand this properly. Thanks.
Click to expand...
Click to collapse
Means that you must have your nook drivers installed and working, if you ever rooted then you should have your drivers working properly.
~ Veronica
Can't get this to work
I have verified that I have the proper drivers (thanks Veronica). I unzip the fix and run the batch file, but the window closes almost instantly. I am using an XP machine, because of installing the drivers when I rooted. I can not for the life of me figure why it wont run. I am booted into the sd card version of CWM. Do I need to mount it some way or just at the home CWM recovery screen. I have been looking for help without asking and bothering, but can't figure it out. Not a noob but totally confused. Any help would be appreciated. Thanks.
Oops! I managed to set the wrong error levels on it, I meant to do 0 and 1, I instead did 1 and 2. Anyway, uploading now.
Still no go.
I got the batch file to run but it does not finish. It starts the Deamon successfully, and it just stays at Deamon Started Succesfully. It has been there for about 45 minutes. Should I wait or can I kill it and start over. Thanks again.
Kill it reboot your machine and start over
Sent from XDA premium using my Nook Tablet
No Go
Thanks Veronica, but the reboot still does the same thing. I just started the Nook&Zergy and the device shows up so I know the drivers are proper, it just stays stuck in Deamon Started Successfully for the fix. I am out of ideas, I fear I have just bricked my first device. I have doing this since the G1, this is sad.
No no, just do:
adb push cwm_internal.img /sdcard/cwm_internal.img
adb shell
then type:
dd if=/sdcard/cwm_internal.img of=/dev/block/mmcblk0p3
First off great work Indirect. This is exactly what I was hoping that image creator would be used for, just working on other things and got preoccupied. I think you might have to do some explaining though.
One thing to note though is that CWM should not be used for any other then rooting your device. As it stands right now there is no reason to flash it to an internal partition, you will only risk messing something up, as it has no gains.
Overview:In the Nook Tablet world there is a locked bootloader, which requires that there be a Secure Chain from u-boot, to the recovery. With the exploit that bauwks discovered and designed, we are able to flash custom recoveries on to the device. However a recovery must be packed.
Packing Structure:There are two ways that we have been able to go about getting around the boot loader, the internal method requires that we use the second U-Boot, with a 256k buffer and then attache the recovery after the buffer.
(0-m bytes) ------> (m-256k bytes) ------> (256k-n bytes)
Bauwks ntBoot Buffer nemiths CWM
The trick is that that 256kth byte must contain the header for the CWM, and this is vital. If that is lost, or something on Bauwks didnt get flashed right, you will enter a boot loop.
FAQ:
What Is a 'broken recovery' NT?
A broken recovery Nook Tablet is one where either the NT's internal recovery structure was not writen correctly or one where the NT's internal recovery structure is missing bauwks boot.
How can I tell if I have a 'broken recovery'?
Assuming you have not messed with any other partitions if you do either the N + pwr method, or the 8 false boots, you should see it open the BN recovery. If your device constantly turns on and off after one of these two methods, then you have a broken recovery partition.
My Nook just continues to boot into the recovery whats this?
Aha now that is not a 'broken recovery' and is actually quite fixable. In the nook Tablet there are two files that relate to the booting structure, aka the selection of where to boot from. These lie on a partition called bootdata, and are named BCB and BootCnt. If you are running stock on your internal partition, just let the stock recovery run, and it will solve your problem. If you are running CWM, you will have to use the following commands,
Code:
adb shell mount -t vfat /dev/block/mmcblk0p6 /data
adb shell dd if=/dev/zero of=/data/BCB bs=1 count=1088
adb shell dd if=/dev/zero of=/data/BootCnt bs=1 count=1
adb reboot
Aaa this is confusing can't I just put the stock recovery on my NT?
Sure. Hopefully indirect will make a script soon, or I will make one tonight that will put the default recovery img back. If you are feeling lucky you can do the following while on CMW.
NOTE: I AM NOT RESPONSIBLE FOR ANY DAMAGES YOU CAUSE TO YOUR DEVICE. One false move and you will brick your device. HIGHLY UNRECOMMENDED
Code:
adb push recovery.img /data (this is the recovery from the 1.4.0 or 1.4.1 update zip)
adb dd if=/data/recovery.img /dev/block/mmcblk0p3 (THIS LINE IS [COLOR="Red"]EXTREMELY DANGEROUS[/COLOR]. It should only be done as a last resort, and you should only do it if you are willing to take full responsibility.)
Dead End.
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Benblanko81 said:
I am going to start from the beginning. I flashed CWM using this app and the hit reboot into recovery from the app as well. Went to the cardboard box. I can reboot into CWM using the sd card method but can get no further. I have been trying the fix for two days and cant get it to work. Indirect gave me some ADB commands but I cant get ADB to work either. I have been on this for 2 days and cannot get it going. I really do not know what else to do. I am not a Noob and i know I have the proper drivers, the fix gets stuck though, and with the tablet in CWM from the sd card I just cant get ADB to work. I do not know if maybe because of usb debugging not being checked off, but again I can not boot up to Android, just to recovery from sd card. If I take out the sd card with CWM it boots to the cardboard box, then to black screen, and there it stays. I checked the thread for the app and people are still having this problem. I really do not know what to do. I have followed every instruction I have found or has been given to me, to the t, nothing.
UPDATE - I deleted the sdk and everything that had to do with Android from my pc. Reinstalled drivers using the method in the root thread that is pinned. I ran NOOK&ZURGY just to see my device appear in list of adb devices, which it did. It gave me my serial and it said recovery. I then redownloaded the sdk and did not download the Drivers from SDK manager. I am not sure but that seems to be the key here, to get rid of google drivers that can be downloaded from SDK manager. I then opened a command prompt, adb devices and bam there it was. I used the commands posted by LogLud above my post under "My nook just continues to boot into the recovery, what is this?". ADB Reboot and ****ing worked. THANKS TO INDIRECT, LOGLUD, and LAVERO.BURGOS. Your patience and help is greatly appreciated. I have never really asked for this much help before on XDA, and you guys were on the money, Thank You, Thank You, Thank You. Please PM me so that I can get you guys and girls beers. I will try to figure out how on my own anyways, but you guys deserve a contribution for taking the time out of your day to help me and others. Anyone with this issue and is having problems fixing, please post here or shoot me a PM and I will gladly give you all I can. Thank you again to all and happy flashing.
Click to expand...
Click to collapse
Oh well you should had started your first post by saying im using SDK and you will have it fixed faster. SDK is not needed in windows, leave that for devs all the necessary stuff that you needed to root is provided in indirects permanent root thread including drivers.
Glad it worked!
~ Veronica
Please help
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
lehite said:
I used Indirects app to install CWM, it seemed to work fine, but when I tried to boot into CWM it flashes the picture of the box, then shuts off. I tried using this method to fix it, but the same thing happens.
What am I doing wrong? Please help. I'd hate to have bricked my nook.
Click to expand...
Click to collapse
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
lavero.burgos said:
Did you try the method posted in this thread? you don't mention that , also can you boot normal if you let it or you cant? provide more info.
~ Veronica
Click to expand...
Click to collapse
Sorry if I was not clear. Here is the entire process:
1. I have a rooted Nook Tablet.
2. I installed Indirect's One Click App to install CWM
3. I used that app to install CWM.
4. I attempted to boot into CWM, but it flashes the box and then shuts off
5. I came to this thread and began following the instructions to fix it, but the fist set of instructions "First, you need to be sure you install the sdcard version of the recovery, otherwise you won't be able to do this.(You need to goto this thread to install the sdcard version and follow instructions.)
6. I followed those instructions, but I still get the box image then shut down.
7. I can't boot normally or into CWM.
Let me know if you need any other information and I greatly appreciate your help.
What I really need to know is how to create the CWM sdcard on a mac. i.e. I don't have a linux machine with gparted and I can't figure out how to get something like Disk Utility to enable boot and lda flags.
Thanks!
bootable sd card with osx
Lehite, I was having the same problem, i.e. disk utility in osx couldn't do the job for me. I ended up using this method.
Download the “size agnostic” CM7 SD card installer image (v1.3 in my case), then write it to your microSD following the instructions on the before mentioned page. The writing takes a little bit without terminal telling you the progress, after 1-2 minutes it should be done.
After succesfully writing the image to your SD card copy the files from Goncezilla's SD Boot thread (here) to your SD card overwriting files if necessary and follow his further instructions.
On a reboot with the boot SD inside your nook you should get to the CWM menu after seeing the cardboard box. good luck!
I myself am also stuck at the black screen after the box and need to figure out how to get the ADB working on osx to be able to do Loglud's commands...
UPDATE: to get ADB working on osx I used this method. Since I'm not a developer I didn't download the whole SDK package from google but rather just the ADB tools from here.
I then connected the Nook to the mac while in CWM, checked if it was properly recognized but typing adb devices, and applied Loglud's adb commands. BAM! worked! Am back in android Many thanks to all for directions, especially Loglud.
Now a question to Indirect, I downloaded your package just today, while using it it verified the MD5 positively and continued flashing. Why did I get the black screen, and not the CWM?
cheers
Hi,
I have a Nook Tablet in version 1.4.1 reset it back to 1.4.0, root it, tried to put cm9 in it...messed up royally, format a whole bunch of things that I shouldn't.
Now it's stuck in CWM v5.5.0.4
Tried just about everything, but can't get out. can't access adb, not very familiar with it anyway...but downloaded sdk, jkd, etc...but can't see device...tried recovery image also...doesn't work.
Is there any method aside from adb method? Is there an SD method...think I messed up the partitions or whatever...
tried this method:
http://forum.xda-developers.com/showthread.php?t=1555832
but doesn't work...
again can't see devices in adb...tried this & other methods...nothing..
http://forum.xda-developers.com/showthread.php?t=1363652
please help...
I actually have 2 Nook Tablets...one for my kids & another I'll give to a nun friend...1 is correctly rooted & has cm9...can I image one & flash it on another? If so, how?
Thank you & God bless
Have you tried making a bootable CM7 or CWM microSD card?
Solar.Plexus said:
Have you tried making a bootable CM7 or CWM microSD card?
Click to expand...
Click to collapse
I have a recovery.img...tried that didn't work
have boot.img tried that...CWM microSD
tried to flash SD_ROOT_NT16gbV4_6 onto microSD, but after that can't add anything else to it...the directions to partition microSD is somewhat confusing to me...don't quite know what to do or where to put boot file, etc...after I partitioned it...any advice is greatly appreciated...
"format a whole bunch of things that I shouldn't." BAD IDEA. Can you tell us what exactly you formatted?
Is always good to have adb working so you should troubleshoot it. In my FAQ there is a link for a how-to i made to install and use adb tool, run the runmefirst.bat from the package i provide is a must.
As an alternative (to non use of adb, etc tools) you can use Adam's total wipe (sdcard), which has been fixed by Adam to not affect serial ID's and MAC address from ROM partition.
~ Veronica
lavero.burgos said:
"format a whole bunch of things that I shouldn't." BAD IDEA. Can you tell us what exactly you formatted?
Is always good to have adb working so you should troubleshoot it. In my FAQ there is a link for a how-to i made to install and use adb tool, run the runmefirst.bat from the package i provide is a must.
As an alternative (to non use of adb, etc tools) you can use Adam's total wipe (sdcard), which has been fixed by Adam to not affect serial ID's and MAC address from ROM partition.
~ Veronica
Click to expand...
Click to collapse
I formatted....
bootdata, cache, data, emmc, rom, system, sd-ext....everything with the format in front of it...I did it...I know...not smart...
did the acclaim_update...doesn't work...CWM seems to be working...but just can't install acclaim_update or SD_ROOT_NT16gbV4_6...again can't access adb at all
What does it say when in CWM when you try to flash something?
thungrac221 said:
I formatted....
bootdata, cache, data, emmc, rom, system, sd-ext....everything with the format in front of it...I did it...I know...not smart...
did the acclaim_update...doesn't work...CWM seems to be working...but just can't install acclaim_update or SD_ROOT_NT16gbV4_6...again can't access adb at all
Click to expand...
Click to collapse
they won't work because you formatted most of your partitions, use Adam's total wipe as i said before or soshite unbrick method but for that one you need adb working.
~ Veronica
lavero.burgos said:
they won't work because you formatted most of your partitions, use Adam's total wipe as i said before or soshite unbrick method but for that one you need adb working.
~ Veronica
Click to expand...
Click to collapse
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
nevermind...found the link...will try...thanks again
thungrac221 said:
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
Click to expand...
Click to collapse
I use virtual box: https://www.virtualbox.org/wiki/Downloads
If he has cwm he has adb.
Just guide him to install correct drivers for it.
Solar.Plexus said:
What does it say when in CWM when you try to flash something?
Click to expand...
Click to collapse
tried to install recover.img, but Error mounting /sdcard..tried mounting, but can't
thungrac221 said:
I don't have ubuntu, think I saw a link from you to create a virtual ubuntu? Please post that again...Thank you
nevermind...found the link...will try...thanks again
Click to expand...
Click to collapse
Well, I download the adam's image for windows, but in CWM cannot mount sd card...oddly, when I plug it into my computer, it sees the nook but cannot start adb...tried methods to recognize usb, but can't...
please advise....thank you
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Make a new recovery card from the instruction. Forget your old recovery card.
Install these two,
flash-restore-stock.zip (use it to restore partition 1-6)
flash_stock_1.4.2.zip (use it to restore to stock 1.4.2)
Then install whatever rom you want after.
succulent said:
Go here, https://github.com/succulent/acclaim_recovery_sdcard
Make a new recovery card from the instruction. Forget your old recovery card.
Install these two,
flash-restore-stock.zip (use it to restore partition 1-6)
flash_stock_1.4.2.zip (use it to restore to stock 1.4.2)
Then install whatever rom you want after.
Click to expand...
Click to collapse
Thank you, thank you...used only this flash-restore-stock.zip & was able to find my way back... thanks a lot...my friend who is a nun will enjoy this when she goes to Ghana on her mission...she wanted this instead of carrying loads of spiritual books...thanks again... & God bless
I second that succulent with your post I was able to find my way back after flash-restore-stock.zip. My issue was Nook kept on booting CWM. Now I have to figure out how to boot CWM via USB again to flash stock rom. For now it takes me up to B&N member setup page, but only shows error when I enter info
Okay I wiped my internal emmc, so there is no OS. When I turn it on I get B&N stock setup menu. Than after account sign in it gives me error message with device info.
I can boot on SD CWM, but when I try to flash any zip it aborts and also I can't seem to find the right CWM SD that leaves me enough room to copy the OS.zip on the SD.
Hi anyone and everyone,
So let me start by saying I am really in need of help two months ago i had a flawless CM7 Nook Tablet 16GB that worked like a dream and now i have a useless brick and im about to through it away the problem i have can be viewed here............ http://www.youtube.com/watch?v=0BAZ...&playnext=1&list=PL05B917C134DF82A7........It gets stuck on the white screen everytime i was able to boot into CWM with a bootable sd card and I have tried to flash many roms from there and yet every time i get stuck at white screen please help help help help!
WOW!!!!!!!!!!!!!!!!!
Thanks in advance to all that reply!
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
ShinnAsuka said:
well for starters it would help if you could tell us how you came to be bricked in the first place. you say that you had a perfectly fine NT before, so what did you do to get to where you are now?
Click to expand...
Click to collapse
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
and as to where I am now......everytime I turn on my nook it gets stuck at the white screen with the cardboard box.....unless I use a bootable sd card which then I have tried to flash old roms new roms and I get nothing
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
Your partitions are : shot / corrupt / messed up. They "really" gotta be working okay . . . Will the near by B&N store put them back in good working order for you ?
Clksk8 said:
I was editing my build prop and I made a mistake so it booted into cwm recovery and I think I might of partitioned my rom or something I really don't know what happens but I do know that everytime I go into cwm I get a bunch of errors and can't even mount it all fails I found my problem alot through these forums with no answer which is why I made the post
Click to expand...
Click to collapse
With a bootable SD card are you able to.use ADB? If you are you might be able to push a normal build.prop to /system and be able to boot back into your rom. If not then like old fart said you may have messed up your partitions.
Sent from my Nook Tablet CM7 BETA using xda premium app
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Clksk8 said:
If my nook keeps loading to the white box which is part of cwm (right) won't B&N know iv rooted and most likely tell me in screwed if not I will gladly ask for there help
Thanks for the quick reply's......in not very familiar with adb
Click to expand...
Click to collapse
assuming you have adb setup correctly the commands aren't too difficult. i believe the following should suffice. i only know windows commands so yeah..
open your start menu, type in cmd and then enter.
navigate to directory where you have adb installed. in my case it was -> cd C:/ntroot
then connect your NT to your computer, make sure usb debugging is enabled which it most likely is if you can get into cwm.
use adb devices, and there should a string of numbers which is your serial number. if you see it then that is a good sign.
then adb remount, which makes the file system writable.
next make sure you have the normal build.prop in that directory that you have adb installed in.
then do adb push build.prop /system
should be very quick, if all goes well you should be able to boot back into your rom. otherwise, your partitions are likely screwed up...
if your partitions are screwed up, there should be a couple of links in the android development section that tell you how to repartition so you can start anew.
good luck.
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
that serial number is normal, you should really learn to use the search function provided by this forum but here are two that i found...
http://forum.xda-developers.com/showthread.php?t=1562130
http://forum.xda-developers.com/showthread.php?t=1605664
those two are assuming you screwed up your partitions.
Clksk8 said:
When I connect to adb I get 0000000000 as my serial does this make since can anyone point me to a link to re do partitions I will look around also
but it is just easier if some one can point me to the right area
Click to expand...
Click to collapse
adb is hooked up correctly but when i put adb devices i get
0000000000 recovery instead of a serial number?
So I have bricked my Nook dozens of time but when I do I just download the acclaim_update.zip from one of these threads and go to a file in it.
Go to /META-INF/com/google/android/updater-script and then I just edit the first two lines. Edit both parts where it says "blaze" and change it to "acclaim". If you're on ubuntu then all you have to do is press saveand it will ask if you want to update the file (or something like that) and click yes. Then just make a CWM bootable sd card and flash that file Hope it helps!
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.