I think I remember reading somewhere that you can dual-boot gingerbread and froyo (I could be totally wrong so please forgive me if I am) My understanding was once both where installed you could just change kernels to change the OS. Is this possible?
I am running CM7 but I still would love to play around with the other froyo builds people are putting out. However because it is not as simple as just simply booting into recovery flashing a new ROM I am less prone to doing so. (I usually download and flash the ROM's while i'm on the go. Don't usually have a computer near me to use ODIN and such)
Thanks in advance
There was a CM7 build a ways back that was psuedo-dual boot. Once you flashed the ROM and were on 2.3, if you ODIN'd over a 2.2 Kernel, it would boot back into Froyo. If you ODIN'd over the 2.3 kernel, it would boot back into Ginger. Pretty sure it's not possible to do that with the current CM7 build that's being worked on.
Thanks for responding. Its too bad, I don't want to go backwards but they do amazing work on these forums
geokhentix said:
There was a CM7 build a ways back that was psuedo-dual boot. Once you flashed the ROM and were on 2.3, if you ODIN'd over a 2.2 Kernel, it would boot back into Froyo. If you ODIN'd over the 2.3 kernel, it would boot back into Ginger. Pretty sure it's not possible to do that with the current CM7 build that's being worked on.
Click to expand...
Click to collapse
CM, DG, Team Phoenix, Supercurio (and everyone else) thank you all for the freedom
I can't find a definite answer for upgrading from 7.0.2 to 7.0.3 stable. I did a tatanium and clockwork back up just in case. Have the latest clockwork recovery. But when you boot into recovery do you first wipe system then cache, installed built, then wipe dalvik then reinstall latest gapps then 4/24 OC kernel? Are those the steps? I just want to male sure that way my apps don't get erased. I'm installing to internal memory.
jzibit17 said:
I can't find a definite answer for upgrading from 7.0.2 to 7.0.3 stable. I did a tatanium and clockwork back up just in case. Have the latest clockwork recovery. But when you boot into recovery do you first wipe system then cache, installed built, then wipe dalvik then reinstall latest gapps then 4/24 OC kernel? Are those the steps? I just want to male sure that way my apps don't get erased. I'm installing to internal memory.
Click to expand...
Click to collapse
I would not even update to 7.0.3 to be honest. I'm assuming you are running 7.0.2, so I would download nightly 69, the fixed OC kernel (not the one you are used to using..it needs to be the ext4 one which is available by reading through the notes on the overclock kernel page over in android development...head towards the end of the pages), boot into recovery, flash nightly 69, flash gapps, flash OC kernel, Wipe Cache, Wipe Davlik, Hard reboot...and you're good to go
GchNYadM said:
I would not even update to 7.0.3 to be honest. I'm assuming you are running 7.0.2, so I would download nightly 69, the fixed OC kernel (not the one you are used to using..it needs to be the ext4 one which is available by reading through the notes on the overclock kernel page over in android development...head towards the end of the pages), boot into recovery, flash nightly 69, flash gapps, flash OC kernel, Wipe Cache, Wipe Davlik, Hard reboot...and you're good to go
Click to expand...
Click to collapse
Why would you recommend against 7.0.3?
Rodney
rhester72 said:
Why would you recommend against 7.0.3?
Rodney
Click to expand...
Click to collapse
Well cm7.0.3 runs off of android 2.3.3. The newer nightlies run off of Android 2.3.4 which is going to be what CM7.1 is going to run off of. Both of my nook colors have run cm7.0.3 and one of them had issues (as have a few other people) while the other one ran okay, but the nightlies continued to out perform the cm7.0.3 hands down. Not only that, the newest nightlies getting incredible battery life compared to what cm7.0.3 had. In a test I ran, I got 2 hours and 6 minutes more battery life off of nightly 67 compared to cm7.0.3. It is just a personal preference, but if the option for a newer OS is available, why update to something that is older?
Well, because stable is...stable. I certainly haven't had any issues with 7.0.3 under very heavy and varied use, whereas the nightlies have their share of issues (not to mention an obvious absence of 'real' overclocking), some of which appear to not be common knowledge despite a great many attempts to make them so. =)
Certainly, if I were recommending to a daily user, I'd advocate 7.0.3 over even the latest nightlies, if for no other reason that (once properly installed) it 'just works'.
It's not even clear whether the 1.2 u-boot can be used with the newest kernel betas when booting directly from a SD card, which in and of itself is a major blocker for me (using verygreen's SD image).
I suppose it comes down to personal preference, but again, I'm unaware of any significant outstanding issues with 7.0.3. If someone's having issues, they should by all means ask for help if they don't want to dip their toe in the unstable pool.
Rodney
rhester72 said:
Well, because stable is...stable. I certainly haven't had any issues with 7.0.3 under very heavy and varied use, whereas the nightlies have their share of issues (not to mention an obvious absence of 'real' overclocking), some of which appear to not be common knowledge despite a great many attempts to make them so. =)
Certainly, if I were recommending to a daily user, I'd advocate 7.0.3 over even the latest nightlies, if for no other reason that (once properly installed) it 'just works'.
It's not even clear whether the 1.2 u-boot can be used with the newest kernel betas when booting directly from a SD card, which in and of itself is a major blocker for me (using verygreen's SD image).
I suppose it comes down to personal preference, but again, I'm unaware of any significant outstanding issues with 7.0.3. If someone's having issues, they should by all means ask for help if they don't want to dip their toe in the unstable pool.
Rodney
Click to expand...
Click to collapse
The 1.2 u-boot has to do with the 2.6.32 beta, not the nightlies. I am and have been overclocked on all the nightlies since 59 when they first made the switch to 2.3.4...I have had no issues with any of the nightlies at all, but if you're an average user, then go with 7.0.3...like I said before I just don't see the point in flashing something that is already old compared to what is available and very stable. And why are you still using an SD card? Flash to stockkkk =) and for now, I think I will continue to swim in the stable pool.
rhester72 said:
Well, because stable is...stable. I certainly haven't had any issues with 7.0.3 under very heavy and varied use, whereas the nightlies have their share of issues (not to mention an obvious absence of 'real' overclocking), some of which appear to not be common knowledge despite a great many attempts to make them so. =)
Certainly, if I were recommending to a daily user, I'd advocate 7.0.3 over even the latest nightlies, if for no other reason that (once properly installed) it 'just works'.
It's not even clear whether the 1.2 u-boot can be used with the newest kernel betas when booting directly from a SD card, which in and of itself is a major blocker for me (using verygreen's SD image).
I suppose it comes down to personal preference, but again, I'm unaware of any significant outstanding issues with 7.0.3. If someone's having issues, they should by all means ask for help if they don't want to dip their toe in the unstable pool.
Rodney
Click to expand...
Click to collapse
I dont need the latest nightly i just want something stable since i use my nook everyday. Battery drain isnt an issue for me since i go the whole day with out having to charge it. So if i decide to use nightly (69) you have to use "ext4-CM7-dalingrin-OC-emmc-042411". Is that the same kernel i have to use if i decide to use 7.0.3? or should i just use "CM7-dalingrin-OC-emmc-042411"
jzibit17 said:
I dont need the latest nightly i just want something stable since i use my nook everyday. Battery drain isnt an issue for me since i go the whole day with out having to charge it. So if i decide to use nightly (69) you have to use "ext4-CM7-dalingrin-OC-emmc-042411". Is that the same kernel i have to use if i decide to use 7.0.3? or should i just use "CM7-dalingrin-OC-emmc-042411"
Click to expand...
Click to collapse
If you use nightly 69 then yes you need to use the kernel you mentioned above. If you use cm7.0.3 then just use the regular overclock kernel. And nightly 69 is very stable. I have been running all of the 2.3.4 nightlies and they run smooth as butter for me.
im going to use nightly 69 heres the kernel for anyone else interested in upgrading
http://forum.xda-developers.com/showpost.php?p=13499750&postcount=2382
jzibit17 said:
im going to use nightly 69 heres the kernel for anyone else interested in upgrading
http://forum.xda-developers.com/showpost.php?p=13499750&postcount=2382
Click to expand...
Click to collapse
good choice and good luck
There is a misconception in this thread......Your kernel selection has to do with your version of Clockwork Recovery. The latest version of Clockwork Recovery will only boot with a kernel that has had an ext.4 script change. Older versions of Clockwork use the "original" kernels found in dalingrin's kernel page. To eliminate anymore problems or confusion. If you have not updated CWM please do so, then update your kernel to the one with the script change attached to this post. Both SD & EMMC versions are attached.....All will be right with your Nook
I upgraded from 7.0.2 to the nightly 69. Everything went fine, but I no longer have USB connectivity. Any advice on how I might get it working?
I use swiftp to transfer files over Wifi from computer use firezilla or any other ftp program to make a connection. I think it's a bug according to what I read on another post...
That works just fine. Thanks.
I have 7.0.3 running from SD card.
I tried putting the 0424 OC on and found it seemed to be causing a problem with at least one program, LCD Density after I increase to 1200. When I ran the app to increase my icon size it would freeze up the NC and only way out was a forced reboot.
Anyone else find problems like this and is this unusual.
Hi guys,
I have previously installed CM7 on this link:
(I wıll just give the file names, I cannot give the link. Damn spam check!)
update-cm-7-06032011-NIGHTLY-GalaxyS-signed.zip
Plus I have ınstalled glitch's kernel V10.
They work fine now. But I want to update to latest nightly of CM7 (Currently #34) that I downloaded from here:
download.cyanogenmod.com/?device=galaxysmtd
When I update I have boot loop.
Any ideas?
Okay, at first you have to run the kernel-cleaning-script which is available in the Glitch-Thread. After this you can run the voltage scheduler if you undervolted before (you don't have to run it but I do it and I have less problems).
If the bootloop isn't gone make a factory reset (other things didn't help on my SGS) or just reboot a second time.
Thanks for the reply.
I have tried the factory reset etc. stuff but it didn't worked. I heard a lot of people having problems even updating the next nightly build. Now I just decided to stick to my current working state until a stable CM7 released
Hey all, I'm running CM7 7.1 rc-1... I just installed dalingrin's latest oc kernel... And it killed my wifi.. It's really bugging me. My nc is currently oc'd @ 1200.. With a min speed of 600. Is the kernel killing my wifi? Or is it the overclocking?
Thanks in advance.
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Olivier! said:
Hi,
interesting. I had the same experience. My case went a little bit further than that as I lost my whole config after trying to fix it ... long story short, after fixing my nook and re-installing back to stock (1.0.1 then upgrade to 1.3). I tried again, installed same distro on SD but I put all the zip files at the same time on the sd card for install (7.1, gapps and OC); everything got installed and no more wifi problems. I also upgraded to full nightly 212. So far, so good.
I also noticed something: after testing a few apps, I would get a weird behavior. In rom manager, fix permissions would fix most of the issues.
Click to expand...
Click to collapse
hmm.. interesting. I'll give that a try and tell you what happens.
update:
I tried to install the stock firmware by deleting cwm, repartitioning boot to stock (after installing stock 1.1)... now it just loops on the "nook color by bn" screen. any suggestions?
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
patruns said:
Follow the instructions here and start all over. Choose nightly 200 or higher and make sure you use the latest version of CWR (3.2.0.1): http://mrm3.net/nook-color-how-to-install-cyanogenmod-nightlies/
Click to expand...
Click to collapse
brilliant! that worked wonderfully. for future reference, the latest version of CWR seemed to do the trick. thanks!
Hi,
I wish to revert back to cm 7.2 from cm10. I wasn't able to find a conclusive thread which could help with the same. I tried wiping and flashing cm7.2 using CWM but later realized it only flashes update packages. Since cm10 is more updated, nothing happened except a format. Kindly help me with this. I am having lots of trouble with cm10 and its affecting my work
princegoyal88 said:
Hi,
I wish to revert back to cm 7.2 from cm10. I wasn't able to find a conclusive thread which could help with the same. I tried wiping and flashing cm7.2 using CWM but later realized it only flashes update packages. Since cm10 is more updated, nothing happened except a format. Kindly help me with this. I am having lots of trouble with cm10 and its affecting my work
Click to expand...
Click to collapse
I think the smartest way is get back to a stock GB rom using smartflash so you can root, mount a cwm and flash cm7.2 based on that old bootloader