Database Users

New to the Nook Color

Hi I just got a nook color for 160 bucks off Craigslist. It is rooted running cyanogen mod 7 encore 7.0.2. I was wondering how to get miui ubuntu and bluetooth working. Also I'm new to this so if there is anything else you guys recommend it'd be great to hear about. Also when I first opened up rom manager it says I need to install a recovery and I accidentally installed a one for a different device and now I can't access the recovery and when I click on flash recovery and I click on nook color it says an error occurred while attempting to run privileged commands
Sent from my HTC Sensation 4G using XDA App

I dont have the links off hand, but you should be able to create a micro SD card with CWR on it and boot into it. From there you should be able to modify and reload everything onto the NC.
Essentially start from scratch. I recommend ditching 7.0.2 and using at least 7.1RC or one of the newer nightly builds. 7.0.2 doesn't have deep sleep and there have been a lot of fixes made in newer builds.

Welcome!
I would also recommend just starting from scratch, unless there is anything on the NC now that you desperately wanted to keep. Who knows what the previous owner did to it. I've personally installed CM7 (just go with the latest nightly) to emmc using these steps:
http://forum.xda-developers.com/showpost.php?p=11452450&postcount=19
If you want to go the SD card route, follow :
http://forum.xda-developers.com/showthread.php?t=1000957
There are steps in each thread about updating to a newer CM7 release. Bluetooth "just works" in any recent nightly. You can enable it in the networks settings panel. If you want to keep what you have, you might try going into the Applications settings and clearing data for Rom Manager (not 100% sure how to undo that setting). There are threads in the Android Development subforum for MUIU and Ubuntu, but [and I'm partial here], CM7 seems to be far and away the better option.

Just a side note here. Since I run bluetooth and host mode daily, I check out each nightly before playing too much. N 161 and 162 have comments about BT issues. If you really need BT, I have found 160 is rock solid.
Sent from my NookColor using Tapatalk

thanks much!

[MIUI] CWM problems.

I made the switch from CM7 (froyo kernel) to MIUI Gingerbread a few days ago.
The "cool factor" on my phone has definitely improved. MIUI is sweet! I've no idea why I held my nose up to it for so long.
Anyway.
It seems The DXC 1.9.23 MIUI that I flashed seems to have automatically updated me to CWM 5.0.2.0.
Bummer. My understanding is these backups aren't compatible with 2.5.0.7?
I THINK that may have something to do with my problem...maybe.
I can't seem to get the "Power Menu" to reboot me into CWM.
I wanted to flash my old BootAnimation back on now that I've decided to stick with MIUI.
Holding the power button and selecting Reboot into CWM brought up an expected SU dialog.
I accepted. I'll attach a screenshot of the package...as it just seems funny to me.
Nothing happens.
No reboot. Nothing.
All the other options work.
Hotboot...bootloader...stock recovery...reboot...
https://lh3.googleusercontent.com/-v...001_063054.jpg
Also, that file on my SD card that it's referencing to doesn't seem to exist.
But I've no idea if that is normal or not.
=] <----Noob.
Rebooting into CWM via ROM manager works fine, however. So I'm confused.
Any ideas?

Hey Jubakuba! I too recently installed MIUI on my Droid X over the Gingerbread kernel. After searching through multiple forums and posting all my troubles, I've come to the conclusion that MIUI and CWM don't play so nicely together. Apparently you must use ROM Manager for all flashing, backups, and recoveries. I was using Droid2Bootstrapper and it caused my phone to factory reset every time, the result being a loss of any settings I had on MIUI (it looked like I just flashed it), Torch not working at all, themes not working, and a factory reset on every subsequent reboot. Try using ROM Manager for all your backup/flashing needs. I'm putting MIUI back on my phone as we speak and I'll be testing ROM Manager out. If you need me to post my results, I will. Good luck!

Sometimes you have to reflash CWM after installing a new ROM. Do it through ROM manager and see if that helps.

Gen1 to Gen2 TPT Upgrade

Sorry for the new thread, but I can't post in the dev section yet - this is really a follow up to http://forum.xda-developers.com/showthread.php?t=1258855 - maybe someone can move it?
I just used the following zip file and it worked well:
CM Nightly 257 Version (Upgrades from Gen1 to Gen2 & installs latest CyanogenMod nightly build - all in one)
Download: cm7-n257-blade-gen1-to-gen2-tpt.zip mirror
Download size: 107.8 MB
MD5: 813ba810ca0a596da4eb6ea7e47205a1
SHA1: 11030dff7b48c79463185b25fc848d488fe77768
A couple of things that weren't clear from the Instructions section (which presumably apply rather to the non all-in-one versions - haven't tried personally) were
a) Does not "reboot into ClockworkMod recovery", rather direct into CM Nightly 257, and
b) Wipes data - presumably must have done because the boot into CM was successful.
This is all very good and nicely automated; could just amend the instructions to be something like:
It should take a few seconds to flash the new Gen2 firmware (you should see some green text), then it should either reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom (for the custom and stock versions), or reboot into CM Nightly 257, no need to wipe or install the CM rom oneself (for the all-in-one).
All in all a great piece of work.

New here and also wish i could post on that thread as i found it extremely useful and it persuaded me to make the jump and finally upgrade my San Francisco.
It honestly feels like a new phone now, after running stock orange 2.1 since i got it about 10months back with some tweaks to launcher etc. I wish id done this a lot sooner. I also used the nightly 257 rom.
I was also (initially alarmed!) a little confused about the points a) and b) you raised above as mine also seemed to skip those steps and just launch straight into the mod. All well and good though this has now left me wondering if the step b was vital. Prior to this on a fresh start and after using Advanced Task Killer to kill all the crap id be looking at around 300mb free memory. Since the new ROM i now have 173mb free in Advanced Task Killer. Odd since i dont have a fraction of the amount of stuff on the phone considering all the stuff that came preloaded with Orange etc.
I dare say the new OS may have a larger footprint. Though my main concern is that as I somehow skipped the part where it says
"then it should reboot into ClockworkMod recovery, use that to wipe data & then install your Gen2 rom." I wonder if this means not all the old ROM has been erased and results in my limited memory.
If i check under Settings > Storage it gives me 294 Total with 203 free under internal storage. Wish id thought to check this value prior to install...
That aside it all works great and im delighted with it.

OK, what do you want free memory for? You should realise that is memory that you have paid for which isn't in use - wasted memory in other words. Android 2.3 uses more ram, when nothing else wants to use it, in order to make your phone run faster, that is a good thing. If you want to use an app which requires a lot of memory then android will free it automatically.
Don't use task killers, they harm system performance by working against Android's own memory & task management system (which is better than any task killer), reduce battery life, cause bugs & you wont get any support at all from anybody involved with Cyanogenmod if you use one.
The all in one version that includes a rom starts straight into that rom, that should be pretty obvious.
It will wipe your data, if you're updating from Android 2.1 then it'll wipe everything. Otherwise it'll miss any apps on your sd card, that's the only reason i say to wipe data - if you're coming from stock Android 2.1 then you can't have any apps on your sd card, so it makes no difference.
Stock Android 2.1 phones have 207mb internal storage ( /data) in total, you gain almost 90mb. The stock Orange bloat apps use up more room (dalvik cache) too, so you end up with much more room to install your own apps & games.

Unable to convert Gen1 -> Gen2 via TPT
Hi all,
I didn't want to start new thread, so I'll post here. In short - I'm unable to convert my Gen1 Blade to Gen2 using wbaw's TPT method.
I followed instructions carefully, tried 2 different zips (Gen1-to-Gen2-TPT-v10-custom, cm7-n257-blade-gen1-to-gen2), used 3 different microSD cards (1GB, 2GB, 8 GB class 4) and still nothing.
Image folder is on the card, all MD5s do match, I turn off the phone, wait few sec (I even took the battery out few times), press and hold menu&vol+ and then power, red power led is on, then green robot shows up, and... nothing, no green text on the screen, just few seconds later my Gen1 ROM is booting.
Any ideas?

make sure that you keep holding menu & vol+ when you press power. that's the only thing i can think of, unless your phone is already gen2. a few sd cards dont work with it, but it shouldn't be that hard to find one that does.

Thanks for the answer, wbaw.
I am holding both - menu (the one in the middle, between home and back) & Vol+ - then I press and hold power, after few seconds I let the power go but keep holding the other two. After few another seconds (while green robot is visible) a regular boot animation shows up.
My phone is definitely Gen1, as I recently installed G1 ROM (mmhmp) and previously used Mr. Pigfish, both report Gen1.
I just reformatted my stock Transcend 2GB card in CWM, put only 'image' folder with all files (MD5s are ok) and still no go. What the hell?....
Btw. I'm using 3.0.2.8 CWM. Does it make any difference? I'm running out of ideas.. what else can I check?

No idea then, sounds like you're doing everything right. The flashing should happen before the green robot shows up, if the robot comes up straight away then it's already failed to flash anything & you have to try again. It's a zte flashing program, built into one of the first bootloaders (the green robot is displayed by a later bootloader), you need to be holding vol+ & menu when you turn it on & for about a second after that, then you can let go. You should see some green text, or maybe just a black screen, then after a minute or two a big version of the green robot & clockworkmod 5.
Clockworkmod is irrelevant, it's a different zte flashing process.
Only thing I can suggest is try another sdcard. I know a few people have reported it didn't work with their sdcard, but it was only a few people & it worked with the 2nd or 3rd sdcard they tried. I got a verbatim 2gb with my phone, that works, sandisk 8gb class 2 works too & so does my new 16gb class 10 verbatim.
If everything fails & you must update to gen2, then there are some windows software phone update packages that let you update your phone using your windows pc. Those packages & instructions are in the zte blade section at modaco.com. It's a bit harder, slightly riskier, but hopefully it'll work.

I just tried another card, some noname 512MB from my old Nokia (I didn't even realized I have so many microSD cards...) and unfortunately this one is also no good. Damn....
So, TPT is built-in and should work with all Gen1 ZTE's no matter what ROM or CWM I'm using, right? Is there any possibility I accidentally removed/erased or destroyed part of it?
I didn't even flash that much, from stock Blade (well, I removed simlock), I installed CWM and went to Swedish Spring (half a year ago). Now I've decided to move forward, installed Gen1 MMHMP, but decided to give CM a try. As you can see not much of a history, therefore I'm even more surprised TPT is not working in my case...
Is there a way to tell this flasher actually works? Something other than just putting gen-to-gen converter image? Any troubleshooting you may think of?
Edit: Tried another card (that's already 5th card!!), 8GB class 4 - no go... I don't think it's a problem with microSD card anymore... it has to be something else.

It turns out TPT is not available on my Blade (some European versions lacking TPT were reported). Anyway, I have successfully converted to Gen 2 using Windows/FTM method. I didn't find it hard, it's just a bit more hassle with repeated flashing. All went good, no need to fear.
Thanks!

Hi, sorry to thread hijack the thread hijack, but I too have a question about this process and can't post in the dev forum.
I just followed the all-in-one process on my girlfriend's brand new stock Orange San Francisco, and it worked flawlessly. I'm now wanting to do the same to mine, but it isn't stock; it has ClockwordMod (3.x, I think) and a FlibbleSan ROM from Modaco installed (Gen1).
What (if any) different steps do I have to take to get everything rolling on my own device? Apologies if it's a stupid question, I was just spooked by the parts about not using it on operator upgraded 2.2 devices and wondered if the same disclaimer applied to user updated phones.
(Merry Christmas )

Never mind, I took the plunge and everything works fine.

Random Reboots after Upgrade
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?

eddiem74 said:
Can't post in Dev forum either so posting here.
I had updated my blade last year from Orange stock to JJF, still GEN1.
I followed the all-in-one process to get to GEN2 CM7 build 257 and all has worked well.
The only issue I am seeing now is random reboots every day or so.
Any ideas? Known issue or fix?
Click to expand...
Click to collapse
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app

karthiknr said:
Have you changed anything under performance tab in CM settings?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
No, just done the update?
Sent from my Nexus S using XDA App

eddiem74 said:
No, just done the update?
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
You did a wipe before flashing right?
Sent from my Blade using XDA app

karthiknr said:
You did a wipe before flashing right?
Sent from my Blade using XDA app
Click to expand...
Click to collapse
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App

eddiem74 said:
There was no option to wipe, it just updated from gen1 to gen2 and booted up after restart from what I can recall.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?

eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Sounds like you need to calibrate the proximity sensor. I think there should be a ZTE Blade settings app that you use to do it.
Probably better to flash one of the latest self-compiled versions of CM7. Its been a while since nightlies were made, but lots of new stuff has been added/fixed since 7.1.0 RCs/stable.

eddiem74 said:
Ok so I used ROM Manager and installed CyanogenMod 7 V7.1.0 as that is meant to be stable, wiped data/cache/etc via the process.
All was well until I needed to make a call, screen keeps going black and I need to remove battery to resolve?
Any ideas?
Click to expand...
Click to collapse
Like Amphoras says calibrate your proximity sensor in the ZTE Blade Settings app. That should do. If you still have a problem,flash the 257 nightly or any other ROM if you don't like CM.
Sent from my Blade using XDA app

this might be a bit offtopic but is there a way to tell from the packaging if the phone has amoled or tft? I suppose tft is best?

[Q] Problem with MIUI

My MIUI rom is MIUI-108050 version and though it's pretty nice when working, I can't enter the Market without it crashing and I can't get it to enter Bootloader or Recovery. Titanium Backup nor Clockwork Recovery nor Rom Manager are available - for some reason they are gone or not accessible. Titanium Backup shows in my App Manager, but it doesn't show in App tray. So my Nook Color is stuck with a barely working MIUI Rom. Does anyone have a suggestion for getting to a different Rom or for getting back to stock?

I briefly tried MIUI and had pretty much the same problem. I read somehwere else that you have to do a complete wipe when you first install it. I haven't bothered going back to confirm if that works, but it might be worth a shot.

Make a new SD card with CWM image on it. I have had great success with eyeballer's image and instructions:
http://forum.xda-developers.com/showthread.php?t=1030227
Then load zip file one of the roms on SD card. 1.11.4 is the latest MIUI rom available at miui.us (my rom of choice)
http://roms.miui.us/
Turn off nook. Load SD card. Turn on nook. In mounts and storage (if it isn't there on initial.screen, tap the power button to go back) format data, format system. Clear cache. Then install zip file of rom.
If my directions don't make sense, post back and I will give you a very detailed list of steps.
Sent from my NookColor using xda premium

I had similar problems with MIUI on NC. I finally had to move to a different ROM. I currently running Phiremond 7.1 and it is very stable.

[Q] CM7 & CM9 Dual Boot Thanks and Questions

I joined the site about a year ago when I first got my TMobile G2 with the intent of modding it. Since I used it mainly for work, I decided to leave it alone and became a lurker since I didn't have much to offer (info wise). Recently I picked up a Nook Color, and after reading about several different mods, decided on Rack's Dual Boot.
Being a noob to Android Systems (but not to computers), I reread the directions a few times. When I got the gist of what to do, I ran through it with no issues. Turned out to be unbelievably easy. Many Thanks to Racks and everyone else that worked so hard to bring us this awesome information (as a side note F**K those douches that are selling cards on fleabay).
Now to the point; There are a couple of questions/issues I have that maybe someone can help with:
1. Occasionally, when I try and download apps from Play, I get an "error in processing purchase" message. When I power down, then boot back and flash the ICS gapps, everything is fine. I have tried clearing cache and data and get the same error message.
2. In CM7, the Nook Tweak App does absolute wonders for the volume of the crappy little speaker. Anything for ICS?
3. I have LG HBS700 Bluetooth Headphones. They work great in GB CM7, but nothing in ICS CM9.
4. Netflix works like a charm in GB CM7 but bogs and freezes in ICS CM9. Same for Youtube. I have downloaded Flash Player with same results.
5. Lastly, is there any way to get sound INTO the NC? That way I can use the Dolphin Voice Browser, Google Voice Search, etc.
Not big on flashing nightlies. Prefer to get system doing what I want and being stable, then sticking to it.
Many Thanks in advance - Mike

UPDATE:
#1 happened again, and reflashed GAPPS. Got the same error message again. Now, I can't download anything from Play Store in ICS CM9.
??????????????????????????????????????
Mike

gollumses said:
UPDATE:
#1 happened again, and reflashed GAPPS. Got the same error message again. Now, I can't download anything from Play Store in ICS CM9.
??????????????????????????????????????
Mike
Click to expand...
Click to collapse
Sorry to hear ur having issues. Only suggestion I would have is to backup whatever apps you have on CM9 with Titanium Backup or any other app that is capable of doing so. Then download a more recent update of a DualbootSD CM9 from the techerrata server. Copy the zip over to the /sdcard partition of the DualbootSD rom and boot into the CWM that is included with the DualbootSD. Then go to "mounts & storage" and choose to format /system & /data then flash the update you just downloaded. That should fix whatever issues you are having with market.
-Racks

gollumses said:
Now to the point; There are a couple of questions/issues I have that maybe someone can help with:
5. Lastly, is there any way to get sound INTO the NC? That way I can use the Dolphin Voice Browser, Google Voice Search, etc.
Click to expand...
Click to collapse
No. The nook has no microphone and bluetooth Mike inputs don't work either. Sorry.

Thanks Leapinlar.
I pretty much already knew the answer to 5, but asked just in case anyone had gotten something to work.
The rest aren't horrible problems. Thanks to the dual boot card, I just reboot into CM7 to watch Netflix. And by the way, the range with my BT Headset is in feet not inches. I was pretty impressed for having no antenna.
The recent Play thing is a pain though. I will walk through your recommendation and get back.
Thanks - Mike
Attached is what I get with Netflix via ICS

Sorry
Meant my last to say "Thanks Racks and Leapinlars"
Mike

racks11479 said:
Sorry to hear ur having issues. Only suggestion I would have is to backup whatever apps you have on CM9 with Titanium Backup or any other app that is capable of doing so. Then download a more recent update of a DualbootSD CM9 from the techerrata server. Copy the zip over to the /sdcard partition of the DualbootSD rom and boot into the CWM that is included with the DualbootSD. Then go to "mounts & storage" and choose to format /system & /data then flash the update you just downloaded. That should fix whatever issues you are having with market.
-Racks
Click to expand...
Click to collapse
Hey Racks,
Okay, I downloaded the MIUI Updates for the Dual Boot Card and put them on the SD Card. I then booted to recovery and open chose zips from SD Card. Installed both GB and ICS Updates. Rebooted into ICS, and everything looked fine. Tried booting into GB and got a nice MIUI.us Boot Screen, then splash screen looks nice, and as soon as I unlock the device I get: "The application launcher (process com.android.launcher) has stopped unexpectedly" and the same with "media" and "acore"
I tried reflashing the old GAPPS, and nothing. My only two options are "FORCE CLOSE" and "REPORT TO MIUI"
Any suggestions?
Thanks Again - Mike

Okay, now I reflashed CM7 MIUI and can't boot into GB. Stuck at MIUI Boot Screen.
On the good news side; I can now download files from Google Play in ICS. WOW! If it's not one, it's the other. HAHAHA
Issues get fixed, and it's still better than the stock Nook Color.
Can I go back to standard Mirage CM7 and keep MIUI CM9, or is it "all or nothing?"
Thanks Again - Mike

gollumses said:
UPDATE:
#1 happened again, and reflashed GAPPS. Got the same error message again. Now, I can't download anything from Play Store in ICS CM9.
??????????????????????????????????????
Mike
Click to expand...
Click to collapse
Try going into Settings, Applications, Manage Applications, All. Find the Google Playstore app. Clear cache. Playstore will then reload your apps when you start it next. If that doesn't work, clear cache and data. You'll have go through the registration process again, but it may work.

Thanks Shumash.
I finally got Google Play working after installing MIUI Update 03252012 (ICS). My big issue now is with CM7.
After doing the update, as soon as I do the unlock, I start getting error messages (see above). I can't get into anything. I can only reboot or turn off power.
I know I can go back to factory settings, reformat and setup the SD Card, and start all over with Mirage CM7 and CM9. Is there a shorter way? Ideally, I would like to revert MIUI CM7 back to the original Mirage, and leave it be (everything worked fine HAHAHA) until someone comes out with a stable HW accelerator, so I can have my Netflix and YouTube in ICS.
Thanks Again - Mike

Convert2Dualboot-SD Tool
Racks,
I've been using your triple-boot for a couple weeks (works great, by the way--thanks!), and I decided to try your Convert2Dualboot-SD Tool (mainly so that I could have ICS CM9 as my primary). Previously I've had Mirage CM7.2-RC1 from 3-23-2012 in primary and ICS CM9 non-OpenGL from 3-25-2012 in secondary. I downloaded everything, including your newest ICS CM9 non-OpenGL (the 5-1-2012 version), to the Nook, extracted, dropped the ICS CM9 zip into the rom-to-modify folder and the ICS gapps file into the gapps-to-modify folder, opened a terminal session and ran the Android script. Everything seems to have been created fine--the new files were in Primary-Mod. I then went into recovery, formatted system1 & data1, then flashed both the ICS CM9 zip and ICS gapps zip.
When I tried to boot into primary, nothing happened. I then booted into secondary and discovered that the secondary partition had been updated to the new ICS version (5-1-2012). It was flaky, so I went back into recovery and re-applied gapps (this time using the non-modified version). It seems to be working fine now, but is in the secondary partition. My primary is apparently currently empty because of the formatting.
So unless CM9 should never be placed in the primary partition, there seems to be a bug somewhere (at least in the Android version). I did see something in the script that appears to be a problem. Within the "ga" leg, it has this coding:
mv gapps_DualbootSD_alternate_${DATE}.zip ../Primary-Mod/gapps_DualbootSD_alternate_${DATE}.zip
I'm not a programmer, but having "Primary-Mod" intermixed with "alternate" would seem to be problematic. But since this is the "ga" leg, I don't know that this would have caused CM9 to be applied to the secondary partition instead of the primary, so there may be a problem somewhere else.
Do you know if anyone else has successfully applied your modded version of the CM9 rom to primary using the Android script? Or should the existing modded version only be placed in the secondary partition?
Thanks,
oldfolkie

oldfolkie said:
Racks,
I've been using your triple-boot for a couple weeks (works great, by the way--thanks!), and I decided to try your Convert2Dualboot-SD Tool (mainly so that I could have ICS CM9 as my primary). Previously I've had Mirage CM7.2-RC1 from 3-23-2012 in primary and ICS CM9 non-OpenGL from 3-25-2012 in secondary. I downloaded everything, including your newest ICS CM9 non-OpenGL (the 5-1-2012 version), to the Nook, extracted, dropped the ICS CM9 zip into the rom-to-modify folder and the ICS gapps file into the gapps-to-modify folder, opened a terminal session and ran the Android script. Everything seems to have been created fine--the new files were in Primary-Mod. I then went into recovery, formatted system1 & data1, then flashed both the ICS CM9 zip and ICS gapps zip.
When I tried to boot into primary, nothing happened. I then booted into secondary and discovered that the secondary partition had been updated to the new ICS version (5-1-2012). It was flaky, so I went back into recovery and re-applied gapps (this time using the non-modified version). It seems to be working fine now, but is in the secondary partition. My primary is apparently currently empty because of the formatting.
So unless CM9 should never be placed in the primary partition, there seems to be a bug somewhere (at least in the Android version). I did see something in the script that appears to be a problem. Within the "ga" leg, it has this coding:
mv gapps_DualbootSD_alternate_${DATE}.zip ../Primary-Mod/gapps_DualbootSD_alternate_${DATE}.zip
I'm not a programmer, but having "Primary-Mod" intermixed with "alternate" would seem to be problematic. But since this is the "ga" leg, I don't know that this would have caused CM9 to be applied to the secondary partition instead of the primary, so there may be a problem somewhere else.
Do you know if anyone else has successfully applied your modded version of the CM9 rom to primary using the Android script? Or should the existing modded version only be placed in the secondary partition?
Thanks,
oldfolkie
Click to expand...
Click to collapse
Goodness! Gotta check my script! But that should have been moved to Alternate-Mod. But as in the appended filename. It should flash to alternate boot. Will correct on next update.
Regarding ur issue, you shouldnt be using my modded zips for conversion as it is already prepped specifically for Primary or Alternate boot.
The script is for converting standard .zips. like a regular nightly. Also note if ur flashing a new rom over default setup. It is recommended to format /system1, /data1 for primary & /system2, /data2 for alternate.
Thanks again for pointing out that error!
Sent from my NookColor using Tapatalk

I figured the issue might be with using the modded zips, but I wasn't sure. Thanks!