Related
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!
CLICK PIC FOR TEAM HOMEPAGE
ClockworkMod 5.5.0.4 Touch Recovery - TEAM DRH (Update 03/05/12)
This version of ClockworkMod Recovery is based on version 5.5.0.4 and has the following "perks:"
Touchscreen
Capacitive buttons can select, move up/down, and go back
Download:
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR_Touch_5504_B15_normalfont_DRH.img (NVFLASH)
http://teamdrh.com/DRH-Downloads/Touch_Recovery/CWMR5504_recovery_B15.zip (Flashable Zip)
How to Install:
There are 2 ways to install. Either run the update through the "CWMR5504_recovery_B15.zip" file or use the "CWMR_Touch_5504_B15_normalfont_DRH.img" image if you will be flashing it with NVFLASH.
NVFLASH Command
To flash use the following commands:
Code:
nvflash --bl bootloader.bin --download 9 CWMR_Touch_5504_B15_normalfont_DRH.img
Changelog:
Added DRH logo
Roboto Font
Changed Mount UDB Storage to the /EMMC
Added the option to format the internal sdcard /emmc
Fixed the magic number mismatch issue
Ability to select update from External SDCard or Internal SDCard
Made internal/external partitions clear
Fixed reboot recovery loop
Allowed the /misc partition to be formatted incase you get stuck in a reboot recovery loop
Swap size bug fixed
Kanged commits to fix the UI overlapping the buttons
Removed /misc (fixes hanging at birds)
Switched from stock Viewsonic kernel to Pershoot's
To Do:
Proper reboot into CWM Recovery
More will be added to the list as more bugs are encountered (if any)
How to Perform a Backup
For those wanting to do backup. Here is the step by step on how to get it to work until a proper fix is done (thanks raj...didnt' understand what you were were saying at first):
REMOVE external sd
Boot to CWMR
Go to "mounts and storage" & select "mount /sdcard" (this is what I didn't understand..how internal could be seen as /emmc & /sdcard)
go back to main menu & select "backup and restore"
select "backup to internal sd"
watch backup complete (including .android_secure on the internal sd)
Thanks to AlAbbo for the instructions!
For the people who wonder what this does:
http://www.youtube.com/watch?v=bGKahQaJadQ
Ported to the G-Tablet by Plastikman
-based on CWM from Koush
-Other credits: gweedo767, cennis91, utkanos
-Original Google+ project page here
Reserved for future use.
I think this was a great idea...nice job...
i have clock work 5.0.2.7...something like that...and wen i install ur zip it works....pull battery...gor right cack into recovery...and its not urs anymore...where can i get clockworkmod 5.5.0.4...so then it willl stay on...i guess i need an update of clock work mod recovery...can you help me out...thanks in advance... ;-)
Guys
I am stuck in a recovery boot loop
How do you fix this?
chief1978 said:
Guys
I am stuck in a recovery boot loop
How do you fix this?
Click to expand...
Click to collapse
Fixed with nvflash
guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?
dony71 said:
guys,
will this CWM 5.5.0.4 work for update froyo / gingerbread rom also?
currently i'm still using beasty rom (froyo) and thinking to try ICS rom
but if i don't like it, i might want to restore using thisCWM 5.5.0.4
from backup which i have created using CWM 3.0.2.8
is it doable like this?
Click to expand...
Click to collapse
ROM backups need to be backed up and restored with the same version of CWM.
Sent from my ICS powered g-Tablet using XDA Premium.
rmarinella said:
ROM backups need to be backed up and restored with the same version of CWM.
Click to expand...
Click to collapse
Not necessarily.
rajeevvp said:
Not necessarily.
Click to expand...
Click to collapse
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.
rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Sent from my HTC Thunderbolt using xda premium.
Click to expand...
Click to collapse
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.
rmarinella said:
Should I change that to should be backed up and restored with the same version? It's not fun to find out a backup won't restore due to incompatibility.
Click to expand...
Click to collapse
fosser2 said:
Should is a better word. I have seen backups restored w/ different versions of CWM but I have also seen them fail due to different revisions.
Click to expand...
Click to collapse
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities with CWM-5.x which only come up when you create a backup in CWM-5.x and then try to restore in one of the older CWM versions. (Going the other way is no problem--ie. CWM-5.x will happily read and restore the backup files created by all the older versions of CWM.):
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.
rajeevvp said:
There is no incompatibility for backups/restores between CWM versions 2.x, 3.x and 4.x. Both the filenames and the contents of the backup files will be the same. Try it: load each of them in turn, do a backup in each, and look at the nandroid.md5 file produced. Apart from the cache.img and recovery.img files, all the other MD5 sums will be the same.
There are 2 minor incompatibilities when it comes to CWM 5.x.
1. File formats. The contents of /data and /sdcard/.android_secure are now in tar files instead of the old yaffs2 image files.
2. Filenames. The backup filenames have changed from partition_name.img to partition_name.fstype.ext.
To fix the first incompatibility, you can add a ro.cwm.prefer_tar=false line to the /default.prop file in CWM. With this change, CWM-5.x will create the exact same backup files (yaffs2 images) that the other CWM versions also output.
The second incompatibility you can just as easily fix by removing the "fstype." from the backup filenames created by CWM-5.x, and then changing the names to suit in the nandroid.md5 file.
Click to expand...
Click to collapse
What you've stated should be the case. However, I have had issues with compatibility between versions. Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Sent from my HTC Thunderbolt using xda premium.
Bottom line is we should point newer users to proven successful methods that will eliminate most challenges. Following one common procedure for each upgrade, backup and restore accomplishes this.
Click to expand...
Click to collapse
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
rmarinella said:
However, I have had issues with compatibility between versions.
Click to expand...
Click to collapse
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.
rajeevvp said:
Very admirable--if a little vague. All of these are "proven successful methods that will eliminate most challenges". In Q&A format:
Q. Can I backup in CWM-2.x and restore using CWM-{3,4,5}.x?
A. Yes.
Q. Backup in CWM-3.x and restore using CWM-{2,4,5}.x?
A. Yes.
Q. Backup in CWM-4.x and restore using CWM-{2,3,5}.x?
A. Yes.
Q. Backup in CWM-5.x and restore using CWM-{4,3,2}.x?
A. No, but it's possible.
There is only one case which doesn't work. None of the other cases will cause problems.
Which specific versions of CWM and while doing what precisely? Except in one case, the files created (and understood) are exactly the same, so no incompatibility can exist between versions as far as backups and restores are concerned.
Click to expand...
Click to collapse
How confrontational! Sorry, I don't keep logs.
Sent from my HTC Thunderbolt using xda premium.
rmarinella said:
How confrontational! Sorry, I don't keep logs.
Click to expand...
Click to collapse
Nope. Helpful, actually. Meant specifically to help answer questions like this one.
Originally Posted by chief1978 View Post
Guys
I am stuck in a recovery boot loop
How do you fix this?
Fixed with nvflash
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.
hungsohlo said:
Can I get some clarification on this? I flashed with nvflash successfully but I'm stuck in a boot loop.
Click to expand...
Click to collapse
What kind of boot loop?
For an ordinary kind of boot loop, simply boot into CWM and do a "wipe data/factory reset".
For a recovery boot loop see this thread.
I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.
same as the above poster
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1
genei.09 said:
I've tried nvflash and the .zip file. I can not boot back into recovery after installing this CWM. Was originally on CWM v08.
Click to expand...
Click to collapse
hungsohlo said:
Also whenever I use NvFlash to go back to stock it works correctly but any attempt to flash another rom and it just sits at the 3 birds screen. When I try to flash this and go back into CW recovery it just says booting to kernal image.
---------- Post added at 02:46 PM ---------- Previous post was at 02:02 PM ----------
Forgot to mention earlier - my currect CW version is 2.5.1.1
Click to expand...
Click to collapse
Both of you have the same problem. You have a 1.1 bootloader, but, this version of CWM has a kernel built to run on a 1.2 bootloader (this is indicated in the thread title, actually).
Use one of the versions of CWM with a 1.1 kernel in it. See this thread.
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
bluevolume said:
I updated to the 7.2 RC Kang via CWM, but now my Nook will only boot to CWM. I was already on a 7.2 beta and working fine. Flashed the newest release, cleared cache and dalvik, now all it will do is boot to CWM.
I have taken the SD card right out and its doing the same thing. I have the Cyanogen boot loader on there (shows Cy logo instead of "The Future...").
Appreciate any guidance.
Click to expand...
Click to collapse
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
If it is booting to CWM recovery and not locking up, that means the 'boot to recovery' flag is set and is not clearing when you leave CWM like it should. Try doing some things in CWM before you exit, like wiping cache or something. And when you exit, exit by the menu, not just powering off.
You can also try using the boot menu to try to force you to emmc. Hold the n button while booting and when the boot menu comes up, pick emmc and normal and reboot.
Edit: You say you take the SD out and it does the same. Why would you expect it to be different? Are you running from SD? If so you should not be flashing things with CWM, that puts things on emmc. Or did you mean you take the bootable CWM SD out? You should always take that out after flashing to emmc. And if your already running CM7 from emmc, you should be flashing with the CWM on emmc, not a bootable CWM SD. I'm confused as to what you were doing and what your configuration was.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
bluevolume said:
I took the SD card out as someone had suggested that in the ROM thread. No, it doesn't make sense that if would just start booting from the SD card when it wasn't before, but it eliminated a variable.
I have gone into the boot menu and checked that it is booting from emmc. I've even changed it to SD and back just to make sure it took.
Click to expand...
Click to collapse
Then it is the set flag issue I mentioned in the first part of my post. Not sure how to get it cleared. Just exercising CWM? Try flashing something else. Gapps again maybe. It won't hurt to flash them twice.
Edit: btw, what version of CWM are you running?
Sent from my Nook Color running ICS and Tapatalk
CWM v3.2.0.1
I installed gapps again, same problem. Gremlins!
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
cmendonc2 said:
I had this problem, but the only way I found to fix it was to flash a stock recovery zip from CWM recovery SD card, then CM7 again
Click to expand...
Click to collapse
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
leapinlar said:
But in his case it is not locking up. It is cleanly rebooting to CWM. A little different scenario than yours.
Click to expand...
Click to collapse
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
Yes, I've had CWM flashed into the emmc for a while. So I could use the boot menu utility to boot to CWM if needed.
BTW - this is the ROM i'm using: http://forum.xda-developers.com/showthread.php?t=1344873
votinh said:
How could it reboot into CwM if there is no flashable CwM uSD installed, where those "Rec" files reside?
Did you some how flash CwM into eMMC before, OP?
Click to expand...
Click to collapse
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Edit: @bluevolume - a possible solution is to make a bootable CWM SD and boot to that. That may reset the flag when it exits.
Edit 2: I found where the recovery flag is stored on the nook. There is a separate partition (2) called /rom that stores basic information like your model number, date of manufacture, serial number, etc. Also there is a file named BCB which is usually an empty file. But if the word 'recovery' is written there properly, it will always boot into recovery. Recovery is supposed to write the empty file back when finished so that on next boot it boots normally to emmc. I'm not sure how much good this information is going to do you, but if you are proficient with adb, you can modify the file even if in recovery.
Click to expand...
Click to collapse
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue. I'll revisit that later today.
bluevolume said:
That is good info, thank you. I have not been able to get ADB working in the past (i'm on Win 7 64); I think its a driver issue.
Click to expand...
Click to collapse
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
leapinlar said:
If you can get adb working in CWM, this is what you want to do in at the dos prompt, one line at a time:
adb shell mount -t vfat /dev/block/mmcblk0p2 /rom
adb shell dd if=/dev/zero of=/rom/bcb bs=512 count=1
adb shell reboot
Edit: if you want help getting adb working this post may help:
http://forum.xda-developers.com/showthread.php?p=21665649
Edit2: I've been doing a lot of experimenting. It is not what's in the bcb file. It's what the file size is. If the file size is 512 bytes or larger it will boot to normal emmc. If it is smaller than 512 bytes or MISSING, it will boot to recovery. It could be yours is missing. But recovery is supposed to create a new big one if it is. Could be a permissions problem. If you get adb going you can fix that.
On a side note I was thinking it could be corrupted boot files causing this, but I purposely messed with them and it does not boot into recovery, it just hangs.
Click to expand...
Click to collapse
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I'm not that comfortable with adb commands so I starting looking for other solutions. Since you mentioned that its the actual boot files that are missing/corrupted, I searched around and found this:
http://forum.xda-developers.com/showthread.php?t=958748
I loaded the RecoveryFix.zip on my SD card and flashed it with CWM. Rebooted, and I was back to the 'Future of reading..." boot logo, but it still went straight to CWM. So I flashed the ROM again (the ROM I listed earlier in the thread), wiped cache, fixed permissions. Rebooted, and the "Cyanogenmod" boot logo was back. And instead of going right to CWM, the screen was blank for quite a while then I saw the little Android guy skate by... And I'm back in business.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
bluevolume said:
Let me first thank you for your time and support on this; its people like you that make these forums such a great resource.
I know other people have had this problem and this seems like a pretty simple solution. I'm good at this point, and hopefully some other people will find this thread helpful.
Click to expand...
Click to collapse
The next step I was going suggest if you could not fix it was to flash a new CWM to your boot files. Good job finding that.
Glad you got it running. I learned a lot myself and maybe that info will help others.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
He is on emmc. He had a CM version on earlier and used ROM Manager to put CWM on the emmc boot partition. This problem only emerged when he flashed the newest CM to emmc from ROM Manager with the CWM on emmc. He now only boots to CWM and it is loaded from emmc boot. It is a flag set problem. The boot loader is telling it to go to recovery instead of normal ROM. That flag is set by ROM Manager when it wants CWM to perform a task for it. Like flash a ROM. That is how the boot loader knows to boot to recovery rather than the ROM. CWM is supposed to reset that flag when it has finished the task that ROM Manager asked it to do. Somehow it is not being reset.
Click to expand...
Click to collapse
Got it, thanks m8
That clears up my mind.
I had the same problem, followed the thread you found. Did the same thing, now I'm back in business too. Thanks!
Just wanted to say thanks for figuring this out! I was in a similar situation after downgrading from cm9 back to cm7. Installed CWM using recoveryfix_3.0.2.8.zip from the thread above, and was back up and running after a restore of a cwm backup. Headed on vacation tomorrow and the wife would have had my head for being such an FW... you're a lifesaver!
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Finding installed ROM
sjs_bebop said:
Hi all. I have a Nook Color running CM 10.2 and am trying to upgrade it without success.
I have Superuser, CyanogenmodRom_Download, and TWRP downloaded.
Using CyanogenmodROM_Downloader configured to use TWRP I can successfully download a new Nightly. When I select Flash it takes me to Cyanboot. I select Internal eMMC Recovery and it brings up a notice saying that the Install Failed.
I tried using TWRP->Install->CyanogenROM_Downloader->cm-10.2-20131009-NIGHTLY-encore.zip. I'm not Wiping anything. Cyanboot into Internal eMMC recovery and the existing release instead of the update is installed.
Also, the only way I can tell which build is installed is with the CyanogenROM_Downloader. I looked around the web for something that would tell me where to look and didn't find anything. I also looked around /etc and didn't find anything obvious. Is there an easy way to tell what nightly build is installed?
I've been beating on this step for a couple of days now and looking around this site and the web and haven't found anything that helps although I'm sure it's out there somewhere. Any suggestions would be appreciated.
Thanks
Steve S.
Click to expand...
Click to collapse
Go into system settings / about tablet (at bottom of settings)
About 3/4 down list you'll see the ROM installed. Also kernel info plus other info.
For updates ;
I go to this link and download directly.
http://download.cyanogenmod.org/?type=nightly&device=encore
Also I copy and paste the md5 sum into MD5 checker (free in play store), run the check.
Reboot into recovery using power button menu and install in TWRP there. I had too many problems using cm downloader, goo manager, etc.
nook color cm10.2 update problems
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Sounds like a problem I had a while back
sjs_bebop said:
Thanks. That helps. I can determine the version now.
But I still can't get update to work. I downloaded from the location you gave using the browser and can see the file using TWRP and selecting install. This boots into the cyanoboot loader, there are two options enabled: 'Internal eMMC Normal' and 'Internal eMMC Recovery.' Normal seems to reboot -- which makes sense. Recovery re-installs the currently installed version. Also, using ADB I can see the new cm-nightly zip file in /storage/sdcard1/Download.
I don't see TWRP during the reboot. Should I??
I also don't get an option to select a new image to install. Should I?
I also tried copying the cm-nightly zip file to the /emmc directory and that doesn't seem to make any difference.
Click to expand...
Click to collapse
You may be having partition problems. I have had either lost the ability to install new nightlies or the ability to backup. Read the instructions through completely first. Get the info together and then start.
If you have a backup App like titanium backup, backup all files and data before anything else. Also if you can, do a backup in recovery before doing the following.
Check this link: http://forum.xda-developers.com/showthread.php?p=28457126#post28457126 by Leapinlar
I set up a 2Gb sd bootable card to run these from using the CWM recovery (If you need help check eyeballer's link below).
I put the partition repair files on it. Also the 1.4.3 Stock rom, the TWRP open recovery. zip 2.4.1.0 (http://forum.xda-developers.com/showpost.php?p=37554712&postcount=129), and the latest Rom you want to install and Gapps.
After following leapinlar's instructions including installing the 1.4.3 Stock rom (fixes other possible problems), then follow eyeballer's install for the Rom, Gapps and recovery here (http://forum.xda-developers.com/showthread.php?t=1030227&highlight=install+cm7+to+nook+color).
After booting and doing the initial CM setup return to recovery and VERY IMPORTANT ***restore only the data*** Not boot or system from your latest backup. This should get you back up and running. If you have a backup like Titanium restore "newer versions of apps" if you had to use an older recovery backup. Once you have everything set reboot into recovery and do another backup for safeties sake.
Including my wife's Nook I have four units and have needed to do this 4 or 5 times. Takes a little time but has always worked great. I keep the card available and update the Rom, Gapps or whatever else needs changing.
This link also contains a lot of helpful info. I have all these bookmarked on both my PC and Nook.
User Tips http://forum.xda-developers.com/showthread.php?p=25354258#post25354258
Caveat emptor: adopt/follow this guide at your own risk.
Below is a procedure that can be used to update your HD+ EMMC to LN14.1 from CM11 (if your HD+ is currently running stock ROM, use the process described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810/).
Download the following files to a location in your user content-media storage space on the HD+:
amaces' flashable TWRP zip file, e.g., twrp-3.0.1-0-ovation.zip ( https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778)
amaces' flashable LN14.1 ROM zip file, e.g., lnos_ovation-ota-NMF26Q.170104.zip from https://notredame.app.box.com/s/26a4bygh9vbaw7jjq08xr5evomvaw5ww/1/3332706778
the flashable zip file of the Gapps pico package open_gapps-arm-7.1-pico-2017[mmdd].zip from http://opengapps.org/
Boot into your current EMMC recovery.
Select install zip and install the TWRP recovery zip file obtained in step 1(a).
Power off the Nook.
Boot into the new TWRP recovery flashed in the step 3 (press and hold the Home button, then press and hold the Power button until after the CyanoBoot Universal Bootloader screen comes on, then release both buttons).
Select wipe /data & factory reset.
Select install zip and install the LN14.1 zip file.
Select install zip and install the Gapps zip file.
Reboot into the new LN14.1.
Once the Nook completes the boot (be patient as it takes quite a bit of time), set up the Wifi connectivity and your Google account info. Note that the Apps you previously have on CM11 will not be auto-downloaded/restored into your new LN14.1.
If you run into problems during initial setup:
- absence of WiFi network setup step: see this post
- setup process crashes (as have been reported with some combos of ROM and GApps build versions): retry the clean install process with the sequence of steps # 6, #7 & #9 (i.e., skipping over step #8 flashing GApps) and complete the initial setup, then reboot into TWRP to flash GApps; see also https://forum.xda-developers.com/showpost.php?p=72104906&postcount=37 for solution for other setup crash causes.
To enable "Root", see https://forum.xda-developers.com/showpost.php?p=72185622&postcount=1915.
Notes
If you encounter errors in step 3 (using your existing CWM recovery to flash the new TWRP zip file):
- If you have a SD card handy, consider using the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
- Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Please post any comment/question on the features or performance of AOSP & LN ROM builds on the Developer's thread at https://forum.xda-developers.com/nook-hd/development/marshmallow-nook-hd-hd-t3239269.
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
stupid_nut said:
I'm on CM11 and am getting hung up trying to install TWRP. I get:
This package is for device: ovation; this device is .
Status 7
Installation aborted
Tips?
I'm running EMMC CWM v6.0.4.6
Click to expand...
Click to collapse
Is your device a Nook HD+?
digixmax said:
Is your device a Nook HD+?
Click to expand...
Click to collapse
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
Have you tried flashing TWRP through their official app? I think I also had trouble trying to flash TWRP through CWM, but the app worked at the time.
You could also flash internal TWRP through Amaces's multi mode bootable SD recovery. It does mean you'd need to setup a spare SD card for it, but it can be good to have handy anyway [emoji6]
stupid_nut said:
Made me question myself but yes.
Nook HD+
I'm running 11-2014-1112-SNAPSHOT-M12-ovation
Even wiped and backed up to a fresh copy of CM. The system info even says the device is ovation. Bit confused. Any ideas?
Click to expand...
Click to collapse
I can't tell why the update script doesn't identify your device as "ovation".
If you have an SD card handy, I'd suggest that you try the procedure described at https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810. Otherwise, you can try to flash the flashable TWRP zip file available at http://www.mediafire.com/file/3gj4g9j1x363dor/cwm-flashable_twrp-3.0.1-0-ovation.zip.
Thanks guys!
I just ended up using the SD card procedure. TWRP app failed as well. CM11 was slowing to a crawl on the NookHD+ so hopefully Lineage will give it new life!
error 20 on gapps (you don't have Android 7)
Hi, had CM11 on my HD+ for over a year. Unfortunately I left it on til battery completely discharged the other night, and even after charging to 100%, it would only go in a boot loop. (cyanogenmod bootloader, then robot face, then cyanogenmod bootloader again, then robot face again, etc, nonstop). So I thought, why not wipe it and put Lineage on?
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader? And if I press "N" I see TWRP as an option, as well as CM (legacy) So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
So something isn't right here, or I'm missing some steps? Any help please?
baytee said:
...
So something isn't right here, or I'm missing some steps? Any help please?
Click to expand...
Click to collapse
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
digixmax said:
Since you're posting in this thread, I can't tell if you have tried the alternative procedure in this thread https://forum.xda-developers.com/nook-hd/general/how-to-installing-ln14-1-internally-hd-t3562810.
Click to expand...
Click to collapse
YES I tried both procedures. In fact I tried that link you have for "installing new" procedure first But it failed on the Gapps part. And like I said the previous CM11 (at least boot part) seems corrupt as its stuck in a boot loop. So ideally if it's not riskier, I was attempting to wipe off the old system. (unless by checking all the boxes except SD, under Wipe, Advanced, I did accomplish that? and just the boot/bootloader portion remains?
baytee said:
...
So first following the link from this thread, for doing a from scratch install (not the link for if you have CM11 since it wasn't even booting for me, so assuming corrupt),
I got to the point of installing TWRP, and it failed with a zip signature verification error. So okay, I uncheck that verification box, and it appeared to install okay. Onto the lnos zip file. As a precaution, I also unchecked the verification box (thinking it might fail like the TWRP install), and besides a couple messages about "E: unknown command [LOG] " which I ignored (from what I read online can be safely ignored?) , and it took a good while (10 or more minutes? didn't time it) and says "script succeeded: result was [10000000] ,updating partition details, ....done" So I assumed it installed? Then tried installing open_gapps-arm-7.1-pico-20170329.zip, and it fails with "This GApps pkg is for Android 7.1.X only. Please download the correct version for your ROM: 4.4.4.(SDK 19) GApps installation failed No changes were made to your device. Installer will now exit Error Code: 20" and install failed basically. So I reboot and what do you know I still see the CM boot loop going on. Does this mean the old CM11 OS is still installed? Or just a bootloader?
Click to expand...
Click to collapse
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
And if I press "N" I see TWRP as an option, as well as CM (legacy)
Click to expand...
Click to collapse
These are just the choices of TWRP & CWM recovery available on the SD.
So I boot to TWRP and go to Wipe, but this time, do Advanced, and select to wipe all items except external SD. Restart, and same CM boot loop is going on. (I had done the basic Wipe before that)
...
Click to expand...
Click to collapse
You should never need to wipe anything other than /data and /cache (/system typically gets wiped automatically (aka reformatted) as part of the process of flashing a new ROM version).
digixmax said:
It appears that the old CM11 ROM is still there, the "... succeed ... " message notwithstanding.
The problem behavior seems to be pointing to the possibility that your EMMC is hosed (not readable/writeable). You can test this by trying to re-install stock ROM (see #6 of https://forum.xda-developers.com/showthread.php?t=2062613).
.
Click to expand...
Click to collapse
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
So, any hope for my HD+ ? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet? Why would my battery going to zero screw things up so badly?
baytee said:
I downloaded the stock rom zip , put it on sdcard, booted to TWRP, didn't do any Wipe but clicked Install, chose that zip, unchecked zip signature verification, swiped to start it, get:
"Failed to retouch '/system/lib/libemoji.so'.
Updater process ended with ERROR: 7
Error installing zip file '/external_sd/NookHDplus-stock-2.1.1.-rooted.zip'
Updating partition details...
...done
Click to expand...
Click to collapse
To flash stock ROM you need CWM version 6.0.2.8 attached at the end of the post I referenced.
So, any hope for my HD+? If eMMC IS hosed as you mention, what causes this? And are there any tricks to UN-Hose it? Or is it now a useless dead tablet?
Click to expand...
Click to collapse
If your EMMC is dead, you can try to run CM11 entirely off an SD card -- see https://iamafanof.wordpress.com/201...-4-4-4-for-bricked-no-emmc-nook-hd-04nov2014/.
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
baytee said:
My Hd is one of those that won't reliably boot to sd card. Any possibility for unbricking , Similar to these (though these steps are for nook tablet, not HD)?
https://forum.xda-developers.com/showthread.php?t=1513583http://bishoptec.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Click to expand...
Click to collapse
That "tool" for unbricking the NT also boots and runs off a SD card.
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
baytee said:
While it never reliably booted to the cm11 OS on the sdcard, it's been booting okay lately to recovery at least Twrp maybe even cwm , so assuming I can boot to those , again,does that repair option for NT also work for HD+?
Click to expand...
Click to collapse
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
digixmax said:
The NT unbricking tool only works for the NT.
Assuming your EMMC is not dead, and its factory-installed partition structure is not corrupted or altered, you can accomplish the same end-goal as the NT tool does by re-flashing to stock ROM using the files linked in the post I had referenced in my earlier reply.
Click to expand...
Click to collapse
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
baytee said:
Thank you but again , i tried that already and it failed, which is why I was asking if any of those procedures in the links I posted would work, which u already indicated the NT one wouldn't. I've seen various other xda posts talking about either ADB or partitioning or formatting commands. Was just hoping this HD+ wasn't dead and that I could somehow hack this back to life instead of chucking it in the trash....
Click to expand...
Click to collapse
The stock rom you tried to install was the rooted version that I customized. Try a plain stock rom from that same thread. Try an older version. That error was a common one for some devices.
Sent from my SM-T707V using XDA Premium HD app
Will this guide also work on the Nook HD? (Using the equivalent Hummingbird files, of course).