I have eagles blood installed and am trying to install the faux kernel but everytime I do it reboots and just stays at a black screen - It tried UV and reg versions - I know the phone can oc it was running tamoguchi or whatever (the japanese named one lol off the tracphone image) with a oc kernel...what am I doing wrong - I clear cache, clear davlik apply zip and reboot and nada..am I just not waiting long enough?
glenroebuck said:
I have eagles blood installed and am trying to install the faux kernel but everytime I do it reboots and just stays at a black screen - It tried UV and reg versions - I know the phone can oc it was running tamoguchi or whatever (the japanese named one lol off the tracphone image) with a oc kernel...what am I doing wrong - I clear cache, clear davlik apply zip and reboot and nada..am I just not waiting long enough?
Click to expand...
Click to collapse
EB is based on an older rom. The newest faux kernels only work on the latest CM nightlies, so you need to flash an older version of the kernel.
omg ty it was driving me crazy
faux's kernels
all of faux's kernels seem to have a problem with every rom either power drain when off over night or boot loop crash
there are 2 kernels by faux one for cm7 and one for ota 2.3.3/2.2, dont download the kernel that is for cm7, download the other kernel that is for ota 2,3,3 (ver 0.4 or something like that )
faux's kernels
yes i have the right ones no matter the combo i get my battery drained all the way over night with the phone off
hmm weird I just put on 4.3 on top of Eagles blood 2.3.7 - the uv 1.53 Ghz kernel...and wow..I landed 4th fastest p999 on antutu...7517 sweet
I recently rooted my TF101 using Razorclaw root and installed clockwerk recovery. I have a B70 tablet that wont use NVflash so im assuming i have the SBK2. I tried to install a kernel and kept booting with a very distorted screen and i couldnt do anything. My question is: is my TF bricked? Does flashing a custom kernel not work on the TFs with the newer SBK's or can my processor not handle being overclocked that high. Because i believe it was a 1.8Ghz kernel that i flashed. I fixed it by pulling out the stock kernel from a rom and flashed that in recovery. Just wondering what's going on here.
Could be your TF not able to handle the 1.8Ghz. Did you install any app to manage
the frequencies, ect.... I use SetCPU but there's other apps that does it.
Make sure it's set to about 1Ghz first before flashing the OC kernel.
After which you can increase it slowly
Well it wouldnt even boot to the lock screen and the screen was all distorted. I dont know if its set at 1.8 right when it boots or lower. or maybe a bad download. but i didnt even have a chance to unlock the thing.
Are you still on the stock but rooted ROM? If so it's probably not compatible with a OC kernel.
im not sure what the problem is. because now, i tried to do custom roms again and im on revolver with a 1.6Ghz overclock and having no problems at all.
kernel flashing problems
I have had the same thing with a couple different kernels. I found some various kernel source trees on git for TF101 and tried rebuilding them and cross-compiling on my Ubuntu system. Most of the time it works fine but there were a couple that when I tried to flash them all I got was a screen full of snowy colored lines, kind of like the snow on an old color TV and could hear some weird 'spacey' sounds coming from it but it wouldn't boot any further. I don't know if these sources were for projects working on ICS or if they were trying to modify source from some other device or what the deal was, but those 2 wouldn't boot.
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.
Few questions after installing Revolver 4.2...
I try to install Guevor's 22.6 kernel, it goes through the process and it says complete. I reboot and the kernel still says 2.6.39.4 android @mars. What am I doing wrong?
Also when I tried to install the kernel through Revolver Parts, it doesn't download the file into sdcard/Downloads. I couldn't find it anywhere so I had to download it manually.
Also, am I able to boot my system so it automatically loads the rom? Everytime I boot it automatically loads into CWM and you have to manually get it to boot. Anyway around this?
Finally, can someone explain overclocking real quick to me? Can I overclock on this android @ mars kernel? (If guevor's works, I'd do it on that). I thought I could go on SetCPU and just change the clock speed to whatever I wanted (1.5GHZ for example). Instead there are two filters, one that is maxed at 1GHz and the other at 200MHz. What would the equivalent of 1.5GHz to set both bars accordingly?
I would REALLY appreciate if someone could help me out, total NOOB lol.
short answers:
its not an overclockable kernel then
and
if you can Nv Flash a rom and recovery then its probably the easiest way to resolve the cwr loop.
if you used rom manager then i would advise not doing that ever ever again on the Tf. (just a guess)
Read me and if you get it resolved with Peri then remember to thank Thing of Doom.
scottyf79 said:
short answers:
its not an overclockable kernel then
and
if you can Nv Flash a rom and recovery then its probably the easiest way to resolve the cwr loop.
if you used rom manager then i would advise not doing that ever ever again on the Tf. (just a guess)
Read me and if you get it resolved with Peri then remember to thank Thing of Doom.
Click to expand...
Click to collapse
I just read that Guevor's 22.6 is a stable kernel. Even if I don't overclock it, it should replace the stock kernel no?
And yeah I used ROM manager to install the latest version, why would it mess it up? What is "Nv Flash"?
Okay got everything working. Transformer boots perfectly, new recovery works a lot better, installed the kernel and have it clocked to 1.5GHz
Thanks again!
BTW- Uninstalled ROM Manager :silly:
Hello Everyone
Given I am new to flashing ROMs and stuff I was still able to install the CM10.1 AOSP 4.2.2 Jellybean [KANG] http://forum.xda-developers.com/showthread.php?t=2115520 and it works fine, but only till version 20130311-b2. Every version afterwards are giving me constant reboots, mosty at the (PIN) lock screen. Tried to install every version from that upward and failed, with only cache and dalvik cache wipe or even with full wipe. When I go back to 20130311-b2 everything is fine again. So I think I can assume safely its not the hardware.
Does anyone have the same problem and/or a solution for it?
I haven't experienced that (yet). Raising your min frequency might help.
I had the exact same issues as you, same Rom ect, was trying to get it running on my sons phone....
Finally I got it sorted (after 2 long days of messing with it) by keeping the phone in the fridge for 5-10 mins and setting up the phone with the fridge door slightly open (no joke), then I quickly went to Google play store and downloaded 'no frills cpu control' (took 2 attempts, phone froze again) then I dropped the max freq to 1.2GHz well closest frequency just under.
Now it has been perfectly stable, why are all aosp roms/kernels overclocked by default, would make more sense to default at the stock sensation frequency and let users choose to overclock.
Anyone know where I can get a 1.2GHz aosp kernel from? Cause sometimes after entering recovery or bootloader no frills will not apply my settings after reboot, and I don't wanna keep doing the fridge trick on my sons phone.
Note: make sure you place your phone in a dry spot in the fridge!
Sent from my HTC One X using Tapatalk 2