Installing CM7 - Nook Color General

I have a nook color and successfully installed CM7 by flashing clockwork via Rom Manager, reboot into recovery pick CM7 Zip and away you go.
However, a friend of mine gave me their nook to fix up and when I get to the install .zip part of the recovery it gives me an error message about getprop failed.
I downloaded the CM 7.0.3 for Encore. Any ideas?
Oh and this nook was bought a month or two prior to mine, it was an original and I had already rooted it for the person.

Posting the full error message may help. Seems getprop errors can come from different scenarios.

Related

[Q] How to install CyanogenMod 5.0.7 on T-Mobile G1?

I have difficulty installing the cyanogenMod 5.0.7 ROM for the G1. I tried installing it thrice over 3-4 days and still cant get over it. I initially had Jesus Freak 1.4.2, from which, I tried installing DangerSPL, although to no avail, from then on, the phone seemed bricked. Hence, I renamed the CyanogenMod ZIP file as update.zip, and retried installing it by pressing home+power. Although I got the error that the script file couldn't be found.
Therefore, I freshly installed the official Android 1.0 release from here: code.google.com/p/android-roms/wiki/Unbrick and again began the process of rooting, and installing the CyanogenMod ROM. Although, I rooted the phone by watching the videos (youtube.com/watch?v=xOo2V9qCauc) and (youtube.com/watch?v=ua8ljJAnTpc) .
Following which, I think, I installed the radio updates.
I then installed Amon Recovery from following the steps: (bit.ly/eMyBlL) and then the DangerSPL (bit.ly/f2xkvp)
It again seemed the phone was bricked since, it didn't went past the G1 logo. But still I went into recovery via home+power, after I reattempted as earlier, by renaming the .zip file (from computer) to update.zip. and then inserted it into the SD card slot. But it still gave out the same error:
Code:
E:Can't find update script
Installation aborted
Bear in mind that, the recovery utility is not the one where there is a HTC logo on the background, but rather, the one with the exclamation mark within the triangle logo. So there is no choice to flash ZIP files which are not named update.zip
I'm thinking I will again start from scratch, and got back to the official release of Android 1.0, and keep upgrading till the last official one which is, 1.6. Therefore in the meantime, do throw away advice on how to properly root and install CyanogenMod 5.0.7 on the T-Mobile G1 with a different network.

[Q] ClockworkMod: An error occurred while attempting to run privileged commands.

ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
You prolly fixed this already but in case someone else has this issue. Try installing Busybox from the market.
Same issue and won't boot into clockworkmod recovery
nutiket95 said:
ClockworkMod: An error occurred while attempting to run privileged commands.
i've tried everything...that i know of or have read of so far...
i just cant get cwm to install
d1 rooted and unrooted thru super one click and z4root, rom manager uninstalled and redownloaded and reinstalled, wifi connected or 3g
su is current and shows list of other apps, tried permisions fix in rom manager too, just stuck w/ that same lousy error and cant install any roms...
some one please help me!!
-n
Click to expand...
Click to collapse
I rooted my phone with eclair installed and used clockworkmod recovery with no issues until I one day wanted to go back to stock and attempted a restore of the backup I made right before flashing the OverStock ROM. The phone wouldn't boot, so finally got the Overstock to go back. Phone worked fine for the most part, but from then on to get into recovery mode, required shutting down and using button presses (Up/down vol/PWR button) and it would go in fine. Could never get Clockworkmod to go into recovery mode with a click. Saw that (finally) Samsung has published a Froyo update, so took back to stock eclair using ODIN3 so I could use Kies mini to update. Did a factory reset to remove all old info directories and data. Update went perfect, but want the option to use the rooted apps (Titanium backup and ClockworkMod--purchased apps) to play with my phone as I see fit. Used SuperOneClick to root phone and verified I can get superuser with using terminal emulator, successfully executing "su" command. Problem is I can't get into CWM recovery. Only get "Android system recovery <3e>". Tried uninstalling CWM and reinstalling. Re-Flashed CWM recovery and it lists version 2.5.1.2 as current and latest.
I obviously need CWM recovery to flash different ROMS, but wanted a current backup before starting. Can't get any further until I figure this out. Any help would be appreciated. I was a noob, just a month ago, but was feeling pretty confident until this happened. Guess I'm still a noob, but just a little more dangerous now. Thanks in advance.
Just noticed that I wasn't in a phone specific thread, so here's my phone details... Samsung Vibrant (T-Mobile).
CWM issues with Milestone
In the last update of the RomManager was added support for version ClockWorkMod 3.x for Milestone - but still unable to use the CWM as standard recovery.
Using another recovery as OR1.4 you can start CMW from the SD card - but that does not solve the problem of RomManager stay with completely limited functions.
The Rom Manager is having updates constantly and I think we have a working version for Milestone soon - but in part I'm upset to see that the Milestone is listed as a supported device - when in fact it is not.
I bought the full version of Rom Manager because I believe it is a great tool and I hope someday I can use all its functions.
I have the same problem. I use OpenRecovery for Sholes to do those things. I hope we can use those tools like a normal user even a day.

[Q]Heimdall problem

Hi, i'm trying to install cyanogenmod on my Galaxy using this guide, but when i try to load 'Hardcore's SpeedMod Kernel with ClockworkMod Recovery' with heimdall i get this error 'Tar header contained an invalid file size'. I received the same error when i earlier tried the FuguRoot method. I'm running windows 7 32-bit.
Any ideas what is going wrong here? Thanks!
So was eventually abel to get it to work by using an older build of heimdall. And i flashed the 'ClockworkMod Recovery' successfully, but now of course, my galaxy is stuck on the boot screen. Great!
Please help, someone.
So i take that as a no then?
Sounds like you're having the exact same problem as me. Tried following the wiki, and first got stuck in a loop. Then after a reboot and a new try got an assert error. Then, after removing the assert somehow got cyanogen's recovery-image and seemingly installed cyanogen successfully from this, but now I'm stuck at boot.
The new Heimdall seems to want a tar-package with a full firmware replacement.

[SOLVED] [Q] Assert failed (Can't install ROMs)

Hello!
I have a Samsung Galaxy S Captivate previously rooted over a year ago. I was mostly using CyanogenMod for a while, and some time ago, I decided to try out some random ROM (can't remember the name, but it was an unofficial port of ICS).
It had some issues and bugs, so I decided to switch back to CyanogenMod. I've tried installing CyanogenMod 7.2, 9.0 and 10.0
Everytime, I get the following error message:
Code:
Finding update package...
Opening update package...
Installing update...
assert failed: getprop("ro.product.device") == "captivate" ||
getprop.("ro.build.product") || ... (and so on)
E:Error in /sdcard/#whateverpackage#.zip
Status 7
Installation aborted.
*Where "whateverpackage" is the zip/ROM I am trying to install.
Things I attempted to no avail:
1. Toggling asserts. I get the same error.
2. Reflashing recovery-clockwork-2.5.1.2, but I get the same type of error.
3. Installed USB Drivers for Samsung, and attempted to run Odin3 One-Click Downloader (I897UCJF6-final-OCD-REV0.exe), but it isn't responding it seems.
I'm thinking of trying to install ADB and see if I can get the device to properly go into "download mode" and see if Odin responds.
This may be important: When I boot in recovery, the top of my screen shows "CWM-based Recovery v5.5.0.2"
So if anyone knows a straightforward fix to this, or can at least give me rough steps to try/follow, I would greatly appreciate your help.
Thanks for taking the time to read this!
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
korockinout13 said:
You could have quickly found an answer if you searched "status 7" or "assert failed." It simply means your phone is identifying as a different device because of the ROM you flashed. You can get around this by flashing a kernel appropriate for whatever you're trying to install, so Devil or Semaphore will do. From there, reboot recovery and install the ROM.
Click to expand...
Click to collapse
I did look up assert failed, but I couldn't get a clear answer.
I didn't occur to me to look up "status 7"; just seemed like a very cryptic error code.
Thank you for your advice nonetheless. I'll update if the error persists.
Semaphore & CyanogenMod
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Headless_One said:
So, I flashed Semaphore 2.8.0 and then attempted to install CyanogenMod 10 (Android 4.1.2, I think).
Got Status 0.
Tried reflashing Semaphore 2.8.0, and 1.2.6. No progress.
Any recommendations?
I tried to flash CyanogenMod 9 on Semaphore 1.2.6 and got Status 7.
Thanks.
Click to expand...
Click to collapse
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
BWolf56 said:
If you would read a bit before doing the flashing you would know that status 0 is from rebuilding the partition. You simply need to flash CM10.1 twice. So it goes like this: Flash CM10.1, reboot recovery, flash CM10.1.
Click to expand...
Click to collapse
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Headless_One said:
I do look up the error. Just no one actually mentioning that until your post.
Thank you for your advice.
I flashed it 3 times (rebooting each time) and I always get Status 0.
More explicitly:
Code:
-- Installing: /sdcard/cm-10.0.0-captivatemtd.zip
Finding update package...
Opening update package...
Installing update...
E:Error in /sdcard/cm-10.0.0-captivatemtd.zip
(Status 0)
Installation aborted.
Side note: I'm on Semaphore 2.8.0 and I used Heimdell to flash it (through Ubuntu).
Any additional thoughts?
Click to expand...
Click to collapse
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
BWolf56 said:
Tried simply booting up?
If that doesn't work, reflash without rebooting recovery.
Click to expand...
Click to collapse
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.
Edit:
Rebooted to Recovery. Updated to CM10.
Noticed that Recovery version changed back to v6.0.1.5.
CM10 seems to be working properly.​
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Headless_One said:
I tried rebooting the device, but, after shortly showing "At&t", it goes straight to the Recovery screen.
I tried installing CM10 again, but same error.
Just reflashed Semaphore. It always gets stuck on At&t after flashing (for several minutes). Is that normal?
So I've been removing the battery, and putting it back in. Then it goes straight to 'Semaphore CWM Recovery v6.0.2.0'.
My steps from there:
Attempted to install CM10. Status 0 error. Turned phone off.
Rebooted straight to CWM-Based Recovery v6.0.1.5.
Tried installing CM10 from there. Status 0 error.
Rebooted. Right back to Recovery v6.0.1.5.
Tried installing CM10 again. Status 0 error
Tried installing CM9. Phone rebooted midway and got stuck on 'At&t' screen.
Rebooted using 3-key button combo (to get to recovery screen).
Went to Recovery v6.0.1.1. (What the hell is going on?)
Tried installing CM9. SUCCESSFUL. Also installed gapps for ICS while at it.
Booted to CM9 correctly.
Rebooted to Recovery and it was still Recovery v6.0.1.1.
Rebooted back to CM9 properly.​
Anyone knows why I am getting 3 different Recovery versions?
Note: Sorry for the somewhat long post. I just figured I should tell you everything I am doing step-by-step.
Click to expand...
Click to collapse
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
BWolf56 said:
Actually that's great details, thanks!
Have you tried flashing CM10 from CM9? It will still have to rebuild the partition so 2 flashes will be needed.
Click to expand...
Click to collapse
Yes sir, I just did that. It works
Thanks for your help.
Just wanted to thank you both for this thread. Totally helped me upgrade my Cappy to CM10.1 today. Thanks!

[Q] Can't seem to get back to stock w/o root

So I rooted the nook hd+ and I'm trying to get it back to stock using CWM and the stock 2.1.1 zip supplied in this thread in section 6. The problem is, whenever I boot to CWM and try to install the .zip, I get this error:
"Failed to retouch '/system/lib/libemoji.so'"
I'm not sure what's causing this, and also if I go through the steps of just reinstalling the stock 2.1.1 ROOTED .zip in that same thread, it goes thorugh fine. Is there anything I can do about this? I'm basically just trying to get it back to a stock, unrooted form. Thank you,
mva5580 said:
So I rooted the nook hd+ and I'm trying to get it back to stock using CWM and the stock 2.1.1 zip supplied in this thread in section 6. The problem is, whenever I boot to CWM and try to install the .zip, I get this error:
"Failed to retouch '/system/lib/libemoji.so'"
I'm not sure what's causing this, and also if I go through the steps of just reinstalling the stock 2.1.1 ROOTED .zip in that same thread, it goes thorugh fine. Is there anything I can do about this? I'm basically just trying to get it back to a stock, unrooted form. Thank you,
Click to expand...
Click to collapse
Go to CWM mounts and storage and format /system before flashing the stock zip. That fixed it for me. If it does not, try the 2.1.0 version.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Go to CWM mounts and storage and format /system before flashing the stock zip. That fixed it for me. If it does not, try the 2.1.0 version.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I gave that a try, it gives me the same error. It actually also says after that error "E: Error in sdcard/NookHDplus....file name" (Status 7)"
Is there something wrong with the file perhaps? Like I said if I run the rooted .zip, it goes through fine.
EDIT: I figured it out. To get it to go through I did it in the following steps:
- booted to CWM, formatted system and wiped data/factory reset
- rebooted to CWM, installed .zip
And it worked. I was doing all of those things, just not quite in that order. Thanks for the help, you do great work here.

Categories

Resources