I want to install Dalingrin's newest OC kernel, however it says in the description:
* All 2.6.32 kernels require an updated u-boot from B&N 1.2 Froyo. If your Nook has "Read Forever" on the screen when you boot then you have the latest version. If it says something else then you need to update.
My Nook runs CM7, with an older version of Dalingrin's kernel. Does this mean I have to go back to the original B&N OS (how?) and update to 1.2 (last mine run 1.1)?
Or can I get this u-boot somewhere else?
(I know that this question should go to the development section, but I am not allowed to post anything there)
IsaakNicks said:
I want to install Dalingrin's newest OC kernel, however it says in the description:
* All 2.6.32 kernels require an updated u-boot from B&N 1.2 Froyo. If your Nook has "Read Forever" on the screen when you boot then you have the latest version. If it says something else then you need to update.
My Nook runs CM7, with an older version of Dalingrin's kernel. Does this mean I have to go back to the original B&N OS (how?) and update to 1.2 (last mine run 1.1)?
Or can I get this u-boot somewhere else?
(I know that this question should go to the development section, but I am not allowed to post anything there)
Click to expand...
Click to collapse
It is my understanding you need to run the beta CM7 to use the .32 kernal. It will not work with nightlies or stable CM7 builds.
As above...stick with the regular nightlies or stable and the last kernel...unless you are willing to help debugging
Sent from my Eris using XDA Premium App
deadbot1 said:
As above...stick with the regular nightlies or stable and the last kernel...unless you are willing to help debugging
Sent from my Eris using XDA Premium App
Click to expand...
Click to collapse
Helpful info.
That said, for the future, would you have to downgrade to 1.2 and then upgrade back to CM7? I'm in the same boat as the OP.
IsaakNicks said:
I want to install Dalingrin's newest OC kernel, however it says in the description:
* All 2.6.32 kernels require an updated u-boot from B&N 1.2 Froyo. If your Nook has "Read Forever" on the screen when you boot then you have the latest version. If it says something else then you need to update.
My Nook runs CM7, with an older version of Dalingrin's kernel. Does this mean I have to go back to the original B&N OS (how?) and update to 1.2 (last mine run 1.1)?
Or can I get this u-boot somewhere else?
(I know that this question should go to the development section, but I am not allowed to post anything there)
Click to expand...
Click to collapse
It is my understanding, and a very short experience, that you can update the uboot to 1.2 without going to the 7.1 beta. I flashed it shortly before the beta and did boot into my nightly 70. That way you will not have to update uboot when 7.1stable comes out.
But do whatever you feel most comfy with.
Related
Details on my kernel were buried in the CM6 thread but I think it makes sense to have a dedicated thread:
Version 2 of my kernel build is available for CM6, which includes koush's camera fixes. I take absolutely no credit for any of the code. I'm merely building a kernel with a combination of patches which are known to work.
Details:
- Latest CM6 incredible kernel from Koush (taken from git repository)
- HTC wifi driver with wireless N enabled (this is the key difference)
- No overclock or undervolt.
- Uses Koush's (with Hydra's modifications) kernel installer scripts/tools.
Download:
http://www.fourty.net/ftp/public/android/kernel-rmk-cm6-v2.zip
<Insert usual disclaimer about not taking responsibility here>
good idea to make a thread for this, much easier to follow
updating the mash-up thread with a link...
curious though, alot of us have been getting lock up issues still related to the wifi bug i think (v2 with latest nightly)
ive had wifi off for three days now and havent had a lock up since
any ideas?
I am running this kernel with the Test 8 CM ROM. I have found that I am unable to start the WiFi Radio when attempting to use Wireless Tether. The WiFi Tether reports an issue starting the radio in its log.
I am using the newest release of WiFi tether that support AP mode, as opposed to Ad-Hoc.
Any thoughts?
Working well on the latest CM6 nightlies
rmk, you should incorporate the 2.2.1 gmail into the kernel too.
Yeah, why doesn't your kernel have gmail? You're really slacking rmk.
tats_06 said:
rmk, you should incorporate the 2.2.1 gmail into the kernel too.
Click to expand...
Click to collapse
joke?
if anything the gmail could be included in the mash up
i would personally not like to see it included with a kernel, thats ridiculous
I was just thinking out loud. No need to be rude. Have a nice day.
Still really new to this whole rooting business. Do I put this on the root of my SD, boot into recovery and flash the zip?
trombone dixie said:
Still really new to this whole rooting business. Do I put this on the root of my SD, boot into recovery and flash the zip?
Click to expand...
Click to collapse
just throw it anywhere on your sd card, then boot to recovery and choose to flash a zip from the sd card, navigate to it and then flash it (can be done from rom manager too)
Works flawlessly!
Sent from my Dinc using XDA App
each time i flash the new CM6 nightly do i have to reflash this kernel?
trombone dixie said:
each time i flash the new CM6 nightly do i have to reflash this kernel?
Click to expand...
Click to collapse
yea, because the nightly will have the standard cm kernel, not with rmk40's patch
theres also a mash up that i put together than includes this kernel as well as another small patch to mount /emmc on boot
ive been keeping up pretty good with nightly roms
invisiblek said:
theres also a mash up that i put together than includes this kernel as well as another small patch to mount /emmc on boot
ive been keeping up pretty good with nightly roms
Click to expand...
Click to collapse
which one is it?
CM6 Nightly 08102010-005435 mash-up (latest):
http://www.mediafire.com/?np50kfp38mfw62g
md5sum: 85ff8c7216fd94198950e6dc4f550f27
CM6 Nightly 08072010-004339 mash-up:
http://www.mediafire.com/?i9aykqnqx34oukd
md5sum: f0e06224355e480f4146068a6e8e47b7
CM6 Nightly 08032010-002702 mash-up:
http://www.mediafire.com/?c97mm8yf3mt58pf
trombone dixie said:
which one is it?
Click to expand...
Click to collapse
the build numbers correspond to the nightly build datestamps
the one called "latest" is gong to be the latest nightly build that ive mashed up. if there are any changes in tonights build, ill do another one
invisiblek said:
the build numbers correspond to the nightly build datestamps
the one called "latest" is gong to be the latest nightly build that ive mashed up. if there are any changes in tonights build, ill do another one
Click to expand...
Click to collapse
does the latest one have the rmk kernel in it?
trombone dixie said:
does the latest one have the rmk kernel in it?
Click to expand...
Click to collapse
they all do, thats the point of the mash up
cool beans. i was curious because i downloaded the latest one last night and my camera stopped working.
Hmmm...
Well, I flashed the updated kernal and now wifi tether won't work at all. I tried the 2.2 tether built in, it gives me an error, and I tried wireless tether, and it tells me that it failed to start the wifi interface.
Also, I'm not sure if this is just me for some reason, but whenever I use usb tether or wifi tether, my data connectivity fails after 10-15 minutes and I have to restart the phone. I'm running CM6-Test 8 and I have the latest baseband as well. Any thoughts?
Rmk or anyone, do u have link to Koush's CM6 test 8 kernel that ROM comes with? I would rather not full flash to just revert back to stock kernel ...thanks.
What is this? It's an experimental ROM install setup that avoids the use of RFS entirely. The install basically pre-voodoo's your phone. If you know you want voodoo, this is faster than installing then doing voodoo, but it's a little more complicated. Not much, but be warned. It avoids the use of RFS durring install completely, so no RFS corruption to worry about.
The ROM itself is mostly untouched. The kernel is my Dragon Kernel, i9k based, so it will eat your battery (froyo only, eclair is better as we have source). I can get about 12 hours out of it. Buy a charger.
The new version is a 1-click install. It installs the kernel, reboots into it, then auto-installs the ROM. I tested it coming from JFD without issues.
These are based on voodoo5 beta code. Curio is releasing voodoo5 stable here soon, and I'll post an updated no-wipe kernel flash for that.
The ROMS are Team Whiskey Obsidian, Onyx, and Fusion. I changed the install procedure and the kernel out, the rest is as they made it. I take no credit for the ROM. Please post bugs here however, so I can make sure they are ROM bugs before letting TW know about them. I'm running the Onyx version as my daily driver. There has been some private beta testing, and they seem stable, but do have Odin handy just in case. I have installed over the top of various ROMs, but the safest way is probably to come from JFD just to be sure.
ALL THESE ROMS WIPE. NO, I WON'T CHANGE THAT.
Obsidian V5b: http://www.tabbal.net/files/Dragon-Obsidian-Installer-v1.0.zip
Onyx 4.2: http://www.tabbal.net/files/Dragon-Onyx-Installer-v1.0.zip
Fusion Final: http://www.tabbal.net/files/Dragon-Fusion-Installer-v1.0.zip
NOTE: THESE INSTALL VOODOO. ALL THE USUAL VOODOO PRECAUTIONS APPLY, IF FLASHING SOMETHING, DISABLE IT FIRST.
The latest voodoo stuff seems to play nicer and I have flashed things from clockwork without bricking, but just be warned.
Updates:
Kernel with the stable voodoo5 release. Should work with any froyo ROM, does not wipe.
http://www.tabbal.net/files/Dragon-Kernel-Voodoo-v2.0.zip
I can conform that these are indeed working. And they work beautifully. I'm evening thinking about going back to some voodoo love.
Love your work ttabbal.
"if you amplify everything, nothing is heard"
Hmmm...cool. Might have to try this with Axura 2.1.
geoffcorey said:
I can conform that these are indeed working. And they work beautifully. I'm evening thinking about going back to some voodoo love.
Love your work ttabbal.
"if you amplify everything, nothing is heard"
Click to expand...
Click to collapse
Curious! So what's the true (RFS free) Quadrant score for Vibrant?
Can we have just a kernel flash that will convert all the partitions? supercurio's i9000 flash doesn't wipe the data, it simply tars it and then untars it back once the conversion is done to each partition. Thanks for the hard work.
dasunsrule32 said:
Can we have just a kernel flash that will convert all the partitions? supercurio's i9000 flash doesn't wipe the data, it simply tars it and then untars it back once the conversion is done to each partition. Thanks for the hard work.
Click to expand...
Click to collapse
The post is about the ROMs, but yes, the kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
It's the custom kernel I reference in the OP. If you want more than about 12 hours off charger, don't install it. I'm going to look at Eugene's recently posted source to see if I can implement whatever he did to get the kernel sleeping better, but no promises. And reports are kind of mixed last time I looked at it anyway.
When Samsung gets around to releasing source, we can do better. Till then, give me a patch or don't complain about it.
ttabbal said:
The kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
Click to expand...
Click to collapse
Nice. I'll hold off trying this with Axura 2.1 until this posted, then. A battery life of 12 hours is fine in exchange for what Voodoo will provide in return.
ttabbal said:
The post is about the ROMs, but yes, the kernel update I'm about to post will convert an existing system to ext4 on reboot with the just released voodoo5 stable code.
It's the custom kernel I reference in the OP. If you want more than about 12 hours off charger, don't install it. I'm going to look at Eugene's recently posted source to see if I can implement whatever he did to get the kernel sleeping better, but no promises. And reports are kind of mixed last time I looked at it anyway.
When Samsung gets around to releasing source, we can do better. Till then, give me a patch or don't complain about it.
Click to expand...
Click to collapse
Sweet, thank you.
i flashed this on obsidian v5 beta w/ jk6 modem and it running like a champ. however, you were right about the battery life
thanks for posting it before hand. i appreciated.
Love the new kernel would u consider an overlook version? Eugene 1256 is so snappy but it corrupts data. That speed plus voodoo is crazy fast. Real 2000 + quadrant.
Sent from my GT-I9000 using XDA App
Froyo Kernel on Eclair?
ttabbal,
I did not know that a Froyo kernel could be backward compatible to Eclair. Is that the case, given that your Dragon 2.0 incorporating Voodoo 5 Stable will work with Bionix Fusion?
Please help me to understand this.
More to the point, I am on Bionix 1.9.1. Would Dragon 2.0 w/Voodoo 5 Stable work on my setup?
Thanks,
Bruce
Would love to use this, however i cant seem to get anything to install from the market no matter what i do. My TitaniumBackup restores just fine(apps only). Ive ODIN'd back to JFD twice but still nada. Ill try starting from JI6 and see if it helps.
dbacchus said:
Curious! So what's the true (RFS free) Quadrant score for Vibrant?
Click to expand...
Click to collapse
So I'm running ttabbal's latest kernel, 2.0, and just ran a quadrant. It gets 1564 as the score. Now, this isn't just from voodoo alone, he's done a few speed tweaked which will bump up the score. But it's snappy as hell.
"if you amplify everything, nothing is heard"
Just put this in my phone and its works fine I'm running axura 2.1 works fine but u will see a second boot up screen the benchmark test is not that high I got in the 2500 with the oclf inthe market download but can't do that one anymore it tells me I have one installed already but over all its smooth
Don't worry about benchmarks, they are easy to fool in a high level system like Android. Cyanogen managed to get something stupid like 10k out of Quadrant.
This setup isn't for being a benchmark queen. It's targeted at a couple things I deem important. Multitasking smoothness/performance, and a test of direct-to-ext4 install. The no-wipe voodoo kernel is really intended to be used as part of the whole, but like I said, it should work with any froyo. Note: NOT ECLAIR. If there is more demand for an eclair version, I'll consider updating my eclair ramdisk as well.
As for the market, couldn't say. It's NOT the rom/kernel though. The market is a finicky thing and sometimes just doesn't work. It's usually the server side or the app itself that has an issue though. There's also an update to Market for Froyo, it seems to be more stable. You should get it downloaded automatically after running for a while. To check, look at an app description, you should have a new tab "Related".
When I've had market problems, I fire up my Wife's G2 on a stock rom (not even root) and she does too, so it's not anything I, or anyone other than Google, can control.
Does anyone know whether the Dragon Kernel that works with any Froyo ROM available from the OP supports use of a BootAnimation.zip?
UPDATE: Thanks geoffcorey for the info!
Tried on Axura 2.1 with larger nand. Flashed, rebooted, converted with no issues and is running very well so far. Haven't been successful getting Voodoo to run before now.
Thanks to TW, ttabbal, Supercurio, et al.
epakrat75 said:
Does anyone know whether the Dragon Kernel that works with any Froyo ROM available from the OP supports use of a BootAnimation.zip?
Click to expand...
Click to collapse
yes, it supports bootanimation.zip
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Sent from my SGH-T959 using XDA App
joe.kerwin said:
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Click to expand...
Click to collapse
I did this very thing in my post #16 above yours. Go for it! Remove any other lag fixes you may have though. I had none installed so I didn't have to do that. PERFORM A NANDROID backup and optionally copy to a computer before flashing the kernel to be safe. Restoring the Nandroid backup won't restore the kernel though.
The dangers are minimal if you backup. Permanently bricking the phone is unlikely. You may soft brick but you probably won't. PLUG IN AND DON'T TURN OFF THE PHONE UNTIL THE "TW" LOGO DISAPPEARS! Around this time, you will hear a voice say voodoo has been activated.
I believe the conversion process may attempt to revert the changes it tried to make in the event of an unsuccessful conversion. If reversion is successful then you should again have access to CWM to flash back to any rom you have stored on your phone. Use nandroid to restore your data and your back to normal.
joe.kerwin said:
So I can flash this kernel over my setup on Axura 2.1 and it'll move everything over? What are the dangers? If for some reason it didn't boot up is there a way to recover without Odin?
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Heimdall... Um if you cant get into download mode perhaps you shouldn't flash experimental things.
Sent from my SGH-T959 using XDA App
I was wondering if the standard honeycomd image in the dev section is an overclocked ROM or do you have to do that? Thanks
I'm running the flash/zip install package containing Deeper Blue's 04 release of Honeycomb. It comes prepackaged with the 1.1 OC kernel.
Works great...got market running fine, all the apps I've installed run great, the B&N reader (hey, it's still a Nook!) works without issues, and to be honest the only issue I'm having is that I cannot relocate (move) apps my 8Gb SD card.
I have been running the Quadrant benchmarks with consistent results in the 1500-1600 range, and after two days have yet to experience a freeze or crash.
However you should also be aware that there are (based on a few posts I've seen) some folks who are having issues.
DeadlyDa said:
I'm running the flash/zip install package containing Deeper Blue's 04 release of Honeycomb. It comes prepackaged with the 1.1 OC kernel.
Works great...got market running fine, all the apps I've installed run great, the B&N reader (hey, it's still a Nook!) works without issues, and to be honest the only issue I'm having is that I cannot relocate (move) apps my 8Gb SD card.
I have been running the Quadrant benchmarks with consistent results in the 1500-1600 range, and after two days have yet to experience a freeze or crash.
However you should also be aware that there are (based on a few posts I've seen) some folks who are having issues.
Click to expand...
Click to collapse
Are you sure the std one comes OC'd? I'm not going to take the time to copy back the old uImage but I know that the kernel that comes with the std HC v04 is not the same as the OC kernel from dalingrin. I am able to run dalingrin's 1.1 OC kernel on v04 and get quadrant scores over 1700.
EDIT: I am running the SD boot HC. I don't know about the zip/flash version.
Well, I'm pretty sure...and the Quadrant results would seem to support the idea that it's packaged with the OC 1.1 kernel.
I followed the instructions over on AndroidCentral. Here is the link:
http://forum.androidcentral.com/bar...oneycomb-internal-memory-emmc-nook-color.html
According to the text in the thread:
"...Credit to samuelhalff for the zip, whose thread can be found here: http://forum.xda-developers.com/showthread.php?t=947071
* Note that the flashable zip uses the 1.1GHz overclock kernel by default. ..."
DeadlyDa said:
Well, I'm pretty sure...and the Quadrant results would seem to support the idea that it's packaged with the OC 1.1 kernel.
Click to expand...
Click to collapse
Agree, I edited my post above after I realized that you were talking about installing the flashable zip to the eMMC vs running off the SD card. The OP did not specify which method he was talking about.
I flashed HC onto the Nook Color, from this thread http://forum.xda-developers.com/showthread.php?t=936995, and it seems to run very slowly, sometimes not registering my touches too well. Is it that way normally or should I flash back to Nookie Froyo? If so, how?
Thanks
Because the source of the rom is a modified SDK image, there were many work arounds that had to be made to the compiled code. As such, the rom can be very shaky, and really isn't suited to be a daily use ROM.
THis image is not representative of Honeycomb; once we get the source code, devs should be able to make a much more stable version and really make an amazing ROM.
Yeah that is normal. Honeycomb at this point is basically a demo. The only fully working non-stock ROM is Froyo.
poofyhairguy said:
Yeah that is normal. Honeycomb at this point is basically a demo. The only fully working non-stock ROM is Froyo.
Click to expand...
Click to collapse
How would I go about getting Froyo instead of HC?
Hey guys I am having a.guy on here ship me his nook color after a deal we made so I will root and dual boot android.is it like just flashing normal roms which I have done on my og droid and my fascinate
Sent from my SCH-I500 using XDA Premium App
Bump plz k
Not trying to steal ur thread but would also like some info are custom roms installable on the actual nook itself or do u boot them just from the SD
Sent from my X10i using XDA App
You can run ROMs from either the SD, or from internal...
Sent from my Nexus One using XDA Premium App
HI,
A very quick summary to get you started:
The Nook color will boot first from a bootable external uSD card - so it can
be easier to 'try out' different ROMs without worrying about bricking the
device.
The internal flash memory is called 'emmc'.
You can root the stock ROMs, either the 1.01 or the 1.1 versions both are
based on Android 2.1, Eclair. You get Android market access this way and
can continue to use the stock Nook eBook app. There are rumors that
a version of Android 2.2, Froyo, with a B&N market is soon to be available.
Android 2.2, Froyo is available by ROM developers for installing on either
the internal memory or to run from external uSD cards. See for example
Nookie Froyo 6.8 in the developer section.
Android 2.3, GingerBread, is available as a pre-release from the
developers of CyanogenMOD ROMS, it is called CyanogenMOD7. They
release a new version almost every night, termed 'nightlies'. There is
a version for internal emmc or from someone else to run on uSD.
Current (3/23) versions have low frame rate hardware codec video
playback, but seem very stable otherwise. Phiremod makes a ROM
based on CM7.
Android 3.0, HoneyComb, has a very early release, based on
SDK version, not full source code.
To dual boot, see the thread in the developers section.
To overclock, see Dalingrin's kernels in the developer section.
To install new kernels and ROMs, see the ClockworkMOD (CWM) recovery thread
in the developer section.
Running a ROM from uSD can be as easy as downloading an image file,
on a PC, burning the image to uSD with "win32diskimager", then booting the
NC with the uSD inserted!
I am running CM7 nightlies and update when there are significant changes
or perhaps weekly - everything I have wanted to do has been working well.
Phiremod 5.1, based on CM7 is another good place to start.
As the NC has only one bottom button, you will also need some type
of on screen button system or button remapping to the volume buttons.
Most ROMs have something in them. I have liked Button Savior from the
market best.
Some other links:
http://nookdevs.com/Portal:NookColor
Long CM7 install description: (slightly dated now)
http://forum.xda-developers.com/showpost.php?p=11535969&postcount=151
Hope this helps.
Peter
peter thank you once i receive it i will get started on rooting and if i have any questions may i pm u also is therea freenode chanel?