Related
How I got to this...
Rooted
Wiped,,,wiped davlik.
Installed stock N1 rom.
Installed MT Update.
Installed highmem kernel update.
Ever since then Im getting random reboots.
Ive been able to replicate the reboots when downloading podcasts via app or videos via browser.
Can anyone give me a clue as to what may be going on ?
I dont know how to work logcat to get a txt file so I pasted a screen cap.
I opened up doggcatcher and commensed update. Then crash.
I had the same issue happen after i installed the himem with the new update from MoDaCo. Mine rebooted when i copied around 50megs+ to my storage card from the computer.
I wiped, installed Enomthers Official then flashed the himem kernel with no problems.
Yep, me too . But I can only see the problem when copying large files from my SD.
I had the issue of random reboots before, but thats not happening very often since Google's latest update.
I want to know how to get rid of the HIMEM bootloader now. Any ideas ?
Guys.....any replies regarding this is really appreciated !!
I really need to know how to get rid of the freakin HIMEM bootloader, I cant copy new music to my phone this way.
Please let me know which bootloader to use now, since im on the latest update from google with a stock rom.
Im using enom with high-mem and no problems at all
Wiped reflashed with newest Modaco.
Formatted sd card.
Now I have issues with Gallery lol. No super steady Roms yet I gues.
not having any of these problems at all with Cyan's Beta4. No reason for me to try b5 since there isn't anything wrong with b4. I would say try and flash Cyan's B5 or download B4 and see if that fixes your guys problems.
Prod1702 said:
not having any of these problems at all with Cyan's Beta4. No reason for me to try b5 since there isn't anything wrong with b4. I would say try and flash Cyan's B5 or download B4 and see if that fixes your guys problems.
Click to expand...
Click to collapse
I also have Cyanogen's beta 5 with no problems whatsoever! Works and runs great!
Good day all. I recently bought a Nook Color. I'm running CM7.0.2 along with gapps 20110613 from a 16gb SanDisk class 4 SD. When set up the apps (after enabling wifi) I got an error, due to the fact that my sucky router dropped the signal. As a result of this I was not able to download gmail, google maps, etc. My android market runs perfectly but I wanted to flash gapps so as to download gmail and the others. I went into ROM manager and updated to the latest CWM. However, no matter what I do I can't but into recovery. I tried n+power button, reboot into recovery from the power button menu, and from within ROM manager. All no go...it just booted into CM7, so I removed the SD card to boot into stock Nook 1.2 software. When I did this it brought me to the CWM recovery menu (SD card not in). Of course I could not select anything on the menu. Put back in the SD while still in the menu to try select an option but nothing. Shut it down by holding the power button and booted it back up and it went str8 into CM7. Shut down took out SD and it booted into stock Nook 1.2 software. What am I doing wrong guys? I'm trying to flash the overclock kernel and reflash gapps. THANKS
Could the reason gmail, youtube, googlemaps didn't install on setup be due to the fact that I'm not in the USA? If so I'd still like to know what the problem is so I can flash the overclock kernel.
No one has any idea? I know one option is to backup and redo everything, but I'd really like some troubleshooting ideas before.
Did you use the 1.3 image from verygreens thread? If so the old 7.0.* stables are not supported. You will need to back up and redo it either with the old image or a new CM7 version.
---
- Sent from my LG Optimus V using Tapatalk
Yea I used the 1.3 in the thread with 7.0.2. What version cm7 would I need to use with the 1.3? 7.0.3 or a nightly,? Where would I be able to find an older image to work with 7.0.2 and what version of the image should it be?
The 1.3 image won't work with any 7.0.* versions. You should upgrade to either a recent nightly or the 7.1.0 RC. You could find an older image somewhere but there isn't much of a point as you would have to redo it all anyway so why not upgrade? Plus your battery life will improve by a lot as 7.1 RC and the nightlys have deep sleep.
---
- Sent from my LG Optimus V using Tapatalk
As I said many times to newbie who runs CM7 off uSD that do not or should not mess up with ROM Manager. In fact, there are members also confirm that if booting off uSD, ROM Manager has no effect.
Based on what you, OP, described, you had flashed the CwM into the internal memory.
Keep your fingers crossed as I do hope you didn't screw up anything else.
Anyway, using verygreen's 1.3 image along with the latest nightly-built CM7 and the latest 06132001 gapps and boot it off uSD again. You should be fine.
Before that, fix your home wireless network first.
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
dna59 said:
I decided to just go with 7.1RC1 since I wanted the better battery life. Is there a way to check about the CWM on the internal and how would I go about removing it if I did? I ask for warranty purposes ofcourse since I opted for the 2 year extended one. Also to flash upgrades and such, since you don't recomend using ROM manager then how should I go about doing it (i.e. overclocking kernel)?
Click to expand...
Click to collapse
1. I never have any issue related to battery with any nightly build that I've ever used. I am currently having the nb153 and it is fantastic.
2. Check CwM and how to remove off the internal memory? I don't know any quick way except restoring the original ROM.
Again, for warranty purposes, strongly suggest running off uSD
3. Updating by loading/copying/dragging the updated files onto the root folder (aka "boot" partition), then TRY loading into Recovery by:
a. combination of power/N buttons if you have skill or
b. let it boot normally into CM7, wait until completely loaded, then reboot and select "recovery" option. Keep yr fingers crossed. This is an easy method but if it doesn't work then option a is the only choice.
Sorry the battery issue was as compared to the current CM7 stable not the nightly. I got everything installed so far besides the overclock kernel. So I will try your recommendation for booting into recovery not using ROM manager.
You don't flash anything when running off an sd card you just boot into recovery and then reboot. Easiest way to get the overclock kernel would be to just upgrade to the latest nightly.
---
- Sent from my LG Optimus V using Tapatalk
Update 20111117: Updated .zip file to Adobe Flash 11.1 and AIR 3.1.
Update 20111020: Updated .zip file to reinstall Flash and AIR, previous version didn't properly fix AIR.
Steps I used to update Adobe Flash (to version 11.0) and AIR (version 3.0) so it doesn't update automatically and thus get me back into the boot loop cycle (again):
Go to Titanium Backup ( Pro )
You need to uninstall with this since these are system apps
Buy a Pro key and keep it on your SD card root, since this app will save your bacon
Uninstall Adobe AIR and Adobe Flash Player from Titanium Backup
It will warn you that you are uninstalling a system app, that's OK
I think that is why the update through Market isn't working
Open Market, Install Adobe Air (3.1.0.488 as of this post) and Adobe Flash Player (version 11.1 11.1.102.59 as of this post)
Nook seems to be working after several reboots. Also, note that Adobe updated their apps. After following the procedure above, I was able to update via Market without any problems with bootlooping.
Obviously, the above steps only work BEFORE Adobe gets auto-updated and you get in the boot loop cycle. If you are already in the boot loop cycle, download this file (Updated link, should work better this time):
FlashPlayer11.1_AIR3.1_Update_Fix_20111117
and install it using a ClockworkMod Recovery SD card.
Get a ClockworkMod Recovery SD card
http://forum.xda-developers.com/showthread.php?p=11987469
Put the zip from the above post on the SD card
Reboot your Nook with the SD card inserted
Install from Zip, Select zip from SD card, select the flash update
This basically will uninstall flash and air as system apps and install as a user apps. This is based on the zip from GMPOWER which updated flash to 10.3, which worked for some but not others, perhaps because it didn't touch Air:
http://forum.xda-developers.com/showpost.php?p=16526691&postcount=7
Also note, I have been through several cycles of restoring backups, restoring to factory, re-rooting, etc. this last week, so I was getting very annoyed and cautious. I think I was able narrow it down to just the Adobe updates causing my problems. I have been able to update ROM Manager, Superuser, and just about everything else with updates; and besides the Adobe updates, everthing worked, and I don't currently have a boot loop problem.
Note, I didn't update Superuser or ROM Manager until after I applied the above updates to Flash and AIR. After several reboots, my Nook is still working fine.
For those of you who are still having trouble getting your Nook back, and the attached zip doesn't work for you, you can do the following. Using the instructions on this site, I got my Nook back up and running to factory new condition:
http://mrm3.net/nook-color-recover-any-bricked-device/
(Quick method at top, not older methods below; instructions slimmed down from several posts here at XDA, updated for stock 1.2) also here on XDA:
http://forum.xda-developers.com/showthread.php?t=914690 (original restore to stock post)
http://forum.xda-developers.com/showthread.php?t=1050520 (update for stock rom 1.2)
Then, I registered my Nook (again).
At this point, I could have tried to update to 1.3, but my patience was a bit low, so I didn't go for it. If you do, be sure to follow the appropriate ManualNooter instructions here:
http://forum.xda-developers.com/showthread.php?t=1054027
Since I was still on Stock 1.2, I rooted using ManualNooter 4.6.16
(while in CMR, after running ManualNooter, I also applied update-Froyo1.2-dalingrin-OC-emmc-090111.zip, and that seemed to work without a hitch)
Then I reinstalled all the other apps I wanted on my Nook,
=== BUT DID NOT YET UPDATE ADOBE FLASH OR AIR ===
Flashed ClockworkMod Recovery, updated a lot of my apps using Market and Amazon Appstore, restored data and other apps from Titanium Backup,
Then I made a full backup of my Nook using CMR. (still booting normal, running fast and clean)
After confirming my Nook was as I wanted it, and that I had a good backup, I did the steps at the top of this post to update Adobe Flash and AIR.
After confirming that was working, and getting another backup on my SD. I then did the updates to ROM Manager and Superuser. It seemed like those updates happened at the same time as the boot loop, so I was cautious. My Nook is still working well without boot loops as of yet.
Results:
Kernel: Stock 1.2
Rooted with: ManualNooter 4.6.16
Additional Mods:
update-Froyo1.2-dalingrin-OC-emmc-090111.zip,
ClockworkMod Recovery 3.2.0.1,
ROM Manager 4.5.0.1, Titanium Backup 4.5.2,
Adobe Flash 11.1, Adobe AIR 3.1 (uninstalled system app, reinstalled via Market, updated via Market)
[Update Zip] CMR zip to update Flash Player and Air
I updated the original post with a link to the zip to fix the FlashPlayer and Air apps. I had intended to post it here, but since I'm new, I can't link externally in a reply.
Please let me know if there are any problems with the zip and I will get it updated. It worked on my Nook.
I updated the zip file 20111020 to fix a problem with the AIR reinstall.
Wow, thank you so much for this! I wish I had known this on the weekend when I was gong crazy trying to figure out why I was getting bootloops over and over. I can't seem to give you thanks though (probably because I never post, just lurk).
So far I haven't done the uninstall/re-install with TB. I am just making sure my Adobe air and Flash don't update, and when Air did I went into Nook Color Tools and uninstalled the update to set it back to what it was originally. That worked but it is a pain if it keeps happening. I will try the TB to uninsall the programs.
I too did a update on ROM Manager and Superuser (and a binary update), and all is still well. No bootloops. I hold my breath though every time my NC gets to the "color" part until the N appears and it all disolves.
thanks for this!!! this was really getting very frustrating.
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Thanks for this information. My nc is currently in a bootloop and won't load CWR. It shuts off before getting to that point (my bootloop is adobe air related). None of the restore to stock via SD card have worked for me. I'm now looking at ADB options, the post you referenced with the fix has some instructions for that. Did you use the ADB or the SD card instructions? I was actually rooted with CM7 before the bootloop.
Thanks,
shy guy1 said:
Well while I would like to report that the flash fix worked, it didn't. It was already on the boot loop so I installed the update with a flashed SD card and nothing. Still stuck in a boot loop. At this point I am just about ready to give up on this device being a fully functional tablet.
Click to expand...
Click to collapse
I realized that my zip was not working to uninstall and reinstall Air properly. Try the updated zip file in the post.
shelly29 said:
Did you use the ADB or the SD card instructions?
Click to expand...
Click to collapse
I used the SD card instructions. Unless you have done something strange to your nook (not sure what), it should always boot from the SD card first, so you should never have problems booting into CMR from an SD card.
If the link in the original post doesn't work for you to get a CMR SD card, try the instructions here:
http://mrm3.net/nook-color-updated-clockwork-recovery-bootable-sd/
If you have a newer Nook, you may need to repartition your Nook's internal memory and use CMR version 3.2.0.1. See details here (this guy just condenses the instructions you can find on various posts on XDA, and tries to keep it up-to-date)
http://mrm3.net/nook-color-how-to-blue-dot-nook-color/
Also note that I updated the zip file in the post to correctly uninstall and reinstall Flash. I re=bootlooped my nook, and after applying the new zip, my nook was working.
Just an update....
I wanted to let U guys know that I had updated Adobe Flash, Air and Super Users and this has worked for me. I also went to double check the versions of both Flash an Air and they are the newest versions!? I still went to uncheck the "Update Automatically" setting in the market for them both just in case for future updates for the time being. Back up and Running! Thanks Again to ALL involved who put contributions to this
This may have worked for me
I tried the updated fix posted here, and the Nook booted properly. Thank you for this fix; I hope it continues to work for me.
I will have to locate the automated back up mentioned here (Titanium), and I will see how this works. I had been leaving my Nook on at all times to avoid the reboot until I turned it off yesterday, forgetting that I did not want to do that.
Awesome post.
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Thanks!!!! You are my new best friend. XD I ended up reflashing several times before I found this post. Followed the instructions and my Nook is happily running Android again without reinstalling (again!). I thank you. My Nook thanks you. And the Angry Birds who would have had to start from scratch thank you.
Thank you! It appears to work now. I've restarted a few times with success!
Took me about an hour to find this thead. I knew there would be an easier fix than starting from scratch. The zip worked on my rooted 1.2
Thanks! Keep up the good work
Thanks! That worked for me.
Stagnation1 said:
I'm having the boot loop issue and neither the zip nor the 1.2 restore work to get past it. Does anyone have any ideas?
Click to expand...
Click to collapse
From my previous searches, it seems the boot loop is usually caused by either an incompatible installation of Adobe flash, or an incompatible kernel (central part of the ROM). Hopefully the OP zip will fix the first, but I'm not sure of another way to fix the second, other than reflashing and rerooting. How far in the reflash/reroot process do you get before it boot loops again?
mastigia said:
So...after all this is said and done and I manage to get a restore image to load and actually boot, now the library doesn't sync and the shop won't load and I get error messages such as " internal error exception executing the command ". It is like the B&N servers are confused. Any ideas about that?
Click to expand...
Click to collapse
Hmm, haven't seen that error. I'm not sure whether its related to the same problem. It sounds like you might need to re-register your nook with B&N. I'm not sure if you can do this without restoring to stock. Not much help, sorry.
I can't post a reply to this ([NC][1.2][1.3] ManualNooter 4.6.16) thread yet - Still new to these forums... I was one of the many in that thread who had installed ManualNooter 4.6.16 on Nook Stock 1.3 only to end up with a boot loop.
Wish I had found this thread last week - would have saved me a lot of headaches!
It's okay though - every boot loop is another opportunity to learn something new.
Thanks much for the easy walkthrough and I hope others find their way here too.
Just saw another new update for Flash & Air .. released yesterday I believe. Has anyone try them yet ? Just don't want to was my time getting into a boot loop again by updating it.
--
Hi All,
I am new here and this is my first post. But i have been reading this forum for quite sometime and know that u guys are now my final stone. I am a proud owner of a Motorola Defy. And I am having this strange behavior, which is effectively rendered the phone almost useless. The phone is acting like its got a restore point in itself, and every time i restart.. it gets back to that point in time.
This includes app installs, uninstalls, stuff placed in system through adb push, theme, everything in the OS. I tried installing a different ROm through clockworkmod, but its not taking effect. Its saying install success but as soon as it restarts, its going back to the old ROM. (takes time to load, so i guess it reinstall back/restored the old version)
Details of device : I am from India and the phone was manufactured in India in around April/May 2011. Its a red lens Defy and and came with Eclair. I updated it officially to the first Froyo release for SEA region. After that i rooted the phone with superone click, and installed WIUI rom. I have been updating the ROM with newer versions around each month. The last one was 1.11.18 though as i waiting for a good ICS version to flash.
The problem occurred after i started installing some gold apps from getJar. It restated in between and install... and that point is kind of acting like a restore point even now.
Things I did: Tried installing different rom by CWM method. Reinstalling second init and CM, both old and new version. Tried restoring nandroid backup of my official ROM. Tried fixed and full sbf flash through rsdlite 4.9.5.2 and now 5.6. First 3 things reset as soon as i restart. For RSDLite, it gives checksum error for each and every ROM i tried. I tried all SEA releases, JORDN_U3_97.21.51, Defy Plus Rom 2.3.6, 2.21 first eclair rom, everything gives the same error. From the RSDLite logs, i could see that there is something wrong as.. say the last successful CG was 33, and the error came for 34, the log says its expecting the checksum on the sbf to be equal to that of CG 33. Its taking the last successful checksum validation and expecting that for all the CGs henceforth. its not showing what the device actually has.
I atlast could somehow, but trial and error, removed all the CGs which were throwing error, and recompiled the sbf to make it pass the RSDLite flash. The CGs present in the ROM (JRDNEM_U3_3.4.3-36-1.7) were 32, 34, 42, 53, 61, 64, 65. And as soon as it booted, it restored back to the checkpoint. Even after i formatted by card and put it in, the app shortcuts remained on the home screen, but as the apps on the card were gone, they are just junk and doesnt open anything.
Thanks in advance. Please let me know what you need from me to help me resolve this issue.
Any help... Anyone?
Can someone please suggest something?
This is what i got from some people. I am not sure how far this is possible, but somehow the theme i installed just before this all happened, from MIUI market.. somehow managed to change something inside phone's kernel, past the locked bootloader? I am totally a noob in this and just a wild imagination?
Or may be some sort of cache wipe is happening everytime the phone boots up, So even when i install the ROM, when it boots up, it gets back the old ROM.. like what would probably happen if i do a factory reset soon after i instal a rom before the restart..?
I would really appreciate it if anyone could help me out with this...
Checksum errors were for me also.
I tried my office computer for flashing and instantly flash was done. The checksum error occurred 7 times on my good computer before that.
Reflashing froyo must take care of all errors happening
Thanks Kapil fr the response. Are you from india? Which sbf did u flash? And waht all did u install in the office pc? I have a pc of my friend where i can try to reflash if you tell me the exact steps that u took in the fresh pc.
Also, can anybody tell me how to use adb commands in CWM mode? Its recognizing my phone in normal mode but as soon as it boots in Moto recovery of CWM, its not recognizing anymore. Want to use adb format commands from recovery.
Hi I was able to use adb in CWM, but format commands were not working. How can i format the system partition? please help me with this.
Is there anyone here who know how to restore a nandroid backup manually using adb commands for MB525???!!!!!
Sounds weird and impossible. Try this. Wipe everything though cwm and flash new rom. Try ms2ginger.
Thanks darshanonline for the suggestion. I tried to wipe everything.. factory reset+cache+dalvik cache wipe. And then tried to install cyanogenmod 7.1 as well as 3 different wiui builds. Everytime it shows that the install was successful, ut as soon as i restart, it would go back to the old ROM.
Is there any checkpoint system in android, seeing the init.rc, i can see comments on something about saving a checkpoint. Is there any particular condition under which this checkpoint may be getting used on very restart?
Also.. is there any way for RSDLite to skip the chksum validations and get the install anyways?.. Some sort of a hack into it?
Ok.. Found something else thats happening. I dont need to shutdown for the system to revert back. Say i install a few things new after a reboot.. After some time.. 1 day at max, i am not able to open them, and neither am i able to open manage applications or market. Everything force closes. I have Ti Backup installed, and i opened it, and i didnt find the new apps to back up. I connected the device and checked through adb, and they were not present in the app folder. They just vanished... So basically after a certain point of tiime, the new stuff just gets deleted on its own.
Guys i know i may sound dumb and stupid with my questions, but i really couldnt find any solution on the net for this. Please tell me waht i should do, and i'll do it. But tell me something. Dont ignore please!
and you did wipe data from within stock recovery (vol down+power etc.), i presume..
Sent from my MB526 using Tapatalk
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Soumik84 said:
Yes i did that too.
wiped data and cache. Restarted to cwm and installed update.zip (renamed cm 7.1 stable) and by selecting zip from sd card. Same results. Installs successfully but reverts back as soon as i restart.
Click to expand...
Click to collapse
DL WIUI 1.12.16 ICS > copy to SD card > Boot in CWM > select zip to install > Install WIUI 1.12.16
Hopefully your problem should be solved.
I found 1.12.16 ICS with lesser FC than the 2.21
labsin said:
Same problem here:
http://forum.xda-developers.com/showthread.php?p=22617834
Click to expand...
Click to collapse
Thanks for the link. Now i know that i am not the only one having this issue. But even there its not resolved yet.
@ headers.chennai - Thanks. I will try that ROM, along with Pikachu ROM with Aroma installer, might be a different installer can try fix it?!
BTW.. does anyone have the TI OMAP board utility? Any chance that it can be available outsite here?
I tried the arora installer and it supposedly formatted the system partition and remade it.. but as soon as it finishes and i restart.. I get back the same ROM.
Is it some way that the files are not getting deleted, like some hardware lock or fault?
Soumik84 said:
I tried the arora installer and it supposedly formatted the system partition and remade it...
Click to expand...
Click to collapse
Hi, bro! What is "arora"? I should try it asap, and all other chance.
My trouble here, same as your.
Hey man.. looks like we are having same problem...
Sorry abt the typo... its Aroma Installer. Its with the Pikachu ROM in this link :
http://forum.xda-developers.com/showthread.php?t=1498843
Its a new installer that launches from cwm when u try and install this ROM. u got some options to select and on selecting the complete install option,, the log shows that it formats the system partition and then creates it. I saved the log file, but for some reason the file shows up blank now. Might be problem with the launcher.. or my phone.. dont know.
Soumik84 said:
Its a new installer that launches from cwm...
Click to expand...
Click to collapse
Not for me, my checkpoint without cwm
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!