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.
Related
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
After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Jakkumn said:
After surfing the forums for a couple days and not finding a completely precise answer to my problem, and due to being limited by posts, I have to ask a question here. I have rooted my phone, installed a number of different roms, but the only issue I have run into is flashing faux123's kernel and the Trinity kernels. No matter what kernel I attempt to flash I receive the wonderful black screen. The touch buttons light up when the screen is pressed, but the rom does not seem to load in the background. I am doing something wrong when I flash the kernel, or is there another problem that I have not found?
I have flashed UV and normal voltage kernels, along with going to advanced under CWM and formatting each part of the phone.
EDIT: Resolved the issue. It appears the only rom that works with these kernels on my phone is the nightlies. Thanks everyone though.
Click to expand...
Click to collapse
if i was me after reading what I've found online i think i would look for a more reputable dev when it comes to kernels.
Reputable? Faux and morfic are among the elite devs for our device. They don't get any more reputable than them.
-custom sig.
CM7 should work, whether nightlies or stable. Trinity requires ext 4 support, meaning CWM touch won't work. Previous version 5.0.2.0 (I believe) should be used to install trinity. Faux should have worked so not sure why it failed on other than nightlies.
All CM7 based ROM should work with these kernels.
-- The noob says:
Three in the morning I woke up... it was hot... the g2x had SODd!
I used to be able to use clemsyn kernels and blades kernels and the roach kernel fine but ever since blades captain awesome kernel or around the time the latest update came out my tf will now only work with blades in a stable condition.
Ive tried clearing every partition through nvflash and going ground up re flashing recovery rom kernel all unmodified still no luck.
What more can I do and why would this happen?
I have delt with it for a few months but it has been bugging the back of my mind and I have tried all I know to fix it so now its time to ask for help.
Thanks in advance for any help and sorry about the odd ball question im just truely stumped on this one.
Sent from my Transformer TF101 using xda premium
maybe you overclocked too high and messed up you cpu?
I don't know why this would happen, and should not happen, unless it it's either a hardware issue or if you are getting orphan files or incomplete flashes while writing over the kernel..try an old nandroid backup, or try flashing with nvflash? Both should reformat your partition, i had similar issues with a rom (not a kernel) on a phone leaving data through wipes and flashes, nandroid was the only thing that fixed that..
Kernels are designed to work with very specific basebands. If the OS you are using has been updated then the kernel must be updated to follow. The Kernel controls how the software and the hardware interacts. You know the hardware will always be the same. So when the OS changes, the kernel must as well.
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: