I in no way take credit for the work that has been done, only testing the mated files..credit goes to MASTER { Devs4Android} and eugene373 {xda-developers}
Ok, so I've been experimenting with axura 2.0.1 and this is what I got working...I'm still testing this but have been running for 4 hours now
I will not be held responsible for anything that happens to your phone as a result of your actions..
Backup all data/files/apps to be safe
Things needed*
Odin { http://forum.xda-developers.com/showpost.php?p=8863820&postcount=138 }
Eugene's 2.2 froyo odin package { http://forum.xda-developers.com/showthread.php?t=833024 }
Axura 2.0.1 rom {cant find link, heres Axura 2.0.2: http://forum.xda-developers.com/showthread.php?t=821468 }
eugene's a11/a12 kernel {link located further down in posting}
1. Odin with eugene's 2.2 froyo package
2. Boot back into recovery
3. Flash axura 2.0.1 rom (reboot)
4. Boot into recovery
5. Flash eugene's a12 "or" a11 kernel(reboot)
6.boot into recovery
7. set up lag fix, tweaks,etc to your desired settings..
8. reboot, it will go to a menu, i suggest using the first option to backup and restore!!
11.DONE!! Enjoy....
***UPDATE***
Ok, so i paired Axura 2.0.3 with #805 kernel and it runs flawlessly!!!
same method as before just a different kernal.. so for future reference when Axura 2.0.3 becomes available to everyone look back for this post{BOOKMARK ME!!]
UPDATE!!!
Axura 2.0.1 rom is the less glitchy..{just released 2.0.4 "early" with the fixes applied, flashing now}
the best kernel available as of now is Eugene's a12/a11 oc/uv!!! has all available lag fixes, tweaks, and misc stuff built into the recovery, and the voltage app allows adjustment in individual speeds!!
100mhz
200mhz
400mhz
800mhz
1000mhz
1200mhz
http://eb-productions.proboards.com/index.cgi?action=display&board=samsungsgs&thread=28&page=1
So has anybody tried this yet? I'm gonna start on the newly "early"release of Axura 2.0.3...
Sent from my SGH-T959 using XDA App
htcfresh said:
So has anybody tried this yet? I'm gonna start on the newly "early"release of Axura 2.0.3...
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It just drives me nuts that these kernels add the I9000 splash screen - but the 800 series, on up to 805 if tweaked correctly work great.
htcfresh said:
I'm still tedting this but have been ring for 4 hours now
Click to expand...
Click to collapse
Not trying to be mean but what are you trying to say?
Works exactly as described!!
Confirmed working on Axura 2.0.2, using the OP exact instructions... Quadrant Score 2072, Linpack 16.777, the I9000 splash screen doesn't bother me, but to each his (or her) own.
Thanks for posting this... works beautifully!
~m00n
i think axura 2.0.1 runs pretty quick already, but I tried this out for fun. It runs even quicker now =D no problems so far.
@mesajoejoe
My bad, I meant to say "I've been running this for 4 hours"...
Sent from my SGH-T959 using XDA App
Axura 2.0.3 work in progress..
No problem peoples...my goal was to find a oc 1.2 ghz kernel that will work with axura roms...trial and error!
i have access to the early releases and will be working on Axura 2.0.3 so hopefully i will have something ready when it hits the public..thanks for the feedback people!!
Sent from my bad a$$ galaxy s...please excuse my swype
htcfresh said:
No problem peoples...my goal was to find a oc 1.2 ghz kernel that will work with axura roms...trial and error!
i have access to the early releases and will be working on Axura 2.0.3 so hopefully i will have something ready when it hits the public..thanks for the feedback people!!
Sent from my bad a$$ galaxy s...please excuse my swype
Click to expand...
Click to collapse
It would be awesome to get Eugene's latest kernel (#106) working on Axura. Eugene stated that it should work on other roms as long as you include the zImage (duh) and the /system/init.rc. Tried doing it with a flashable zip as well as flashing just the kernel and then using adb to push the init.rc but still couldn't get it to boot. Maybe a much more talented individual could get this set up working.
Is it possible to flash axura 2.03 and flash the kernel by using CW? I believe kernels can be induvidually flashed right without odin correct? Thanks.
htcfresh said:
1. Odin with eugene's 2.2 froyo package
2. Boot back into recovery
3. Flash axura 2.0.1 rom (reboot)
4. Boot into recovery
5. Flash eugene's#802 kernel(reboot)
6. Download oclf 2.0 from market
7. Install ext 2 tools
8. Restore boot image
9. Install 2.2+ lag fix(phone will reboot)
10. Change scheduler to your preference (not necessary)
11.DONE!! Enjoy....
Linpack average... 16.5
Quadrant average..2019
Click to expand...
Click to collapse
So I'm already on Axura, so I can just jump right to the flashing of eugenes kernel through cw recovery, correct? Don't get why I'd have to odin eugenes froyo package. I hate odin if you haven't guessed by now lol.
Also, which one is supposed to be better? 802 vs. 805
joe.kerwin said:
So I'm already on Axura, so I can just jump right to the flashing of eugenes kernel through cw recovery, correct? Don't get why I'd have to odin eugenes froyo package. I hate odin if you haven't guessed by now lol.
Also, which one is supposed to be better? 802 vs. 805
Click to expand...
Click to collapse
Yeh I hate odin also. I believe we should be able to flash in cw. I dont see why one would have to flash eugenes rom also. Im curious. Anyone care to expound. Thanks!
Correct...if your already on Axura your fine, except if you have any voodoo lag fix our oclf lag fix..you would have to remove them first...I personally like #802..but to each his own
Sent from my SGH-T959 using XDA App
jcc332006 said:
Is it possible to flash axura 2.03 and flash the kernel by using CW? I believe kernels can be induvidually flashed right without odin correct? Thanks.
Click to expand...
Click to collapse
Yes as long as it is a flashable .zip
Kernel and not made for odin..but thus far out of all the kernels eugene's #80x kernels are the only ones that work and are cwm flashable..
Sent from my bad a$$ galaxy s..please excuse my swype...
After I install the ext2 files, it says I already have a lagfix installed. I followed your procedure correctly but with Axura 2.0.3 and kernel #802.
I had voodoo installed before but I flashed disable-lagfix.zip before I did any of this.
Xencer said:
After I install the ext2 files, it says I already have a lagfix installed. I followed your procedure correctly but with Axura 2.0.3 and kernel #802.
I had voodoo installed before but I flashed disable-lagfix.zip before I did any of this.
Click to expand...
Click to collapse
did you restore boot image!?! if so i dont have an answer, other then odin and reinstall axura rom and this time use the newest working kernel, build a5 #120..links in the first post now..
Im getting reboot issues with the a5#120 kernel anyone else?
shaw89614 said:
Im getting reboot issues with the a5#120 kernel anyone else?
Click to expand...
Click to collapse
What kind of reboot issues? Were you running a rom other then axura when you flashed 2.0.3? Best bet is to odin and do it all fresh and only flash one at so time with reboots between flashes...and disable any lag fixes!!
Sent from my SGH-T959 using XDA App
How's the battery life on this?
802 gave good battery life with 2.0.3 for me
Hi Guys,
I just got my Captivate couple days ago. I were able to unlock, root, get a new ROM (Cognition v2.3b8) and install some apps. I'm looking to get a new kernel for the ROM. How would I go about flashing it to a different Kernel like SpeedMod K12I ? Thanks.
Sgs kernel flasher app in market
To be safe always disable lagfix prior. App is very easy to user and quick
Sent from me
adrian18w said:
Hi Guys,
I just got my Captivate couple days ago. I were able to unlock, root, get a new ROM (Cognition v2.3b8) and install some apps. I'm looking to get a new kernel for the ROM. How would I go about flashing it to a different Kernel like SpeedMod K12I ? Thanks.
Click to expand...
Click to collapse
I am a noob here. But I am wondering what are/is the benefits/risk of replacing the kernel that comes with Cog v2.3b8 with another. I recently flashed Cog v2.3b8 from stock (batch 1006), and find this is pretty much as stable as stock. Only issue is with GPS (which was hit and miss on stock). So do the benefits of replacing the kernel in Cog v2.3b8 outweigh the risks?
Thankshttp://media.xda-developers.com/images/icons/icon7.gif
Well kernels have different features and abilities in them. It depends what you want from your kernel. Some might support BLN while others will have OC/UC or just OC. Various combinations of options. You just need to make sure that the kernel/ROM/modem are from the same family, etc. I9000 or Captivate. If you flash a i9000 kernel into a Captivate ROM you might have issues.
Cog v2.3b8 is a Captivate ROM I believe. You can flash Kernels which are for it.
cog runs fine with an i9000 kernel so long as you also use an i9000 modem. i can't run the i9000 roms because of service drops but this set-up is still very good.
Kernel flash
adrian18w said:
Hi Guys,
I just got my Captivate couple days ago. I were able to unlock, root, get a new ROM (Cognition v2.3b8) and install some apps. I'm looking to get a new kernel for the ROM. How would I go about flashing it to a different Kernel like SpeedMod K12I ? Thanks.
Click to expand...
Click to collapse
If you want to install a new kernel over the existing kernel,
1. Download the Kernel from http://forum.xda-developers.com/showthread.php?t=893880
2. Go to CWM recovery. (directly or through ROM Manager)
3. Choose the zip from SD
4. Flash and Reboot.
Make sure that there is atleast one boot after the ROM is installed.
To confirm,
check Kernel Version in Settings-> About Phone
You should see something like
[email protected]#116
Kernel benefits/risks
jperiod said:
I am a noob here. But I am wondering what are/is the benefits/risk of replacing the kernel that comes with Cog v2.3b8 with another. I recently flashed Cog v2.3b8 from stock (batch 1006), and find this is pretty much as stable as stock. Only issue is with GPS (which was hit and miss on stock). So do the benefits of replacing the kernel in Cog v2.3b8 outweigh the risks?
Thankshttp://media.xda-developers.com/images/icons/icon7.gif
Click to expand...
Click to collapse
Well each kernel has it's own benefits.
For instance, Speedmod uses sztupy's Universal Lagfix unlike other Kernels that use Vodoo Lagfix.
The main differences would be in the speed and battery. Samsung uses 250hz (as default), firebird kernel uses 300Hz and Speedmod uses 500Hz. Doesn't change battery consumption much but provides more smoothness.
Then the RAM Available. It varies from Kernel to Kernel from 300-350MB.
Cappy Kernels are for Captivate Only because of reorientation fixes and button mapping.
Hope this helps
Hi guys, another newbie question from me
Correct me if I'm wrong, but if I flash a v2.1 SBF, then the kernel will also be flashed to v2.1 as well right?
Ok, so we also have a variety of custom roms. Some are based on v2.2 kernel, while some are for v2.1.
Now my question is, I know that CM7 is based on v2.2 kernel. Currently, I'm using a stock v2.1 SBF, so the kernel is also v2.1 as well. I want to know that despite this, can I still flash CM7 custom rom (which again is based on v2.2 kernel) on my phone? Or can I only flash a CM6 custom rom that is based on v2.1 kernel?
chaoscreater said:
Hi guys, another newbie question from me
Correct me if I'm wrong, but if I flash a v2.1 SBF, then the kernel will also be flashed to v2.1 as well right?
Ok, so we also have a variety of custom roms. Some are based on v2.2 kernel, while some are for v2.1.
Now my question is, I know that CM7 is based on v2.2 kernel. Currently, I'm using a stock v2.1 SBF, so the kernel is also v2.1 as well. I want to know that despite this, can I still flash CM7 custom rom (which again is based on v2.2 kernel) on my phone? Or can I only flash a CM6 custom rom that is based on v2.1 kernel?
Click to expand...
Click to collapse
Are you rooted on stock 2.1? Even CM6 is on the 2.2.1 kernel, so you would have to flash the 2.2 Vulnerable Recovery and then reroot, if I'm not mistaken.
Sent from my Milestone using XDA Premium App
i think you can flash CM7 (if you editing rom)
XT720 use milestone's rom on 29 kernel
chaoscreater said:
Hi guys, another newbie question from me
Correct me if I'm wrong, but if I flash a v2.1 SBF, then the kernel will also be flashed to v2.1 as well right?
Ok, so we also have a variety of custom roms. Some are based on v2.2 kernel, while some are for v2.1.
Now my question is, I know that CM7 is based on v2.2 kernel. Currently, I'm using a stock v2.1 SBF, so the kernel is also v2.1 as well. I want to know that despite this, can I still flash CM7 custom rom (which again is based on v2.2 kernel) on my phone? Or can I only flash a CM6 custom rom that is based on v2.1 kernel?
Click to expand...
Click to collapse
your kernel will update after install the CM7, because CM7 contain the new 2.2 kernel, you can flash CM7 directly, but remember to flash the BPSW update.
skadude66 said:
Are you rooted on stock 2.1? Even CM6 is on the 2.2.1 kernel, so you would have to flash the 2.2 Vulnerable Recovery and then reroot, if I'm not mistaken.
Sent from my Milestone using XDA Premium App
Click to expand...
Click to collapse
Yes i'm rooted on stock 2.1. Initially, I couldn't get into OpenRecovery after flashing the stock 2.1 SBF, whereas I could when I was on stock 2.2. I did some searching and found this:
http://android.doshaska.net/rootable
and flashed the vulnerable recovery and now everything works fine. I got my phone rooted and currently using the TelusLite v5.2 for Eclair. However, i'm not sure if the vulnerable recovery is the 2.2 or not, i'm guessing it is?
Charles_l said:
your kernel will update after install the CM7, because CM7 contain the new 2.2 kernel, you can flash CM7 directly, but remember to flash the BPSW update.
Click to expand...
Click to collapse
Ok now i'm confused. From what I know, the bootloader for Motorola devices like the Milestone is locked. Therefore, we can't properly flash a custom rom on the phone, and we can't flash a different kernel either (which is why if you try to change one of the settings that relate to the kernel in OpenRecovery, you'll brick your phone).
So I've always thought that only flashing a stock SBF will change the kernel, and that the custom roms will rely on the stock kernel, hence why there're custom roms for different Android versions, like Eclair and Froyo? So ya i'm a little bit confused here.
Also, what's the BPSW update? What does it stand for and is that included in the CM7 custom rom topic? I couldn't find it and Google didn't find anything either.....
chaoscreater said:
Yes i'm rooted on stock 2.1. Initially, I couldn't get into OpenRecovery after flashing the stock 2.1 SBF, whereas I could when I was on stock 2.2. I did some searching and found this:
http://android.doshaska.net/rootable
and flashed the vulnerable recovery and now everything works fine. I got my phone rooted and currently using the TelusLite v5.2 for Eclair. However, i'm not sure if the vulnerable recovery is the 2.2 or not, i'm guessing it is?
Ok now i'm confused. From what I know, the bootloader for Motorola devices like the Milestone is locked. Therefore, we can't properly flash a custom rom on the phone, and we can't flash a different kernel either (which is why if you try to change one of the settings that relate to the kernel in OpenRecovery, you'll brick your phone).
So I've always thought that only flashing a stock SBF will change the kernel, and that the custom roms will rely on the stock kernel, hence why there're custom roms for different Android versions, like Eclair and Froyo? So ya i'm a little bit confused here.
Also, what's the BPSW update? What does it stand for and is that included in the CM7 custom rom topic? I couldn't find it and Google didn't find anything either.....
Oh and one more thing, I think this is a bug so can someone look into it? The statusbar hides itself and to unhide it, you have to ADWSettings (press the Menu capacitive button, in between the back and home button, and then click More, then choose ADWSettings).
Then, click on System preferences, and the first option is "Hide Statusbar".
The problem is, that option is by default already un-ticked, which means it does NOT hide your statusbar. And yet, the statusbar is hidden........the only way to fix this is to enable the option so that it actually hides it, then close everything and go back to your desktop, and then open ADWSettings again and then un-tick it. This will fix it and make the statusbar appear.
However, if you move your shortcuts/icons on the desktop around, or if you move it to the Trash, then this will undo the statusbar change and will make it hide again. So then you'll have to do this constantly, so I suggest you guys make sure your desktop shortcuts are fully configured, and then make the statusbar change at the end.
Click to expand...
Click to collapse
Yes, VR is based on 2.2.
sorry, what does VR stand for? And I still don't understand it, can you please explain?
chaoscreater said:
sorry, what does VR stand for? And I still don't understand it, can you please explain?
Click to expand...
Click to collapse
VR is vulnerable recovery, it's what is on android.doshaska.net/rootable
ahh I see......but I still don't understand the part about the kernel.
I thought that every new firmware version update will use a newer version of the kernel? If yes, then how can custom roms like CM7 that requires kernel for v2.2, be installed on stock v2.1? Unless both the v2.1 and v2.2 stock SBF use the same kernel version? But then again, why are there specific roms for Eclair and Froyo? If you look at this topic here:
http://forum.xda-developers.com/showthread.php?t=966812
the OP says that some of those roms might not work because of different kernels. So it leads me to believe that if you're on stock v2.1, then the kernel is different than if you're on stock v2.2, hence why the custom roms you can install are separated by Eclair and Froyo......
And lastly, if custom roms like CM7 will install the v2.2 kernel, shouldn't that require the bootloader to be unlocked?? I thought we can't change the kernel yet? I'm confused....
chaoscreater said:
ahh I see......but I still don't understand the part about the kernel.
I thought that every new firmware version update will use a newer version of the kernel? If yes, then how can custom roms like CM7 that requires kernel for v2.2, be installed on stock v2.1? Unless both the v2.1 and v2.2 stock SBF use the same kernel version? But then again, why are there specific roms for Eclair and Froyo? If you look at this topic here:
http://forum.xda-developers.com/showthread.php?t=966812
the OP says that some of those roms might not work because of different kernels. So it leads me to believe that if you're on stock v2.1, then the kernel is different than if you're on stock v2.2, hence why the custom roms you can install are separated by Eclair and Froyo......
And lastly, if custom roms like CM7 will install the v2.2 kernel, shouldn't that require the bootloader to be unlocked?? I thought we can't change the kernel yet? I'm confused....
Click to expand...
Click to collapse
What you're confusing is that the version of android such as 2.2 is NOT the Kernel. The only way for you to change the kernel per se is to flash an sbf such as the Eclair or Froyo sbf. These are signed by Motorola and have holes in the code that have been exploited so we can flash Custom ROMs. The only things that we can do is flash a custom ROM or flash an SBF through RSD Lite. Kernels cannot be changed otherwise.
Sent from my Milestone using XDA Premium App
ya I understand that, and that's exactly the reason why i'm confused.....
If you flash a v2.1 SBF, then your Android version is v2.1 (Eclair).
If you flash a v2.2 SBF, then your Android version is v2.2 (Froyo).
Now, the problem is that custom roms like CM7 requires the kernel for Froyo. In other words, you have to flash a stock v2.2 SBF first, so that your phone will be running Froyo and that the kernel will obviously be for Froyo as well.
So what I don't understand is, I'm using Eclair right now because I flashed a New Zealand v2.1 SBF. The Android version I'm running on is Eclair, and the kernel version should be for Eclair as well.
Then why is it that you guys said I can still flash CM7, which requires the kernel for Froyo?
chaoscreater said:
ya I understand that, and that's exactly the reason why i'm confused.....
If you flash a v2.1 SBF, then your Android version is v2.1 (Eclair).
If you flash a v2.2 SBF, then your Android version is v2.2 (Froyo).
Now, the problem is that custom roms like CM7 requires the kernel for Froyo. In other words, you have to flash a stock v2.2 SBF first, so that your phone will be running Froyo and that the kernel will obviously be for Froyo as well.
So what I don't understand is, I'm using Eclair right now because I flashed a New Zealand v2.1 SBF. The Android version I'm running on is Eclair, and the kernel version should be for Eclair as well.
Then why is it that you guys said I can still flash CM7, which requires the kernel for Froyo?
Click to expand...
Click to collapse
I have never tried flashing CM7 from Eclair, so I can't tell you that it will work. I upgraded to stock Froyo on Telus the day it came out and got frustrated with it and rooted the same day.
Sent from my Milestone using XDA Premium App
Hmm well I'd flash to stock Froyo as well, then I wouldn't have a problem installing CM7 because I know it'll definitely work. Except that the kernel for Froyo doesn't work well on my Milestone. Many people have problems with the Froyo kernel, mostly to do with connection problems like wifi or 3g.
I've had problem with my wifi where it connects to my router, but isn't sending/receiving any data. Either that, or it works for 5 mins and then disconnects itself afterwards.
Many people suggested to flash back to stock Eclair, so I did and my wifi works awesome right now and never had a connection problem yet. Currently, i'm using the TelusLite v5.2 custom rom for Eclair, and it works great but I wanna try out custom roms for Cyanogen Mod, like CM6 or CM7.
From what I know, CM6 is for Eclair because it uses the Eclair kernel. Whereas CM7 is for Froyo as it uses the Froyo kernel. However, I think the latest version of CM6 also uses the Froyo kernel, as somebody mentioned it in the CM7 topic somewhere.......so ya I'm pretty sure you CAN'T install CM7 on Eclair since the kernel requirement is different.
And yet, i'm confused with the answer in the 4th post:
http://forum.xda-developers.com/showpost.php?p=16834339&postcount=4
chaoscreater said:
Hmm well I'd flash to stock Froyo as well, then I wouldn't have a problem installing CM7 because I know it'll definitely work. Except that the kernel for Froyo doesn't work well on my Milestone. Many people have problems with the Froyo kernel, mostly to do with connection problems like wifi or 3g.
I've had problem with my wifi where it connects to my router, but isn't sending/receiving any data. Either that, or it works for 5 mins and then disconnects itself afterwards.
Many people suggested to flash back to stock Eclair, so I did and my wifi works awesome right now and never had a connection problem yet. Currently, i'm using the TelusLite v5.2 custom rom for Eclair, and it works great but I wanna try out custom roms for Cyanogen Mod, like CM6 or CM7.
From what I know, CM6 is for Eclair because it uses the Eclair kernel. Whereas CM7 is for Froyo as it uses the Froyo kernel. However, I think the latest version of CM6 also uses the Froyo kernel, as somebody mentioned it in the CM7 topic somewhere.......so ya I'm pretty sure you CAN'T install CM7 on Eclair since the kernel requirement is different.
And yet, i'm confused with the answer in the 4th post:
http://forum.xda-developers.com/showpost.php?p=16834339&postcount=4
Click to expand...
Click to collapse
I haven't heard of Eclair to CM7 directly. Every ROM except for the Eclair roms like you are running now are ALL based on Froyo. GB is based on the Froyo kernel, but is a gingerbread port.
Sent from my Milestone using XDA Premium App
yup I know. After all, there is no official Gingerbread support for Milestone (yet), that's why we don't have a v2.3 SBF to flash (therefore not able to get the kernel for Gingerbread).
But ya i'm pretty sure I got this sorted, after all the OP did specifically say that some roms might not work due to different kernels, which is mentioned in this topic here:
http://forum.xda-developers.com/showthread.php?t=966812
so ya you either have to flash the stock v2.1 SBF or v2.2 SBF in order to install specific custom roms that you want, depending on what kernel they're based on, right?
Oh well, guess i'll just stay with TelusLite v5.2 for now. It's pretty fast and stable so I guess that's good enough.
chaoscreater said:
yup I know. After all, there is no official Gingerbread support for Milestone (yet), that's why we don't have a v2.3 SBF to flash (therefore not able to get the kernel for Gingerbread).
But ya i'm pretty sure I got this sorted, after all the OP did specifically say that some roms might not work due to different kernels, which is mentioned in this topic here:
http://forum.xda-developers.com/showthread.php?t=966812
so ya you either have to flash the stock v2.1 SBF or v2.2 SBF in order to install specific custom roms that you want, depending on what kernel they're based on, right?
Oh well, guess i'll just stay with TelusLite v5.2 for now. It's pretty fast and stable so I guess that's good enough.
Click to expand...
Click to collapse
The issue is that TelusLite is no longer updated. Any issues that you will encounter may not be fixed. I've always found RSD Lite to be finicky, but you can always flash the 2.2 VR and try other ROMs and if you aren't happy, you can reflash the 2.1 and go back to TelusLite.
Many options for you to try out!
Sent from my Milestone using XDA Premium App
ya it seems like it. But the latest build (v5.2) was updated on July 2011 so it's only a month old? So ya not too bad. I haven't had any issues with it, and all the stuff that I use my phone for works fine on this rom so i'm pretty happy with it.
I only wanted to try out CM7 because it looks nice and that many of my friends recommended me to use it. But ur right, there're still other great roms out there that I can test out.
RSD Lite works well for me, never had a problem with it so i'm pretty happy. At least the flashing and rooting process on Android is fairly easy. Whereas on Windows Mobile or on Maemo (when I still had my Nokia N900), it was a pain in the ass, especially that the flasher program for Maemo doesn't work on Windows 7
Anyway, thanks A LOT for your help. You've helped me in the other topic I posted as well, I really appreciate you taking the time to answer my newbie questions
chaoscreater said:
ya it seems like it. But the latest build (v5.2) was updated on July 2011 so it's only a month old? So ya not too bad. I haven't had any issues with it, and all the stuff that I use my phone for works fine on this rom so i'm pretty happy with it.
I only wanted to try out CM7 because it looks nice and that many of my friends recommended me to use it. But ur right, there're still other great roms out there that I can test out.
RSD Lite works well for me, never had a problem with it so i'm pretty happy. At least the flashing and rooting process on Android is fairly easy. Whereas on Windows Mobile or on Maemo (when I still had my Nokia N900), it was a pain in the ass, especially that the flasher program for Maemo doesn't work on Windows 7
Anyway, thanks A LOT for your help. You've helped me in the other topic I posted as well, I really appreciate you taking the time to answer my newbie questions
Click to expand...
Click to collapse
Anytime! Let me know if you need anything else
Sent from my Milestone using XDA Premium App
chaoscreater said:
Hmm well I'd flash to stock Froyo as well, then I wouldn't have a problem installing CM7 because I know it'll definitely work. Except that the kernel for Froyo doesn't work well on my Milestone. Many people have problems with the Froyo kernel, mostly to do with connection problems like wifi or 3g.
I've had problem with my wifi where it connects to my router, but isn't sending/receiving any data. Either that, or it works for 5 mins and then disconnects itself afterwards.
Many people suggested to flash back to stock Eclair, so I did and my wifi works awesome right now and never had a connection problem yet. Currently, i'm using the TelusLite v5.2 custom rom for Eclair, and it works great but I wanna try out custom roms for Cyanogen Mod, like CM6 or CM7.
From what I know, CM6 is for Eclair because it uses the Eclair kernel. Whereas CM7 is for Froyo as it uses the Froyo kernel. However, I think the latest version of CM6 also uses the Froyo kernel, as somebody mentioned it in the CM7 topic somewhere.......so ya I'm pretty sure you CAN'T install CM7 on Eclair since the kernel requirement is different.
And yet, i'm confused with the answer in the 4th post:
http://forum.xda-developers.com/showpost.php?p=16834339&postcount=4
Click to expand...
Click to collapse
Well, you can open a CM7 zip package, you should see a file named "boot.img", that is the kernel, came from the stock Froyo SBF, so that it can pass the bootlooder checking, and it will replace the old kernel during the CM7 installation. That is why the kernel will update to the stock 2.2 kernel after you installed the CM7.
Charles_l said:
Well, you can open a CM7 zip package, you should see a file named "boot.img", that is the kernel, came from the stock Froyo SBF, so that it can pass the bootlooder checking, and it will replace the old kernel during the CM7 installation. That is why the kernel will update to the stock 2.2 kernel after you installed the CM7.
Click to expand...
Click to collapse
I see......in that case, can I replace the boot.img with the one for Eclair? I.e, use the 2.1 kernel instead of 2.2? I'm pretty sure this isn't possible since the custom rom is made to work with that particular kernel version, but maybe it does work?
Hi all,
I'm new to android and some things I do not understand, for example I have the galaxy captivate with the following characteristic:
Rom Android 2.3.4 I897UCKH3
boog_kh3_kernel3
su-2.3.2-efgh-bin-signed.zip
I updated my cellphone using these files, and all works fine but I wanted install a new kernel the last talondev, but after install it I think that my sgs is on soft bricked, displays the logo of AT & T and then starts "loading talon...", but then restarts.
This kernel can be used with the rom? it is compatible? or What should I do to choose a kernel?
Best regards
Talon is I9000 port kernel you are using native I897 rom. Use Samurai, Corn kernel or Boog's kernel. Actually Im not sure there is a corn or samurai kernel for KH3. I know they have it for KJ roms.
I have to find kernels for KH3, right?
Thanks
Correct. Or update to a newer leak like KJ3 as a example.
And I can change to a custom rom? or that such the cm7 rom?
I talk to do this to exit the soft brick and have it back.
thanks
CM7 has its own special instructions. I haven't kept up with it so go to their thread and read. But ya you can change to custom roms like Fusion IX, Fasty and others that are based of a newer firmware version.
RanuTo said:
And I can change to a custom rom? or that such the cm7 rom?
I talk to do this to exit the soft brick and have it back.
thanks
Click to expand...
Click to collapse
You need to flash back to boog kernel. If this does not work it is best you re-flash to stock KH3 with the one-click solution here. http://forum.xda-developers.com/showthread.php?t=1300843
Choose the one WITHOUT bootloaders since you already have those on the phone. It is safer that way.
Regarding CM7 ROMs. You must know they are completely different system compared to the normal Captivate ROMs. Read this thread before flashing:
http://forum.xda-developers.com/showthread.php?t=978150
Don't get me wrong. THEY ARE VERY GOOD CUSTOM ROMs...absolutely. But you cannot mix and match.....Follow CM7 instructions strictly.
thanks for the replies, I will be reading information about their opinions.
thank you very much , I'll let you know the results.
chappatti said:
You need to flash back to boog kernel. If this does not work it is best you re-flash to stock KH3 with the one-click solution here. http://forum.xda-developers.com/showthread.php?t=1300843
Choose the one WITHOUT bootloaders since you already have those on the phone. It is safer that way.
Regarding CM7 ROMs. You must know they are completely different system compared to the normal Captivate ROMs. Read this thread before flashing:
http://forum.xda-developers.com/showthread.php?t=978150
Don't get me wrong. THEY ARE VERY GOOD CUSTOM ROMs...absolutely. But you cannot mix and match.....Follow CM7 instructions strictly.
Click to expand...
Click to collapse
Why would you send him to the nightly page and not the 7.1 stable current nightlys are a bit broken.
I am not amused by your phones performance