Ive flashed the trinity kernel...and although it boasted high speeds.....My wifi would not work....... I then flashed the netarchy kernel and that seemed fine at first but after starting an intensive memory app it kept rebooting phone.....I seem to be having no luck with any kernels...can someone maybe suggest a kernel that just works with CM7 Rc2 and just gives me slightly better gains to make NS run a bit smoother......
Netarchy is fine. I'm using it with the latest nightly build #25. Never encountered reboots, its something else.
1. Wipe Cache & Dalvik-Cache
2. Fix Permissions
3. Flash Netarchy 1.3.0-CFS (CM7 Compatiable)
Should cause the best possible performance with the kernel.
zephiK said:
Netarchy is fine. I'm using it with the latest nightly build #25. Never encountered reboots, its something else.
1. Wipe Cache & Dalvik-Cache
2. Fix Permissions
3. Flash Netarchy 1.3.0-CFS (CM7 Compatiable)
Should cause the best possible performance with the kernel.
Click to expand...
Click to collapse
Ditto to this.
Try the CFS version (if you haven't) IIRC it *seems* to work slightly more reliably than the BFS version.
Also I assume you're not trying to OC the CPU - if you are, just leave at default if you're getting stability issues.
try ogdobbers kernel for cm7. I have version 1.3.1.5 and its smooth as butter. I have tried others but they seem unstable and I also am not a fan of overclocking my phone. Its a stock kernel with the ext4 hack that makes your phone run very fast and smooth without risks of overclocking. I haven't had a single problem with it and have been running it for about a month now.
mattdub1 said:
try ogdobbers kernel for cm7. I have version 1.3.1.5 and its smooth as butter. I have tried others but they seem unstable and I also am not a fan of overclocking my phone. Its a stock kernel with the ext4 hack that makes your phone run very fast and smooth without risks of overclocking. I haven't had a single problem with it and have been running it for about a month now.
Click to expand...
Click to collapse
All of netarchy's kernels are not OC'd by default. To OC it you have to manually do it. So what you said about kernels being OC'd is wrong. This thread has only mentioned Netarchy's kernel so I'm assuming that you thought Netarchy's kernel OC'd by default. It's automatically set at stock speeds. It includes ext4 hack as well.
Ogdoober's modified stock is just too plain for me.
What's this app that you're talking about? Was it a game?
I've only used Netarchy's so far and never had a problem. Make sure to at least try the CFS version. My phone doesn't like 1.4 ghz, but I've used it without any problems at 1.2 ghz. Right now I'm back to stock speed since I don't see any benefits to overclocking it for my usages.
zephiK said:
All of netarchy's kernels are not OC'd by default. To OC it you have to manually do it. So what you said about kernels being OC'd is wrong. This thread has only mentioned Netarchy's kernel so I'm assuming that you thought Netarchy's kernel OC'd by default. It's automatically set at stock speeds. It includes ext4 hack as well.
Ogdoober's modified stock is just too plain for me.
Click to expand...
Click to collapse
Correct. My builds enable the ability to over clock, but run at stock speeds by default. It's always your choice.
For what it's worth, I usually run at stock myself ;D
Thanks too all of you...much appreciated....coming over from the DHD and incredible S Forums was a bit daunting....but you guys are really helpful.....
Related
Can someone explain to me how kernel's work and if I flash one will I be able to get rid of it? Say flash a stock one? Someone please explain.
Make a nandroid before flashing the kernel
Darrien13 said:
Can someone explain to me how kernel's work and if I flash one will I be able to get rid of it? Say flash a stock one? Someone please explain.
Click to expand...
Click to collapse
The kernel provides the subsystem on which the OS itself operates. It is the interface to the physical hardware, handling access to physical devices as well as memory management. An optimized kernel can make a significant difference over a "vanilla" configuration.
Make a nandroid before you flash any kernels to go back easily. Otherwise you could reflash the full 2.3.3 rom.
thank you guys
If you're using CM7 and want to flash a kernel over it. You can just reflash CM7 without wiping anything and it would override your kernel with stock. CM7 includes stock kernel in it.
Yarr when I upgraded from 2.3.2 to CM7 RC1, my netarchy 1.2.5 resetted back to stock as I lost my Overclock. I just wasn't sure it was a stock kernel or a modified one specifically for CM7 that happened to not have an OC.
Aria807 said:
Yarr when I upgraded from 2.3.2 to CM7 RC1, my netarchy 1.2.5 resetted back to stock as I lost my Overclock. I just wasn't sure it was a stock kernel or a modified one specifically for CM7 that happened to not have an OC.
Click to expand...
Click to collapse
its stock. if you use SetCPU and check the info, its labeled as google.com
or about phone it says #google
Some of the user's here, myself included, have been having issues installing any ROMs/ kernels built by Faux. What I'm trying to do is pinpoint the exact cause of this and hopefully rectify the issue.
I'm currently downloading all available ROMs and will install each to determine which are flashable and which are not.
Flashing Procedures
0. Boot into CMW Recovery: External with EXT 4 support using volume down + power method
1. Wipe Data
2. Wipe Cache
3. Wipe Dalvik
4. Format /System
5. Flash ROM
6. Select Power Down from CMW Menu
7. Power on phone without wall charger plugged in
ROM List:
Bionix- Confirmed as working
EagleBlood GB- Confirmed as working
EagleBlood FR- Confirmed as working
Ultimate- Confirmed as working
Light&Sinister- Confirmed as working
Dark&Sinister- Confirmed as working
Faux AOSP-NOW WORKING!!
CM7- Confirmed as working
LG Stock- Confirmed as working
Observations:
Bionix converts /system and /data to ext3. I figured that if the issue we were having with Faux was due to format errors then I could just flash Faux over Bionix and it would boot. In testing, it seems like Faux gets further when flashed this way but still refuses to boot. Before I would only get the initial LG screen and then it would black out. Now I can get to the second LG screen with blue background but it hangs there. Will run logcat to see what is causing the freeze once I get logcat running again.
My current theory is that there is a difference in the boot.img that Faux has built for his ROM that will not boot correctly. I have the same issue with his kernels as well. They boot to the first LG splash screen and then the screen shuts off. Still struggling with my logcat issue so I'm at a standstill until that is fixed.
Development:
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Morfic's CM7 kernel. I personally believe this definitely proves that there is something in Faux's boot.img that doesn't function properly on all devices.
At Faux's suggestion, I flashed his Stock Voltage kernels in order to see if I could get the phone to boot.
Kernel:
[ Start @ 1.0 GHz, Stock Voltage, Max @ 1.2 GHz ]
(Official LGE/Tegra Voltage Values, Same as STOCK LGE Kernel)
CM7 Kernel Version 0.1.9- Boots to second LG splash screen then freezes.
CM7 Kernel Version 0.1.9 With EXT4-Booted fine but still displayed Morfic boot animation for some reason. Kernel version shows as Faux's in about phone, though.
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Mikeglongo said:
I want to flash my first ROM, any suggestions on which one is the most stable and better with battery life than the Stock ROM?
Click to expand...
Click to collapse
I didn't test any of the ROMs for quality but I would personally stick with a Froyo based ROM for now. Gingerbread is simply too buggy and missing a lot of features.
[B][U]SUCCESS!!![/U][/B]
I was finally able to get pure AOSP to boot by flashing Faux's AOSP and then flashing Trinity's CM7 kernel. I personally believe this definitely prooves that there is something in Faux's boot.img that doesn't function properly on all devices. That would explain why I am unable to flash any of his kernels, either.
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
faux123 said:
Most likely scenario is that you have a "weaker" chip which cannot handle the default OC to 1.1 and Under volting. Because of your case and a few others like you with the "weaker" chips, I have decided from next version on to include LG STOCK VOLTAGE version of my kernel as default kernel for the ROM and it's up to the users to install the OC/UV version themselves afterwards.
My solution is while in CWM, after you flashed the ROM, before you reboot, FLASH my STOCK VOLTAGE (SV) version of the kernel, then reboot. You should have NO ISSUES with STOCK VOLTAGE kernels.
So far for MT4G and G2x, I have been lucky with my phones. Both phones I can Undervolt and overclock AT the SAME TIME with very aggressive settings and remain stable with multiple runs of stress tests and benchmarks.
Click to expand...
Click to collapse
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
hiko36 said:
The only problem with that theory, Faux, is that Morfic's kernel undervolts as well. Flashing his kernel on top of your ROM is the current workaround that I've found.
Click to expand...
Click to collapse
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
faux123 said:
I don't know what Morphic is doing with his under volting, theres no source code to compare. My source is based on CM7 with my tweaks added and its available via github for inspection.
Click to expand...
Click to collapse
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
hiko36 said:
Please don't view my opinions as doubting your ability. This has just been a frustrating journey for a lot of us because we want to use your kernels/ROMs. I couldn't find anywhere where this had been addressed so I decided to take it upon myself. At this time, the two options we have are flashing your stock voltage kernel or Morfic's. Now that it's booted and running, I can say that you've built a beautiful ROM and I hope you continue to support it. Amazing work.
Click to expand...
Click to collapse
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
faux123 said:
I took NO offense of your investigation or posts. I am actually glad you did all these. You have provided me reason for using stock voltage kernel as default. I was contemplating about this change a while back, but since your post, I decided to do it so more people can try my ROM without having random reboots or issues due to UV/OC combination.
I am simply posting what I can and cannot do. I can do only what I can read and see.
Click to expand...
Click to collapse
Glad I could help and especially glad I finally figured out a way to boot your ROM. I was feeling left out haha.
Doh! He said rectify lol
Sent from my Xoom using XDA Premium App
I've been figuring out how to install custom roms and kernels lately, and was wondering if it is possible to combine an Infusion kernel with an Infused rom, and what the best procedure for that would be.
I tried Infused 2.1 and then loading the 1.8 Infusion kernel but was met with bootloops. Would it be more stable perhaps to install Infused 1.6 and Infusion 1.5.1/2 ?
And just to be sure, would I install the Infused rom, then the Infusion kernel, and then root + load rom manager backup image? Or would titanium be a better option to recover with? I have both of them backed up.
AntiCommon said:
I've been figuring out how to install custom roms and kernels lately, and was wondering if it is possible to combine an Infusion kernel with an Infused rom, and what the best procedure for that would be.
I tried Infused 2.1 and then loading the 1.8 Infusion kernel but was met with bootloops. Would it be more stable perhaps to install Infused 1.6 and Infusion 1.5.1/2 ?
And just to be sure, would I install the Infused rom, then the Infusion kernel, and then root + load rom manager backup image? Or would titanium be a better option to recover with? I have both of them backed up.
Click to expand...
Click to collapse
woah... you are WAY off on absolutely everything.
first and foremost, you need to be rooted before you can do anything that you are attempting to describe. figure out how to root in the "development" section.
as for flashing things, this guide is for a tablet, but same general process applies to the infuse: http://www.androidtablets.net/forum...m-manager-nandroid-backup-custom-kernels.html
and then as for the kernels you are referring to - as a general rule (few exceptions), you may only flash froyo kernels with froyo ROMs, and gingerbread kernels with gingerbread ROMs. you can find out what kind of ROM/kernel you are attempting to flash by reading the title of the thread, or the original post.
research everything THOROUGHLY, so that you know what you are doing before you do this!
AntiCommon said:
I've been figuring out how to install custom roms and kernels lately, and was wondering if it is possible to combine an Infusion kernel with an Infused rom, and what the best procedure for that would be.
I tried Infused 2.1 and then loading the 1.8 Infusion kernel but was met with bootloops. Would it be more stable perhaps to install Infused 1.6 and Infusion 1.5.1/2 ?
And just to be sure, would I install the Infused rom, then the Infusion kernel, and then root + load rom manager backup image? Or would titanium be a better option to recover with? I have both of them backed up.
Click to expand...
Click to collapse
You could not use the 1.8 kernel because it is a froyo kernal and infused 2.1 is gingerbread.
If you want both flash infused 2.1 and then infusion kernel 1.6 for gingerbread.
Sent from my SGH-I997 using xda premium
I've already rooted my phone, got the modified 3e recovery, and flashed the update.zip from CWM.
Now, I've downloaded infusion-GB.1.1.zip and am downloading update-infused-v2.1.0-full.zip.
Now, to my understanding I would go about installing both of these by first using Rom Manager to install update-infused-v2.1.0-full.zip (and clearing user data/cache), thus installing the GB rom. Then I would use CWM (getting to it via two volume buttons plus power button) and pressing the update option on the list.
Can anyone point me as to where I might be going wrong with my logic? If this rom and kernel are not compatible (even though they both clain to be GB) then should I instead use the Infusion 1.5.1/2 kernel and update-infused-v1.6.0-full.zip files?
Also are backups from FROYO roms incompatible with GB Rom Manager?
AntiCommon said:
I've already rooted my phone, got the modified 3e recovery, and flashed the update.zip from CWM.
Now, I've downloaded infusion-GB.1.1.zip and am downloading update-infused-v2.1.0-full.zip.
Now, to my understanding I would go about installing both of these by first using Rom Manager to install update-infused-v2.1.0-full.zip (and clearing user data/cache), thus installing the GB rom. Then I would use CWM (getting to it via two volume buttons plus power button) and pressing the update option on the list.
Can anyone point me as to where I might be going wrong with my logic? If this rom and kernel are not compatible (even though they both clain to be GB) then should I instead use the Infusion 1.5.1/2 kernel and update-infused-v1.6.0-full.zip files?
Also are backups from FROYO roms incompatible with GB Rom Manager?
Click to expand...
Click to collapse
those are compatible. no need to clear anything when installing the kernel, only the ROM - just go into red CWM, using the buttons like you said, and flash the infused ROM zip, and then the infusion kernel zip.
once you're done with that, get voltage control or setCPU from the market, and you should be able to adjust the maximum frequency to 1.6, although it may not be stable.
I managed to get it all working. I followed all the steps from this post and after doing those steps I used red CWM to update the kernel meaning that my cetCPU can OC and manage the cpu up to 1.6ghz.
Thanks all for info and help! Much appreciated
Now, while we're still here... can anyone recommend a good icon/theme changer for Infused? It'd be nice to have icons like what gtg465x has on the screens in the link I posted.
P.S. I didn't restore my apps/data with my backups simply because in his post, gtg465x said not to use them unless absolutely necessary.
i have infused 2.1 installed on my infuse and i was wondering which kernel you used to get it all working
i also wanna know how you oc ur phone
e0mandaniel said:
i have infused 2.1 installed on my infuse and i was wondering which kernel you used to get it all working
i also wanna know how you oc ur phone
Click to expand...
Click to collapse
You'll want to use the Infusion 1.0/1.1 kernel for Infused 2.1. You must use gingerbread kernels with gingerbread roms. You can download Voltage Control or Setcpu from market to be able to OC/UV. Once you've downloaded either, set your max to 1.6, you can go through the setting and set what you like as far as speed and volts. I use Voltage Control, my setting are:
Cfq scheduler ondemand Governor
200-1600mhz
200, 400, 800, 1200, 1600mhz enabled. dont use more than 5-6 settings.
UV
1600-75
1200-75
800-50
400-50
200-50
I know you can UV more than what I am using, but I dont like to push it to its max UV.
what is cfq
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
oh and any suggested rom?
e0mandaniel said:
what is cfq
---------- Post added at 05:13 AM ---------- Previous post was at 05:12 AM ----------
oh and any suggested rom?
Click to expand...
Click to collapse
Cfq is a setting for the scheduler in voltage control, I believe it means completely fair queuing. You can use the ROM infused 2.1.0 with that kernel, its what im running.
Sent from my SAMSUNG-SGH-I997 using XDA App
Nevermind i read on and on
I've been running imnuts 0115 PB&J Kernel & Eclipse v1.1 for awhile and I loved it despite a few random FC's. I upgraded to Eclipse v1.3 Monday and it seems much more stable, I decided to do a quadrant just to see, and my score was super low.. like a 1250? I think it should be much faster, so I think I tracked the issue to not everything using ext4, using terminal emulator I found that data and cache are both still rfs.
What I have been doing is using ODIN to flash debloated_deodexed_ep4d.tar.md5, then flashing imnuts kernel, and then Eclipse. Can anyone suggest a kernel that will handle the ext4 conversion prior to flashing PB&J? The phone doesn't feel slow, but if it can be faster, I'm all for it
Eclipse v1.4 + PBJ kernel is doing wonders for me.
About quadrants...cool story bro!
haha oh I have absolutely no plans to run any other kernel/ROM combo... just looking for something to do the RFS > EXT4 conversion prior to flashing PB&J kernel.
There is a version of TweakStock with PJB that auto converts to ext4. Or you could flash IMO 4.0 kernel which will auto convert to ext4, then u can flash PJB. Why r u on eclipse 1.3 anyway? 1.4 has been for a couple months now. I think u have to flash with CWM tho, not sure if u can use odin.
I just grabbed the latest release over at rootzwiki. Obviously outdated haha, time to do a full update. Thanks for the tips.
They recently updated Quadrant to be more accurate. All scores are lower than they used to be.
Sent from my SCH-I510 using xda premium
I agree
cnoevl21 said:
There is a version of TweakStock with PJB that auto converts to ext4. Or you could flash IMO 4.0 kernel which will auto convert to ext4, then u can flash PJB. Why r u on eclipse 1.3 anyway? 1.4 has been for a couple months now. I think u have to flash with CWM tho, not sure if u can use odin.
Click to expand...
Click to collapse
I used to be me but then I took an arrow to the knee!
If you do everything right with PBJ kernel overclock at 1200 with ext4 you should able to reach 2400 with quadrant. Overclocking above 1200 and achieved over 2500 quadrant...you're blessed, cause you have a "high quality silicon" chip in your phone.
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
stompysan said:
I have been having issues getting my TF101 to overclock in ICS. I have tried Codename Android, CM9, TeamEOS, and Revolver, and ALL of them I could not overclock in. I have tried SetCPU, No-Frills, and (if applicable) the built in frequency control. They all show that the maximum frequency is 1000MHz. I have no clue what is going wrong here. They all were able to gain Superuser, so that isn't the problem. Any and all help would be highly appreciated. I just have no clue what I could be doing wrong.
Click to expand...
Click to collapse
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
sidneyk said:
Antutu CPUMaster Free works for me on Revolver4_1.3.1 and Blades_meh kernel. You have to manually go into it after installing a OC kernel and set the min and max frequencies and choose a governor and there's a checkbox to tell it to set these at boot. After that it works all day everyday for me up to 1680MHz and deep sleep works, too.
Click to expand...
Click to collapse
Just tried Antutu CPU Master. Same issues. It says that my max frequency is 1000MHz.
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Tekfrog said:
Have you manually loaded a new kernel to replace the stock one? Setcpu and the like only modify settings that a kernel exposes, and the default kernel does not allow anything higher then 1000.
Click to expand...
Click to collapse
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
stompysan said:
Yes. After doing so, I also go into my settings and clear the cache and data from SetCPU, so I could set it up again. Still, I am getting max 1000MHz.
Click to expand...
Click to collapse
Which kernel are you running now?
Tekfrog said:
Which kernel are you running now?
Click to expand...
Click to collapse
Thanks for trying to help, but I have found my problem. My recovery was still borked from when I tried flashing the official one in Rom Manager. Wiped my recovery, installed the roach recovery, reflashed all of my files, and now I am good to go. I feel like a derp now. LOL
Same issue w/ OC...but wipe recovery?
Your issue sounds exactly like the one I am currently having.
I would like to try your fix...but I am not understanding how the "wipe recovery" process goes. Would you mind please explaining that in more detail? Im pretty sure it IS NOT as simple as just doing a complete cache/data wipe then flashing the recovery over itself is it?
I am:
ViperMOD Prime rooted
ClockworkRecoveryMOD installed (but I think I may have fubar'd it doing the same thing you did trying to recover stock recovery)
FROZN 1.0.9 rom w/ included Guevor kernel and NoFrills CPU app
...but none of the CPU apps will let me OC...wether I flash the kernel seperate from the ROM or use the one included w/ the ROM.
Hope you can help me.
UPDATE: apparently this inability to OC the kernel in any way is happening to those of us experiencing the CWM bootloop issue...so since the loader goes immediately to CWM it never runs the flashed kernel.
So in these forums is a thread to fix the CWM bootloop and if you follow the instructions carefully, you fix the bootloop and thus allowing the flashed kernels a chance to actually install. I chose the Roach method which you can install the code using Terminal Emulator pretty intuitively. I didnt choose the other method because I didnt want to mess w/ setting up an ADB terminal on my PC, which seemed MUCH more difficult.
So...now FINALLY
ViperMOD Prime rooted
ClockworkMOD Touch Recovery 5.8.8
FROZN 1.0.9 ROM (w/ built-in Guevor kernel @ 1.2 default) and am OCd @ 1.54 (np's at all so far, lightning fast, havent even tried 1.6 or 1.7).
Only issue so far is File Manager app crashes on startup...which isnt good because now the other file manager app I tried doesnt see my ext_SDcard...the stock File Manager did.
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
WU55 said:
I've tried using both tastyMEH and Blades using Revolver, CM9 and Android HD, and the stock ICS ROM, using Set CPU and ROM Toolbox pro to try and overclock. I've flashed the ROM first and then the Kernel, and the Kernel and then the ROM. Nothing I've done thus far has enabled me to set the CPU sliders past 1000 mhz. I know people are running these combos and getting 1.6-1.8 clocks. What am I screwing up? I'm using Clockwork Mod recovery to flash. I couldn't even get CM9 to boot.
Thanks so much in advance
Teh Wuss
Click to expand...
Click to collapse
When you flash the kernel go to the about section in android and make sure the flash was actually successful.
fwbflash said:
Please see above solution...I know it seems unrelated but it is the fix for both CWM bootloop AND being able to accept and install a flashed kernel.
If you need additional help, please ask. I am willing to share my solution in more detail to help others out.
Click to expand...
Click to collapse
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
WU55 said:
Thanks, this may be a step in the right direction. However I've tried 3 times now to flash the 5.8 touch to no avail. Everytime I reboot I end up with standard 5.5.0.4. I tried flashing with CWM. What am I doing wrong? If it helps ever since I flashed CWM, if the tablet retboots for any reason it automatically boots into CWM, and I have to cold boot into Android manually using the power and volume rocker.
Thanks again-
Teh Wuss
Click to expand...
Click to collapse
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
horndroid said:
Because your version of CWM is bad. You need to read this thread: http://forum.xda-developers.com/showthread.php?t=1530337
It's on the front page of general discussion, how did you even not see it yet.
Click to expand...
Click to collapse
Thanks, this was it, I didn't see it, because I was a noob and didn't look for it.