Database Develop

After booting aospCMod 2.3.2

So for the past two days I've been trying to flash the new AOSP Gingerbread ROM, but although I follow everything straight from the wiki it always seems to get stuck on the HTC screen after the last reboot. Help me please!
EDIT: So I somehow got the rom to boot last night using RA recovery but after loading up a notice says Setup Wizard not being able to respond...etc, etc. Also after booting my home, call, and search buttons don't work at all. not even for other roms. PLEASE HELP!
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.

Make sure u install manually through clockworkmod mod first format boot system data and cache then install the rom let it boot then reboot and install gapps without wiping and reboot then you should be good I'm using the normal clockworkmod 2.5.2 and it works great
Sent from my HTC Hero CDMA using XDA App

okay thanks! ill try that and get back to you.
so no luck at booting. i'm still stuck at the HTC Boot screen.

i tried also and still no luck .. i hate this

to anybody having problems flashing GB, try these steps EXACTLY:
1) use clockwork 2.5.0.1 and follow the wipe/format process in the wiki
2) flash the rom then gapps
3) FLASH A CAPPED 691 KERNEL
This seems to be a continued issue, and I think it is because some phones can't handle high clock speeds like 768. The recovery currently posted by aosp (cwm 3.0.0.5) is overclocked and therefore will not boot, same with the kernel in the rom. Report back here if it works, I have already updated the wiki to advise people of this. Good Luck.

So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.

I'm upgrading aosp 2.3.2 rom from nightly build #188. Before flashing aosp rom plesae try to wipe everything like data, dalvik-cache, battery and rotate status. BTW, I'm using RA-Recovery not ClockworkMod.

i installed it after the standard wipes and thats it and its working just fine at 768 on my hero200. didnt have any issues and im loving the rom, but i am having one issue. this link is to my issue in q and a. if you can help feel free to hop on my thread and reply. other than that, i juast wanted to say this rom is great!

sai5o4 said:
So i tried it again with the capped kernel and it still didn't work. also tried it without firerat's MOD but still a no go.
Click to expand...
Click to collapse
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass

il Duce said:
Did you also flash a capped recovery?
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
I agree with that. He should try a recovery that's not overclocked.
Root-Hack-Mod-Always™

Yeah I'm using clockwork 2.5.0.1.

sai5o4 said:
Yeah I'm using clockwork 2.5.0.1.
Click to expand...
Click to collapse
Well, I hate to say it but you must be missing a step somewhere. FYI in the OP for gingerbread the cwm3.0.0.5 is now capped at 691, so try that one again. Wipe both wipe options, go to mounts and format boot,system,data,cache, then gn into advanced wipe dalvik twice. Flash the rom,gapps,deca #43 capped 691 kernel, reboot. The first boot should take a while so be patient. Report back here if you can't get it, and I would recommend going into the live help room (aospbot IRC) which in the OP for GB. Good luck.

So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App

sai5o4 said:
So still no luck. But I'm determined to somehow fix this no matter how many times I try!
Sent from my HERO200 using XDA App
Click to expand...
Click to collapse
I think you should back up your sd card and then format it in your pc. Then start all over. From the recovery on down. Skip any mods till you get booted up. Like keyboards and boot screens etc. And try the capped cwm recovery. Hope it helps good luck
Something.About.Me.You.Dont
Like.Its.Cool.I.Understand.AWAH

Still no luck on booting aospCMod. Like they say no two heroes are the same. But that doesn't mean I'm still not going to try again and again and again (xinfinity).

got it to boot but...
so i somehow got it to boot using ra-recovery but right as i loads it says the setup wizard has unexpetedly stopped processing. any help?

sai5o4 said:
020211 So after following instructions from this post: http://forum.xda-developers.com/showpost.php?p=11078749&postcount=4860 i was finally able to boot CM7 fully and without problems. If you're having problems with booting aosp's gingerbread rom just use this guy's instructions (at the bottom) and you should be good to go.
Click to expand...
Click to collapse
Glad I could help man! Glad to see you got it worked out!

There's a readme in the Aosp 2.3.2 OP. It's right under the files, labeled README. I think it would help if anyone having trouble actually reads through this. skipping steps causes problems.
also, Factory reset skips over the /system partition. I recommend wiping /system partition if you're coming from another rom, or if you are decided to start fresh. You have to go into the partitions menu to actually format the /system partition.

mtran2988 said:
You have to go into the partitions menu to actually format the /system partition.
Click to expand...
Click to collapse
This is true if you use CWM (which I do not ) but if you fastboot wipe all the partitions you will have no issues w/ RA as the OP discovered once he used the instructions that I posted.

touble with vvm
uh not quite sure if this is rite place to post this but looked better than the rest, so i got the rom running fine and it is wonderful improvement to my what use to be my wifes stock hero. Only problem is with the visual voice mail, i copied it from the stock hero before flashing, than after flashing copied it back, it works in the sense that i can see the voicemail in the app and even the voicemail to text works, but 2 things are wrong, 1 is i cant clear voicemail notification in the status bar without rebooting phone, and now she gets a text from a 9069 that tells her phone has recieved a voicemail, found a work around for the second one i blocked the number using blacklist so the text dont come thru nomore, but how i can i fix the fact that the only way to clear the voicemail notification is to reboot the phone? Any help, comments or suggestions would be greatly appreciated. Or is there somewhere i can dl the latest sprint vvm app?? or are they device specific. Thank you in advance for any help

CM7 Stable

http://forum.cyanogenmod.com/topic/...r-barnes-noble-nook-color-v700-10-april-2011/
here it is

[email protected] said:
http://forum.cyanogenmod.com/topic/...r-barnes-noble-nook-color-v700-10-april-2011/
here it is
Click to expand...
Click to collapse
Thanks bro

thanked. just took the plunge from froyo to cm7 on friday! shoulda waited 2 days but hey, should be a lot quicker this time around.
looking forward to checkin it out

Holy shiznit! Looks like I'm going to have to upgrade from Froyo sooner than expected. I was wondering why dalingrin's kernel thread was so quiet this weekend. Sounds like he and the rest of the Encore team were hard at work.
Sent from my DROID2 using XDA Premium App

lol.. wouldn't matter. CM7 is constantly making updates. I usually flash every other day.

anyone know if this fixes sleep issues?

Yes, the answer is no.
Sent from my Desire HD using XDA App

samuelhalff said:
Yes, the answer is no.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
OUCH!!! The sleep thing and huge battery drain prevented me from shifting from old-but-sturdy 2.1 stock, which I charged last time...let me think...31 March.
If I had CM7 I would have charged it already 5 times.

Cm7 power problems / sleep death
This may be a dumb question but if Nookie Froyo doesn't have either of the power or sleep problems that CM7 does, would it be possible to track down and fix these bugs by comparing their source codes?

so many awesomes. but im guessing flash still dosnt work?

jabrams said:
This may be a dumb question but if Nookie Froyo doesn't have either of the power or sleep problems that CM7 does, would it be possible to track down and fix these bugs by comparing their source codes?
Click to expand...
Click to collapse
I believe they've found the problem and have fixed it in the kernel, but since it was so close to the release date, they've decided to release CM7 first with the existing kernel first, and then bug test the new one with the fix.
So we can look forward to having it fixed in the next few nightlies, hopefully.

boogerboy72 said:
so many awesomes. but im guessing flash still dosnt work?
Click to expand...
Click to collapse
Flash has been working flawlessly since mid-March in CM7. The only major issues to be worked on still with CM7 are improved Bluetooth range, eliminating the Sleep of Death (although it uses only ~1%/hour for me now while in sleep), and as with every device continued performance tweaks. There are plenty of smaller things to be fixed as well including screen shot support (which was fixed by Fattire and just needs verified/added to source), integrated button remapping (in works by Mad-Murdock), and anything else people can think to work on.

boogerboy72 said:
so many awesomes. but im guessing flash still dosnt work?
Click to expand...
Click to collapse
Flash works fine with CM7 stable.

Awesome. So far it's running great.
Sent from my NookColor using Tapatalk

Just got it installed..
So far so good. I took the plunge last night to get it installed. Well, first try after formatting system, data, and cache went ok. Then rebooted and it got stuck on "Android" text at the bottom. Simply restarted holding the "power + n", then it successfully booted into CWR. Flashed and viola. Looks good. Love the included Cyanogen wallpapers. =)
So far, no issues, but then again, I haven't played with it much. My Bluetooth option is listed and when I try to turn it on, it tries for a bit, then does nothing. Any ideas?
Oh yeah... I used the OC kernel and it seems to be fine. =P

hvuong2 said:
So far so good. I took the plunge last night to get it installed. Well, first try after formatting system, data, and cache went ok. Then rebooted and it got stuck on "Android" text at the bottom. Simply restarted holding the "power + n", then it successfully booted into CWR. Flashed and viola. Looks good. Love the included Cyanogen wallpapers. =)
So far, no issues, but then again, I haven't played with it much. My Bluetooth option is listed and when I try to turn it on, it tries for a bit, then does nothing. Any ideas?
Oh yeah... I used the OC kernel and it seems to be fine. =P
Click to expand...
Click to collapse
BLuetooth is a known issue. You need to either hard reboot, which is holding the physical power till it shuts off, or choose "Fix permissions" in Rom Manager then reboot, or a combination of both.

eozoon said:
I believe they've found the problem and have fixed it in the kernel, but since it was so close to the release date, they've decided to release CM7 first with the existing kernel first, and then bug test the new one with the fix.
So we can look forward to having it fixed in the next few nightlies, hopefully.
Click to expand...
Click to collapse
That is great news! I hope the new kernel comes ouut soon to! How or where did u hear/read about it?
Also a seperate question. The link i have for the CWR image for my sd card is bad. Not for a bootable sd. I want to nstall cm7 from scratch on the EMMC but i first need to image a CWR sd card then put cm7 stable on it. Do you have that image link?
Thanks!!!

hey guys i have somewhat of a dumb question. I have my nok running hneycomb using that dual booth method. If i wanred to flash cm7 on it, should i completely undo the dual boot? Or go ahead and boot into recovery and try installing it?

You have to first undo the dual boot, because the dual boot created a second partition (hd) on your nook color. If you don't undo the dual boot, you'll just lose that space as cm7 will overwrite the file that allows you to boot into honeycomb.

none of the widgets I downloaded are showing up on the widget list with this rom

Help a newb and feel special today!

Just got a rooted incredible S, I got told there is a ROM on it but on boot it just shows the HTC splashscreen then the wavering android logo and didnt do anything for 5mins so I took out the battery
Went into... CWM? Power+vol down now im wondering what to do. There is no MicroSD card currently in it.
VIVO PVT SHIP S-OFF RL
HBOOT-1.13.0000
RADIO-3805.09.03.27_M
eMMC-boot
-insert date-"
Am i not mistaken I need a microsd card to install a ROM?
Where to go from here?

P1n3apqlExpr3ss said:
Just got a rooted incredible S, I got told there is a ROM on it but on boot it just shows the HTC splashscreen then the wavering android logo and didnt do anything for 5mins so I took out the battery
Went into... CWM? Power+vol down now im wondering what to do. There is no MicroSD card currently in it.
VIVO PVT SHIP S-OFF RL
HBOOT-1.13.0000
RADIO-3805.09.03.27_M
eMMC-boot
-insert date-"
Am i not mistaken I need a microsd card to install a ROM?
Where to go from here?
Click to expand...
Click to collapse
Yes you will need to get a microSD card to install and flash a new ROM using CWM.

Actually I'm not sure if it is CWM... Its a white background with 3 droids down the bottom on skateboards
Selecting recovery takes me to 4EXTRecovery v2.1.0 which also tells me the current ROM is Nik_IncredibleS_TriNiTy_Sen and cuts off, how do i boot the rom from there?
Or is the SD card also required here? backup/restore under Nandroid part tells me it cant mount the SD card.

P1n3apqlExpr3ss said:
Actually I'm not sure if it is CWM... Its a white background with 3 droids down the bottom on skateboards
Selecting recovery takes me to 4EXTRecovery v2.1.0 which also tells me the current ROM is Nik_IncredibleS_TriNiTy_Sen and cuts off, how do i boot the rom from there?
Or is the SD card also required here? backup/restore under Nandroid part tells me it cant mount the SD card.
Click to expand...
Click to collapse
You are going to want to get a SDcard in there so you can backup the system and download a new ROM or at least download Nik Trinity ROM so you can reflash it.
In the mean time from the recovery menu you could try a wipe data/system reset to see if you can get it booted.
The good thing is that you have permanent S-Off, so you should be able to get one of the ROMs to load and boot.

Will try that now, should i try:
wipe data/factory reset
format system
format data
Or something else? I presume the first option? Dont wanna screw anything up

P1n3apqlExpr3ss said:
Will try that now, should i try:
wipe data/factory reset
format system
format data
Or something else? I presume the first option? Dont wanna screw anything up
Click to expand...
Click to collapse
Yes since you don't have a SD card to flash a ROM, just do the first one.

freedom548 said:
you need reflash the rom.
1.format my SDcard first then copy all zip file to SDcard..
2.use ARHD super wipe
3.flash the rom
Click to expand...
Click to collapse
Don't have a readily available SD card atm, will steal the one from my old phone when I can or buy one in the next couple days

tpbklake said:
Yes since you don't have a SD card to flash a ROM, just do the first one.
Click to expand...
Click to collapse
Same old, same scenario as before
So when I get the SD card I put the rom files on the SD card then what...?

P1n3apqlExpr3ss said:
Same old, same scenario as before
So when I get the SD card I put the rom files on the SD card then what...?
Click to expand...
Click to collapse
You will need to flash/reflash a ROM zip file from recovery. As a previous poster noted, run the ARHD super wipe script first and then flash a ROM.

Gotcha makes sense now, would you recommend the ARHD ROM or something from CM or MIUI? Or is it down to the usual personal preference thing?

P1n3apqlExpr3ss said:
Gotcha makes sense now, would you recommend the ARHD ROM or something from CM or MIUI? Or is it down to the usual personal preference thing?
Click to expand...
Click to collapse
Personal preference. On my original HTC ARia I went with CM6 and CM7 because HTC Sense was too slow, but on my IncS it runs Sense 2.1 so well I have just stuck with a rooted version of the WWE stock 2.10.405.1 ROM. To each his own.

tpbklake said:
Personal preference. On my original HTC ARia I went with CM6 and CM7 because HTC Sense was too slow, but on my IncS it runs Sense 2.1 so well I have just stuck with a rooted version of the WWE stock 2.10.405.1 ROM. To each his own.
Click to expand...
Click to collapse
Thought so. One last thing, when I flash a ROM using the SD card, it is okay for me to swap them out isnt it? Ill just lose some temp data, maybe some app data and whatever media files I had on it?

P1n3apqlExpr3ss said:
Thought so. One last thing, when I flash a ROM using the SD card, it is okay for me to swap them out isnt it? Ill just lose some temp data, maybe some app data and whatever media files I had on it?
Click to expand...
Click to collapse
Yes you can swap them.

P1n3apqlExpr3ss said:
Gotcha makes sense now, would you recommend the ARHD ROM or something from CM or MIUI? Or is it down to the usual personal preference thing?
Click to expand...
Click to collapse
Really depends on weather u want a Sense ROM or not. Niks Trinity sensation XL v2 is turning out to be a great sense ROM heavy on the eye candy, although this can also be a bit heavy on the battery consumption. CM or arhd for non sense ROMs. Flash one, try it out, back it up then flash another, try that out, if u like back it up, if not restore the older flash and use that or flash another. With CW recovery the possibilities are endless. Happy flashing....once u get an sd!
Sent from my HTC Incredible S using XDA App

Thanks for the help tpbklake
Exactly what I was thinking Vader, may as well try out a few before deciding on anything
Any idea when we can expect semi-stable AOSP builds? I have noticed GalnetMIUI have started introducing some of the ICS framework into their builds http://galnetmiui.co.uk/landing/ics-builds/

Anyone want to help guide me through this?
Got the MicroSD and formatted as FAT32, currently downloading ARHD and CM and will use whatever downloads sooner
EDIT: Looks like CM will be done a lot sooner, with the installation process http://wiki.cyanogenmod.com/wiki/HTC_Incredible_S:_Full_Update_Guide do i need to put it under a root folder? ARHD doesnt mention a specific folder, only the SD card. Does it really matter?
EDIT2: Installed CM7.1 fine, then ran the super wipe script and couldnt install Galnet's MIUI for some reason. Will try again and also try ARHD

Well flashing roms in the end is easy enough, anyone want to give me a semi-detailed crash course in backing up apps, back up the rom, restoring apps and old roms?

P1n3apqlExpr3ss said:
Well flashing roms in the end is easy enough, anyone want to give me a semi-detailed crash course in backing up apps, back up the rom, restoring apps and old roms?
Click to expand...
Click to collapse
In recovery mode you can do a nandroid backup which is a complete backup of the phone at that point in time; ROM, apps, settings etc. Restoring a nandroid backup will return the phone to that point in time.
To backup apps and then restore them when you flash a new ROM, IMO I like My Backup Root. Titanium Backup is another choice.

Awesome, that was all easy enough, just restoring apps and their permissions one by one is a pain in the ass
That galnet ICS ROM and a ICS theme is really nice

this is the first time i've heard people trying to flash a rom without a sd card. (where did he put the rom in the first place anyway?)

CM 7.2 release candidate

http://www.cyanogenmod.com/blog/cyanogenmod-7-2-0-rc1-is-upon-us
It’s been a long time in the making, but it’s finally here: CyanogenMod 7.2, the latest version based on Android 2.3(.7), has reached the release candidate stage!
We’ve been delaying it for too long, mostly because new devices kept being submitted to us, and now we feel that at 69 70 devices, CM7.2 is more than ready for everybody to enjoy
7.2 adds a couple of backported features and fixes from Android 4 (ICS), over 20 new devices when compared to 7.1, and even some new features to boot (be sure to check out the new predictive contact search in the phone dialer!). We’ve also fixed some bugs along the way. Some of them device-specific, others that affected everybody, and one in particular that’s been plaguing Android for a long time: the mysteriously vanishing SD-card ringtones are no more! You can check the full list of noteworthy changes at the CHANGELOG.
As usual, you can submit bug reports on these builds: if you find anything broken in your device while running CM7.2-RC1, (as downloaded from our mirrors or ROM Manager! Please do not submit reports if your build came from elsewhere), be sure to submit a report through http://code.google.com/p/cyanogenmod/issues/ , so that we can fix it in time for the final 7.2 release.
from Cyanogenmod Blog

What are the significant differences between this official CM7.2 and the unofficial CM7.2 KANG that we have been using in the last couples of months?

Excuse a noob, but is this file good for SD as well as emmc installs?
thanks

Assuming you have already got a flavor of cm7 installed on an SD card you can copy the update file to the boot partition (I did it from my PC with a card reader), then insert the card in your NC and either access your boot menu and select Reboot Recovery or boot normally and then Reboot with the Recovery option. The files unpack and the penguin is displayed. The unit shuts off and you have to restart (seems to take forever with the android boot animation but wait it out) and all should be well.
Sent from my NookColor using Tapatalk 2 Beta-2

votinh said:
What are the significant differences between this official CM7.2 and the unofficial CM7.2 KANG that we have been using in the last couples of months?
Click to expand...
Click to collapse
KANG 03042012, the latest, *has* CM7.2RC1 so the differences are detailed in that thread but boil down to mr666's enhancements.
For instance, I get the impression from your sig that you run Dalingrin's as a separate update. Dalingrin's has been a part of M-K,(one of the above mentioned enhancements), for a while now.

MISRy said:
KANG 03042012, the latest, *has* CM7.2RC1 so the differences are detailed in that thread but boil down to mr666's enhancements.
For instance, I get the impression from your sig that you run Dalingrin's as a separate update. Dalingrin's has been a part of M-K,(one of the above mentioned enhancements), for a while now.
Click to expand...
Click to collapse
Phrrrrrrr??? What???
Forgive me but what are you talking about?

votinh said:
Phrrrrrrr??? What???
Forgive me but what are you talking about?
Click to expand...
Click to collapse
Glad you said it, so I didn't have to show my ignorance

I was happy to see that 7.2 fixed the magazine stacking in the Nook App. I have the official and the M-K running on different NCs and they're running great!
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk

Sherip said:
The unit shuts off and you have to restart (seems to take forever with the android boot animation but wait it out)
Click to expand...
Click to collapse
I tried to update but I can't even get to the boot animation. It shows CM is loading, flash of light, then goes black. Time for a fresh install I guess.

bp_ said:
I tried to update but I can't even get to the boot animation. It shows CM is loading, flash of light, then goes black. Time for a fresh install I guess.
Click to expand...
Click to collapse
Took awhile even to get to the animation, you may have given up too soon.
I like the update, have noticed improved battery life, nice colors and screen transitions. I have twice had a glitch where it wouldn't wake up after sleeping (twice in the last few days). Hope that doesn't persist.
Sent from my NookColor using Tapatalk 2 Beta-2

libertus77 said:
I was happy to see that 7.2 fixed the magazine stacking in the Nook App. I have the official and the M-K running on different NCs and they're running great!
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Actually it didn't. It's that Nook for Android released a brand new version that fixed the magazine issue. A week prior the older version still stacked all the magazines on top of each other on my 7.2 build.
How do you know if you have the latest version of the Nook app? Download some comic books, it's the first version that supports Nook Comics.

SeaFractor said:
Actually it didn't. It's that Nook for Android released a brand new version that fixed the magazine issue. A week prior the older version still stacked all the magazines on top of each other on my 7.2 build.
Click to expand...
Click to collapse
Hmm. But is the newer version not stacking on 7.1 either? I'm curious, but not enough to flash back to test, I don't think. I just had a friend switch to 7.2. A few days ago specifically because of the stacking, so that would be a good coincidental timing. Anyone still on 7.1 that can check?
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk

libertus77 said:
Hmm. But is the newer version not stacking on 7.1 either? I'm curious, but not enough to flash back to test, I don't think. I just had a friend switch to 7.2. A few days ago specifically because of the stacking, so that would be a good coincidental timing. Anyone still on 7.1 that can check?
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
I had rotated out of 7.1 awhile back and I use B&N app everyday. When they provided the new update for the app, that is when my magazines stacked correctly. The update was actually made for the tablet and the version of the new update is: 3.1.0.19.ANDTBL (and tablet). I updated when it came out and it fixed it immediately. I would think it would still work correctly on 7.1, but like you, do not want to mess with a good think.

Okay, curiosity was bugging me. I tested, and yep, no stacking on 7.1 either, guess it was a B&N fix. 7.2 is good in any case.
Sent from my Eclipsed & V6Supercharged DROID BIONIC using Tapatalk

I did a new install to SD card with the CM7.2RC Most things work as should. Biggest issue is that after some point, the unit will not accept a charge. I plug the cable in (NC Cable/charger) and the light on the cable goes straight to green. Leaving it plugged in for awhile doesn't change the amount of charge (actually is discharging per normal use). After a power off and re-boot, all works as normal. Not sure what the trigger is that causes the Nook Color to not take a charge, but it is not locked up, all programs work normally. It will take a charge and discharge-lets say over a few days, then at some point will not allow a charge. Battery % meter seems to be accurate; tracking appropriately.
I also have a Nightly (#75 I think) SD card that I use, as well as stock Rooted 1.1 on EMMC, and neither have this issue, device is fine electronically.
Any ideas?
Thanks, Mark

Are you sure it's not the cable? They have a bad habit of going south on us.

CM7.0.3 to CM7.2 non rooted on SD card
Hello,
I'm a noob here and found that I should ask questions here on the general forum and not the developers forum.
I have very recently created a sd card non rooted using CM7.0.3 encore and have kernel version 2.6.29-omap1 and its Android version 2.3.3.
I want to keep the ability to return to B&N mode from internal memory to keep my warranty from B&N in check.
I have had issues with using the Google Market app and don't see a lot of apps that I would normally see on my Droid Bionic...like Facebook and others. I have hacked around that issue by finding apps and manually installing them as a work around which is fine for now.
A couple of questions?
By going to a nightly version...can I still remain non-rooted and keep emmc stock and intact with B&N Color flash and boot from my sd card?
will this fix my Google Market issues and have more applications that I can see?
Will I be able to just drag the new CM7.2 ??version code to my /boot directory on my sd card and go into recovery mode to boot it in?
Does this new CM7.2 ??? get put in a particular partition or just under the /boot directory?
Will this wipe out my apps or any data on my sd card?
Will this CM7.2 ??? version support USB host mode for a USB webcam for Skype?
Apparently, this opens another can of worms in that I need to provide USB power from an external hub and I need some kind of Nook Tweaks app to adjust settings?
Can someone explain this?
I have searched these forums and I must say spent a lot of time and nothing seems to be in one place or current on pre-requisites.
Should I get a second sd card to practice on so I don't wipe out my bootable CM7.0.3 version
Any help here would be GREAT!
Thanks in advance!
BB

I'm in a similarsituation as BeaconBob. The following applies to me as well.
BeaconBob said:
... using CM7.0.3 encore and have kernel version 2.6.29-omap1 and its Android version 2.3.3.
A couple of questions?
Will I be able to just drag the new CM7.2 ??version code to my /boot directory on my sd card and go into recovery mode to boot it in?
Does this new CM7.2 ??? get put in a particular partition or just under the /boot directory?
Will this wipe out my apps or any data on my sd card?
Should I get a second sd card to practice on so I don't wipe out my bootable CM7.0.3 version
Any help here would be GREAT!
BB
Click to expand...
Click to collapse
I set up my 8GB card months ago and have forgotten all the details of flashing a ROM. Thanks for any suggestons/help.

Make sure your screen density is set to 180. Clear market cache and data, reboot, and try again.

If you don't want to spring for a new Sandisk class 4 card -- I have five now ) -- just use your Win32Disk Imager to write an image file of your current setup to your computer and go blithely on experimenting like crazy. You will always have an image file to write back to your freshly formatted sd card to take a giant leap backward. But I'd bet you'll never even use it. It's too much fun going forward.
And it never hurts to have a zipped backup of the Titanium BU files available to upload and restore at various stages.
Currently running a racks triple boot, the latest Kang cm7, a dualboot miui/stock, and somewhere I could swear I had an old 253m from back in january. Just so my NC flap doesn't break, I'm good...

Can we dual boot on our note 4

So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.

egren58 said:
So ive been trying to dual boot because i want to try aosp based rom but i need to be a ble to get back to touchwis. Now ive tried the patcher app which aome people said it worked but ive tried everything with no succes.
Click to expand...
Click to collapse
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.

glm0025 said:
I dont't know if this helps but in the thread for the patcher app it was mentioned that if you needed to dual boot with a TW based rom it would need to be the primary in order for it to work properly otherwise the mods would need to be patched before flashing.
Click to expand...
Click to collapse
I swt tw as primary patched cm12 and gapps. But recovery was freezing so i tried to manually paych the file as stated. But than when i got to flash vie recovery it says fail. I have no idea what to do since i did exactly as it said.

My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4

BACARDILIMON said:
My guess would be try asking in the dual boot thread. Others have gotten it to work.
BAD ASS NOTE 4
Click to expand...
Click to collapse
Good idea. But for some reason i cant find the dam thread now. Wtf.

egren58 said:
Good idea. But for some reason i cant find the dam thread now. Wtf.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3058835
All u need
BAD ASS NOTE 4

http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/
I can confirm this works in T-Mobile note 4. You just have to follow the steps.

It works trust me, I'm a senior member

I managed to get it to flash but....
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?

Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
It should when you reboot the device.

Dhat Boi Swerve said:
after i manually patch the gapps and rom, i flash the two files successfully and then i reboot into my secondary rom. I set the kernel then i set up my rom up with the apps i use. I went into the dual boot patcher app and tried to dual boot to my primary rom, it says "please wait"...then it says successfully switched ROM..but it never switches back to my primary rom. Any ideas?
Click to expand...
Click to collapse
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...

suhridkhan said:
Struggling with this thing for the last 2 days. Same issue as your. Cannot switch back to the primary rom...
Click to expand...
Click to collapse
you cant dual boot stock Samsung roms for some reason...

frr1 said:
you cant dual boot stock Samsung roms for some reason...
Click to expand...
Click to collapse
Just got it working, after so much trouble. Tmobile Note4 running TW Rapture as primary and CMRemix as secondary. Still no luck with the second step of patching, but manual patch has worked. This one is a better written guide, I suppose.
http://www.linuxmolecule.com/how-to-dual-boot-roms-on-the-galaxy-note-4/

I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211

jazzmachine said:
I can't believe it's taken me this long to get into trying to dual boot my phone... both my desktop and laptop have ridiculous multi-boot schemes :laugh:
The main reason I haven't yet delved into this is a fairly simple question that I haven't been able to find the answer to: How much free storage space is required / will be used by installing an additional ROM and on which partition(s)?
I'd really appreciate if anyone who has this working could fill me in on that info
BTW another great thread with instructions, etc. is here: http://forum.xda-developers.com/note-4/general/dual-boot-n910f-snap-dragon-variant-t3065211
Click to expand...
Click to collapse
AOSP roms has very small footprint, that's why they are insanely fast... The roms itself with gapps only takes about a gigabyte, if it's CM or other aosp roms. If you dual boot 2 TW roms, of course it's gonna take huge space. It also depends on how many apps you are going to install on the second rom