I downloaded CM 7.1 stable for my Nook color, and when I go to install I get an assert error with a "status 7".
I've done a lot of flashing of ROMs on my DX, but I'm wondering if there's a step I'm missing. I've pretty much just done the usual routine for flashing a new ROM:
- nandroid backup
- wipe cache,system,data,dalvik cache
- flash ROM zip file
No luck for any ROM I've tried. Anyone know what I need to do to get this to work?
Go over the steps in my sig. If that's no help check out the links in it particularly eyeballer's and mrg666's.
Thanks, I'll try it out. Why don't the official CM7 and MIUI builds work?
Are there other Mirage Kangs I can try out? Any good ICS ones?
Thanks again,
Mike
Also, I'm assuming if I have CWMR already installed I don't need the boot SD, correct?
Same problem. I get
assert failed: getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore" || getprop("ro.product.board") == "encore"
E: Error in /sdcard/download/encore_CM72_MiRaGe-06082012.zip
(Status 7)
Installation aborted.
Does this mean I have to do the SDcard boot?
In theory you could put any ROM in place of M-K you wanted but if you are wanting ICS I would install using one of those instruction threads. All I was suggesting was that you go over the basic steps I outline to make sure you weren't missing anything.
And yes, it sounds like something got corrupted and you need to start from scratch. I would at this point. I always look at it as time to flush the old and try out some new.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
mikecico said:
So, I tried unrooting and doing a stock recovery, then using a boot-sdcard to flash any number of ROMs. I still get the same error.
At this point it seems something is fundamentally wrong. I tried several options on the flashing, nothing seems to get around this error.
Is there anything else I can do here?
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
leapinlar said:
When you say you were able to do a stock recovery, what did you mean by that? Were you able to flash a stock ROM to emmc with recovery? Or did you do an 8 failed boot reset?
Also, what version of CWM are you using?
Click to expand...
Click to collapse
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
leapinlar said:
The problem you are having is the install zip cannot verify that it is flashing to the correct device. If it can't find that 'encore' in your properties it will abort. I'm not sure where that property is stored on your emmc, but the zip is not finding it.
Sent from my Nook Color running ICS and Tapatalk
Click to expand...
Click to collapse
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
Click to expand...
Click to collapse
No, you'll need to either flash the original version of your firmware or do an 8+1 reset.
mikecico said:
What do you mean by emmc?
Click to expand...
Click to collapse
Embedded Multimedia Card. The flash memory internal to the Nook Color.
Keep listening to leapinlar. Nothings broke beyond repair and he's teaching more than you in this thread.
mikecico said:
I did a factory reset from the nook settings. Is that not sufficient?
I'm using CWM 5.x (don't have it handy to check, I can get the exact version if needed).
What do you mean by emmc? I'm having to dig a little deeper on this one than I usually do, so I'm not familiar with all the terms.
It sounds like my root-revert wasn't as complete as I thought.
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Emmc means embedded multimedia card. It is basically an SD card built into the Nook. It is where all of your internal information is stored. It is partitioned into 8 partitions to hold various kinds of information, like the system files for your ROM, and data that is specific to your installation (application settings, your login info, etc.).
When you did the factory reset it cleared the data info, but not the system info. That is good if you want your stuff off, but it does nothing to the system files (including the root files). So someone else could put their info in and yours will be gone.
Somewhere on one of those 8 partitions is info stored that tells the zip you are an encore. (It's 1, 2 or 3, I just don't know which). The zip is not finding it. That could be because one of those partitions is corrupt. Or the data could just be missing.
If you truly did a factory restore, like flashing a factory zip to emmc, then the info might come back.
OK, thanks! Looks like I've got some homework to do.
Sent from my DROIDX using Tapatalk 2
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
Try looking here (post 148). It is a Stock Rom zip for 1.4.1. Try flashing that with your CWM. Use the first one. It still has an assert statement in it so it may also fail, but it is worth a try.
status 7 error
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Heretic09 said:
I'm on and a nook tablet and I'm trying to flash 7.2 stable, I already have CM7 Alpha on the nook which the install had gone smoothly. I tried to use rom manager which gets me to clockworkmod but I get the same error - status 7 when trying to install the cm-7.2.0-encore.zip that I downloaded from cyanogenmod.com.
I've tried downloading it a couple of times, I've tried a bootable sd card but I still get status 7 when trying to install. I've followed the install guide cyanogenmod's wiki to the letter but I cannot get past that error. Anyone have any idea what might be causing it? Right now I'm back to CM7 Alpha.
Click to expand...
Click to collapse
It's because you are on a Nook TABLET. CM 7.2 is for a Nook COLOR. They are completely different devices. If you want to brick your Tablet, keep trying to install this!
Sent from my Nook Color running ICS and Tapatalk
mikecico said:
I also think I had modified some of the system info when I originally rooted this thing. It's not my device, and now the owner (much father in law) wants more than just a rooted device, he wants the full tablet experience. And I like hacking someone else's device.
Long story short, I'm learning quite a bit here, so thanks...
Sent from my DROIDX using Tapatalk 2
Click to expand...
Click to collapse
mikecico, are you sure you are on a nook color? They look almost identical, but the nook color has a black bezel and the nook tablet is silver. Like I said in my post above, they are different devices and that may be why the zip is rejecting the install. It's doing its job.
Sent from my Nook Color running ICS and Tapatalk
I just did a check on the model number, BNTV250. It's a tablet.
Sorry for the noise guys. I think he had told me it's a NC, and I used a NC root method successfully, so I had assumed that was correct.
Mike
Related
ok so after 3 days of trying, i keep getting stuck on a boot-loop I am asking for some help.
before I begin, I have successfully rooted and installed cm7 on 2 nooks that came factory 1.2,I have searched google and these forums but can't find anything with my specific needs.
I have followed the directions on this thread to a tee:
http://forum.xda-developers.com/showthread.php?t=1054027
i am using a bootable cwm card (2GB) (cwm version 3.0.2.8)
after installing ManualNooter-4-5-18.zip then ManualNooter-4-6-16.zip I remove the sd card and reboot and I get a boot-loop with the "n color" screen animation. It has not booted successfully yet.
I have already used the 8 failed boots method to restore to factory and re-registered the nook.
Then I redid everything again and im back at the boot-loop.
any ideas
i do not have an answer but this answers my question of whether I want to run manual nooter on my 1.3 or try cm7. the cm7 steps seems more intimidating
Well i tried several more times last night with no luck. Then i got brave and just wiped everything (data,system,cache,dalvick) then flashed cm7 and gapps straight from my cwm boot card. I somehow
Ended up with a fully functional nook. App market works. Rebooted several times to be sure. I even tried usb host with my homemade adapter. Mouse, keyboard, and sandisk cruzer all work splendidly thru a powered hub.
My only mistake was i cant find my backup of stock 1.3 rom. Is there one floating around?
Sent from my LG-VM670 using Tapatalk
If I'm understanding correctly, you're trying to go from CM to 1.3, correct?
From what you've described, I suspect Clockworkmod 3.0.2.8 is your problem. If you look carefully as you format /data in preparation for reloading the BN 1.3 firmware, I think you'll see that the format is actually failing. That version of CWM doesn't handle the partitions correctly.
You want 3.2.0.1. See the edits at the top of this thread: http://forum.xda-developers.com/showthread.php?t=987735
If you're already on CM7.1, you probably have the correct version of CWM installed. You can save yourself a step by formatting the /data and /system partitions using that, then continuing on with the rest of the procedure for restoring BN 1.3. I went through all this myself a few days ago while preparing to go to BN 1.4.1.
I forgot to mention in my last post that i realized i was using the wrong cwm image and i burned another card with cwm 3.2.01.
I was still getting a boot-loop so i wiped everything and went straight to cm7.
Sent from my LG-VM670 using Tapatalk
@bobstro
I didn't read your post correctly.
I had a stock nook that i want to install cm7 on. Not the other way around. I asked about a stock 1.3 file just in case i need to do a restore. The nook is done. Its running cm7 just fine and i have given it back to my friend.
I really need to get myself one :-(
I usually mess around with my sons but he's at his mothers for the weekend with it. After christmas im getting one. Dont know if it'll be a color or a nook tablet but im getting one for sure!
Sent from my LG-VM670 using Tapatalk
If you intended to install CM7 from beginning, then why you wasted time messing around with ManualNooter?
Im still rather new to working on nooks. I thought that it was required to use manual nooter first. Im still not sure.
Can someone clarify for mr. If i just bought a nook and i want cm7 on it, whats the best procedure?
Sent from my LG-VM670 using Tapatalk
pdrift said:
ok so after 3 days of trying, i keep getting stuck on a boot-loop I am asking for some help.
before I begin, I have successfully rooted and installed cm7 on 2 nooks that came factory 1.2,I have searched google and these forums but can't find anything with my specific needs.
I have followed the directions on this thread to a tee:
http://forum.xda-developers.com/showthread.php?t=1054027
i am using a bootable cwm card (2GB) (cwm version 3.0.2.8)
after installing ManualNooter-4-5-18.zip then ManualNooter-4-6-16.zip I remove the sd card and reboot and I get a boot-loop with the "n color" screen animation. It has not booted successfully yet.
I have already used the 8 failed boots method to restore to factory and re-registered the nook.
Then I redid everything again and im back at the boot-loop.
any ideas
Click to expand...
Click to collapse
The only boot loop issue I'm aware of is related to Adobe AIR and Flash. The fix is to uninstall them and then reinstall from Market.
Sent from my NOOKcolor using XDA Premium
pdrift said:
Im still rather new to working on nooks. I thought that it was required to use manual nooter first. Im still not sure.
Can someone clarify for mr. If i just bought a nook and i want cm7 on it, whats the best procedure?
Sent from my LG-VM670 using Tapatalk
Click to expand...
Click to collapse
I hope you do use Windows at some points.
Let's put it this way.
You bought a PC with Windows XP pre-installed, get home, you don't want XP, so you install Windows 7 on the PC. You just whack the XP.
Same theory applied here, B&N shipped their NC out with the original stock ROM, which is Froyo-based OS. You want to install CM7, which is Gingerbread-OS ROM. You just whack the stock and install CM7.
oh I get it know. so its pretty easy if you want to go straight to cm7 just wipe and flash.
After reading some posts from the nook tablet section, i guess i'm getting a nook color.
what a shame about the locked bootloader :-(
i didnt technically solve the boot loop issue, i just erased everything, but should I mark this as solved and if so how?
The current Nook Color bootloader is not locked. The Nook Tablet's is. I wouldn't necessarily rule anything out, though. The bootloader on the Motorola Droid 2 is also locked, and there's quite an active Cyanogenmod community around it. The only problem is that we're stuck with whatever kernels B&N release, so ICS may be a long way off. I suspect the NC will remain the tuner's machine of choice, but the performance on the NT is very nice. If you can live with a rooted B&N ROM, it's a nice device for now.
billingdl said:
The only boot loop issue I'm aware of is related to Adobe AIR and Flash. The fix is to uninstall them and then reinstall from Market.
Sent from my NOOKcolor using XDA Premium
Click to expand...
Click to collapse
No, it seems that some 1.3 based NC units will bootloop if 4.6.16 is used to root them. I'm not sure why. Even after repartitioning to original nook partition sizes, or using CWM 3.2.01 (which supports the new partitioning), it'll still bootloop if 4.6.16 is used. Might be because of the different kernal included, but I'm not knowledgeable enough to know for sure. They root fine with 4.5.18. Haven't tried one with the new 1.4.1 compatible nooters.
To the original poster;
I'm having the same problem here, installed 4.15 successfully, installed 4.16 and am getting stuck in boot loop at the rainbow nook color screen.
I'm not understanding the 8 boot fail procedure though. Is this when you let the boot loop run through 8 times or when you get to the point of when the boot loop starts, shut the NC off and power it back on?
Also, to install cm7, all you did was put it on your sd card, and installed it through cwm?
The 8 boot method if i recall correctly is when you boot the nook and wait until the splash screen shows up immediately hold the power button and shut it down. Repeat 7 more times. If you did it correctly it should take over and do a restore on its own.
If you want to go straight to CM7 I dont think you need to go thru with this procedure because if you create a bootable cm7 card and insert it in your nook while its off then power up, it should boot you into cwm recovery. Once in the recovery you can flash cm7.
sent from my OV CM7 IHO using tapatalk
pdrift said:
The 8 boot method if i recall correctly is when you boot the nook and wait until the splash screen shows up immediately hold the power button and shut it down. Repeat 7 more times. If you did it correctly it should take over and do a restore on its own.
If you want to go straight to CM7 I dont think you need to go thru with this procedure because if you create a bootable cm7 card and insert it in your nook while its off then power up, it should boot you into cwm recovery. Once in the recovery you can flash cm7.
sent from my OV CM7 IHO using tapatalk
Click to expand...
Click to collapse
Thank you good sir! I was stuck in boot loop forever and couldn't find a clean explanation of the 8 boot fail process. I always tried to turn it off when the rainbow nook color screen came up.
I got it reset, made a flashable CWM SD card with 3.2 and then flashed CM7 on there and it works great!!
That was very frustrating, thank you!
Dont mention it, Glad to here I was able to help you out. I felt the same way when I was in that situation. Lots of googling to get a clearer idea on what that 8 boot method entailed. CM7 really makes it feel like a totally different device.
To all the devs that work on these projects, thank you
sent from my OV CM7 IHO using tapatalk
ive recently purchased a nook color version 1.3 and did all the steps to build cm7 on sd ard inserted it into my nook it downloaded then rebot and seem to come up im cm7 but my touch screen isnt working any suggestions?
Hi all,
I just had a question about upgrading to CM 7.2RC. I am currently running the stable version of CM 7.1. It has been awhile since I changed out the rom. Did I have to do a full wipe of the device before upgrading to the RC? Or can I just wipe the cache and install the update so it maintains everything else on the device.
Any help on this would be appreciated. Thanks.
sdutta6 said:
Hi all,
I just had a question about upgrading to CM 7.2RC. I am currently running the stable version of CM 7.1. It has been awhile since I changed out the rom. Did I have to do a full wipe of the device before upgrading to the RC? Or can I just wipe the cache and install the update so it maintains everything else on the device.
Any help on this would be appreciated. Thanks.
Click to expand...
Click to collapse
Just do the second thing. No full wipe.
This thread down in the cyanogenMod forums shows you how to upgrade if you did not know how or want to gleam more information on this. Or for anyone else that is interested. http://forum.cyanogenmod.com/topic/40698-installing-nightly-builds-and-new-71/
Ok, but what do I do if I'm running off a bootable SD card? I was told to just copy the new rom to my F boot, then boot into recovery. I have done this over and over again with no success. I'm sure I'm doing something wrong. if I'm supposed to copy the rom to a specific partition, then Im screwed because I don't know how to do that.lol. By the way, till about 3 months ago I could count on one hand how many times I'd sat down at a computer. Got a nook color as a gift
,and have been in love ever since. I'm running cm7.1 stable, at 1200mhz. I've had to teach myself every step, every step of the way. So if I sound like a idiot, its because I know nothing about computers, but I am learning. Thank you for your patients
Sent from my NookColor using xda premium
purpleurkle said:
Ok, but what do I do if I'm running off a bootable SD card? I was told to just copy the new rom to my F boot, then boot into recovery. I have done this over and over again with no success. I'm sure I'm doing something wrong. if I'm supposed to copy the rom to a specific partition, then Im screwed because I don't know how to do that.lol. By the way, till about 3 months ago I could count on one hand how many times I'd sat down at a computer. Got a nook color as a gift
,and have been in love ever since. I'm running cm7.1 stable, at 1200mhz. I've had to teach myself every step, every step of the way. So if I sound like a idiot, its because I know nothing about computers, but I am learning. Thank you for your patients
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
You are probably not renaming the zip to begin with update-. You must do that before the installation script will recognize it.
Sent from my Nook Color running ICS and Tapatalk
Yes I have renamed it. it was cm-7.2 and I changed it to update-cm-7.2 but still nothing. here's the thing, when I try to format this card on my PC, its saying its write protected, and to switch it off. I assume it means the lock switch on the sd card adapter. If thats the case, something is screwed up, because its not locked. I don't think its my adapter cause its not saying that with other cards. When I copy the cm7.2 it says its copying just fine and I can see it on the card but if I take it out and put it back in, its not there. Sorry for the pain in the butt question, and thank you for your time.
Sent from my NookColor using xda premium
purpleurkle said:
Yes I have renamed it. it was cm-7.2 and I changed it to update-cm-7.2 but still nothing. here's the thing, when I try to format this card on my PC, its saying its write protected, and to switch it off. I assume it means the lock switch on the sd card adapter. If thats the case, something is screwed up, because its not locked. I don't think its my adapter cause its not saying that with other cards. When I copy the cm7.2 it says its copying just fine and I can see it on the card but if I take it out and put it back in, its not there. Sorry for the pain in the butt question, and thank you for your time.
Sent from my NookColor using xda premium
Click to expand...
Click to collapse
I had the same thing happen to one of my sdcards. I could not format it, or write things to it. I could read it fine, just not change anything. I tried all kinds of readers and software (formatters, partitioners, etc.) It would look like it wrote to it, but take it out of PC and put it back, it was not there. I finally had to throw it away and get a new one. This all happened on my phone, not my nook.
This is my FINAL VERSION of my Idiots Guide for the HP Touchpad. Now that a stable enough version of CM10 is available, I finally created a guide for you.
Here are links to the files you will need:
CM10 03/04/2012 Build
GAPPS 10/11/2012
ACMEInstaller3
Moboot 3.8
Anything else that you might need, you'll find on http://www.reverendkyle.com
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
aujbman said:
Thanks for the video. It came just in time as I just purchased a used TP that had an older version of android ICS already on it and I wanted to upgrade but seeing as how this is the first device I have sort of inherited already rooted, it is hard to just jump in and know everything that I would have learned from the beginning like i did with my previous phones.
Anyways, I did everything you said except I used the newest AOKP rom. But my tp is still booting to the older version of android that I had on it. Any ideas? Feel free to pm me if you prefer that.
Click to expand...
Click to collapse
If the AOKP ROM is using a unique uImage file, then you may see two different entries on your moboot screen for two different Android builds.
What does your moboot menu have in it?
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
-SGA- said:
Maybe your install failed. Try downloading and flashing it again. If you're trying AOKP JB, you should wipe both /data and dalvik cache to avoid a boot loop!
If using AcmeInstaller3 remember to rename the ROM with ”update-” at the beginning so that it looks like update-AOKPJB_UnOfficial.zip
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
I believe it was the "update-" thing that was keeping it from updating. I followed another video tutorial which provided files that had the "update" in front of them and it worked.
I haven't tried yet but now that it worked will the regular method of wiping and flashing through recovery work? (Like, if I want to try out different JB Roms) Are there any files that need to be in a particular place for the recovery method to work? I tried that method first and it would never take, would always revert back to the original version. Don't know if, because I just jumped in and haven't been here from the beginning, I am just missing a necessary step that is hardly even talked about anymore.
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Jubmasterflex said:
Love your work Rev! Thank you again for everything that you do!
Update went like clockwork, unfortunately I can't seem to get the camera to work (not a terrible loss, but I was sorta excited to see it actually working with this release).
Click to expand...
Click to collapse
I can attest to the improved battery life on this cm10 build. Amazingly, it holds battery life when it's sleeping now.
Thank you so much for taking the time in making the video for us. Your instructions are easy to follow, hard for anyone to mess up.
(The hosting site for the files is not working, not sure if you were aware)
Hi, I have CM9 running on my TP. With the latest release, the camera works great. But before updating it to CM10, I'd like to know about the issues currently in this build.
Thanks.
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
ljderm said:
Where does one go when the goo.im site appears down, to get the needed files? Mirror somewhere?
Click to expand...
Click to collapse
Don't go for external mirrors unless some recognized developer suggests them. Best will be to wait for goo.im to come up again, being a prime site, it won't be down for long.
The goo servers do appear to go down on occasion. They always come back up a bit later.
Problem with installing GAPPS using ACMEInstaller3
Excellent tutorial for an idiot like me. Thanks for again for the guide! Question:
I followed the instructions step by step and was able to get CM10 installed successfully. However, I wasn't able to get GAPPS installed using this method. From researching I understand sometimes there is a problem installing GAPPS through ACMEInstaller3 and one can simply get GAPPS installed through CWM Recovery. However, I would like to use/have TWRP instead so is there a way to get GAPPS installed properly through ACMEInstaller3 and then I can install TWRP through GooManager?
Alternatively, is there a way to install GAPPS without using CWM Recovery?
Or, I guess I can install CWM Recovery first, then install TWRP Recovery, then remove CWM Recovery while keeping TWRP and not go back to the stock Recovery? I tried to search the forums and wasn't able to find instructions on removing CWM Recovery WHILE still keeping CM10 and not go back to the Stock recovery.
Any help would be much appreciated. Thanks in advance for your help.
@reverendkjr - appreciate your videos. they're awesome. definitely helped me (and several other friends) many times and saved a ton of time. super easy to follow.
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
waynekirby said:
Yes you can install TWRP normally, flash gapps in CWM then install goomanager app, open and click the 3 dot menu and install custom recovery script then it will install it
Now using a root file manager go to the directory called boot and delete uimage.cwm.img (this is from memory but still should be correct
Sent from my cm_tenderloin using XDA Premium HD app
Click to expand...
Click to collapse
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Crwolv said:
Dumb question. I had dual boot installed with moboot and one day my dumbarse clicked erase SD card.well it did...EVERYTHING accept twrp. I successfully reinstalled webos and installed preware. Its actually pretty cool.its like a fledgling play store for webos. Now....where should i go from here.i no longer think twrp is on it. All i have is webos with preware.sorry if this is newbie
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My goodness you have forgotten everything, you will need to install acmeuninstaller 3, moboot, CMW and the rom you want along with the relevant gapps. Sounds complicated this thread will make it easy
http://forum.xda-developers.com/showthread.php?t=2147284 and has all the necessary links. Have fun.
Sent from my Transformer Prime TF201 using Tapatalk 2
Heck ya i did lol. That refreshed my memory instead of a long video. Thank yo very much
Awesome!
Sent from my cm_tenderloin using xda app-developers app
Great vid!! Finally got CM10 on my Touchpad.
TL;DR: Back to factory settings, on version 1.4.1, can't for the life of me manage to make a bootable SD card to install CM10.1, or 7.2, and I have no idea why.
Alright, I'm on my wit's end, and i need some help. I bought my Nook Color a while ago. At the time I just rooted and went with whatever version of android the guide offered me.
Yesterday i tried to upgrade. First I just downloaded the CWM ROM Manager, and instead of having under the first option ("flash ClockworkMod recovery") a legend displaying the version of my recovery, it said "You must have the ClockworkMod Recovery installed to flash and restore ROMs!"
Ok, so i don't have CMW recovery, I tried to get one from the CWM Rom Manager, but the nook was listed under "unknown device", when I clicked in manual install, it asked which version, i selected 3.x. if my memory serves right, and immediately said "current recovery: ClockworkMod v5.5.0.4.
"great", i though, the manager installed it for me... so I downloaded the new CM10.1, loaded the zip to the SD, rebooted into recovery mode, effectively, it said "CWM-base Recovery v5.5.0.4" and proceded to backup everything, do a factory reset, and try to install zip from sd... error:
Finding Update package....
Opening update package...
Installing update ...
assert failed: getprop("ro.product.device") == "encore" || getprop("ro.build.product") == "encore"
E:Error in /sdcard/cm-10.1.0-encore.zip
(status 7)
Installation aborted.
So I revert everything back to the backup, and go find a few guides online. I come up with this one, http://forum.xda-developers.com/showthread.php?t=1030227, follow all the steps, but I never manage to boot from the SD card. Later I realise i was using the Nook to format the SD, big mistake, and go and get a USB card reader, still nothing.
In the midst of all this, I make yet another dumb mistake, and do a factory reset of the tablet WHILE i'm formatting the SD on the pc... losing my backup (yes, im an idiot :S)
So now I have what I believe is not quite a stock Nook Color, running software version 1.4.1 according to the about menu, any attempts to boot from SD are failing miserably (by the way, I'm using a 32gb Class 4 microSD from SanDisk), and to make matters more weird, if i power into recovery mode, it still seems to have the CWM, because it keeps saying "CWM-base Recovery v5.5.0.4"... which now i think i never even had to begin with.
I'm completely out of my depth here, any help is greatly appreciated
I think your problem is you have a Nook Tablet instead of a Nook Color. Does it have a silver bezel? If it does it is a Nook Tablet and those NC SDs will not boot.
My clue was the assert failure for encore (NC) when you tried to flash.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
I think your problem is you have a Nook Tablet instead of a Nook Color. Does it have a silver bezel? If it does it is a Nook Tablet and those NC SDs will not boot.
My clue was the assert failure for encore (NC) when you tried to flash.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The model is BNTV250... when googling around that seems to be a nook color?
It does have a silver (gray?) bezel tho...
Edit: starting to feel like more of an idiot... the nook color doesn't have a mic, does it? because mine does...
Yeah, the BNTV250 is the tablet.
Sent from my ADR6410LVW using xda app-developers app
wmuflyer said:
Yeah, the BNTV250 is the tablet.
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
O god... I feel even dumber
Thanks for the help! any particular guide I should follow to install CM10.1 on the nook tablet? i'm seeing a couple in the forums, what's the "easiest"/"safest" one?
Best bet is to head over there and ask. Enough changed that what happens here doesn't apply there. I think the screen and the case are about all they actually have in common.
Rathke said:
O god... I feel even dumber
Thanks for the help! any particular guide I should follow to install CM10.1 on the nook tablet? i'm seeing a couple in the forums, what's the "easiest"/"safest" one?
Click to expand...
Click to collapse
wmuflyer said:
Best bet is to head over there and ask. Enough changed that what happens here doesn't apply there. I think the screen and the case are about all they actually have in common.
Click to expand...
Click to collapse
Yep. Thanks again, can't believe i missed that!
I've spent hours at this now, and Im kind of wondering if my Nook Color is damaged in a way that it allows CWM to think it's written an image to the EMMC but it is actually failing to write anything.
I still have cyanoboot on the device, it still goes into Cyanogenmod boot screen and sits there indefinitely OR it reboots a couple times and gets stuck loading infinitely.
This is AFTER I have tried imaging it back to stock, CM 11, formatting it's partitions with the images on this site and various other things.
So either there is something common in all these tasks Im just blindly missing each time I try this and read/watch another tutorial that doesn't work out for me.....or something is wrong with my the Nook Color.
Can't even do the 8 failed reboots thing Im ASSUMING because the cyanoboot thing is there catching all the failed attempts.
Hadn't used the Nook Color in awhile because my wireless router died and it was kinda pointless to try to use it...now got a nice new router and the damn Nook is making me want to strangle it. So it was in some state other than stock, and I really don't remember if I was trying something new or if it worked fine when the router died at this point. I am just trying to get it to some point where it boots into some kinda of OS so I got some kind of baseline to start from at this point.
So ideas? I can get more specific if need be on what exactly I tried if it seems relevant, but I pretty much pulled the images and guides off the various posts referenced all over the net back to this forum. Hoping I missed something, going to be rather upset if this device is essentially dead since I haven't used it a whole lot since purchase..
First off, make sure you really have a Nook Color and not a Nook Tablet. The Color has a black bezel and the Tablet is silver. If it is a Tablet, the files on this forum will not work.
If you really have a Color, you need to explain more the steps you have taken to try to revive it before we can help.
Sent from my BN NookHD+ using XDA Premium HD app
It's a Nook Color, I've actually rooted and put it back to stock over a year ago. But even the methods I used then will not remove the Cyanoboot or whatever version of CM it's trying to boot into that never goes anywhere.
I've tried
http://forum.xda-developers.com/showthread.php?t=1759558
To see if it's a partition problem AFTER I tried to rewrite the boot/etc to stock and CM 11 with no luck.
Even went to Youtube to make sure I Was getting the proper screens and responses from the device.
https://www.youtube.com/watch?v=vUEoFPApfeQ To try to restore it.
https://www.youtube.com/watch?v=pj_DGZaKwBw To try to put a different version of CWM on it.
Used this link for GApps http://wiki.cyanogenmod.org/w/Gapps, I tried the "small" version along side CM 11
Tried using http://forum.xda-developers.com/showpost.php?p=22809801&postcount=148 to try to restore it to a Nook Color rom.
Tried following http://forum.xda-developers.com/showthread.php?t=2653483 Which is a collection of help postings on the Nook Color....havent had any luck with anything on there.
http://download.cyanogenmod.org/?device=encore&type=snapshot is where I got my images for the Nook Color Cyanogenmod. I used M12, with no results.
And while Im posting all the stuff I used.... I had http://forum.xda-developers.com/showpost.php?p=50438799&postcount=4 opened if I ever got it to boot into CM to use for further issues....maybe it'll help someone else.
And I can't tell you what order I did them all in at this point because I tried and retried different things. And I still have cyanobootloader coming up, if I select EMMC recovery it goes to what looks like a barnes and noble original screen to me and says "Install failed". If I let it do the standard EMMC bootup it just loads forever.
I HAVE NOT tried to load a bootable SD with the OS, etc on it because I was trying to get the device to work properly on the EMMC first. But if that is something that needs to be done to fix it, I can do that if you point me in the right direction. I'll even try to use ADB on it if I can get some kind of guide to it...most of the ones I found were no longer valid /missing links and other things with just a few random command lines but no images or anything to use and I didn't want to risk screwing the device up even more.
Thanks.
The reason you see "install failed" when trying to go to internal recovery is because you still have stock recovery installed on internal memory.
And after you did the partition repair and you want to install CM11, you must upgrade your recovery to v6045 or newer before flashing the CM11 zip.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
The reason you see "install failed" when trying to go to internal recovery is because you still have stock recovery installed on internal memory.
And after you did the partition repair and you want to install CM11, you must upgrade your recovery to v6045 or newer before flashing the CM11 zip.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Is this referring to the CWM version on the SD card, EMMC or both? I used some of the premade images for booting and they were all older versions of CWM.
I believe I attempted to use "cwm-6.0.5.0-encore-emmc+sd.zip" when I attempted to install CM11. If it wasn't that one it was "cwm-6.0.4.7-encore-signed.zip". It was CM11 Snapshot M12 with gapps-kk-20140105 since it's smaller than 20140606. It did the blue text scrolling install of both, autodetecting gapps and installing it. Then removed both from the SD card when I did it. I didn't catch any errors.
I have not been able to get the Nook Color to enter the CWM version on the EMMC to verify it's version number....but this may be because Cyanoboot is catching it or Im doing something wrong.
If I were going to describe this problem on a PC, I'd say it was pointed at a corrupted boot device and ignoring the one you're trying to use in it's place.
Xaxl said:
Is this referring to the CWM version on the SD card, EMMC or both? I used some of the premade images for booting and they were all older versions of CWM.
I believe I attempted to use "cwm-6.0.5.0-encore-emmc+sd.zip" when I attempted to install CM11. If it wasn't that one it was "cwm-6.0.4.7-encore-signed.zip". It was CM11 Snapshot M12 with gapps-kk-20140105 since it's smaller than 20140606. It did the blue text scrolling install of both, autodetecting gapps and installing it. Then removed both from the SD card when I did it. I didn't catch any errors.
I have not been able to get the Nook Color to enter the CWM version on the EMMC to verify it's version number....but this may be because Cyanoboot is catching it or Im doing something wrong.
If I were going to describe this problem on a PC, I'd say it was pointed at a corrupted boot device and ignoring the one you're trying to use in it's place.
Click to expand...
Click to collapse
Blue text scrolling means you are trying to install to SD, not emmc.
What are you trying to install, emmc or SD? If trying for SD, you are using files made for emmc.
If you want to go back to stock, go to my NC tips thread linked in my signature and use an older version of CWM to flash the stock zip from item A15 there.
Sent from my BN NookHD+ using XDA Premium HD app
Really Im just trying to get what's on it, replaced with something that is functional so I can tell when Im doing something right or wrong.
I will attempt to do this again and try to document it a little better. I would like the EMMC to be functional at the very least no matter what version it ends up being... I will attempt stock again from your guide which I thought I did right the other night but Ill try it again.
OK.
Using:
NookColor-emmc-format-partitions-5-6-7-8.zip
TWRP-2.1.8-bootable-SD-encore.zip
nookcolor_1_4_3.signed.zip
I imaged the TWRP img onto an SD, copied both zips onto it.
Put it in the Nook Color, powered on and I saw the cyanoboot, then it loaded into TWRP.
From the install menu I installed the format partitions zip. It ran without errors. I wiped the cache/dalvik.
Then went back into the install menu and ran the nookcolor_1_4_3signed.zip. I see this:
-- Install /sdcard/nookcolor_1_4_3_signed.zip ...
Finding update package. . .
Opening update package. . .
Installing update . . .
E: Error in /tmp/sideload/package.zip
(Status 0)
*Verifying filesystems ...
* Verifying partition sizes...
Error flashing zip '/sdcard/nookcolor_1_4_3_signed.zip'
I will try it with another microSD card just incase it's defective.......and then see if trying another signed nookcolor might work from the guide.
Tried a different micro sd and used signed version 1.4.1 stock.
Did same steps. It errors, but as soon as it errors, it's like the TWRP resets real fast and gets the blue boot screen, flickers a couple times then rolls back and away to show the buttons again...takes 30 seconds or so.
Xaxl said:
Tried a different micro sd and used signed version 1.4.1 stock.
Did same steps. It errors, but as soon as it errors, it's like the TWRP resets real fast and gets the blue boot screen, flickers a couple times then rolls back and away to show the buttons again...takes 30 seconds or so.
Click to expand...
Click to collapse
Try it using the CWM instead of TWRP.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Try it using the CWM instead of TWRP.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Ok... I'm using CWM 6.0.1.2 from your guide. Format partitions zip and 1.4.3 stock signed that I used prior.
I just got done flashing the format and then stock to the nook color and no errors are reported untill...
I just finished writing Nookcolor_1_4_3_signed.zip...
Finding update packing
opening update package
installing update
boot files...
Install from sdcard complete.
And here's the first errors:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I don't know if they mean anything, but something similar popped up in other attempts. I am rebooting device now to see what happens.
Going to EMMC 01 in top left of Cyanoboot screen....blank screen...waiting.
Cyanomod rotating load screen comes up. And if it holds true, it'll do this until the battery dies.
I don't think the stuff is being written to the EMMC. Which...maybe it's damaged or maybe there's some kind of lock out in place preventing it that needs turned off?
If I can get it running off an SD I'll be happy at this point...perhaps it'll be easier to tell if the EMMC is screwed up then.. If you are out of ideas or think it's damaged. Only reasons I can think of since it's been sitting for a couple months is was kind of near a speaker and I know magnets can damage HDs but really strong magnets can fry phones and stuff....so might have gotten the EMMC in some weird way.
Or some sort of power surge got it when I had it plugged in before I stopped using it.
Did you try my partition repair zips from my partition repair thread linked in my signature?
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
Did you try my partition repair zips from my partition repair thread linked in my signature?
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Yes I tried 1-4-5-6-7-8 and the separate 2 one. But if you want me to try again I can.....any specific version of CWM you want me to use?
Xaxl said:
Yes I tried 1-4-5-6-7-8 and the separate 2 one. But if you want me to try again I can.....any specific version of CWM you want me to use?
Click to expand...
Click to collapse
I've always liked the v5504. If the repairs do not work, something is wrong with the NC.
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
I've always liked the v5504. If the repairs do not work, something is wrong with the NC.
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
I figured.......I'll try it a little later and see if any luck with the repair partition zips..but I doubt it.
Meanwhile, I should probably get you to point me to some SD images to see if I can get it to boot up into CM something and work successfully off the SD card.
I'm hoping I can find a way to fix the EMMC once Im able to successfully boot the device....or even with ADB. I dunno. Pisses me off since I never used the Nook excessively and took pains to keep it safe.
Oh and I saw people asking for specific partition repair files (like unique to their device), does that sound like a possibility here?
Xaxl said:
I figured.......I'll try it a little later and see if any luck with the repair partition zips..but I doubt it.
Meanwhile, I should probably get you to point me to some SD images to see if I can get it to boot up into CM something and work successfully off the SD card.
I'm hoping I can find a way to fix the EMMC once Im able to successfully boot the device....or even with ADB. I dunno. Pisses me off since I never used the Nook excessively and took pains to keep it safe.
Oh and I saw people asking for specific partition repair files (like unique to their device), does that sound like a possibility here?
Click to expand...
Click to collapse
Go to my NC SD installation instruction thread linked in my signature to install CM to SD. I recommend CM10.1.3 from the CM site.
You can also put stock on SD. See my NC Tips thread, item B11 in the second post there.
Sent from my BN NookHD+ using XDA Premium HD app
So using 5504 of CWM with your partition repairs did nothing...still has cyanoboot and infinite load screen.
Working on SD installation now base on your recommendations.
Is there something you can think of that could be done from the SD boot to diagnose the EMMC more? It doesn't seem like there's really anything coming up on google even remotely similar to my issue.
And I've done this once with a much larger SD card but it had kind of **** transfer speeds so it might be defective... So Im repeating it as I type this.
Generic-sdcard-v1.3......rev8c.zip is what I used to image the card.
Then I used CM-11-20141112-SNAPSHOT-M12-encore.zip
and gapps-kk-20140606-signed.zip
The device ran through all the blue text and turned itself off. Loaded up with Cyanoboot going to SD01 and then it would blank screen for awhile and reboot...and repeat itself.
Now this one just error with not enough space on google apps, but Im going to see if the thing will even attempt to boot up.
Then Ill try your recommended version of CM...I already had all these images and was just hoping to see some results after all this.
OK. Some kind of success....
I actually got it to boot up using your rev8c, CM 10.1.3 and gapps-jb-20130301
BUT it gives TONS of popup errors....I was able to get through the setups somewhat. But once it's at the desktop...
I see
Unfortunately, Email has stopped. ----- Press OK then I get
Unfortunately, Trebuchet has stopped. --- Press OK, back to email.
I can kind of get into the settings and stuff, but with the continuous errors popping up it's hard to do anything productive.
So I'm going to let it sit and see if you have any input on that. I find it weird that it loaded with this version...but not the other.
As soon as I got it connected to the wireless network, a couple errors popped up, screen flashed and it went back to the cyanogenmod loading screen WITHOUT rebooting.
I don't even know what information would be useful at this point, lol.