My problem is almost similar to this , except the cause, and the seriousness
http://forum.xda-developers.com/showthread.php?t=2325101.
Could anyone report the rom problem to the official(i do not know how to access to them) and could the official give a solution? :crying:
If anyone could help me solve the problem, please tell the method step by step , i am not good at computer. If solving the problem need any files please post the downloading threads.Thanks.
I think the reason why I could not install the cm10.2 again maybe caused by load the internal memory too much. I saw someone said to install the cm would not format the data in the internal memory. When the memory is almost full , it won't install apps . Maybe it can not rewrite the rom. If so , how can i delete my personal data .?Now i can not boot the tablet , and even can not connect it to a PC. I am at a loss and very worried. I am out of USA , and it is almost impossible for me to return it to B&N to have it repaired. Could anyone here give some advice to repair it .
I asked verygreen , and he gave me an answer
There appears to be a bug in internal storage software used in Nook HDs that leads to internal storage dying under certain conditions, though the conditions are not exactly clear, but it also seems to do with a new feature added in Android 4.3
I disabled this feature on 8/15, though it's not yet clear if 8/15 nightly was built with that added or not.
The bug is not unique to Nooks too, Some Galaxy Note devices that use a very similar samsung-branded internal storage also have this problem.
But not gave the solution , could anyone solve this problem and give the solution step by step to me, thanks. i am just at a loss here
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Ogre6473 said:
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Click to expand...
Click to collapse
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
nookhdplus said:
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
Click to expand...
Click to collapse
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Same problem here.
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Now I can nearly confirm there is a fatal bug in the 8/15 rom , so many are affected by it .I recommand others not to update to the cm10.2 before the problem is solved and the official should offshelve it from the website and give a solution as quickly as possible.
talha970 said:
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Click to expand...
Click to collapse
BTW, which rom did you use when the problem occured ? Is it the 8/15 version?
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
verygreen said:
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
Click to expand...
Click to collapse
I would donate my totally bricked tablet to you but there is too much personal info in it.
Riddleric said:
I would donate my totally bricked tablet to you but there is too much personal info in it.
Click to expand...
Click to collapse
The info is likely not recoverable without some significant effort anyway, but I certainly can understand this decision too.
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Edit: BTW I never installed fstrim or anything like that. It probably was the 0813 version that initiated it but I wonder why it failed in 0815 when trim has been removed?
excalibar001 said:
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Click to expand...
Click to collapse
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Also failing that if you are just interested in warranty service, boot from my noemmc cwm, adb shell in and execute this:
dd if=/dev/zero of=/dev/block/mmcblk1p1
dd if=/dev/zero of=/dev/block/mmcblk1p2
this will make the cyanogen logo display go away and you'll just have black screen on boot.
verygreen said:
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Click to expand...
Click to collapse
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
excalibar001 said:
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
Click to expand...
Click to collapse
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Riddleric said:
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Click to expand...
Click to collapse
it does not really matter. "repair" is a codeword for "replace" these days, it's just they get your unit in and then send you one of their pile of repaired units, then see if they can fix yours and if they can, they add it to the refurbished pile to send to whoever send their stuff in next, or to sell through some side channel.
And of course I do recommend you to go the repair/replace route (unless you want to donate a broken unit to me for further research, of course ). Who knows, you might even win the emmc lottery and get emmc that is not buggy too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
excalibar001 said:
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
Click to expand...
Click to collapse
see if you can mount /cache:
in adb shell:
mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache
if that does not work, try reformatting it:
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
see if that succeeds.
then try rebooting again without sdcard and see if that helped.
Related
First off, I need to address credit where credit is due. All credit goes out to Samuelhalff, Nootered, thecubed, iomonster, Decad3nce and anyone else involved with any of the methods I will mention.
As always, everything in this guide is completely at your own risk, I am not responsible for you messing up your device further nor am I responsible in the event that your Nook Color explodes and kills your cat, grandma, etc.
The Fatal Black Screen:
This is the issue where your Nook "refuses to boot up" usually after running Froyo (or possibly HC) off of your internal memory. This is usually caused by, but is not limited too, formatting your sdcard from within Froyo (or versions of HC prior to the flashable zip).
99.99% of the time, this does not mean your Nook is bricked in any way, what simply happened is your boot partition has become corrupted. For you newbies out there, the boot partition is what allows your Nook Color to turn on. The boot partition contains the instructions for what your Nook Color needs to do in order to start up and run.
The Fix:
Thanks to the guys that developed this neat toy, the Nook is set to boot from the sdcard before booting from the internal memory. What this means is, your nook will first search for a boot partition on the sdcard before searching for a boot partition on your Nook's internal memory. Because of this, we are able to boot and run OS software directly from the SDcard. This is how we will be fixing your "bricked" Nook Color.
First visit this link:
http://forum.xda-developers.com/showthread.php?t=922870
Download either the Rootpack, or the Clockwork Recovery image (1gb).
Next visit this link and download the 1.0.0 or 1.0.1 restore to stock files:
http://forum.xda-developers.com/showthread.php?t=914690
From this link you should also download the very last zip on the page. It is titled-flashable boot repartition zip. or something of the like. If you followed all these steps and still nothing, I would recommend flashing this as it can fix a completely screwed boot partition.
If you wish to instead restore to a pre-rooted 1.1, visit this link:
http://forum.xda-developers.com/showthread.php?t=932145
Once you have the either version of the bootable Clockwork Recovery (Rootpack or normal standard Clockwork Recovery) and a software version you would like to restore to, you must write your clockwork recovery to an sdcard to make it bootable in the Nook.
In order to do this, you must use Win32DiskImager on Windows or the command line on Mac and Linux. Follow theses instructions for writing the file to an sdcard (substitute the Clockwork file in place of Nooter):
http://nookdevs.com/NookColor_Rooting
Once the image is done writing, open up your sdcard on your computer and copy whichever restore to stock zip you choose earlier onto the card.
Now with your Nook Color unplugged from the computer, insert the sdcard and plug the Nook into the computer. Your screen should flash to life. After a short loading screen you will see a menu, using the volume keys, you are able to navigate up and down. Navigate down to the menu item that reads "mounts and storage." Navigate down and press "Format Data" then "Yes." Next do the same thing except format system. Using the power button to go back to a previous menu, return to the "mounts and storage" menu, make sure the sdcard is mounted. (If your sdcard is mounted, you will see the option to 'unmount /sdcard'. If it is not mounted you will see 'mount /sdcard'. In this case you would want to press the 'mount /sdcard' option in order to mount it. Again using the power button as the back button, navigate back to the main menu. You will see a menu item that reads "Install zip from sdcard." Select it. Now select 'choose zip from sdcard.' Now pick the zip you placed on the sdcard earlier. Scroll down to the 'Yes' option and select it. Clockwork Recovery will begin flashing the stock image to your internal memory. After a few minutes, the process should complete and you will see a message that says 'Done. Installation Complete.' From here you should remove your sdcard and navigate back to the main menu. Select the 'Reboot Now' option.
Note: Sometimes after you see the 'Done. Installation Complete.' message, Clockwork will freeze up and you will be unable to navigate back to the main menu in order to reboot. If this is the case do a hard reboot (hold the power button for 15 or so seconds so the screen turns off, then hold the power button again till it turns on).
Congratulations, you've unbricked your bricked Nook Color
TO EVERYONE STILL HAVING PROBLEMS AFTER THIS, YOU MAY/SHOULD FLASH SAMUELHALFF'S REPARTITION ZIP MENTIONED EARLIER. (LOOK UP A FEW LINES, SAME LINK AS THE 1.0.0 AND 1.0.1 RESTORE TO STOCK ZIPS)
UPDATE:
IF YOUR STILL HAVING PROBLEMS, USE THIS LINK TO INSTALL 3.0.1.0 ON INTERNAL EMMC AND THEN BOOT TO IT.
http://forum.xda-developers.com/showthread.php?t=958748
note: to do this, you need to be able to atleast boot to the N screen.
MORE UPDATE:
This link has an updated bootable CWM version on it with ext4 support. Write this to your sdcard, format /system and /data and flash CM7.
http://forum.xda-developers.com/showthread.php?t=959240
If anyone has anything to add to this tutorial, post here or IM me and I will edit the OP.
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
bartimeus said:
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
Click to expand...
Click to collapse
Not hosed at all, all you did was format the internal boot partition. When you insert the sdcard and turn the power on, your Nook will find the boot partition on the Clockwork Recovery sd card and boot to that, enabling you to do a full restore.
Well then there may be something more wrong with my nook. I have performed this 3 times and I am still just stuck at a blank black screen.
Are you sure you wrote the image to the sdcard right? Have you plugged in your nook and let it sit for a while? The Nook does have a pretty strange way of running its battery completely dead. What OS were you running before you went to restore to stock?
bartimeus said:
So I was doing the 'restore to stock' method earlier today and accidentely reformatted my boot partition is there a fix for this or am I completely hosed now?
Click to expand...
Click to collapse
Yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
nootered said:
yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
Click to expand...
Click to collapse
lmfao .
Oh dear god this just happened to me today. Thank you for posting this up.
nootered said:
Yes, it is totally effed. Just send me the nook, it's garbage now anyhow.
Click to expand...
Click to collapse
lolololololololololololol
Sorry. But if the boot partition is corrupt these files wont suffice. You'll need to flash my boot repartiton zip..
Sent from my HTC Desire using XDA App
Hi, thanks for putting this topic up and of course full credit goes to everyone who's been so helpful replying to bricked NC posts.
After 4 days of searching and trying to revive my bricked NC (tried the conventional 8 reboots, power+n methods), I believe I have a unique situation where I:
1) Can't load 128MB/1GB CWR SD ('loading' word appears, then black screen of death appears)
--tested a variation of power + n + up/down arrows (for 2-3mins or more)
--used PC USB / AC to turn device on
--used a Sandisk 256MB/2GB/4GB-CL4 and Transcend 8GB-CL6 uSDs
--used Win7, Ubuntu, EASEUS Partition Master, SD Formatter and another Android device to format the uSDs
--burned the .img using both Win32DiskImager and WinImage
2) Can't load any Froyo/HC SD roms (same results as above)
--same conditions as above
--plus tried every available version of NookieFroyo/HC out there
3) Can't access ADB at any given point. devmgmt.msc does not show any hardware with any VID of 2080. When the NC is powered on by USB, windows detects it and chimes, but that connection disconnects instantly.
Simply put, how it happened was:
OOBE -> BN 1.01 -> Autonooter -> block OTA -> Root + gApps > Rom Mgr'd CWR into eMMC -> HC v4 SD -> gApps -> manual su -> dalingrin's 1.1ghz oc kernel -> reboot success > checking on symlinks -> sudden auto-reboot to stock -> reboot done -> HC loads ok -> blacks out, unable to reboot anymore.
Has anyone else encountered this scenario? In my searches I've not come across anyone with this failure. Is it possible that my CPU has fried due to the OC to 1.1?
P.S. Sam, not able to try your methods as I'm not able to even boot anything from the SD.
I'mm in the same boat (nook) tried everything here as well as a similar guide on androidtablets and nothing. I can't boot at all. No power on, just a black screen. Any help at all would be welcome.
samuelhalff said:
Sorry. But if the boot partition is corrupt these files wont suffice. You'll need to flash my boot repartiton zip..
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
Ya, I realized that I forgot that, I'll add it in when I get home today, Thanks.
I flashed the 1.1 CWR image and all is fine now.
RileyGrant said:
Ya, I realized that I forgot that, I'll add it in when I get home today, Thanks.
Click to expand...
Click to collapse
The second link in your original post has a link to it as part of step 5.
It took a couple times of me re-writing the CWR image before I could get it to boot. Now I have it booting into CWR but when I flash the 1.0.1 recovery the nook refuses to boot. Any ideas?
edit: I am removing the micro SD before I reboot
edit 2: sam's repartition boot FTW....I think
LocalStain said:
I'mm in the same boat (nook) tried everything here as well as a similar guide on androidtablets and nothing. I can't boot at all. No power on, just a black screen. Any help at all would be welcome.
Click to expand...
Click to collapse
Glad you found this, it was my next recommendation after the charge break.
Sent from my LogicPD Zoom2 using Tapatalk
How about a dummies guide to the dummies guide for the dummies?
Or, better, WTF! ITS BRICKED!
Already did all the things suggested. Twice. Purchased last Nook Color from Best Buy yesterday, brought it home, charged it to 100%, played with it and ran Auto-Nooter 2.12.25. When I plugged in the cable to boot, it came up with the battery low-wait 15min screen. (Battery was at 100%) Tried again, same thing. Re-flashed Auto-Nooter and tried again, black screen. Nothing. Bricked. What I do get is a black screen with a flash of backlight every 20 seconds or so. Tried to re flash Auto-Nooter and boot, nothing.
Today same story, just wasted 5 hours trying: Auto-Nooter, Clockwork Recovery image, Nookie-Froyo, complete restore-1.0.1.......nothing brings up any life in the nook.
Suggestions? (Ready to return......)
Cant boot to SD
I am running the HC v4 flashed rom and I have tried numerous .img files. It is like it doest see the boot image I just created and boots into Honeycomb everytime? Any thoughts or help please sorry I am a noob.
< snip >
RileyGrant said:
Clockwork Recovery will begin flashing the stock image to your internal memory. After a few minutes, the process should complete and you will see a message that says 'Done. Installation Complete.' From here you should remove your sdcard and navigate back to the main menu. Select the 'Reboot Now' option.
Click to expand...
Click to collapse
< /snip >
After spending the better part of four hours trying to solve a fatal error with my reverted-to-stock NC, I ran across the fix for the problem.
First of all, the problem: After diagnosing a bad NC USB cable that was causing USB device mounting issues within Windows, I began to encounter a fatal error modal dialog that stated, "Your NOOKcolor encountered a problem that requires a system restart" at the home screen. No matter what I did in terms of formatting & re-imaging, the message remained. In an effort to fix it, I decided to restore to stock 1.1 using a bootable CWR SD image. After following the instructions to the letter, including formatting /System and /Data after shooting the stock 1.1 image onto the NC, the message persisted. I then attempted to back-rev to 1.01 and 1.0, with similar results.
I suspect that what happened to me was that during the process of diagnosing the USB cable issues, I booted from a uSD card that had AutoNooter 3.0 on it, and interrupted the process mid-stream, thus causing data or partition corruption. I'm not a Nook expert, so I'm not certain of this, but based on my general experience level, that's what it 'felt' like.
How did I finally recover? As a last step to the standard revert-to-stock process, after rebooting from CWR, I used a three-finger salute to reset the device. It was only after I did this that the fatal error disappeared.
Just thought that I'd post this in case anyone has a similar experience and is desperate for something else to try.
DS
My Boot will not boot no matter what I do. I encountered this issue after flashing to phiremod v4, which worked beautifully until I decided to free up some storage space on my SD card and format it through the Nook. The next time I tried to boot, I got the dreaded black screen.
I've burned Clockwork Recovery (4gb v .7) onto the SD card and copied the Nook Color V1.1.0_r2 rom (found here http://forum.xda-developers.com/showthread.php?t=932145). From there, I formatted the data, system, and cache, then installed the rom from the SD card. Everything went through smoothly, until I rebooted the Nook (with the SD card out). Nothing happens! The Nook simply will not reboot without the SD card inserted. Even if it boots (with the SD card) it just sends me back to Clockwork Recovery.
I also tried recovering the Nook through ADB (using the steps found here http://mrm3.net/2011/01/24/113/). I install everything, but I cannot locate the ADB device in the device manager. I've even used the .bat file to auto installs ADB, but it is still not found in the device manager.
I've read that it is nearly impossible to brick a Nook, but I'm not sure what else to try. I'm a Android noob, so please bear with me. TIA!
Fairly certain I read about a bug with formatting the SD card on the NC, that it would format the internal memory instead. I would imagine you will need to flash a new image to the internal memory (should be stock image floating around here somewhere).
No worries, you are most likely NOT bricked. There are hundreds of posts about people thinking they bricked their device.
First thing is first, IF YOU READ THE POST IT SPECIFICALLY STATES DO NOT FORMAT THE SDCARD USING THE NOOK AS IT WIPES THE /BOOT
My suggestion to you is do some research on XDA there are PLENTY of posts about "unbricking" your device.
I have only seen 1 nook be bricked, and it was hardly bricked because it could be booted from an SDCard.
Try following the instructions here to return back to the stock OS:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Reneg4d3 said:
No worries, you are most likely NOT bricked. There are hundreds of posts about people thinking they bricked their device.
First thing is first, IF YOU READ THE POST IT SPECIFICALLY STATES DO NOT FORMAT THE SDCARD USING THE NOOK AS IT WIPES THE /BOOT
My suggestion to you is do some research on XDA there are PLENTY of posts about "unbricking" your device.
I have only seen 1 nook be bricked, and it was hardly bricked because it could be booted from an SDCard.
Try following the instructions here to return back to the stock OS:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Click to expand...
Click to collapse
Yeah, I realize that was a big no no. I am unable to perform any of the steps in the link you provided because my nook doesn't even reach the 'Welcome to the future of reading' screen. Also, I can't try method 2 because ADP is not working properly.
I should mention that I also tried samuelhalff's first method to no avail. Any other ideas?
So you CAN boot from an SDCard correct? Only way to boot again is to flash the boot file...
Reneg4d3 said:
So you CAN boot from an SDCard correct? Only way to boot again is to flash the boot file...
Click to expand...
Click to collapse
Yes, I can boot (to Clockwork Recovery) if the SD card is inserted and the power cord is inserted and I hold the power button for 10 seconds. If I install a rom from the SD card, doesn't it flash the boot file? If not, how do I flash the boot file?
I know you said you tried Sams method, I would re-read how to flash his boot repartition file found on his froyo on emmc thread
thadeus_d3 said:
Yes, I can boot (to Clockwork Recovery) if the SD card is inserted and the power cord is inserted and I hold the power button for 10 seconds. If I install a rom from the SD card, doesn't it flash the boot file? If not, how do I flash the boot file?
Click to expand...
Click to collapse
Here's the link to the boot file. I did the same thing not long ago (formatted SD from within CM7) and I fixed it by flashing this file to repartition the boot.
It's the last link in the OP of this thread (repartition-boot-with-stock.zip):
http://forum.xda-developers.com/showthread.php?t=914690
If that doesn't work, he has a couple of restore to stock methods in that thread as well.
C Dippa said:
Here's the link to the boot file. I did the same thing not long ago (formatted SD from within CM7) and I fixed it by flashing this file to repartition the boot.
It's the last link in the OP of this thread (repartition-boot-with-stock.zip):
http://forum.xda-developers.com/showthread.php?t=914690
If that doesn't work, he has a couple of restore to stock methods in that thread as well.
Click to expand...
Click to collapse
YES! This did it! I missed this link somehow. Many thanks to all that helped.
Ok, now I'm stuck on the screen that says "Contains Reader Mobile technology by Adobe Systems Incorporated". Did this happen to you C Dippa? I'm going to try a reset and see if that helps.
thadeus_d3 said:
Ok, now I'm stuck on the screen that says "Contains Reader Mobile technology by Adobe Systems Incorporated". Did this happen to you C Dippa? I'm going to try a reset and see if that helps.
Click to expand...
Click to collapse
Nope...it just booted up, may have taken a little longer.
Any luck with it?
Yeah, I had to do the 8 failed boot attempts to bypass that screen, then re-root. Now, I'm all set! Phiremod is installed again.
Glad to have helped! Happy nooting!
Sent from my Droid using Tapatalk
So I was going to try and change roms. And I couldn't boot into recovery, so I made a recovery bootable sd card. Me in my glorious thinking decided I would just use it to install the internal recovery and my rom.
Once the sdcard booted into recovery I did a system/data/cache wipe. then installed clockworkmod. It succeeded, so I went to the rom I had on my card. It failed. I said I know, I'll power down, take the sdcard put cm on it and try again. wrong.
Now I can't boot into recovery on either an sdcard or without and turning on the nook regularly flashes loading and goes to the page that says android with the flashing underscore.
so as far as I can tell I have no operating system, because I wiped system. and I'm not sure what is up with my recovery.
I'm looking at this page,
http://forum.xda-developers.com/showthread.php?t=914690
but I'm not sure how I would flash the zip if I can't boot into anything?
any ideas would be appreciated
constellanation said:
So I was going to try and change roms. And I couldn't boot into recovery, so I made a recovery bootable sd card. Me in my glorious thinking decided I would just use it to install the internal recovery and my rom.
Once the sdcard booted into recovery I did a system/data/cache wipe. then installed clockworkmod. It succeeded, so I went to the rom I had on my card. It failed. I said I know, I'll power down, take the sdcard put cm on it and try again. wrong.
Now I can't boot into recovery on either an sdcard or without and turning on the nook regularly flashes loading and goes to the page that says android with the flashing underscore.
so as far as I can tell I have no operating system, because I wiped system. and I'm not sure what is up with my recovery.
I'm looking at this page,
http://forum.xda-developers.com/showthread.php?t=914690
but I'm not sure how I would flash the zip if I can't boot into anything?
any ideas would be appreciated
Click to expand...
Click to collapse
Try Re-burning the Newest CWR to to your SD card, maybe your SD card has gotten corrupted
CWR 3.0.1.0 http://forum.xda-developers.com/showthread.php?t=971197
Also http://forum.xda-developers.com/showthread.php?t=949699
trying out your steps and I think I've realized the problem... but I can't figure out why it's doing what it's doing. I can't seem to correctly use dd to burn the image to the sdcard anymore... it worked the first 3 times I did with no problem. But now it's not working...
is there a certain format these cards need to be in? fat32, ext2/3/4?
constellanation said:
trying out your steps and I think I've realized the problem... but I can't figure out why it's doing what it's doing. I can't seem to correctly use dd to burn the image to the sdcard anymore... it worked the first 3 times I did with no problem. But now it's not working...
is there a certain format these cards need to be in? fat32, ext2/3/4?
Click to expand...
Click to collapse
what OS are you using? Linux? I don't know anything DD in Linux sorry.
I have been using Windows and Win32DiskImager
I think they are Fat32 images.
Maybe try Reseting the computer, and trying again.
Yeah it keeps writing phantom images to the directory that is supposed to be where my sdcard is located... and not on to the sdcard itself...
and yeah it's linux... I'm baffled... I think I will try a restart not only on my computer but on my day...
if any linux users have any advice on writing this image I'd appreciate... goodnight all I will try again tomorrow at some point
thanks for the help though!
constellanation said:
Yeah it keeps writing phantom images to the directory that is supposed to be where my sdcard is located... and not on to the sdcard itself...
and yeah it's linux... I'm baffled... I think I will try a restart not only on my computer but on my day...
if any linux users have any advice on writing this image I'd appreciate... goodnight all I will try again tomorrow at some point
thanks for the help though!
Click to expand...
Click to collapse
Make sure your Burning to the device directory and not the mount folder. (ie: /dev/sdc not /media/cardstick )
____________________________________________________
Sent from Nookie Froyo using Tapatalk
well that was what I was doing wrong writing the image. However the nook still won't boot from them...
It just goes to the dark screen that says android in light blue with a blinking cursor at the bottom left of the screen...
constellanation said:
well that was what I was doing wrong writing the image. However the nook still won't boot from them...
It just goes to the dark screen that says android in light blue with a blinking cursor at the bottom left of the screen...
Click to expand...
Click to collapse
well at least you boot Partition is intact, but sounds like you have no system or data partition.
Its very odd that the Nook wont boot off the SD card, it should look for that first in the boot Process, all i can think of is that your SD card is still not right.
I tried two different cards. The clockwork 4gb version and the 8gb version. Both looked right with the appropriate files. :/
So I don't think, though it's still a possibility, that it's the card itself
I think in the morning I'll try this http://forum.xda-developers.com/showthread.php?t=922870]
In combination with this http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151
Specifically the reverting to aosp part. To tired to deal with cli right now.
Edit: if that fails I may try this http://forum.xda-developers.com/showthread.php?t=914690
therealguppy said:
Try Re-burning the Newest CWR to to your SD card, maybe your SD card has gotten corrupted
CWR 3.0.1.0 http://forum.xda-developers.com/showthread.php?t=971197
Also http://forum.xda-developers.com/showthread.php?t=949699
Click to expand...
Click to collapse
Silly question as I haven't been able to find the info as of yet. Could you explain how we can go about burning the newest CWR ( ie 3.0.1.0 ) so we have a bootable sdcard running it ( 3.0.1.0) instead of the older 3.0.0.6 that all the burnable imgs are currently. I looked threw the thread and I don't see any instructions or talk about how to update a bootable sdcard. It only seems to discuss updating the recovery of the eMMC using ADB or the *.zip file that is linked. Any input,advice, or link would be greatly appreciated. Peace
I must say that the monster rootpack is amazing, and I am up and running
seriously when all else fails (or if you just want to cut down to it) http://forum.xda-developers.com/showthread.php?t=922870
anyway problem solved, running cm7 rc1 right now!
OK to start I have CM7.1 on my eMMC works fine for many months. I want to install MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer ROM and it does not seem to work. Using CWM 3.2.0.1 flashing looks successful but when I reboot CM&.1 is still on the eMMC.
Tried doing a reset to default using EVRY technich suggested on these forums. No Go.
Using ADB I thought I would manually delete and push the system files over. I mount the system partition /dev/block/mmcblk0p5 and removed the existing files then pushed the new system files. But once I unmount and remount it reverts to the old files. The changes don't write dispite seeing the differences with an ls -al in ADB before the umount.
So I thought I would check the partitions and using fdisk via ADB. Deleted partitions 5, 6,7,8 and rebuilt them but when I write I get.
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
I also used the 1 - 5 - 6 - 7 - 8 fix and format zips with no joy.
I can boot to MIUI via SD but I want to put this on the eMMC.
Any ideas on how to fix this?
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Edit: oh, you changed the version in your original post to 3.2.0.1. That version is ok.
leapinlar said:
Yes, the first thing you do is upgrade that CWM. It is too old. You can get a new bootable CWM on my tips thread linked in my signature. Then I would reflash my repair zips as instructed in my partition repair thread. (Sounds like your partition 2 is ok, skip that). Don't forget to reboot between the repair and reformat. Then flash your rom with the new CWM.
Click to expand...
Click to collapse
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
The partition table has been altered!
Calling ioctl() to re-read partition table
fdisk: WARNING: rereading partition table failed, kernel still uses old table: Device or resource busy
Click to expand...
Click to collapse
Which matches the results I was seeing from adb.
rodneyshupe said:
Thanks for trying to help.
OK created a bbotable SD using the CWM-based Recovery v5.5.0.4 (CWM-5.5.0.4-bootable_SD.zip from your tips page)
Used that to apply NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip
Rebooted into CWM-based Recovery v5.5.0.4
Applied NookColor-emmc-format-partitions-5-6-7-8.zip
The applied MIUI.us_encore_1.9.16_Eng_Deo_ZipA_Signed_andmer.zip
Rebooted the eMMC and still running CM7
I then retried the repartitioning and the following message was listed when I checked the log:
Which matches the results I was seeing from adb.
Click to expand...
Click to collapse
When you boot to your SD version of your ROM, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip. They act like they have been written to, but when you come back, nothing has changed.
leapinlar said:
When you boot to your SD version, can you save anything to the emmc media partition? I am wondering if somehow your emmc chip became read only. I have had that happen to my SD cards before, so it may be possible that it happens to your embedded chip.
Click to expand...
Click to collapse
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
rodneyshupe said:
OK Booted the SD with MIUI on it and was able to (or what seemed to be) save a file to the eMMC
BUT when I rebooted it was gone. It is like the write does not take on reboot.
I can even edit the file and it seems fine but the file is gone once I reboot.
It is like the changes are cached but not committed.
So I thought I would try creating the file and even edited the file from USB after booting the MIUI SD. Then when I stopped and restarted USB connection and then the file was gone.
So Somehow the eMMC is readonly.
So how do I fix that?
Click to expand...
Click to collapse
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard of anybody that this happened to their embedded chip. Sorry.
leapinlar said:
That is exactly what happened to my SD. Looked like everything took, but take card out and put back in and changes did not last. This happened on my phone SD. No amount of trying different PCs, different device readers, formatting programs, partition managers, nothing would work. I could read and copy things from it, but never got it to accept anything. I just bought a new one. I know that won't work on your embedded chip.
You are lucky at least you can use your SD to run things. I have found there is no significant difference between running on SD and emmc.
Maybe someone else has some info how to fix it. I searched the web for a long time looking for solutions and found nothing. One other user here on XDA has reported the same symptoms on his SD, but I never heard anybody that this happened to for their embedded chip. Sorry.
Click to expand...
Click to collapse
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
rodneyshupe said:
Thanks for trying to help. It is appreciated.
In the case of your SD did you try burning an image over top?
I was thinking if I had a complete image of the eMMC I might be able to use dd via ADB to overwrite the whole thing. Back up the files from partition 2 first and then write them back once it was finished.
Thoughts?
Problem is where could I get a "good" image of the entire eMMC?
Click to expand...
Click to collapse
For my SD I tried everything. Images, formatting, partitioning, etc. Nothing could be written to the device.
You can make your own images of emmc by dding in reverse and write emmc partitions to your SD via adb. But if it is truly read only like my SD was, you will be able to write nothing back no matter what tool you use.
Yea I was hopping I could get an image of the entire working eMMC that included the partition tables and see if that worked in case the problem is related to a setting in the partition table.
Hi there,
i'm having huge problems getting my HD+ fixed.
what happened: shut down out of nowhere, didnt boot the ROM, just TWRP recovery loops. Flashing and wiping did nothing good to the device. I always got errors when trying to install zips (data1 not found or something like this), but somehow the installation of CWM worked.
At the moment: CWM 6.0.4.5, when booting into recovery, under mounts/storage it says that system, data rom and bootdata arent mounted (but i can mount them from there).
trying to flash a new ROM or other zips doesnt work: Status 7.
I've read several threads over here, but I'm still confused and dont know how to save my HD+. Which exact files should i flash in which order? How to get rid of status 7?
Thank you so much.
Greetings
Richy
ohrenstaebchen said:
Hi there,
i'm having huge problems getting my HD+ fixed.
what happened: shut down out of nowhere, didnt boot the ROM, just TWRP recovery loops. Flashing and wiping did nothing good to the device. I always got errors when trying to install zips (data1 not found or something like this), but somehow the installation of CWM worked.
At the moment: CWM 6.0.4.5, when booting into recovery, under mounts/storage it says that system, data rom and bootdata arent mounted (but i can mount them from there).
trying to flash a new ROM or other zips doesnt work: Status 7.
I've read several threads over here, but I'm still confused and dont know how to save my HD+. Which exact files should i flash in which order? How to get rid of status 7?
Thank you so much.
Greetings
Richy
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2062613
Go to section 6 and restore to stock.
ohrenstaebchen said:
Hi there,
i'm having huge problems getting my HD+ fixed.
what happened: shut down out of nowhere, didnt boot the ROM, just TWRP recovery loops. Flashing and wiping did nothing good to the device. I always got errors when trying to install zips (data1 not found or something like this), but somehow the installation of CWM worked.
At the moment: CWM 6.0.4.5, when booting into recovery, under mounts/storage it says that system, data rom and bootdata arent mounted (but i can mount them from there).
trying to flash a new ROM or other zips doesnt work: Status 7.
I've read several threads over here, but I'm still confused and dont know how to save my HD+. Which exact files should i flash in which order? How to get rid of status 7?
Thank you so much.
Greetings
Richy
Click to expand...
Click to collapse
That v6045 of CWM is causing the status 7 errors. You need an older version for older zips. Go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a. Then you can flash whatever you want, including that plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Hi,
thanks for your answers.
I made a CWM SD as described. I put it into my HD+. But how do I avoid my Nook booting into the already-installed emmc-6.0.4.5? I rebooted it several times and always landed in the 6.0.4.5, so I assume i'm not in the SD-CWM which i desperately need. I also pushed "NookHDplus-CWM-6036-for-internal-memory-rev1-(09.22.13).zip" to the internal memory and tried to flash this, but no chance - status 7.
As I see it, the problem is to get into the older CWM-SD because the 6.0.4.5 won't let me install earlier CWMs (status 7)?
ohrenstaebchen said:
Hi,
thanks for your answers.
I made a CWM SD as described. I put it into my HD+. But how do I avoid my Nook booting into the already-installed emmc-6.0.4.5? I rebooted it several times and always landed in the 6.0.4.5, so I assume i'm not in the SD-CWM which i desperately need. I also pushed "NookHDplus-CWM-6036-for-internal-memory-rev1-(09.22.13).zip" to the internal memory and tried to flash this, but no chance - status 7.
As I see it, the problem is to get into the older CWM-SD because the 6.0.4.5 won't let me install earlier CWMs (status 7)?
Click to expand...
Click to collapse
Can you boot 11? I have found my new nook won't boot from the SDcard unless I boot unmount the old card and mount the new one before booting.
Seems as if i have the problem lots of other users have encountered: http://forum.xda-developers.com/showthread.php?t=2288688&page=6
When I installed CWM/CM the first time, I didnt have any problem with this, using the exact same hardware. Is it even possible to boot right from SD with my emmc-installed 6045, or is it just bad luck like those other guys in the thread mentioned?
Sideload doesnt work neither, CWM 6045 tells me to begin sideloading, but ADB gives me the whole "help"-listing instead (as if I used a wrong command or something: adb sideload filename.zip) of a working sideload-process. When I start sideload in CWM, "adb devices" gives me "host", dont know if this is good.
jpisini said:
Can you boot 11? I have found my new nook won't boot from the SDcard unless I boot unmount the old card and mount the new one before booting.
Click to expand...
Click to collapse
You mean I should try to boot CM11 from SDcard (i assume i end up with the same problem that the Nook doesnt want to boot from SD-CWM)? Where should I unmount the card? I dont think i'm getting your idea
Thank you!
ohrenstaebchen said:
Seems as if i have the problem lots of other users have encountered: http://forum.xda-developers.com/showthread.php?t=2288688&page=6
When I installed CWM/CM the first time, I didnt have any problem with this, using the exact same hardware. Is it even possible to boot right from SD with my emmc-installed 6045, or is it just bad luck like those other guys in the thread mentioned?
Sideload doesnt work neither, CWM 6045 tells me to begin sideloading, but ADB gives me the whole "help"-listing instead (as if I used a wrong command or something: adb sideload filename.zip) of a working sideload-process. When I start sideload in CWM, "adb devices" gives me "host", dont know if this is good.
You mean I should try to boot CM11 from SDcard (i assume i end up with the same problem that the Nook doesnt want to boot from SD-CWM)? Where should I unmount the card? I dont think i'm getting your idea
Thank you!
Click to expand...
Click to collapse
On my new replacement Nook I can't boot to any SDcards no matter if they are CWM or CM unless I boot into a working OS unmount the card I have in there eject it and put another one in while still booted then do a reboot it then boots every time off the new card.
Now the stock OS is installed. But I have problems getting into the SD-CWM. At the moment, it doesnt boot at all when the SD card is my Nook. Very strange behaviour.
I don't have a second SD-card, so I can't try that.
ohrenstaebchen said:
Now the stock OS is installed. But I have problems getting into the SD-CWM. At the moment, it doesnt boot at all when the SD card is my Nook. Very strange behaviour.
I don't have a second SD-card, so I can't try that.
Click to expand...
Click to collapse
My Nook has Version 2.2 of B&N Software. I have to restore the Nook to get it to boot from SD Card. I am new so I am having issues finding the right combination of files to install the nightly build of CM11 without getting a status 7. There are so many builders and files on this forum and everything I have tested so far has been a no go. Can someone give me a specific set of files that will work with the nightly build of CM 11? It would be greatly appreciated!
Create a bootable SD card: http://forum.xda-developers.com/showthread.php?t=2062613
- format SD card with SDFormatter
- set the only partition to "active" with MiniTool Partition Wizard
- "flash"/"burn" a bootable-CWM-image, for me it OINLY worked with "NookHDplus-bootable-CWM-6028-for-stock-small-rev4-(05.15.13).zip" (boots every time to SD-CWM, using the 4GB-version didnt work even after 30+ trys
- add your CM11-zip to the SD card using your windows explorer
- add flash_recovery_ovation_CWM_6.0.4.5b_internal.zip from http://goo.im/devs/succulent/ovation/recovery
- put it in your Nook, boot it up, if you're lucky you see CWM
- flash the 6.0.4.5b CWM, then you're ready to flash the newest CM11. If you want to flash an older version of CM such as 10.1 or 10.2, you need a lower CWM version to avoid status 7 errors.
- flash CM11
That was my way to CM11, but there is one huge problem at the moment: CM won't boot, it loops the CM-bootlogo infinitely. several wipes did nothing, still looping. My CWM always says on bootup that /system/ (besides others) isnt mounted, but I can mount them without a problem, flashing the CM-ROM doesnt produce errors.
I don't know how to avoid the CM bootlogo-loop
Had to reboot about 8 times to get my nook to read 32 gig SD card.
leapinlar said:
That v6045 of CWM is causing the status 7 errors. You need an older version for older zips. Go to my HD/HD+ CWM thread linked in my signature and make a bootable CWM SD per item 1a. Then you can flash whatever you want, including that plain stock zip from item 6.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I had to reboot my nook at least 8 times to get it to read my SD card so I could install succulents 07FEB2014, using TWRP, because I was getting error 7 when installing via CWM.6.0.26 If I had known better, I would have copied the 07FEB2014 (stable) build to my internal memory and installed with TWRP from there. I somehow got into a loop where I could only boot into TWRP, finally being able to install seemed to fix this. I am loving the 07FEB2014 build. Keep up the good work gentle men and women! I really love this build.