I hope someone can help me. I have a 16gb nook tablet that I rooted using the method described here http://liliputing.com/2012/03/how-to-dual-boot-cyanogenmod-7-nook-tablet-os-with-a-microsd-card.html over a year ago and I've never had an issue until last weekend. My daughter was playing a game and the nook started acting up. The touch screen became unresponsive and the screen started to flash. I let the Nook charge overnight and when I turned it on the next day the screen became stuck at the white Nook welcome screen. After 20 minutes I tried the holding down power and N button to see if I could get it to restart, but unfortunately that may have made it worse. Now my Nook won't start at all. I've read many many threads here on how to fix it, but I am not tech savvy in the slightest. The first thing I tried was Rays method http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/ but instead of getting the green checkmark I got the red X and the "nook is shutting down" message. I tried so many things that I cannot remember them all but I do know that one of the methods I tried I got this message.
E:Can’t mount / cache/recovery/command/
E:Can’t mount / cache/recovery/log/
E:Can’t open / cache/recovery/log/
E:Can’t mount / cache/recovery/last_log/
E:Can’t open / cache/recovery/last_log
After that I tried to use the method described here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 and I did make the booktable cwm-sd and I went to lavero.burgos' thread to download the mmcblk files, but they weren't there.
Also I don't understand what adb is but I'm desperate, when I found the thread that explained it and tried to download the ADB + Fastboot + Drivers.zip that was in said thread (I'm sorry I can't remember which thread it was) the zip file didn't work.
I'm really sorry for posting yet another, "please help my nook is borked" thread but after all the reading I've done this past week the only thing I've become is very confused and frustrated. Thank you in advance to anyone who can help.
Notice on the link you posted
Ray Waldo; said:
If this procedure fails, try one of these:
Celtic has a possible solution on XDA here: http://forum.xda-developers.com/showthread.php?t=1513583
Succulent has more info on his Github page: https://github.com/succulent/acclaim_recovery_sdcard.
Click to expand...
Click to collapse
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
udownwitopp said:
Notice on the link you posted
I can see how you got lost. There aren’t really any detailed instructions there.
I got the following zip from 2nd link
Flash the zip with CWM then try the bn_142_factory_recovery.zip SD card again and you should get a green checkmark this time.
Click to expand...
Click to collapse
Thank you for your reply. I will try this tonight and hopefully it will work.
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
evm22 said:
Well I tried, and I hate asking but how exactly does someone add a zip file to an sd card after an image has been flashed to it? I've tried numerous times with sd cards of various sizes and I'm pretty sure I should have been able to do this with a 16gb card, but every time I try to drag and drop the flashstock zip over onto the card it says that there is no room available. Now I have been doing a lot of reading on here and I'm pretty sure I did not set the card up right, I did format it correctly with the sdformatter program, but I'm guessing I have to do something with the partitions on the card. I am not familiar with the programs because I've never had cause to use them before so I am not entirely sure how to do that. I tried following the directions found here http://forum.xda-developers.com/showpost.php?p=24995518&postcount=1 but I couldn't figure out how to enable boot, and lba flags. I realize that this has probably all been answered already, but again, there programs are so foreign to me that I'm not even sure what to look up first. Thank you again for any help that any one can give me.
Click to expand...
Click to collapse
I'll try to explain the process for you. "The Red X" is a very common issue that people have with their devices. It's usually caused by digging into something that you don't fully understand. It's VERY important to understand the process of flashing custom ROMs because it could screw up your tablet, delete ROM partitions and such.
The first issue you need to attend to is "The Red X." First download the bn_142_factory_recovery.zip from the ray waldo site found here:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Unzip the zip file and you should have a repart.img. Use win32diskimager to write this to an SD card. Once it's done writing, put the SD card in your device and it should boot from SD card and flash stock B&N 1.4.2 to your nook (if you have problems booting from SD card plug in the USB to your computer).
If you still get "The Red X" during this process please use the following method:
http://forum.xda-developers.com/showthread.php?t=1513583
If you have further problems please post or PM me. Once you have the issue fixed I HIGHLY recommend using the SDC version. It's a lot easier than the Internal Version and will prevent mistakes from happening.
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
evm22 said:
Thank you for responding. I retried the method described on Ray's site, but sadly it's still a no go. I have downloaded the parted binary and I know how to get it onto the sd card, but what I don't know is how to ADB into my device. I'm not even sure I understand what ADB is.
Click to expand...
Click to collapse
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
datallboy said:
I'm not extremely knowledgeable with the ADB tool, but it's setting up your computer so you can write commands into your command prompt that will execute actions on your device. The link for setting it up is here:
http://forum.xda-developers.com/showthread.php?t=1474956
Once you get it set up just follow the rest of the directions in the parted binary post.
Click to expand...
Click to collapse
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
evm22 said:
Thank you for a link to the post with a working zip file for adb, I've downloaded and I've tried to follow the video, but unfortunately my laptop will not read my nook at all. Every time I connect it with a usb my device manager tries to find it, but it blinks, makes an error sound and I see
OMAP4330 under other devices. I' did a search for that error and came across this thread, but again the instructions call for installing an apk on the nook and since I can't get mine to turn on, it's a no go
Click to expand...
Click to collapse
There is a possibility you could have deleted some partitions important to the nook then. Have you tried making an sdc version of cm10 to see if it could boot at all? You could see if you still have the device information to backup, recreate the partitions and flash back to stock.
Use this to make a bootable cm10 card:
http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/
Just write the image file to an SD card and put it in your nook. It will boot into cm10. Once there go into your file manager and turn on root access. Go to your root drive/ROM/devconf to access all your device information. Make a backup of all them. There is a picture of my devices root drive. If you do not have the various partitions you will have to recreate them. There is a method on the Nook General Thread for doing this named "Unbrick Internal Partitions On NT" or something similar. You can use that recreate the internal partitions essential for your nook.
If you deleted the ROM partition with the Nook's product information you may be out of luck. The serial number and Mac address are the most essential, and can be found on your device hardware. The SN is under the SD slot (if readable) and Mac address is located inside your device. Not sure where I've never opened my nook to look, but probably on the WiFi chip.
Slight chance you may be able to fix it with this information and the rest of the device information you can use from a different nook since it doesn't have to do with internet and registration. There may be a way to fix that, but I don't know of any.
Best of luck. If you have problems just post a reply or send me an email.
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
evm22 said:
I can get the Nook to turn on with the bootable cm10 card in it. I get the cyanoboot screen and see the boot menu, but honestly I don't know where to go from there. I think it's time for me to try and find someone who understands all of the programs involved in trying to fix this because I know I'm going to end up making things worse, if that's even possible. Thank you for trying to help me though. I do appreciate it
Click to expand...
Click to collapse
Hello! Did you ever figure out how to resurrect your Nook? I had trouble signing in Gmail and wanted to just unbrick and have the plain Nook again. I've been struggling getting the device to boot from the sd card with the repart imaged. I'm trying to get back to the ClockworkMod recovery screen but I can't at that moment. Someone suggested that I "flash" the B&N zip to the card but I'm trying to figure out how to do that.
Would love help!
Related
I have a GTab that was running Calkulin + Clemsyn Combo Overclock at 1.5 ghz V8 on the 1.2 branch fine for a couple months now, then something happened today. Woke up to find there was no sound coming from it (I'd left an Anti-mosquito app running all night), so I tried to play a couple music files. Seemed to get frozen instead of playing, so I restarted. That's when it went into a boot loop from 3 birds to the first splash screen of the loaded ROM.
Attempted to do a backup via CWM, and it failed on /data. Tried a data wipe/reset, then reflashing the ROM and finally NVFlash. Still goes into a bootloop. Repartitioning and mounting doesn't do anything; ADB doesn't see the device at all in CWM or APX; /data cannot be mounted and /sdcard mounts only when a card is inserted (doesn't see the internal space) but still doesn't mount USB storage and says: "E:Unable to write to ums lunfile (No such file or directory)"; drive shows in Win7, but is inaccessible;
As mentioned, APX mode and NVFlash along with CWM works fine. And I can mount /cache and /system fine. I've gotten to Code Double Red here and now I'm draining the battery for the next step (really don't want to pull any screws). Also tried the fix here, but it seems that's just for CM7, which I'll probably try flashing some time.
I'm going to return to the 1.1 branch and try a couple ROMs there, but I have a really slow connection and it's taking a while to get nvflash 1.1.
Did a quick search of the forum and didn't find anything quite similar. Obvious question is, has anyone ever experienced this before? What are some other steps I can take to fix this? Is there a way to backup the internal SD before I probably have to wipe it?
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Connected the charger long enough to run the command, but all I get is "error: device not found". As I'd said, ADB doesn't detect the tablet, even though Windows knows when it's connected and disconnected. Is there anything that I can flash to get me a terminal? That's the only way I can think of to get that command run and hopefully direct the output to my SD. Thanks.
I now have a completely dead battery. Wondering what to do next since it's supposed to have been hard reset now. Not seeing anything different after booting; same boot loop even though I just flashed a ROM again.
rajeevvp said:
Connect the USB cable to the tablet, then boot it into CWM, and run this command on your PC:
Code:
C:\SOME\PATH> [B]adb shell dmesg > dmesg.txt[/B]
Post that dmesg.txt file here. We'll see what's wrong.
Click to expand...
Click to collapse
I had seen this thread before where you were helping someone last year. Wish I'd read further to see that he eventually got the same problem I now have. I'm currently working my way through everything. First I need to get ADB running though, so I'm working on that now. Think I may be needing that partition swap trick, but we'll see...
Having issues getting the right USB drivers installed for ADB on Windows 7 64 bit. Using instructions here. But each time I uninstall the device, as soon as I plug in the tablet, it installs the default drivers. Using both Device manager and USBDeview. Updating and other options are also disabled when there is nothing installed. Considering to do a direct registry hack of the device info if I can, and hopefully not break anything important.
Try using Linux.
I finally got ADB working on my system and did some experimenting. Seems there's definitely something wrong with my internal SD according to the dmesg output. Luckily I have a SD which I used in my SG3, and it is already properly partitioned, so I'll try using that. Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped. Any guidance is still welcomed. Thanks alot.
Skele Drew said:
Seems there's definitely something wrong with my internal SD according to the dmesg output.
Click to expand...
Click to collapse
Yeah. There are clear error messages relating to the internal SD card. You can either return the tablet and get a replacement, or, use my SD card device swapping technique to use the external SD in place of the non-working internal one.
Tried making a fstab file in /etc (mtdblock3) but I got "Magic Value Mismatch" error, so I NVFlashed to return it to how it was. I'm currently researching how to create update files, because it seems that's the only way I can get the SDs swapped.
Click to expand...
Click to collapse
If you use my files, you don't need to modify anything manually. What're you trying to change, BTW?
I can definitely use some help there. Where are the files? I tried modifying the custom ROM I use by adding a custom fstab and vold.fstab to /etc, an init script to init.d and replacing the /data mounting command with:
Code:
ui_print("Copying Data Files");
run_program("/sbin/mount", "-t", "ext3", "/dev/block/mmcblk2p2", "/data");
ui_print("Mount information:");
ui_print(run_program("/sbin/mount"));
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
rajeevvp said:
Not sure what you're attempting to do here...
If you just want to use an external SD card in place of your non-working internal one, then all you have to do is a) flash either one of the CWM zip files and then b) flash the SD card swapping zip file right after you install the ROM of your choice. And, if you tell me which ROM you plan to install, I can look inside it and tell you if my scripts will work with that ROM.
If you can read shell/awk scripts, you can look inside the zip files to see what they do and how they do it.
Click to expand...
Click to collapse
I was trying to make a swap script myself, but it's not working. /system dir gets corrupted. I'm using Clemsyn_Caulkinver8final2, a Froyo ROM.
Look at my scripts. If you have any questions, just ask.
Where are the scripts? That's what I've been asking...
EDIT: If this is what you use, then all should be ok. Let you know the result when I'm again online. Thanks alot for your help!
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
rajeevvp said:
That's what I was talking about. I modified the device-swapping script today to fix-up an additional shell script, /system/etc/inandop.sh, on the various Clemsyn/Beasty ROMs (incl. yours), so use the newer zip file.
Click to expand...
Click to collapse
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Skele Drew said:
Appears it still doesn't work. However, now instead of having a boot loop, it's just stuck at the splash screen after the 3 birds. I'm going to try combining your script and the ROM to see if I can get better results. I'm also going to try inserting some log/debug messages where I can.
Click to expand...
Click to collapse
THANK YOU RAJEEV!!!!!!!
Today I got the time to work on my tablet again, since I just restarted college and it's been a bit hectic. Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted). The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected. Then I flashed your script and VOILA! everything started great. So now I have my tablet again for my classes .
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Again, thanks for all your assistance. It's much appreciated. I really didn't have that much time anymore to work on it myself too. I will continue to learn more as time goes on though, and I hope one day I'll become a guru like you .
Skele Drew said:
Decided to try CM7 since when I looked into your script I saw direct management for it, so I NV'd back to 1.1 (I didn't know what branch CM7 was on, but flashing CM7 on 1.2 gave an error and aborted).
Click to expand...
Click to collapse
The official CM7 is, right now, only for 1.1. However, since you can replace just the kernel and instantly make a 1.2 ROM, you'll have to look at the kernel messages to tell which bootloader version you have (Note: this is only for pershoot kernels).
The first time I tried the CM7, it got to the CM7 logo, then was there for a while until I only had a black screen. The only way I knew the tablet was still on was because ADB was still connected.
Click to expand...
Click to collapse
This is to be expected. When a ROM first runs, it writes a whole bunch of stuff into /data; but, your internal SD card is messed up, so every write would've ended up with the kernel retrying for quite a bit and then failing.
You should've flashed the ROM and immediately afterwards my script to fix-up the mount points on the ROM--ie. before the first boot.
I am planning to still run a few tests to see if I can somehow recover/fix the internal SD, so I downloaded your set of e2fsprogs. Think I'll make a flashable file for the entire package.
Click to expand...
Click to collapse
I doubt if you can "fix" your internal SD card error using any of the e2fsprogs--it looks like a card-controller error rather than a media error. You have one of the non-standard internal SD cards which has caused problems for some other users as well.
Ok. I do have a few issues I hope I can get some help on. For one, flash player doesn't work, and that's something very important. All my browsers direct me to get flashplayer. It worked pretty well in my previous ROM, so it may be an issue with CM7, but I haven't seen any similar issues on their site.
Also, the tablet is less responsive now, though I think this has to do with the /data partition being on external SD, though it's a class 6 card.
Sent from my GTablet using Tapatalk
Did you partition the external SD card correctly into 2 partitions (the first as VFAT and the second as ext3) before you installed CM7? I'm not sure what steps from my post you followed and what steps you skipped: you mentioned you were planning to modify the scripts/ROM, right?
It is also possible that my script is not doing the right thing on CM7 since it doesn't touch the vold.fstab on it. Get me the output of a mount command in CM7, and these files:
Code:
/system/etc/vold.fstab
/system/build.prop
Also make sure that you, or the ROM provider, haven't enabled the SD card switching in Settings > Cyanogenmod settings.
The SD I'm using was in a SG3 using this ROM, so I think it's correctly partitioned. I've accessed the partitions before and the correct names are associated with the contents. I only followed steps 1 & 4. The option to use removable for apps and media is disabled.
build.prop
mount.txt
vold.fstab
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 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!
Need some help with the "AdamOutlerUbuntuTotalReFlash" method. I am missing or overlooking something but, can't figure out what. I have installed the Ubuntu 12.0.4 on an older laptop in an effort to 1) learn but 2) mostly to restore my 16GB NT. Currently the Nook will only boot to CWM. I have tried a few different methods and images but, can't seem to get anything to load. Do I need to repartition and can anyony help with that, I am at apoint wher maybe I have tried to learn or do to many new things at once and am frustrated and confused. I don"t believ all is lost but could sure use a little more help/direction. I have followed all of Adam Outler's steps but, seem to run into trouble with having success writing the image to the SD card.
Is this what you are trying?: http://forum.xda-developers.com/showthread.php?t=1470910
If so, you do not need to have Ubuntu on your computer, nor know anything about it!
Scroll down to "WIndows" instructions and go!
1. Download - extract - rename Adams file
2. Open your disk imager and load the img you "created" in step 1.
3. Burn the image to your sd card
4. Boot into the card created in step 3 and follow the instructions below the picture. starting with "Theory of..."
thanks
asawi said:
Is this what you are trying?: http://forum.xda-developers.com/showthread.php?t=1470910
If so, you do not need to have Ubuntu on your computer, nor know anything about it!
Scroll down to "WIndows" instructions and go!
1. Download - extract - rename Adams file
2. Open your disk imager and load the img you "created" in step 1.
3. Burn the image to your sd card
4. Boot into the card created in step 3 and follow the instructions below the picture. starting with "Theory of..."
Click to expand...
Click to collapse
I would like to say thank you for the help and appreciate the support. I will give this a shot. this evening. a few Questions 1) when renaming the AdamOutlerUbuntuTotalReFlash.tar.gz file do i delete the .tar.gz extensions and replace them with the .img extension? or do i do i leave them so that the extension is now .tar.gz.img ? 2) when powering on the device do I power on with the power button on the NT or use the USB cable and let the device power itself on and does it matter if the device is plugged into the charger or the PC? Any specific instructions or specific utilities for formatting the SD Card?
Thanks Again!
I haven't done this recovery myself, so I really don't know anything about it. I would suggest you to read through that topic and see if the answers are there.
The instructions do say "extract" and THEN "rename"
Some general things I can say though:
When burning an image to sd card the card doesn't need to be formatted before doing it.
To get the NT to boot from sd crad is individual from device to device. Many say they only get theirs to do it by inserting charging cable to power adapter.
The three that have passed through my hands have booted to sd either by themselves when turning on power. If they haven't done so right away I hold down the "n" and that's it.
1_ton said:
Need some help with the "AdamOutlerUbuntuTotalReFlash" method. I am missing or overlooking something but, can't figure out what. I have installed the Ubuntu 12.0.4 on an older laptop in an effort to 1) learn but 2) mostly to restore my 16GB NT. Currently the Nook will only boot to CWM. I have tried a few different methods and images but, can't seem to get anything to load. Do I need to repartition and can anyony help with that, I am at apoint wher maybe I have tried to learn or do to many new things at once and am frustrated and confused. I don"t believ all is lost but could sure use a little more help/direction. I have followed all of Adam Outler's steps but, seem to run into trouble with having success writing the image to the SD card.
Click to expand...
Click to collapse
You should read this post before trying out any "unbricking" method and end up permanently bricking your NT.
asawi said:
I haven't done this recovery myself, so I really don't know anything about it. I would suggest you to read through that topic and see if the answers are there.
The instructions do say "extract" and THEN "rename"
Some general things I can say though:
When burning an image to sd card the card doesn't need to be formatted before doing it.
To get the NT to boot from sd crad is individual from device to device. Many say they only get theirs to do it by inserting charging cable to power adapter.
The three that have passed through my hands have booted to sd either by themselves when turning on power. If they haven't done so right away I hold down the "n" and that's it.
Click to expand...
Click to collapse
o.k. so i have downloaded the image, extracted it using winrar but, when i use the win32diskimager to write the image i can find the file but, the win 32 diskimager does not recognize the sd card or doesn't even let me open the little file foled at all for that matter as far as where to chose to write it to?
Hi all,
I tried Adams' method along with a few days worth of other methods. I've been unable to get past the writing MLO portion in Adams' method. Has anyone been able to get past this?
p.s. I'm a semi-n00b, this is my first tablet If it was a phone I'd be fine lol
Nvmd, I think I was using an old file, got it working now. Large thanks and respect to Adam!
Sent from my DROID RAZR using xda app-developers app
Here it is
http://forum.xda-developers.com/showthread.php?t=2179403
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"?