Related
Just a heads up: The instructions for @samuelhalff 's Honeycomb emmc ROM include this:
Boot with SD inserted, go to 'mounts and storage', and:
- format system, then data and THEN format boot (CWR may crash, simply hard reboot, format should have worked).
If you do format /boot, you will lose the ability to boot into CWR. That may be okay with you, but after trying Honeycomb on my emmc I went back to Froyo, and couldn't figure out why I couldn't boot into recovery.
See this thread: http://forum.xda-developers.com/showthread.php?t=883175&page=103
if you want to restore the original /boot files.
Q: do I have to start over per the thread above or can I just push files to my /boot via ADB? or just boot from SD and restore that way if files are available?
Thanks!
you can boot to cwr via sdcard. that's how those of us on HC do it to make backups and such. works perfect.
Yep I *can* boot to CWR on SD. That's how I installed Honeycomb to the emmc. What I'd like is to restore CWR to /boot
Thanks though.
ahh. sorry, misunderstood.
you could try it... though from what i've read, it's risky. they say it's safer to just run it from the sd card.
if it works out well for you, please post up!
Ran it for a day. Too many force closes for me, but really cool that it runs at all!
Sent from my Nook Color (zoom2) using Tapatalk
My main concern is that I followed the instructions to install Honeycomb via CWR and it worked fine, but I didn't know that reinstalling from scratch ie. nook 1.x would be required since just reinstalling @cicada's Froyo port does not replace all of /boot
No tragedy. Restore just takes a bit longer.
If anybody can tell me how to restore /boot without wiping my current Froyo install that would be pretty nifty.
@xawen to the rescue!
Thanks!
http://forum.xda-developers.com/showthread.php?t=958748
I noticed more people are having same issue as me and I wanted to create a thread to find the solution.
I was running CM7 RC4 / OC 40311 - It was running fine and one day system hung and so I rebooted and that was it.
Symptom :
System boots and pass the "Touch the future Reading" and displays "ANDROID _" on the bottom of the screen and after 10-15 sec it reboots and loop this process.
Things I tried so far :
CWR 3.0.0.5
- Repratition to stock nook.
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3
- Try to restore from back up I made
- Nothing works but goes back to boot loop
CWR 3.0.0.6 - One I got from CM7 install to emmc thread
- System format works
- Install latest nightly
- Restore from back up
- ADB can't find device - This is odd and couldn't find a way to fix it yet.
- Tried to install Stock zip but going back to CM7 boot loop
CWR 3.0.1.0
- Can't format data/system
- ADB to delete partitions and create them again but it doesn't help
- Tried all zip files to bring it back to stock - no go
- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.
- Deleted partitions and reboot but some how I got back to CM7 loop
If you are having same issue please post and share your experiences so we can find the solution!!!
tuxhacker said:
Symptom :
System boots and pass the "Touch the future Reading" and displays "ANDROID _" on the bottom of the screen and after 10-15 sec it reboots and loop this process.
Click to expand...
Click to collapse
This means the kernel is loading, and most likely the init.encore.rc is running as well. Have you tried grabbing a log from adb logcat? Or perhaps checking if the shell works?
tuxhacker said:
Things I tried so far :
CWR 3.0.0.5
- Repratition to stock nook.
Click to expand...
Click to collapse
How are you repartitioning?
tuxhacker said:
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
Click to expand...
Click to collapse
What is the error?
tuxhacker said:
CWR 3.0.1.0
- Can't format data/system
Click to expand...
Click to collapse
Again- if its getting an error, what is that error? Have you tried formatting manually?
tuxhacker said:
- ADB to delete partitions and create them again but it doesn't help
Click to expand...
Click to collapse
Errors? Logs?
You have to be more specific.
- I was flashing "repartition-boot-with-stock.zip" also tried to delete the partitions using fdisk - from adb shell
- And I was getting "Error formatting / system!" and "Error formatting /Data!" from CWR format system and format data
I also tried to format it manually using "mke2fs /dev/block/mmcblk0p1,2 and 3..."
And could you please tell me how to get the log?
Thank you.
have you tried booting off an cwr 3.0.1.0 bootable sd card and formatting reinstalling?
john10101 said:
have you tried booting off an cwr 3.0.1.0 bootable sd card and formatting reinstalling?
Click to expand...
Click to collapse
Yes I have. I tried several times. It seems like my nook is a read only device now. It won't take any changes.
tuxhacker said:
Yes I have. I tried several times. It seems like my nook is a read only device now. It won't take any changes.
Click to expand...
Click to collapse
unpossible!
chisleu said:
unpossible!
Click to expand...
Click to collapse
Here's one example. I did this from CWR 3.0.1.0.
- Mount mmcblk0p3 to emmc
- Copied factory.zip to emmc
- ls -l /emmc to check the new file
- umount /emmc
- Mount /emmc again
- ls -l as you can see old file date again.
Code:
~ # mount -w /dev/block/mmcblk0p3 /emmc
mount -w /dev/block/mmcblk0p3 /emmc
~ # mount
mount
/dev/block/mmcblk0p3 on /emmc type ext2 (rw,errors=continue)
~ # exit
C:\Program Files\Android\android-sdk\platform-tools>adb push factory.zip /emmc
3779 KB/s (168335604 bytes in 43.492s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # ls -l /emmc
ls -l /emmc
-rw-rw-rw- 1 root root 168335604 Apr 17 04:06 factory.zip
drwx------ 2 root root 12288 Oct 23 05:27 lost+found
-rw-rw-rw- 1 root root 2567 Nov 17 22:27 rombackup.zip
~ # umount /emmc
umount /emmc
~ # mount /dev/block/mmcblk0p3 /emmc
mount /dev/block/mmcblk0p3 /emmc
~ # ls -l emmc
ls -l emmc
-rwxrwxrwx 1 root root 168332495 Nov 11 23:35 factory.zip
drwx------ 2 root root 12288 Oct 23 05:27 lost+found
-rw-rw-rw- 1 root root 2567 Nov 17 22:27 rombackup.zip
~ #
May I ask why you had to mess around with the partitions at all?
lechiffre said:
May I ask why you had to mess around with the partitions at all?
Click to expand...
Click to collapse
It was keep rebooting itself so I was trying to reflash CM7 but didn't work. Next I was going back to stock to start over and that didn't work. Found one thread about DD boot.img, system.img and factory.zip to mmcblk0p3 then 8 failed attempt to restore to stock. etc...
I'm sure that while I was trying to fix I made more mess.
I did adb logcat and got the permission denied error.
Code:
C:\Program Files\Android\android-sdk\platform-tools>adb logcat
- waiting for device -
- exec '/system/bin/sh' failed: Permission denied (13) -
Did you try going into clockwork recovery and using the fix permissions option?
tuxhacker said:
It was keep rebooting itself so I was trying to reflash CM7 but didn't work. Next I was going back to stock to start over and that didn't work. Found one thread about DD boot.img, system.img and factory.zip to mmcblk0p3 then 8 failed attempt to restore to stock. etc...
I'm sure that while I was trying to fix I made more mess.
Click to expand...
Click to collapse
I still don't get why you decided the partitions were faulty.
This might not help you now but might help others in you situation. IMO the process should be when you encounter bootlooping:
1. Reflash current OS using CWR 3.1.0 uSD.
2. If Step 1 fails, using CWR 3.1.0 uSD: format /system /data /cache. Attempt to install CM7. If CM7 install fails, attempt to install stock.
3. ***Requires a a working CWR backup which should contain your original boot partition***
If Step 2 fails, using CWR 3.1.0 uSD: format /system /data /cache and /boot. Restore stock /boot partition only via advanced restore. Attempt to install CM7 or stock.
4. ONLY if the previous steps fail should you even touch any partition tool. I've never had to use any, but I've never messed with the partitions in the first place (ie double booting off eMMC).
Just wanted to share that getting stuck on the boot screen may not have anything todo with what or how you've flashed.
On a fresh install/flash of CM7 I can reboot just fine as many times as I want. As soon as I restore all my apps and reboot I get stuck on the boot screen.
So SOMETHING amongst all the apps I have backed up gets me stuck on the boot screen. Really don't want to go through a reboot for each app one at a time though
FIXED - wipe battery status in CWM
This problem seems to occur when the battery runs out, Nook is plugged in and then it hangs at "the future..."
So to fix this problem, boot into CWM (using CWM for SD) and go to Advanced-Recovery and Wipe Battery Status. Remove the CWM SD and go back to the root menu and reboot.
Your CM7 would boot now just fine. I don;t know what the problem is yet, but that seems to fix it. It saved me from reinstall.
the Nook gets into this state only when the battery is completely drained.
TuxHacker, did you ever resolve your issue of what seems to be the internal memory being in a write-protected state? I'm in the exact same boat you are but instead of CM7 I got CWR 3.0.0.5 installed on my boot and brianf's custom froyo installed.
I agree it seems like the device is now write protected as I've mounted boot/system/media and deleted everything in there, ls'd to double check, but once I remount, all the old stuff is back there again.
I also tried using samuelhalff's NookUMC app to mount all the partitions in windows, deleted everything, and upon remount, all the files are back. The NookUMC app was the one I initially used to copy a bunch of mp3's and vids to the media partition in the first place and now this partition behaves as if it was write-protected as well.
lechiffre said:
I still don't get why you decided the partitions were faulty.
This might not help you now but might help others in you situation. IMO the process should be when you encounter bootlooping:
1. Reflash current OS using CWR 3.1.0 uSD.
2. If Step 1 fails, using CWR 3.1.0 uSD: format /system /data /cache. Attempt to install CM7. If CM7 install fails, attempt to install stock.
3. ***Requires a a working CWR backup which should contain your original boot partition***
If Step 2 fails, using CWR 3.1.0 uSD: format /system /data /cache and /boot. Restore stock /boot partition only via advanced restore. Attempt to install CM7 or stock.
4. ONLY if the previous steps fail should you even touch any partition tool. I've never had to use any, but I've never messed with the partitions in the first place (ie double booting off eMMC).
Click to expand...
Click to collapse
I can't speak for TuxHacker, but mucking around with the partitions seems to be a last ditch effort to at least *change* anything on the device. I've followed a few guides on here about showing the partition table and mine matches a stock partition table. I haven't gotten around to actually modifying any of the partitions yet though...
In all of your steps, the first sub-step is to format one or all of /system /data /cache /boot. This is precisely the step that fails for us with "Error Formatting /system!" or any of the others The only CWR that it doesn't fail on is CWR 3.0.0.6, but any flashes don't take, the NC just reverts back to what it was just before the system decided to go read-only.
I'm running off SD now but that is a pretty crappy experience... if anyone can fix the mess we got ourselves into I will def buy that guy a cold one!
drazil22 said:
In all of your steps, the first sub-step is to format one or all of /system /data /cache /boot. This is precisely the step that fails for us with "Error Formatting /system!" or any of the others The only CWR that it doesn't fail on is CWR 3.0.0.6, but any flashes don't take, the NC just reverts back to what it was just before the system decided to go read-only.
I'm running off SD now but that is a pretty crappy experience... if anyone can fix the mess we got ourselves into I will def buy that guy a cold one!
Click to expand...
Click to collapse
Yes. And on CWR 3.0.0.6 I can't connect via ADB so can't do much with it. On CWR 3.0.1.0 and CWR 3.0.0.5 I can connect via ADB but can't format. I tried all the ADB connect tips and tricks but no go.
I think it coubd be a permission issue since I get - exec '/system/bin/sh' failed: Permission denied (13) - when I tried ABD logcat while its rebooting.
I'm also running off SD now and it is really bad.
I'm in the same boat as you guys and I just wanted to add my two cents.
I've tried multiple times to use the partitioning tools that drazil22 is talking about, but every time I reboot, the partitions come back. What is weird is that while I'm still in adb, after I've written the partition table back to the device, is that it shows the new partition table when I tell it to print it out. I can exit all the way out of adb and, unless I've rebooted my nook, the partitions are back to the way they were. However, once I reboot my nook, the partitions come back...
I've gone as far as deleting every single partition and then rebooting just so that I could have a brick to take back to B&N, but the stupid partitions keep coming back...
lol that's what I was thinking too... brick the thing and get the store to reflash it, as someone else with a bricked nook did. I think the store must have another utility or device to reflash it back to stock.
The weird thing is any changes I make stay for the session until I unmount. I tried to copy the system.img and boot.img which is a little over 500MB to the /media partition (mmcblk0p8) but because I filled it with mp3's and videos, only about 200MB was free and of course the adb push errored out saying not enough space. I then navigated to the /media partition, deleted a bunch of videos and was able to adb push the two files over. I was also able to run the dd commands and got the expected results. Upon reboot, of course nothing got dd'd, the two .img files I copied to /media were gone, and the videos I deleted to free up space were back!
I was also hoping that with the new B&N update to 1.20, they might have released a flashing utility but I guess that was wishful thinking...
Edit: one other peculiar thing I noticed is that when I use adb when booted into CM7 (using the SD), it shows the serial number as 11223344556677. When I use adb booted up using the CWR on my boot partition, or with a bootable SD, it shows the actual serial number written on the sticker behind the sd cover.
getllamasfast said:
I'm in the same boat as you guys and I just wanted to add my two cents.
I've tried multiple times to use the partitioning tools that drazil22 is talking about, but every time I reboot, the partitions come back. What is weird is that while I'm still in adb, after I've written the partition table back to the device, is that it shows the new partition table when I tell it to print it out. I can exit all the way out of adb and, unless I've rebooted my nook, the partitions are back to the way they were. However, once I reboot my nook, the partitions come back...
I've gone as far as deleting every single partition and then rebooting just so that I could have a brick to take back to B&N, but the stupid partitions keep coming back...
Click to expand...
Click to collapse
This is odd, but I dont think this is limited to CM7 as I've seen it happen with different phones running AOSP. Over on the Evo there was numerous accounts of peoples devices suddenly rebooting and then getting stuck in a bootloop, all partitions seemed to be corrupted including the recovery partition and there was absolutely no way to write to the system anymore. Complete booting brick. No one was able to find the cause and no one was able to find a fix.
RileyGrant said:
This is odd, but I dont think this is limited to CM7 as I've seen it happen with different phones running AOSP. Over on the Evo there was numerous accounts of peoples devices suddenly rebooting and then getting stuck in a bootloop, all partitions seemed to be corrupted including the recovery partition and there was absolutely no way to write to the system anymore. Complete booting brick. No one was able to find the cause and no one was able to find a fix.
Click to expand...
Click to collapse
I really hope this isn't true...
On an unrelated note: Do you think that B&N would notice if I microwaved my nook for a few seconds?
Ok, backstory, picked up this Nook Color on craigslist, came with Honeycomb v4 on microSD, booted fine into that, but without uSD would boot to 'n' screen and freeze/stall. Got another uSD formatted with CWM Recovery and the clean original nook image to try and load that from scratch. While following the instructions to restore the original image I would get errors while trying to format system and data (something to the effect of Error cannot format system/!). So I tried to install both CWM to the internal and CM7 to the internal and both would say install complete from microSD, but when booting without the uSD, it would still try to boot into the original nook software and hand on the 'n'.
I tried this to see if my partitions were messed up, but I had the same partition structure and size as it should be (according to the post):
http://forum.xda-developers.com/showthread.php?p=13003431#post13003431
Possibly because I ran this "repartition-boot-with-stock" from this post:
http://forum.xda-developers.com/showthread.php?t=914690
Please help, would prefer to run this off the internal!
Got CM7 running off yet another microSD with this thread:
http://forum.xda-developers.com/showthread.php?t=1000957
Assuming the partition table is in tact then try formatting /system /data /cache in Clockworkmod.
If that doesn't work if might be time to entertain the possibility that you were sold a Nook with a bad emmc.
Sent from my NookColor using XDA App
When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?
mattdogg02 said:
When I try to format /system /data /cache in CWM, I get an error message. What is the function of the emmc?
Click to expand...
Click to collapse
Putting it in PC terms, the emmc functions as the ROM for the bios, and as the solid state drive for whatever you're running on internal memory.
(What is the term for the tablet/smartphone equivalent of the "bios"?)
akaCat said:
(What is the term for the tablet/smartphone equivalent of the "bios"?)
Click to expand...
Click to collapse
Bootloader.
As to the OP - It's still possible your internal flash is bad but the fact that you can list your partition table gives me hope that isn't the case.
I read through JoJa15's post you linked in "Dummies Guide to Fixing 'My Nook Won't Boot'" - It sounds like you listed your partition table per his post and found that it matched what he posted but didn't modify anything right?
The fact that your partition table appears to be in tact is good but the contents of those partitions could be complete gibberish which may explain why CWM errors out when trying to format them. What is the exact error CWM is giving?
I think the next "safe" step is to have a look at DeanGibson's post here: http://forum.xda-developers.com/showthread.php?t=1094371
Dean's CWM scripts will essentially blow away partitions 6-8 (/data / cache and /emmc) and re-create them. If your problem happens to be in one of those partitions then his tool may be a quick fix without having to play with fdisk. That said, I doubt it will work since you can't format /system (partition 5) and his tool doesn't touch the /system partition.
At that point you are pretty much left playing with fdisk, unless you can sweet talk DeanGibson into putting together a CWM flash that will re-do partitions 4 and 5 (extended partition and /system partition) which he may do.
From there it boils down to how comfortable you are with the Linux commands dd and fdisk...?
Good Luck,
Martian21
Ok, followed Dean's instructions with the packages from his post, but still no go.
The error I'm getting when going to Mounts and Storage Menu and running the format /system /data /cache options are:
ClockworkMod Recovery v3.0.2.8
Formatting /system...
Error formatting /system!
Formatting /data...
Error formatting /data!
Formatting /cache...
Error formatting /cache!
Really want to try and get this resolved as I want to install stuff onto the internal!
No one with any other advice on this?
mattdogg02 said:
No one with any other advice on this?
Click to expand...
Click to collapse
Your previous post showed that you were using clockworkmod recovery v3.0.2.8, that version does not have support for the “blue dot” NC. Not knowing for sure if your NC is really a “blue dot” or an original one, I would follow these steps.
1. Create a bootable CWM v3.2.0.1 SD card using the image located HERE. The instructions for it are located HERE. I know the post says v3.0.2.1, but it is miss-marked.
2. Once the card is made, download the repartitioning files located HERE, and the stock 1.2 image file “update-nc-stock-1.2-signed.zip” located HERE.
3. Put all those zip files onto the SD Card
4. Shut down the NC
5. Insert and start the bootable SD card
6. Follow the directions to flash the repartitioning files
7. Once that completes, flash the stock 1.2 image
8. When that is done, remove the SD card, and reboot the device
Hopefully at this point, you will be booting into a stock 1.2.0 system. You can now do whatever you want with the device.
Several users have complained that they get blank screens and cannot flash new roms to their Nook Color. And sometimes they end up in a recovery bootloop where it will do nothing but boot to recovery no matter what they choose in the boot menu. Sometimes this is due to corrupted partitions on internal memory.
DizzyDen has prepared some .img files that can be burned to emmc to repair some of these issues, and they work well. But some of the files are very large and it takes a little knowledge of adb commands on the part of the users. And some users cannot get adb working on their machines. So I started investigating other solutions, and I have made some tools that work that I hope are user friendly.
Dean Gibson has a thread that describes how to repartition emmc to set the partition sizes for data and media to the user's preference. He repartitions partitions p6 (data), p7 (cache) and p8 (media). In studying his zip, I figured out how to make his tool repair partitions p4 (extended), p5 (system), p6 (data), p7 (cache), and p8 (media). And I was able to add additional commands to also repair partition p1 (boot). I asked Dean's permission to post his tools as modified by me and he agreed. Thanks Dean!
So that takes care of partitions 1, 4, 5, 6, 7, and 8.
Partitions 2 and 3 are very special and one must be very careful with them. Partition 2 is 'rom', which holds information that is specific to the user's device (serial number, etc.), and it is used by the system to set flags for deciding whether to boot to recovery or not and set the boot count that is used to decide whether to do a reset to factory conditions (8 failed boots). Partition 3 is 'factory' and holds the factory.zip file used by the 8 failed boot reset (if you want to learn more about the 8 failed boot reset, go to my tips thread linked in my signature). It also holds a backup of the device information in partition 2. So it is possible to repair partition 2 if partition 3 is still intact.
A few users have somehow managed to flash Nook Tablet ROMs to their Nook Colors and really messed up partition 4. (Edit: and now I know how it happened, some idiot recommended that they remove the first line of the updater script. NEVER do that! That line is a safety check to make sure you are flashing to the right device. You can also defeat the safety check by using an old CWM that has the toggle, 'disable asserts'. Never do that either.) And since partition 4 is the extended partition that holds partitions 5, 6, 7, and 8, they get messed up too. To repair those partitions along with partition 1, use CWM recovery to flash the two zips attached below. Be warned that everything in emmc media (p8) will be wiped out, so you may want to back that up first if you still can. The first zip to flash is 'NookColor-emmc-repair-partitions-1-4-5-6-7-8.zip'. It will recreate those partitions on emmc. As soon as you have sucessfully flashed that zip, you must reboot the Nook Color back to CWM so that the updated partition table is read by CWM. Then you need to flash 'NookColor-emmc-format-partitions-5-6-7-8.zip' (partitions 1 and 4 do not need formatting). It will format the newly created partitions to the correct structure. Now you can use CWM to restore an earlier nandroid backup or flash your favorite ROM (including stock, get version 1.4.3 that I have modified to be flashable with CWM here, or DizzyDen has posted some excellent 1.4.1 stock ROMs here). If you are going to flash a stock ROM, you must be sure to use the format zip or the stock ROM will not boot properly.
If you are in a recovery bootloop, the first thing I recommend trying is to use my CWM version 5.5.0.4 bootable SD that is discussed in my tips thread linked in my signature and has been modified to help get out of some kinds of recovery flag bootloops. If you are in a recovery bootloop that just hangs, it may get you out of it after exiting my CWM with the 'reboot' command in the menu. But if you are still in the loop after doing that, it may be because your device info is missing or corrupted in partition 2. It will not boot to a ROM without this info. (Specifically, it needs a file in /rom/devconf named DeviceID. It is a text file with your 16 digit serial number in it followed by a line feed, 17 bytes.) Try flashing with CWM my 'NookColor-emmc-repair-partition-2.zip' attached to this post to recreate that info. But I recommend this as a last resort, since messing with that partition is risky. That zip will recreate the partition, reset the flags and copy your device specific information from partition 3. But your partition 3 must be intact for this to work. If it is not, the zip will abort and do nothing.
Additionally, for those that do not want to use CWM, I have made a bootable SD that has an older version of TWRP here. Newer versions of TWRP will return an error message when trying to flash these zips. It also has been modified to get you out of some kinds of bootloops.
Two points of information. First, I have included a temporary copy of CWM 5.5.0.4 on the boot partition of my repair so that if tries to reboot to emmc before you put a ROM on it, it goes to CWM. It will be removed as soon as you restore a backup or flash a ROM. Second, the new partition scheme created with my zip is for the original Nook Color's 1GB data and 5GB media. If you want one of the other schemes (5GB data/1GB media or 2GB data/4GB media) go to Dean Gibson's thread and flash his zips after you have repaired your system with mine. See his thread here.
I'm adding a little extra information about emmc partition structure for those interested. With any MBR disk there can be a maximum of four primary partitions. So to have more than four partitions the last primary partition is created as an extended partition so multiple logical partitions can be made inside it. The emmc structure is: p1 (boot, fat, primary), p2 (rom, fat, primary), p3 (factory, ext3, primary), p4 (extended, going from end of p3 to end of the disk), p5 (system, ext2, logical, inside the extended), p6 (data, ext3, logical, inside the extended), p7 (cache, ext3, logical, inside the extended) and p8 (media, fat, logical, inside the extended).
You save my nook color
Thank you so much. My serial number and other information were recovered successfully. Without those information I could not boot into any rom. If you cannot boot into ROM after following the first 2 steps, try recover partition 2. It works for me.
:laugh::laugh::laugh::laugh::laugh:
Thanks
My nook has been stuck in a "will not boot" state for about a week. I could run CWM and cyanoboot, but when ever I tried to boot CM I would get stuck at the "loading..." screen. I tried loading both CM7 & CM9 but neither one would boot.
I ran both repair scripts, reloaded CM7.1 and success!
Thanks Leapinlar! :good:
THANK YOU!!!!!!
Right from my 1st install I couldn't get the bar at the bottom of the screen, which made using the Kindle app more than a little difficult. This finally cleared everything off so I could start with a clean slate, and BINGO! I know have the bottom bar on all the screens. I assume when I go in to the Kindle app it will be ok now also (I just have to format a 16gb microSD and put in the Nook Color 1st).
I can't thank you enough!!!!
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
czarofthefrozentundra said:
Ugh! Tried this method too, and I still cannot get the nook to boot into CWR or CWM. I tried the 8 boots thing too, but I don't know if I ever did it right because I have cyanogen mod installed on emmc. Not sure how to repair the partition if I cannot even boot into anything that allows me to flash the zip to the chip. I thought it may be the sd, but the sd cards work on my other nook. I have now basically dissembled my nook color trying to find any other solution I wish I knew what happened in the first place.
Click to expand...
Click to collapse
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
leapinlar said:
Did you try my version of the CWM bootable SD card? It is on my tips thread and has been modified to boot in certain types of recovery bootloops. Unless you get CWM running you cannot flash things to internal memory. And depending on where in the boot process it hangs, you may not be able to get adb working to put things there either. And the 8 failed boots will not work unless you have stock recovery still on emmc.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
czarofthefrozentundra said:
Yup. Tried the card. I believe I replaced the emmc with cyanogenmod back in the day. Starts, goes to loading, turns black, then done. Cannot do anything after that. Bummer, sounds like it is actually toast.
Click to expand...
Click to collapse
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
leapinlar said:
If you can get adb working while it is sitting there black, you can push the stock recovery files to partition one. Then you may be able to do the 8 failed boots. You can extract the stock recovery files from my zip in my tips thread.
Click to expand...
Click to collapse
Worth a shot. Have nothing more to lose other than time. Maybe adb will work with you card in it. It didn't work with everything else I tried.
OMG OMG thank you soooo much for this thread , you saved my reading addict self from going insane ......
You've done a great job on collecting all of these useful things, especially for those who are stuck with their Nook Color boot looping. (I was once that guy) Dean helped me out with his data zips as well way back! Thanks for all this! :good: :victory:
Much thanks, leapinlar. Restored a nandroid with TWRP that was corrupted and lost my boot partition. I used your first 2 repair zips and I'm back in business. Your many contributions are greatly appreciated.
Mike T
OMG! Thank you so much for putting this up! Back at the beginning of the year I was having problems with my NC not going into USB Mode and only showing a black arrow when trying to load books and following this finally fixed it. Great write-up and instructions, thanks for the hard work.
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
jmiklus01 said:
I've been trying to restore my NOOK for about 2 weeks and this post has gotten me the farthest but i'm stuck at the point where my nook will start up, the "Read Forever" splash screen will come up and then it attempts to recover the system since i see an greenish Android screen come up for a second and then i get an error screen saying "Install Failed" with an image of a nook with an exclamation point in it's screen. I'm assuming i've really messed the nook up but here is where I am.
I've reformatted the partitions using your 1-4,5,6,7,8 zip
Rebooted to recovery
Formatted partiions 5,6,7,8 with your zip
Flashed your 1.4.3 stock rom
At this point I can't get any further since it appears something else is wrong and i didn't want to attempt the reformatting of partition 2 without asking if there is anything else i should try. Any help would be appreciated.
Thanks
Click to expand...
Click to collapse
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
leapinlar said:
Do the partition 2 repair. That is what is messed up and causing the reboot.
Sent from my Nook HD+ using Tapatalk
Click to expand...
Click to collapse
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
jmiklus01 said:
I've tried the partition2 zip and received an error trying to mount the factory partition. Status 7 was the error code. Is there a way to fix this?
Click to expand...
Click to collapse
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Restore NC back to stock
View attachment 1500490
leapinlar said:
Oh, that is really bad news. That means your partition 3 is corrupted and there is no way to retrieve your device info, like serial number, etc. PM me and maybe I can help you get it partly working, but much of the device info is lost if that partition is truly corrupted.
Sent from my BNTV600 using Tapatalk
Click to expand...
Click to collapse
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
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
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
big64dave said:
View attachment 1500490
I've been trying to restore my daughter NC back to stock for couple months now and no success.
I did flash the P 1-4-5-6-7-8.zip and got this message after reboot:
"CWM-based Recovery v5.5.0.4
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
during the reboot, there is a menu option to hit "n" for reboot mode option. when i hit "n" it gives me (attachment).
but it won't let me move up or down to select except for the 1st option
Help would be very appreciated
Click to expand...
Click to collapse
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
leapinlar said:
During reboot it should automatically go to CWM because everything else is wiped. The boot menu only lets you make the first choice because that is all that is there, everything else is wiped. You need to continue to use the CWM to flash the format zip next. Then you can flash a ROM. If the CWM that pops up is not working, use the bootable CWM SD.
Click to expand...
Click to collapse
Thx for replied, the Nook just stock on loading and it won't let me do anything except for power up and down
Perhaps someone can help. I've read a lot of the great content here but I've hit a wall.
A few weeks ago my ovation device was running cm11+cwm but began random rebooting. Clearing the cache+dalvik only helped briefly.
I tried an upgrade with a twrp 3.0.0.0 (using the amazing multiboot recovery SD), but it hung formatting the cache partition (I waited about an hour). Tried again, same thing.
I used adb shell to fix a blank file system type on the cache partition but was only successful in creating an ext2 partition there. I got cm13 booting but it trebuchet kept crashing. I tried twrp again and flashing a different image and tried a factory reset. Big mistake.
Now when I try to boot any recovery SD it doesn't boot all the way. Using adb shell, my dmesg shows that umount is hanging. No emmc partitions seem to be mounted. The partition data exists in dmesg but calls to parted hang. Mkfs.ext4 also hangs (naturally).
So I've lost the ability to fully boot recovery SDs (they are probably hanging when they try to mount the emmc partitions). As such I can't flash a recovery. I have a clockwork backup that has a system.ext.tar file in it, but I don't know how to use it at this point.
I can't mount /rom so I'm worried.
Is my emmc shot? Is there any way to tell?
Thanks!
Would a noEMMC SD be safe?
I guess what I was hoping to do was use adb to completely wipe and restore the device to a sane state, which would include repartitioning and formatting the emmc partitions. Is that possible? Maybe not at this point.
I guess another question would be: if my NookHd+ emmc is technically working but currently unrecoverable, is it possible for me to safely use a NOemmc SD card? There seem to be some warnings about those wrecking emmc but I can't find any technical explanation as to why.
Based on further diagnostics, my emmc is one of the faulty Samsung models and so I think the crashes and ultimate recovery failures were the failure of the emmc.
I've successfully installed 10.1 noEMMC on one microsd. Runs Okay but a lot of apps I am interested in don't work on android from this vintage.
I tried to install 4.4.4/CM11 noEMMC but it can't mount the necessary partitions as per the install process on the iamafanof Wordpress page. I also see SELinux errors in the twrp recovery log. Does anyone know how to overcome this mount issue that apparently impacts some people.
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Sorry to resurrect this thread, But it exactly speaks to my issue. You mention that the blk0 and blk1 devices need to be switched for cm11 image to mount partitions properly. Does anyone know specifically where this might be done. Can files of the existing nov4 cm11 image be altered to reverse these two devices?
CalculonsTalent said:
Assuming there are others out there who find this useful, I have some updates.
I was determined to figure out why the CM11 NoEMMC was not working for me but CM10.2 noEMMC works fine. I get the error that many others get: unable to mount /boot, /data, /system.
I used adb shell to connect to the twrp 2.8.0.0 that runs when you boot the CM11 noEMMC SD boot/install image and compared the Linux system differences between that and the system you can see connected to the cwm 6.0.4.? That runs when you boot the CM10.2 noEMMC SD boot/instal image.
First things first: cm10 noEMMC remaps the internal emmc as /dev/block/emcblk1 and the external microsd card slot as blk0 (this is swapped from the norm and correct for a situation where you want to install to the SD as though it were the internal device).
CM11 noEMMC does not do this. I think that the author assumed that if your emmc is bricked then the system won't see your /dev/block/emmcblk0 at all so your external sdcard will take over that number. Clearly that's true for some, but it's not true for me.
I also began poking around the post boot script (in /sbin) to see how the cm11 noEMMC prepares the partitions on the Sd card and to see what Command it uses to create the data partition
Here's the kicker. I was able to mount my emmc rom partition and copy off all that data with an adb pull. I was able to initialize the cache partition (9) as a blank ext4 partition. I was even able to initialize the user partition (10) as ext4... Though I'm not sure that's right. I began mounting partitions and got greedy and tried to mount the whole partition map and it failed.
So, there's something wrong with (at least) one of my partitions. When recovery tries to mount the partitions, mount hangs and recovery fails to fully load. The noEMMC sd card got me around this because it doesn't try to mount any of the emmc partitions let alone all of them.
So, does anyone know if I can make new file systems on every partition and if by luck I'm able to get a twrp or cwm to fully load, will flashing a stock recovery put data on all those partitions?
Thanks
Click to expand...
Click to collapse
Could you please teach me how to mount EMMC partitions and retrieve data specially /factory partition with ADB?
I can only boot my Nook HD+ with with bootable SD card with TWRP or CWM.
Thanks.