Related
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
mathfeel said:
I have been playing with HC, CM7 etc on my Nook color and decided to go back to running auto-nooker on top of stock, but I want to keep the SD CWR image I made, which has a lot of free space for me to play with future ROM. Has someone packed an CWR zip for auto-nooker?
Thanks.
Click to expand...
Click to collapse
BOOM Wining.
http://forum.xda-developers.com/showthread.php?t=932145
therealguppy said:
BOOM Wining.
Click to expand...
Click to collapse
LOL. Thanks.
My current ROM is phiremod nook V4.1. After flashing this and reboot. The Nook U picture flashes, then it's flashing "A N D R O I D _" prompt at the lower left and nothing...
There are three of us currently stuck on that damned android_ screen right now. As I posted in the other one if you get out of this please post your steps!
I reflashed phiremod nook V4.1. That boots pass ANDROID_.
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
I already did that. Right now as I turn it on, it displays the "Touch the Future of Reading" line instead of the "Loading..." line from CWR. Or do you think this is not sufficient?
There is message when installing repartition-boot-with-stock.zip:
"This will install stock boot 1.0.1 Eclaire --- This won't boot with Froyo!"
Can this the issue too?
EDIT: During the 5 minutes delay b/t post, I installed repartition-boot-with-stock.zip and Nook Color-v1.1.0-r2.zip, now it boots and stucked at the Nook icon with the "Contain Reader Mobile by Adobe" line.
Okay, so I restore stock image, albeit 1.0.1 using images form this page:
http://forum.xda-developers.com/showthread.php?t=919353
Steps:
1. download/extract boot.img and system.img to bootable sdcard (with CWRv3.0.0.6)
2. boot using sdcard, mount /sdcards
3. use adb to dd the image as described in article.
4. repeat failed boot to force recovery.
I thought this would restore /system and /boot ext3 again, but it doesn't...still getting stuck at "ANDROID_" prompt after reflashing the Nook Color v1.1 above. I am going back to CM7...sigh...
EDIT: Actually, it DID work! My problem was when I reflashed Nook Color v1.1-r2.zip, I wiped system and data, which I shouldn't have.
therealguppy said:
Hmm maybe this is due to CM7 using EXT4 and stock using EXT3,
after flashing the Stock restore also try flash the Restore Boot Partition..
http://forum.xda-developers.com/showthread.php?t=914690
At the bottom of the first post on this one you can find the Restore Boot. which restores Stock B&N boot.
Click to expand...
Click to collapse
FYI I've been in the same boat as you a couple of times now with my Nook not wanting to boot. And it seems it gets to different points each time before locking up and not booting. I'm starting to think the same thing as your comments here. This whole ext4 stuff is what seems to be causing issues for a lot of folks specially when wanting to go back to a different ROM or stock. To further compound it is the fact the newest CWR is 3.0.1.0 and all bootable sdcard files are still 3.0.0.6 or 3.0.0.5. With that said I can tell you making a backup using the 3.0.1.0 CWR that is on the internal mem and then getting stuck booting is no good. Reason being from wha tI've found so far is if you take your 3.0.1.0 backup and put it on a bootable sdcard that has 3.0.0.6 so you can restore, it does not work right from what I've found. The only way I've found to fix it easily so far is to first flash the " Remove CWR * .zip from the link posted here. After that then flash the repartition-boot-with-stock.zip file. Once I've flash those 2 files I'm able to flash a new ROM and have it boot like it should.
Another way I've got around it was to power the device on into recovery with no sdcard in the device. Once it booted into recovery ( ie CWR 3.0.1.0 ) I put the sdcard in the device that had my 3.0.1.0 CWR backup. I restored that backup using the actual 3.0.1.0 recovery from internal mem. Once finished tried to boot and it got stuck. When it did I then powered it down and fire it back up but this time booting to the sdcard and then I flashed the repartition-boot-with-stock.zip and it would finally boot up like it should.
Bottom line IMO at least is it seems to be hit or miss on what is the best way to get it back up and running after the boot partition gets hosed. And that can make it a bit frustrating.
Sorry I don't have time to read all of this. Just keep in mind that > 3.0.0.6 formats to ext4 (ie CM). For stock and froyo, use 3.0.0.5 to format to ext2 and 3..
System, data and cache need formatting before flashing a new rom.
Repartitioning boot is only useful if your NC doesn't boot.
Sent from my HTC Desire using XDA App
thought 3.0.1.0 was supposed to work for everything.
My nook color recently got stuck on the boot screen for CM7 where the blue android text just chills out in the left corner. This happened right after my nook ran out of battery power.
I have gotten it to boot all the way into CM7 occasionally. However, it is not reliable at all, so I've tried to restore it to stock and reflash the whole thing.
I tried to do this by booting into recovery and then flashing the restore to 1.01 stock zip file, but when the nook rebooted it was still stuck on the android text. I have tried flashing everything related to restoring nooks, but to no avail.
I thought that maybe my CWR was broken, so I tried making a CWR sd card but even when I flashed the restore zip, my nook's boot still gets stuck on the android text.
What do you think I should try to do now?
You are able to boot into cwr though? If so have you tried downloading the stock image file again? Could be the file is corrupt.
I just downloaded it again and it still doesn't work.
I don't think that the problem is the zip files. I think that CWR is the problem since I've tried formatting /system and /data and tried repartitioning boot, but nothing happens...
I just tried to restore my nook to stock through ADB, but it still tried to boot into CM7. I guess that rules out CWR as the problem...
I also made an ext4 compatible CWR SD and tried the restore 1.01 zip again. This time I got past the android text and instead got to the grey android text from the rooted nook boot. However, it just sat there, stuck in a loop.
Odd, that even after wiping system and data that you'd have anything to boot into. You aren't leaving a bootable sd card in place are you?
I make sure to take out the SD card before rebooting.
Is it possible to check to see if CWR/ADB is actually writing to the correct partitions?
EDIT: I do not think that my nook is keeping any changes that I make to it...
I managed to boot into CM7 and I uninstalled a few apps and changed the max clock to 800mhz. Then I rebooted and eventually got back into CM7 and my apps magically came back and my max clock was reset to 1.1ghz.
okay that is very odd. Unfortunately I've never run into this or even read about it before. Hopefully someone here will be able to give you a tip that will help you fix this.
I've been having same issue for a week now. I tried everything I was able to find here but nothing is wokring. It seems like my nook became a read-only device. No matter what I do it goes back to previous stage.
I was running CM7 RC4 and system hung so I rebooted and that was it. It displays "Android_" on the bottm for about 10-15 sec and reboot.
I tried
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
I see people start to talking about CM7 boot loop issue. I saw this thread and man this is same issue I'm having! Let me know if you some how resolved this issue. I will do the same if I can find one.
Naw, I haven't resolved it yet...
I will post the solution if I do though!
Perhaps it's just a coincidence, but I am also stuck running RC4. Maybe there's some weird glitch in RC4 that makes the file system read only or something...?
I went from RC4 to stable with no problem. I did notice that CWR was not mounting the system and data partitions so I did have to do that when updating. Not sure why they aren't mounting automatically.
From the Dummies guide link....Here...
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.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
deadbot1 said:
From the Dummies guide link....Here...
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.
I had to use that last file after my hard crash. Seems that te /boot gets corrupted and tis seemed to fix it for me. After this you will probably need to do a full wipe and reinstall.
My order was...
rebuild /boot
reflash to stock
reflash to CM7
not sure why this worked...just did.
edit: just noticed my H key isn't always working...makes me type like a alf drunk brit..
Click to expand...
Click to collapse
I tried this too but mine didn't come back.
Hmm. dunno. Maybe you can get samuelhalff to chime in...he was helping another guy out with something similar. searc in the threads for his name and your problem...wasn't to long ago.
edit---http://forum.xda-developers.com/showthread.php?t=1022941 this was the thread I was talking about...doesn't appear they came up with a solution.
I tried all the things you suggested guys, but nothing worked...
Although I think I made some kind of progress... I tried to dd stock boot.img and system.img files onto my nook and now CM7 just bootloops instead of hangs!
Hopefully we can get this sorted out soon, or else I may try what one member suggested about microwaving it so that you can get a new one...
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?
I have a nook color that was stock 1.3 and i installed cyanogen 7 on it. i reverted back to 1.0.1 but found that i could not update my nook because it wouldn't mount anymore. so i rerooted and did a restore of a backup i made using cwm. i was able to revert back to 1.3 and my nook mounts again but i put the 1.4 update on the nook and when it tries to update it fails. i think it has something to do with cwm since thats what comes up telling me that the update failed. any tips on what i should do? thank you
p.s. i am currently on 1.3 stock on the emmc and i have cyanogen 7 on the sd card, booting with multiboot so i can choose which to boot. thanks
aminthemachine said:
I have a nook color that was stock 1.3 and i installed cyanogen 7 on it. i reverted back to 1.0.1 but found that i could not update my nook because it wouldn't mount anymore. so i rerooted and did a restore of a backup i made using cwm. i was able to revert back to 1.3 and my nook mounts again but i put the 1.4 update on the nook and when it tries to update it fails. i think it has something to do with cwm since thats what comes up telling me that the update failed. any tips on what i should do? thank you
p.s. i am currently on 1.3 stock on the emmc and i have cyanogen 7 on the sd card, booting with multiboot so i can choose which to boot. thanks
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1391931
This will get you back to stock 1.4.1, then you can reuse your dual boot SD...
followed that thread. everything was going ok but after returning to stock 1.0.1 my nook won't mount when i plug it into my computer. i just get 2 new disks in my computer that are lightly grayed out and i can't open them. under device manager i have 2 b&n ebook usbdevices under disk drives. i have uninstalled them and tried to plug the nook back in but they still show up the same. so i again did a restore with cwm back to the 1.3 i had but still can't update to 1.4, cwm interferes when the nook is attempting to install 1.4 and says
verifying update package...
E: failed to verify whole-file signature
E: signature verification failed
Installation aborted.
I had a Nook setup with Dual Boot (not using an SD Image) and now I am trying to restore the device back to factory settings.
I've been trying to do a full factory restore (removing my root) to my Nook Color.
I've used this ROM http://forum.xda-developers.com/showthread.php?t=959461 to remove the dual boot and reparition.
I've formated EVERY partition (except SDCard, which seemed like a bad idea if I booted from it).
I've created a bootable Clockwork Recovery MicroSD Image (3.0.2.8). I can boot from this fine.
I've tried 3 different factory ROMS (1.0.1, 1.2, 1.3, etc) and I can get them all to install and boot up.
However I can't get past the "B&N registration screen". I always get an error registering the device.
When I select "Shutdown" the device, from this screen, I believe I can STILL see the "soft keys" on the bottom of the screen, which makes me feel like the Android system is still "hacked".
Have I restored this correctly? Is there some reason I can't register the device with B&N?
Are you sure /data is getting formatted? Watch it carefully at that step. If you're using an older Clockworkmod, it will fail with newer Nooks due to filesystem changes. IIRC cwm3.2.01 is the latest. I had the same symptom, realized /data was not formatting and tried with a newer version and had no problems restoring to 1.3.
Use version 3.2.0.1 of CWR found here: http://www.multiupload.com/N5C1846GH3
Wipe everything and then install this stock 1.3 .zip: http://www.multiupload.com/3Y5MWE773D