Related
I just bought an NC 1.2.0
no need to bore anyone with details but it is safe to say that it is virtually bricked. i would love a surefire way to get it completely back to the stock to start all over again.
i tried the repartitioning and reformatting technique using cm7 without any luck whatsoever. when i boot the device gets to the big N and "contains Reader mobile technology..." screen and never fully boots.
does anyone have a solution?
Presumably, one of those boring details involved writing an image to an SDcard:
eyeballer said:
Download 1gb CWM 3.2.0.1 sdcard image from here. MD5 of .zip: 1319739d33642ed860e8044c3d55aa56. (I made this based on work in this thread. credit: to cmstlist and DizzyDen, and kevank for hosting). You really only need the 1gb image ... no matter what the size of your card is. A smaller image will burn faster, and when you're done with the guide you can reformat the card anyway.
Click to expand...
Click to collapse
There's a decent chance the problem with your install is that you were using an older version of CWM on a newer NC, and it didn't write all the partitions correctly. Regardless, get the current version now.
Grab a B&N 1.2 image:
nemith said:
I modified the official 1.2 update to allow CWM to flash them. You can use these to upgrade to 1.2 or to return to stock.
There are two files. One replaces CWM with the stock recovery (good for going back to stock). The other doesn't replace CWM (but will replace uboot).
Other than that they are identical to the update from B&N.
update-nc-stock-1.2-keepcwm-signed.zip
update-nc-stock-1.2-signed.zip
Please note neither one of these are rooted yet.
Click to expand...
Click to collapse
and install zip from sdcard > choose zip from sdcard in CWM.
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
mvnsnd said:
Another option, if will at least start to boot, is to start the boot process and then hold the power button down to shut it off. Repeat this 8 times in a row and the unit will initiate a self restore to the way it was shipped.
One thing to remember is that if you have a blue dot on the box for the nook, it has a different partition size and must be accounted for when installing CM7.
Click to expand...
Click to collapse
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Taosaur said:
If he has CWM on his internal recovery partition, I don't think 8 failed boots will work.
Also, the latest version of CWM can install CM7 correctly regardless of partitioning, though the old-style partitions are going to be preferable for most people running CM7.
Click to expand...
Click to collapse
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
mvnsnd said:
Ah. I did not know that CWM installs on the internal recovery partition. Thanks.
Click to expand...
Click to collapse
It does if you flash it from ROM Manager, regardless of whether you have ROM Manager running internally or on a CM7 SD install. If he hasn't done that, 8 failed boots should work, but I'm not 100% sure on a repartitioned device.
I would like to remove CWR so that I may sideload the Nook 1.3 software. Right now, CWR is blocking the installation of 1.3 with an error each time I sideload the file and the Nook restarts. I found a CWR Removal zip file but it only works with Nook 1.1 .
joej said:
I would like to remove CWR so that I may sideload the Nook 1.3 software. Right now, CWR is blocking the installation of 1.3 with an error each time I sideload the file and the Nook restarts. I found a CWR Removal zip file but it only works with Nook 1.1 .
Click to expand...
Click to collapse
I'm pretty sure this has been asked before and the answer is you have to do a complete reinstall of the stock ROM.
Let me guess, you used verygreen's guide to installing CM7 to the card?
joej said:
I would like to remove CWR so that I may sideload the Nook 1.3 software. Right now, CWR is blocking the installation of 1.3 with an error each time I sideload the file and the Nook restarts. I found a CWR Removal zip file but it only works with Nook 1.1 .
Click to expand...
Click to collapse
That's one of the reason, I never and not suggest others to flash CwM into eMMC.
I guess, you have to completely reformat to remove CwM.
I never install CwM into eMMC so I have no experience how it goes
Managed to do it. It's a tedious process.
1. Make Backup of rooted 1.2 with CWR SD
2. Restore the signed 1.2 ZIP to make it a fresh install and generate a new /boot
3. Backup fresh 1.2 with CWR SD
4. Restore backup of Step 1
5. Do an advanced restore and restore /boot from backup of Step 3
6. Install OC Kernel
7. It will boot up the Rooted 1.2 but without CWR in EMMC
Hope this will help anyone else who might have installed CWR into EMMC
joej said:
Managed to do it. It's a tedious process.
1. Make Backup of rooted 1.2 with CWR SD
2. Restore the signed 1.2 ZIP to make it a fresh install and generate a new /boot
3. Backup fresh 1.2 with CWR SD
4. Restore backup of Step 1
5. Do an advanced restore and restore /boot from backup of Step 3
6. Install OC Kernel
7. It will boot up the Rooted 1.2 but without CWR in EMMC
Hope this will help anyone else who might have installed CWR into EMMC
Click to expand...
Click to collapse
Excellent advice! Thanks for sharing. I am sure others will appreciate it.
It's a good sign for those who intentional or unintentionally flashed CwM into eMMC and want to restore back to stock.
Good work, m8
Glad you guys like it. Quite a few steps but at least it lets us wipe off CWR
First and foremost,
Standard Disclaimer
By flashing this you should understand that I am not responsible for bricked devices. In order to flash this file, you would have already rooted your device, voiding the warranty. YOU are choosing to make these modifications, and I take no blame or responsibility if you brick your device and/or your device catches fire.
I would like to start off saying that I used the eMMC dual boot option referenced here [eMMC]Updated Dual Boot Guide[CM 7.1+][Phiremod 7+][Stock 1.3] and ran into the problem where the main partition (CM7 in my case) was booting normally, however, the alternate partition (Stock 1.3 rooted) would continually boot loop. After research, I found out that it was boot looping due to the incorrect versions of Adobe Flash and Air being installed. They were also installed to /system instead of /data.
I found two excellent guides located here and here that helped diagnose the problem. Unfortunately, these only helped with the primary partition.
In order to fix the boot looping of the alternate partition, I modified the updater-script provided by jaromnelson to reflect the alternate partition.
What this file does is removes the incorrect Adobe Air and Adobe Flash from /system folder on the alternate partition and installs the correct Adobe Air and Adobe Flash to /data folder. DO NOT INSTALL THIS FILE IF YOU ARE NOT RUNNING eMMC DUAL BOOT by Taosaur. If you continue to boot loop after you install, you are not boot looping because of Adobe Air and/or Flash.
To Install:
Download the file located here
Put the file onto your SD Card
Boot into CWM recovery
To be on the safe side, Wipe Cache and Dalvik (not sure if this helps but I do it anyway).
Code:
CWM > Wipe Cache Partition
CWM > Advanced > Wipe Dalvik Cache
Install the attached ZIP through CWM.
Reboot into your alternate partition and enjoy.
I am by no means a developer, just a guy that does a lot of research.
Full credit goes to:
Taosaur for creating the eMMC dual boot guide
jaromrnelson for creating the guide to fixing the boot looping
GMPOWER for the initial ZIP
Do you happen to still have this file, file seems to not exist.
I'm having the same issues you were
You can always upload it here as an attachment
Wow. I can't believe this may actually help someone. All this time, I thought I would have been the only one to encounter this problem. Unfortunately it would not let me attach the file to the post. Anyhow, here is an updated link. I'll update the OP too.
http://www.mediafire.com/?8e8vxgl8haag2a5
Mikey, after looking, it appears that the original referenced thread has been updated to a new method of installing dual boot to emmc. When I get home I will check to make sure that the new version uses the same boot partitions. So for now (until I can check) this zip is only good for the old method.
edit: I looks like the new method uses the same boot partitions (primary system: 0p5 and primary data: 0p6 --- secondary system: 0p9 and secondary data: 0p10) as the old method. So, if you are using the new method and experiencing the same boot loops as before, it should be safe. In reality, I'm not even sure if the Adobe problems exist anymore with the new method. As stated in the OP though, I'm not responsible for bricked devices.
To be honest, my wife has been reading on the nook so much lately, she hasn't let me mess around with it. As soon as she finishes up this book that she's on now, I plan on updating to the newest stock and ICS.
Sent from my LG-P999 using XDA
Always boots to CWM
My problem is a little different, but I'm hoping you can direct me where to go. I've been running the dual boot for about a week and it worked great. Stock on Alt and CM7 Kang on Primary. Today I backed up and then installed a theme that created a boot loop. So I tried to restore from the back up... no good. It boots up the little green Cyanogenmod, says loading, then straight to CWM. Then I tried to format the system, data, cache, and Dalvik, then re-install CM7...same, straight to CWM. I tried from the beginning, repartitioning and installing Stock with CWM... now Read Forever comes up and then to CWM. Suggestions Please.
Hoser88 said:
My problem is a little different, but I'm hoping you can direct me where to go. I've been running the dual boot for about a week and it worked great. Stock on Alt and CM7 Kang on Primary. Today I backed up and then installed a theme that created a boot loop. So I tried to restore from the back up... no good. It boots up the little green Cyanogenmod, says loading, then straight to CWM. Then I tried to format the system, data, cache, and Dalvik, then re-install CM7...same, straight to CWM. I tried from the beginning, repartitioning and installing Stock with CWM... now Read Forever comes up and then to CWM. Suggestions Please.
Click to expand...
Click to collapse
Try this post. Not exactly the same issue, but this person solved his CWM boot loop issue.
http://forum.xda-developers.com/showthread.php?p=23864432
Sent from my Nook Color running ICS and Tapatalk
@Leapinlar
Thanks for the help. That thread was perfect. I'm up and running now!
I inherited a failed dual-boot install, Nook BNRV200-A.
It starts and runs perfectly from SD card. But nothing successfully starts and runs from internal; mostly just boot loops. When I try to get into recovery, I get the dual-boot selector menu. This works OK, but if I select to boot recovery through it, no recovery comes up. If I try the trick with holding down both volume + and volume -, it just boot loops.
I would like to completely blow away all the internal partitions, recreate them and then restore standard boot, some ROM and CWM recovery. Is there a (current) procedure out there to do this? Happy to do this through ADB if somebody could tell me what to type.
The main thing is the dual-boot menu itself. I have tried reformatting /boot from CWM, but the durned thing still comes back.
(Wish we had something like the RUU or NVFlash utilities...)
TIA,
glg
Possible solution
Try following this guide ...( http://forum.xda-developers.com/showthread.php?t=1275859 )(eMMC 2/22 Dual Boot Guide 2.0 ) make sure you download all the needed files too.. It will allow you to wipe and repartition the internal eMMC .... then sets up a dual boot internal for you. Works slick and easily... Takes 20 - 30 min to do and is rock solid.
I used it and I am running CM7.2 (Mirage) on primary and B&N 1.4.1 on Alt boot... works great and is soooo fast (works great using Nook Tweaks to overclock to 1300)
Try it ... I think it will work fine
Tinpau
tinpau60 said:
Try following this guide (eMMC 2/22 Dual Boot Guide 2.0 )
Tinpau
Click to expand...
Click to collapse
Thanks for the quick reply. I did try that (at least the part about Revert from Dual-boot. I don't want a dual-boot setup).
So far, I have a working CM9 setup that successfully reboots and will now boot into recovery. But, for some reason, it doesn't recognize the SD card. I think it still has something to do with the partition table being messed up.
glg
I recently went from a dual boot back to single boot. I *think* this is what I did:
Ran revert dual boot zip
Rebooted into recovery. Important to reboot!
Ran repartition zip to 2 GB data/4 GB media (you can go back to stock 1 GB/5 GB if you prefer)
Did the usual wipe everything, clear caches
Installed rom of choice
Reboot
Worked just fine for me.
Sent from my NookColor using xda premium
Problem solved
k8108 said:
I recently went from a dual boot back to single boot. I *think* this is what I did:
Ran revert dual boot zip
Rebooted into recovery. Important to reboot!
Ran repartition zip to 2 GB data/4 GB media (you can go back to stock 1 GB/5 GB if you prefer)
Did the usual wipe everything, clear caches
Installed rom of choice
Reboot
Worked just fine for me.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
These steps were very helpful. I had an additional problem where the SDcard I was trying to use was formatted oddly. Instead of a single Primary partition, it was a /logical/ partition on an extended partition. Probably the vendor loaded some crapware on there in the empty space. So it never was seen by the Nook. When I deleted the logical and extended partitions and created a single 8GB primary partition, and formatted it as FAT32, the card was usable. Totally up and running.
Thanks,
glg
I have a Nook Color purchased in Dec 2010. It has been running fine on BN ver. 1.3 and MN 4.6.16a. I decided to update the BN firmware to 1.4.3 and reroot using MN 5.08.20. I reverted to factory image with CWM bootable card, wiped /system and /data, updated to stock 1.2 then stock 1.4.3. I registered and made a backup with my CWM bootable card. Now to root.
My first attempt used the App2SD file and the stock 1.4.3 A2SD kernel. When I flashed these files in CWM and rebooted, I was unable to get wi-fi to connect--wi-fi status notification said error. I reverted to my CWM backup of 1.4.3 and tried the basic MN5 file. With this one I was able to get wi-fi connected, but when I opened the Market I would get error message "Download unsuccessful" or error 498. I could restore my files using TB that I installed from a sideloaded APK. I have tried the market visibility fix listed in OP multiple times; I have uninstalled the market and reinstalled from TB. I have reflashed the MN5 basic package. No luck.
So, Market/Play store is not working properly and Apps2SD file breaks wi-fi. Any suggestions? I have some technical background and can do basic things in ADB.
I hope I have given enough info here. Thanks in advance for your help.
Sarah
S_NE_snow said:
I have a Nook Color purchased in Dec 2010. It has been running fine on BN ver. 1.3 and MN 4.6.16a. I decided to update the BN firmware to 1.4.3 and reroot using MN 5.08.20. I reverted to factory image with CWM bootable card, wiped /system and /data, updated to stock 1.2 then stock 1.4.3. I registered and made a backup with my CWM bootable card. Now to root.
My first attempt used the App2SD file and the stock 1.4.3 A2SD kernel. When I flashed these files in CWM and rebooted, I was unable to get wi-fi to connect--wi-fi status notification said error. I reverted to my CWM backup of 1.4.3 and tried the basic MN5 file. With this one I was able to get wi-fi connected, but when I opened the Market I would get error message "Download unsuccessful" or error 498. I could restore my files using TB that I installed from a sideloaded APK. I have tried the market visibility fix listed in OP multiple times; I have uninstalled the market and reinstalled from TB. I have reflashed the MN5 basic package. No luck.
So, Market/Play store is not working properly and Apps2SD file breaks wi-fi. Any suggestions? I have some technical background and can do basic things in ADB.
I hope I have given enough info here. Thanks in advance for your help.
Sarah
Click to expand...
Click to collapse
The aps2sd and the kernel and kernel module have to be done all at once. Wifi will not work with it unless you get it all right. I would start over. You can get the CWM flashable 1.4.3 rom on my tips thread linked in my signature. Before you flash it, use my format 567 zip. Then reboot and register, then flash the MN5 with apps2sd support then the kernel. Then if you want, restore your TB backed up apps. Don't restore your cwm backup because that will bring back all those problems.
Sent from my Nook HD+ Running CM10 on SD
Still no working wifi with MN5 Apps2SD
leapinlar said:
The aps2sd and the kernel and kernel module have to be done all at once. Wifi will not work with it unless you get it all right. I would start over. You can get the CWM flashable 1.4.3 rom on my tips thread linked in my signature. Before you flash it, use my format 567 zip. Then reboot and register, then flash the MN5 with apps2sd support then the kernel. Then if you want, restore your TB backed up apps. Don't restore your cwm backup because that will bring back all those problems.
Click to expand...
Click to collapse
I followed the instructions in your Nook Color Tips post. I used your 567.zip file to reformat and then flashed the stock 1.4.3. file you posted for CWM recovery. I rebooted, registered, downloaded a couple books to make sure it was working, then booted again into CWM. I flashed the MN5 file with A2SD support, followed immediately by the A2SD stock kernel. I removed the card and rebooted. When my NC finally came up, the wi-fi again showed an error. I am now going to try with the MN5 basic package and see if I can get that to work.
EDIT: The basic package flashed fine, and I am able to update Market to Play store and restore TB backups. I don't know why that apps2SD doesn't work for me.
S_NE_snow said:
I followed the instructions in your Nook Color Tips post. I used your 567.zip file to reformat and then flashed the stock 1.4.3. file you posted for CWM recovery. I rebooted, registered, downloaded a couple books to make sure it was working, then booted again into CWM. I flashed the MN5 file with A2SD support, followed immediately by the A2SD stock kernel. I removed the card and rebooted. When my NC finally came up, the wi-fi again showed an error. I am now going to try with the MN5 basic package and see if I can get that to work.
EDIT: The basic package flashed fine, and I am able to update Market to Play store and restore TB backups. I don't know why that apps2SD doesn't work for me.
Click to expand...
Click to collapse
Same here. App2sd just doesnt work. After flashing app2sd manual root and then the kernel i take out the CWM boot SD and what then? should i partition my 32gb before rebooting and put it instead of bootable sd?
I made complete restore, updating to 1.4.3 and want to go back to rooted 1.4.3 without app2sd from this thread :c
http://forum.xda-developers.com/showthread.php?t=1494901