[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT EMMC from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., from http://wiki.cyanogenmod.org/w/Google_Apps
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file (obtained in step 1(a)).
Select reboot to boot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously enabled Google backup service on your CM10.x your Google Playstore apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
A day before i moved from CM 10 to CM 11 , with the help of mikeataol
Anyway Thanks a lot for this guide.
Few questions
* Any good custom kernel ? I tried Bexus but its giving me "android.phone" stopped responding error and wont allow me to do anything , it just keeps on coming even after pressing "OK"
* What happend to multi touch feature ? any ROM , way to enable it ?
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
naveen_reloaded said:
...
* What happend to multi touch feature ? any ROM , way to enable it ?
Click to expand...
Click to collapse
Look for the Touch FW Flasher app on the App Drawer screens.
* Is it only me or others too feel that the screen lags a lot wrt to touch input ? Its more evident during scrolling or reaading pdf. Also anyway to resolve it ? I desperately need a fix for this.
Click to expand...
Click to collapse
Did you do wipe /data and /cache in the CM11 installation process?
* I used gapps from here : http://wiki.cyanogenmod.org/w/Google_Apps
CM 11 20140105 , is it fine or i should use PA Gapps only ?
Click to expand...
Click to collapse
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
digixmax said:
Look for the Touch FW Flasher app on the App Drawer screens.
Did you do wipe /data and /cache in the CM11 installation process?
The Gapps KK package you installed is fine, the PA package just has a few more apps (such as Maps and YouTube, etc. -- all of which you can get from the Google Playstore) and is more frequently updated (-> less likelihood/need for updates for the apps in the package immediately after first installation).
Click to expand...
Click to collapse
Thanks , I heard that multitouch has bug which makes tablet slow at <50% battery , is it so ? also does that app work on cm 11?
Yes , i did wipe everything and installed CM 11 , still the screen is stuttering. very annoying. Is there a way to increase the fps ? or see if GPU drivers are working properly ?
The default Gapps are giving error when flashed with Bexus kernel
---------- Post added at 08:12 AM ---------- Previous post was at 07:32 AM ----------
https://play.google.com/store/apps/details?id=com.aatt.fpsm&hl=en
Used this app and saw that fps varies and it varies like from 7 - 50 during reading pdf.
On slow scrolling of pdf , it only shows 11 or so fps , which is why i think shows the stuttering effect
Used the same app on my GS3 to see the difference and it holds its FPS at 60+ and not dropping below 50.
I think if i can make this tablet to render everything at 30+ fps i might not feel this stuttering effect.
https://dl.dropboxusercontent.com/u/15488514/nooktablet.mp4
here is the video i tried to take regarding the screen lag.
its all real time , there is no , afaik any camera lag ( taken with sg3) , its pretty much how it looks . Also i have shown the FPS . You can see when i scroll slowly , the FPS drops to 20 or so making it jerky. if i do it fast , it reaches 50+ but not stable and not very responsive to my touch feedback either.
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/#xjwc1a482a6ll which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
The mediafire link does work anymore. Could you reupload the zip file?
Hannibal2050 said:
The mediafire link does work anymore.
Click to expand...
Click to collapse
Link fixed.
digixmax said:
Link fixed.
Click to expand...
Click to collapse
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Hannibal2050 said:
WHen I pressed to Install zip from sd card, the screen only show the symbol of ROM Manager (a hat), and stucked.
What should I do now?
Click to expand...
Click to collapse
What version of CWM do you currently have on emmc?
digixmax said:
What version of CWM do you currently have on emmc?
Click to expand...
Click to collapse
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Hannibal2050 said:
Sorry, I handled this issue.
But now if I selected the ZIP file I downloaded from the first post, CWM reported that this file is BAD, and I cannot install.
I am using CWM 5.5.0.4.
I downloaded this file several times, but the issue does not disaapear
Click to expand...
Click to collapse
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
digixmax said:
You need a newer version of CWM 6.0.[1-3].x to install CM10.x.
If you have a SD card handy, try the method outlined at http://forum.xda-developers.com/showpost.php?p=51377882&postcount=163.
Click to expand...
Click to collapse
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Hannibal2050 said:
Hi,
I did exactly like that. I tried to update CWM to 6.0.45 and the current CWM reported that the zip file of CWM 6.0.45 is BAD
Click to expand...
Click to collapse
For CM10.x you need 6.0.[1-3].x (e.g., 6.0.2.8).
6.0.4.5 and later versions are for CM11 only.
If you follow the SD-based CWM recovery method in the referenced post the CWM recovery you'd be using (to flash the new CWM, ROM, Gapps) is provided by the file recovery.img (downloaded and copied to the SD card) rather than your current 5.5.0.4 on emmc. Make sure that you boot the NT off the SD card as prescribed in step #3 (otherwise you will end up booting emmc cyanoboot and CWM).
FYI, i'm pretty sure TWRP 2.7 (official from GooManager/TWRP site) doesn't work. if you click on the console button (square with lines in it, top) it'll say "This kernel doesn't support configuring SELinux" or something like that. i tried wiping stuff and it would just do a soft reboot. i may go file a proper report to TeamWin but i have CWM on there now and i don't particularly feel like reflashing a broken recovery.
TL;DR don't use TWRP
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
phrozen_flame said:
Hello, I'm new and trying to learn so please don't be too harsh. In following the instructions I somehow overwrote the stock rom and now duel boot CM 10.1 and 11. Any clue as in what I have done wrong?
Thanks in advance.
Click to expand...
Click to collapse
This thread OP is for updating the NT Internal Emmc to CM11 (from CM10.x), i.e., CM11 would be installed internally. If you were still running stock ROM internally, it wold be replaced by CM11.
good looking out
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
Ive been trying to update for a while now and i just couldn't figure it out until i came across your thread.and as right now i am running cm 11 and its all good so far.you made my day.
Help
digixmax said:
[Caveat emptor: adopt/follow this guide at your own risk].
[Important Note: this process is applicable for CM11 builds that still maintains two separate partitions for /data and /media – as in CM10.x and stock ROMs (see http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more info). If/when these two partitions get merged in some future CM11 builds (as being contemplated by our NT CM developers – see http://forum.xda-developers.com/showthread.php?t=2560827&page=28) this "CM10 to CM11" update process will not be valid for those future builds with merged /data+media partition].
Below is the process that can be used to update your NT emmc from CM10.x to CM11.
Download the following files to a location in your user content-media storage space on the NT:
the flashable_CWM_6.0.4.5_chrmhoffmann.zip file from https://www.mediafire.com/folder/xjwc1a482a6ll/Nook_Tablet which contains the CWM recovery v0.2 provided by Chris Hoffmann (in the first post of the XDA Official CM11 thread http://forum.xda-developers.com/showthread.php?t=2560827).
the zip file of CM11 ROM build of your choice from http://download.cyanogenmod.org/?device=acclaim (see http://www.cyanogenmod.org/blog/cm-11-m4-post-release-items for considerations in choosing nightlies vs. snapshot/stable builds)
the zip file of the Gapps package corresponding to CM11 – e.g., pa_gapps-modular-mini-4.4.2-20140301-signed.zip from http://goo.im/devs/paranoidandroid/roms/gapps-mini
Boot into your current emmc recovery
Select install zip and install flashable CWM recovery zip file.
Reboot into the new emmc recovery (flashed in the preceding step).
Select Wipe data & factory reset.
Select install zip and install CM11 zip file.
Select install zip and install Gapps zip file.
Reboot into the new CM11.
Once the NT boots up, set up the wifi connectivity and your google account info. If you had previously used Google backup service your apps will be auto-downloaded (but their settings will not be auto-restored).
If the NT on occasion boots or reboots into a black screen (in lieu of CM boot animation), then you have encountered one of the "random boot crashes" – more info and potential remedies, see http://forum.xda-developers.com/showpost.php?p=48941796&postcount=94 and http://forum.xda-developers.com/showthread.php?p=48301259#post48301259.
A few additional points worth noting:
Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later. To create a flashable recovery zip file for TWRP, use an archive file manager such as 7-zip to delete and replace the recovery.img inside the flashable recovery zip file (obtained in step 1(a) above) with your choice of TWRP internal recovery image file from http://techerrata.com/browse/twrp2/acclaim (e.g., openrecovery-twrp-2.6.3.1-acclaim.img). Remember to rename the downloaded TWRP .img file to recovery.img before inserting it into the recovery zip file, and also rename the resulting new recovery zip file to some other name like flashable_TWRP_2.x.y.z.zip to avoid future mix-up.
Installing CM11 ROM and Gapps will override your NT's CM10.x boot, recovery, ROM, and Apps, so make sure that you backup all this stuff using recovery backup function, for easy in reverting to CM10.x if desired. See my post at http://forum.xda-developers.com/showthread.php?p=48612997#post48612997 for more "Info and Tips for Mitigating Risks in Rooting and Flashing Custom-ROM".
I would advise against using any other functions of the recovery without first carefully researching to understand what they really do.
My thanks to all the developers who collective work created the wonderful CM11 ROM for the NT as well as the tools and info I made use of to install it.
Click to expand...
Click to collapse
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
11lump said:
So, will pa_gapps-modular-mini-4.4.2-20140608-signed.zip work with any cm11?
Click to expand...
Click to collapse
Yes.
Can't seem to figure this out myself. I have Twrp 2.6.3.0 and it won't let me flash CWM or CM11. Just gives the standard flashing error. Any ideas?
Sent from my XT1058 using XDA Free mobile app
Related
UPDATE: Since some of you guys are still finding this useful, I updated the CWM version to 3.0.2.8. Please note that ROM Manager is the best way to install CWM 3.0.2.8. You should only need this .zip if you need to restore the B&N boot loader.
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
This worked fantastic! Thank you!
byproxy said:
is this for use with any flashable rom or only certain ones? i'm on hcv4 and want to make sure this is safe to use before flashing it.
Click to expand...
Click to collapse
This is a standalone fix - its only necessary if you've flashed a rom and could no longer boot into CWM recovery afterward.
thanks again xawen!
Thanks so much for this! Great work!
Signature verification failed
Will This work with the Froyo builds?
Thanks
huemedia said:
Will This work with the Froyo builds?
Thanks
Click to expand...
Click to collapse
It should work with any build. It does not replace any of the build specific files, just the boot loader and the recovery images.
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Just what I was looking for... thanks!
omarsalmin said:
Works on phiremod (CM7). I was stressing why I couldn't reach my internal recovery, but was too lazy to do any research on the matter. Just stumbled upon this and everything is fixed again
Click to expand...
Click to collapse
what do you mean by "everything is fixed again"?
I like phiremod and all, but no internal storage is irking me and I want to go back to rooted stock and try to make a CM7 bootable SD.
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
This should be stickied. There are a LOT of CWR files around here right now.
oshigeru said:
Flashed this, now I'm stuck on the "Touch the Future of Reading" splash screen. Running CM7 nightly latest, dalingrin's 1100MHz Overclock.
Edit: Trying to boot, won't get past that damn splash screen. Tried reflashing cm7-encore-full-5.zip, gapps, got nothing. Going to try flashing the overclock again and see if that helps.
Edit2: No dice. I don't have a backup, either. Guess I have to flash a whole new boot.img?
Click to expand...
Click to collapse
Same thing kept happening to me. I would hold down the power button or power+n button or power+volume up + n button to get the NC to shut down. Then, I'd press the power+volume up + n button for a few seconds; this would get it to boot into CWR. From CWR I'd select reboot system. After that it would have no problem fully booting (until the problem happeend again). I did notice that after a while the startup boot took longer. After pressing the power button to power on the NC it would take several seconds before the "touch the future of reading" screen to come up, and it would take several more seconds (30 or so) for it to get past that screen.
I'm not sure what the beneft is of doing this; as long as I have a CWR bootable microSD with me (always in the NC's case) I don't need this.
xawen said:
There are a number of CWM installable .zip files being distributed that break Clockworkmod in a way that Rom Manager will not fix. This .zip file will reinstall the B&N bootloader (to enable the recovery buttons) and install ClockworkMod on your internal memory. This .zip will only help if you have installed a "flashable" .zip and can no longer get into CWM by holding N + Power on boot.
This file can be installed with IOMonster's bootable CWM to re-enable the ability to use CWM without an SD card.
How to use:
1) Create a bootable CWM SD card from the link above.
2) Mount the SD card on your computer and copy the RecoveryFix.zip file to it.
3) Boot the Nook into CWM from the SD card.
4) Choose "install zip from sdcard"
5) Choose "choose zip from sdcard"
6) Browse to the RecoveryFix.zip and select it.
7) Choose "Yes - Install RecoveryFix.zip"
CWM should now work by booting and holding the N + Power buttons.
Technical details:
The bootloader (u-boot.bin) file included with the stock image has code to look for the recovery key sequence on boot. It also contains the "Touch the Future of Reading" splash screen. Some of the update .zip releases include a custom uboot.bin (to change the splash screen) that does not look for the recovery keys...so there's no way to boot into recovery without an SD.
Currently the only automated way to put the correct files back is by using one of the stock recovery .zips. These take the entire system back to stock though. All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition. This can also be easily fixed by booting any image from an SD card and copying these files manually.
Click to expand...
Click to collapse
This fixed my nook. Thanks!!!!!
Works - after a few tries!
Really appreciate the work. Thanks!
While I keep my boot disk with me, I am very happy to have the ability to power+N into CWR.
Great work, thanks m8s!
xawen said:
All this .zip does is replace the stock u-boot.bin file, CWM uRecRam and CWM uRecImg files on the /boot partition.
Click to expand...
Click to collapse
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
ADude said:
Can you be more specific about exactly which u-boot.bin, uRecRam and uRecImg files are included - including source and version ?
Click to expand...
Click to collapse
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
xawen said:
This .zip has the stock (B&N) u-boot.bin and the uRecRam and uRecImg for CWM 3.0.0.5. It was built a while ago to fix an issue with specific CMW installable Froyo .zip files that were being distributed. I haven't seen any CM7 images with this problem, but if anyone still has a need for this I can update to a current CWM version and post tonight.
Click to expand...
Click to collapse
Aha - I looked more closely and saw that it is an old thread that was brought to the surface by a "thanks" comment.
question
So I flash this fix and can get into CWM 3.0.0.5, then I flash the official CWM 3.0.1.0 and can no longer get into recovery. I also tried the manual procedure using adb. Still no dice.
What am I doing wrong?
CWM 5.8.0.9 for Huawei MediaPad
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
I don't know how much this CWM version improves over the existing one by segler11.
However these build were more aimed at compiling and testing the new kernel sources.
I have tested compiling with both arm-eabi-4.4.0 and arm-eabi-4.4.3 with success on Ubuntu 10.04.
This is experimental, however with the new kernel sources it will just be a matter of time.
I have compiled the kernel included in this CWM recovery image but I didn't recompile the complete image.
I took as base Pyramid CWM 5.8.0.9 and I replaced the files from those found on a stock C232B005 kernel.
As the default build configuration I have used the /proc/config.gz of a C232B005 running kernel.
I have tested this CWM to be able to backup these partitions (I have not tested "restore" yet, just checked the tar archives):
boot.img - 12.582.912 (match 12Mb)
recovery.img - 16.777.216 (match 16Mb)
data.ext4.tar
cache.ext4.tar
system.ext4.tar
custom.ext4.tar
as you can see my hand tweaks to "recovery" require the name of "cust" partition to be "custom" instead but I believe this is a no issue while you backup and restore with the same CWM. Suggestions welcome.
BUGS:
data & time on archives are wrong
mount USB storage does not work
adb not enabled in recovery mode
Formats and Wipes do not work don't use them
The "busybox hwclock" applet doesn't work to set the hardware clock of our device.
The "adb shell" is not active while in CWM recovery, I don't know why and this was my objective so if you have suggestion please help.
As usual flash both "recovery" and "recovery2" partitions using "fastboot" and one of the attached CWM recovery:
Code:
fastboot flash recovery recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot flash recovery2 recovery-5.8.0.9-HWMOD-eabi-4.4.3.img
fastboot reboot
WARNING !!! DON'T FORMAT AND DON'T WIPE PARTITIONS USING THESE CWM !
.:HWMOD:.
.
Reserved CWM HWMOD
This version seemed to work better for me.Tnx dude!
john9 said:
This version seemed to work better for me.Tnx dude!
Click to expand...
Click to collapse
Thank you for trying it.
Remember to absolutely avoid formatting or wiping partitions.
If you need to format/wipe do it ONLY after reinstalling the original "recovery.img" in both "recovery" and "recovery2" partitions and then reset the device from:
"Settings -> Backup and reset -> Factory reset"
ATTENTION !!! You can safely do a wipe or factory reset only after reinstalling the original recovery image.
Sorry for insisting but I don't want to create problems on users devices and I know those operations will create problems.
.:HWMOD:.
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
cmstlist said:
Just a note: I used your 4.4.3 version to try making a nandroid backup last night. Good news and bad news.
This morning I inspected the result using the app Nandroid Browser.
Good: Your CWM does successfully backup /data/data. The other CWM that had been posted here did not do so properly.
Bad: Your CWM also backs up the entire internal SD storage contents inside the folder /data/share. It is customary *not* to include this in a nandroid backup because a) you don't want to inflate the file size unnecessarily, and b) you don't want to overwrite the internal SD on a restore.
Idea: After you fix it, and until you manage to get ADB over USB working, maybe you could add a menu option to make a separate backup archive of internal SD to external SD. This would allow a route to save the internal storage if the device becomes unbootable and requires a data wipe.
Click to expand...
Click to collapse
Thank you for trying it. I wanted to compile/test a kernel with new sources in a CWM.
Yes, in our device the internal memory "/mnt/sdcard" is also mapped under "/data/share".
Unfortunately I don't have the skills (yet) to build a complete recovery image from scratch,
so what I did was just compiling the kernel part of the recovery image, using the new sources.
Then I simply hex tweaked the "recovery" executable of a 5.8.0.9 Pyramid CWM (HTC Sensation).
So, in conclusion, I have no control over what is copied during the backup process of those partitions.
Though I could control which partition is processed by removing them from "fstab", but there is no gain into it.
We will have to wait somebody with the specific knowledge, or maybe I will have some time to learn once I return from holidays.
.:HWMOD:.
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
after_silence said:
Today i have builded bootable CWM 5.5.0.4 from sources, so now we can adjust all what we need
Click to expand...
Click to collapse
well done
HI, can anyone share buckup from working device created by CWM.?
Thanks to all.
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
.dredd. said:
Hi,
Is it possible to flash update zips from this CWM recovery (like Beats Audio which is in flashable zip format)?
I don't want to use it for backup-recovery.
...and how about doing wipe cache and wipe dalvik cache?
Click to expand...
Click to collapse
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
hwmod said:
Haven't tried installing a ".zip" archive from CWM but it should work.
Avoid "wiping" and/or "formatting" partitions, they will be messed up.
Click to expand...
Click to collapse
The main reason for use of CWM would be to have the possibility of flashing update zips from CWM... but I am afraid of messing up my device... to understand: no problem if I have to reflash the rom but I would not want to cause mistake which could be repaired only by service.
fastboot is always available if something goes wrong and if you flash cwm you wont be able to install official roms because cwm will overwrite stock recovery
so i was stupid and wiped data and cache - then remembered that it said not to - how do i fix this paperweight? i tried fastbooting all the usual partitions (system, boot, userdata, cache, etc) but still nothing - i can get to fastboot but i cant flash any dload updates. any suggestions are greatly appreciated.
flash stock recovery (2 files) from zipped rom via fastboot and then you should be able to flash stock rom
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
byt3b0mb said:
flashed three different stock recoveries to recovery and recovery2 - still only get the media pad logo twice (flashed androidani intl rom before bricking) cant boot to recovery - think the partition table is screwed. is there a way to create partitions from fastboot, and if so, still would be nice to know the names of the partitions to flash as referenced in tmo stock thread.
Click to expand...
Click to collapse
The time needed to reformat and rewrite all the firmware partitions (the first time) will be between 10-15 minutes.
Be patient and give enough time to the device to execute all the needed processes.
When the device finally boot it need to completely regenerate dalvik-cache (the first time).
So try again as instructed above, rewrite "BOTH" partitions named "recovery" and "recovery2", both using the same "recovery.img" file found in the latest stock Huawei firmware.
Now extract the stock Huawei firmware archive on your PC and copy the "dload" folder on an empty formatted SDCard, then insert the SDCard in the MediaPad reboot it and wait until success or failure message.
If you wiped partitions you will have to wait more time (20-30m). It may be that after waiting a while a message about "Encryption not possible" could appear, just say no to encryption and let it reset the device.
It already happened to some of us so hope you are also able to recover your tablet.
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
byt3b0mb said:
thanks i will give it a shot - while it is rewriting partitions, should it be on the huawei logo? or should i see the android / gears turning?
Click to expand...
Click to collapse
First time restoration takes time on both moments during the 1st Huawei log and even during animation.
Trying to recover a partition that was wiped takes much longer for the OS to show the error.
When I tried wiping "data" and rebooted the device I recall I went for a long walk and when I returned the device was showing the "Encryption failure / Reset" message (about half an hour later).
So I can only suggest that when you retry you wait at least that amount of time (30 min.) with charger connected, whatever happens leave it alone until it display or ask you do something. Let me know if it works when you have tried.
Download links do not work for me. Can you upload in mediafire please?
I have some questions about this whole process.
Is one rooted nook the same as another rooted nook (before using a ROM)?
Is this a good rooting tutorial:http://www.youtube.com/watch?v=5n2D5-Q6UFg
I think I would like to follow this tutorial, option C: http://forum.xda-developers.com/showthread.php?t=2081981
The first part of C says:
1. You need a bootable CWM card. Instead of making my own I use Albert's root image from B (above) because this image includes CWM 5.x.x. I use this to flash a higher version CWM internally. I erase the zip files from the card to make room for a flashable CWM 6.x.x
That refers to this link: http://forum.xda-developers.com/showthread.php?p=21275927#post21275927
That tutorial says:
6. Reboot using CWM settings
9. Follow Video for Root Calibration with Apps
7. Sideload all you want (See folder for select games and other stuff)
What does reboot using CWM settings mean? And the video for root calibration with apps is no longer available. And as far as sideloading goes, I wouldn't know what to sideload.
Then back to the original tutorial, it says:
2. Find a flashable CWM 6.x.x I found mine through http://forum.xda-developers.com/show....php?t=1640958
I use the one named "flash_cm9-10_cwm v6...." Download and copy to your sd card.
I'm not sure what a good version is. Do they all do the same thing? Can you install any version?
As you can tell I'm pretty confused on the details of these things.
I've probably got more questions but haven't gotten that far yet.
I wrote that tutorial, but I have since changed my way of doing things.
Anyway, you are not meant to jump between the two tutorials and do the rooting with that first card. It's simply a way to get a bootable CWM 5 card without having to set up partitions or anything like that. You only use that card top boot into CWM 5.
I understand from another topic that Albert's root image may not be available at his download link, but Brian's boot that I mention in the "B" section should work as well and so would a couple of others as well.
I give a link and a name of the CWM 6 file I used back then, and it should still be good.
That "changed my my of doing things" now is I skip the CWM5 step and use the CM10 sd-card that I had been using before installing it internally. I link to that image in section "A". You can use that card as a bootable CWM 6 card. The process if using that would be something like
1. Download and burn the image to a 2GB or larger sd-card. No need to expand partitions since you won't actually use this the way it was intended.
2. When booting, hold the "n" key to get into Cyanoboot menu. Once in the menu there should be a "sd recovery" or similar choice to make.
3. You should now be in CWM 6.x.x and be able to flash your ROM and gApps.
Once your CM10 (I would suggest staying with Succulent (Iamafanof) CM10, dated 1231) CWM 6 and Cyanoboot are both included and you can boot intoi Cyanoboot without the CWM bootable card.
If you feel very lost when trying to follow different tutorials, consider running from sd-card insteda with one of Succulents ready-made images (he has bot CM10 and CM10.1 images). Ther is very little loss in performance in my experience.
SuperGCNBoy said:
I have some questions about this whole process.
...
Click to expand...
Click to collapse
You can find some helpful background info and pointers at http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31 and http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1.
I have an 8gb nook tablet that I rooted probably 2 and a half years ago and haven't changed anything on it since. I am wanting to undo and update to current root and flash a 4.4 rom like on my phone. What is the best way to go about this? I know how to unroot, I just need to know the best way to root currently. Thanks.
Custom ROMs like CM comes with built-in root capability, and moreover once installed replaces completely the existing ROM currently in place (be it stock ROM, rooted stock ROM, or another custom ROM). As such, there is no need to root (or re-root) prior to flashing a custom ROM. See http://forum.xda-developers.com/showthread.php?t=2575489 for more background info and pointers.
Cool, thanks for the reply and links. I have some reading to do.
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also? Will it work for CM11 also?
ryknow27 said:
Will your guide for Installing CM10.1 Internally on Nook Tablet work for the 8gb model also?
Click to expand...
Click to collapse
Yes.
Will it work for CM11 also?
Click to expand...
Click to collapse
It should work (with the usual caveat YMMV). Flashing CM11 requires CWM version 6.0.4.5 or later, or TWRP version 2.6.3.0 or later (in step 2(b) of http://forum.xda-developers.com/showpost.php?p=43326042&postcount=123); you can find the SD version of TWRP 2.6.3.x at http://techerrata.com/browse/twrp2/acclaim. You also need a recent Gapps version corresponding to the CM11.
Alternatively, if your NT is already on CM10.x (as my NT was), you can:
download CM11 ROM and the corresponding Gapps zip files onto your NT (user content media partition).
use SD based recovery to flash a flashable emmc CWM zip (http://forum.xda-developers.com/showpost.php?p=48855275&postcount=2) or flashable emmc TWRP zip (http://forum.xda-developers.com/showpost.php?p=49111924&postcount=8) into emmc.
remove SD then boot onto emmc recovery (which is installed in step 2) and use it to install the ROM and Gapps zip files downloaded in step 1.
Remember to use SD based recovery to backup your current ROM before flashing CM.
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
ryknow27 said:
I need help once again. In step 2a. of Installing CM10.1 Internally on Nook Tablet, I do not see the boot.zip with the 3 files needed and I am not sure how to extract them from the .img file from the pre-made SDcard images. I've only used linux like once and that was to root my Droid DNA. Thank you for your patience with me.
Nevermind...I found a Linux Reader program that let me extract them.
Thanks again.
Click to expand...
Click to collapse
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
digixmax said:
For future reference, you can use 7-zip (which is available for windows) to open .img files and extract its content.
Click to expand...
Click to collapse
I did try 7-zip first and it didn't work. I may have just done something wrong. I'll try it again. Thanks for all the help.
Looking for some help.
I tried to update my old Samsung Galaxy S2 to Android 6.0.1 - while I did this successfully, I wasn't aware that I needed to increase the system partition size, so the GAPPs installation failed.
I thought that once the system partition size was increased, then I would be able to just go back and unzip the GAPPs file in recovery mode, but now when I enter recovery mode it's Cyanogenmod recovery which doesn't have an option to open zipped files from the SD card.
I have tried unzipping GAPPs via file manager on the phone, but it says that the file is too large.
I'm new to this, but feel that if I could just get back to the old TWRP recovery with the unzip option I could just wipe everything and reinstall everything from the mini SD card, but with no such option with the Cyanogenmod recovery I'm stumped as to what to do next.
Any thoughts on where to go from here would be very much appreciated.
Jimsin said:
Looking for some help.
I tried to update my old Samsung Galaxy S2 to Android 6.0.1 - while I did this successfully, I wasn't aware that I needed to increase the system partition size, so the GAPPs installation failed.
I thought that once the system partition size was increased, then I would be able to just go back and unzip the GAPPs file in recovery mode, but now when I enter recovery mode it's Cyanogenmod recovery which doesn't have an option to open zipped files from the SD card.
I have tried unzipping GAPPs via file manager on the phone, but it says that the file is too large.
I'm new to this, but feel that if I could just get back to the old TWRP recovery with the unzip option I could just wipe everything and reinstall everything from the mini SD card, but with no such option with the Cyanogenmod recovery I'm stumped as to what to do next.
Any thoughts on where to go from here would be very much appreciated.
Click to expand...
Click to collapse
2 important things when updating to cm13:
Increase Partitiones to 1 GB System and 4 GB data
before flashing.
Flash isorec twrp recovery 3.0.2-1 before or together with rom and gapps.
All files are zip-files to be flashed with recovery.
Do not unzip this Files.
Read noob friendly Guide by Saber "want to update to cm 13 .....
You will find everything you need there.
Sent from my ME173X using XDA-Developers mobile app
Many thanks for the reply - yeah, I realise now that I should have increased the system partition size BEFORE CM13, but sadly I didn't.
My issue is now that I have no idea how to change the recovery mode back to something like TWRP that will allow me to unzip files again - I tried simply flashing it with ODIN, but it failed & I'm still stuck with CM13
Jimsin said:
Many thanks for the reply - yeah, I realise now that I should have increased the system partition size BEFORE CM13, but sadly I didn't.
My issue is now that I have no idea how to change the recovery mode back to something like TWRP that will allow me to unzip files again - I tried simply flashing it with ODIN, but it failed & I'm still stuck with CM13
Click to expand...
Click to collapse
You have to flash a Recovery whith Odin.
So i would repit again to bei Sure its done properly.
- in Odin Flash pitfile 1gb System _4 gb Data
together with Gustavo Kernel KK with cwm Recovery.tar (Flash Recovery in PDA and do not forget to tick on repartition)
- in cwm Recovery Format: mounts and storage/Format sd0 (Internal SD)/select "default"/swipe
- then wipe Data, Cache, System
- Install cm 13 + gapps + isorec twrp recovery 3.0.2-1.zip in ONE GO (do not reboot in between !!)
- reboot system
Sent from my ME173X using XDA-Developers mobile app
Follow my complete tutorial to do so. Odin not needed.
https://forum.xda-developers.com/galaxy-s2/help/guide-tutorial-samsung-galaxy-s2-i9100-t3538601