Database Info

Switching between bootloaders

My new G Tablet is charging overnight before I flash it ... so while I was checking out my ROM options, I got a little turned around regarding the bootloader. I know that some ROMs are for 1.1 and some for 1.2, but I haven't seen anything about upgrading/downgrading between them.
My new tablet is 1.1, right out of the box, which is to be expected (I think). If I wanted to use clemsyn's Beasty ROM, which requires 1.2, how would that affect CWM? Would I still use v08?
To upgrade/downgrade to/from 1.1/1.2, do I need to remove CWM? And if so, how?
I did some searching on the forums and haven't found anything yet, so I thought I'd post. I can't believe this isn't a duplicate question, but I can't find a thread with this info.

follow this guide to get to 1.2 bootloader 4349 firmware
http://forum.xda-developers.com/showthread.php?t=1039000
That will install the stock recovery which can be used to flash any roms. CWM just adds options, like partitioning, data wipes, backups, etc.
If you want to flahs CWM AFTER flashing Beasties, then you'll need the 1.2 friendly CWM. .8 will NOT play well with 1.2 You can find it on slatedroid, along with a lot more support for 1.2 roms.
if you ever want to play around with the Honeycomb port (Bottle of Smoke) then you'll need to be on 1.2. I'm running Brilliant Corners, which is a 1.2 version of Vegan 5.1.1, and I'm loving it.

Issues with installing certain ROMS [SUCCESS!!!]

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

Overclocking in ICS?

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.

Very unreliable TF101 and confused

Hi,
I have had a TF101 for over a year. However it was used by someone else who upgraded it 0.17 and when it came to be me was unreliable and would often randomly reboot and then get stuck on the 'EEEpad' screen (before it says ASUS etc).
I am new to Android (been on webOS for a few years) so rooting etc is new ground for me, but I am pretty technical. Had lots of webOS patches and overclocking installed.
I 'upgraded' to 0.24 and then started reading as much as I can on this site after the reboots remained. I now realise I made two fundamental mistakes
1) Going to 0.24 at all seems to be a no-no from what I'v read.
2) I didn't do a clean restart before upgrading.
I'm not too worried about staying with stock but I do need the thing not to re-boot as often (15 times yesterday !!), so I am wondering.
1) Is 0.24 on a factory reset machine better for rebooting ? If so how do I get back to that state given that I have 0.24 already so can't reset and then re-install 0.24 (as I think I should have) ?
2) Is the only way to make it reliable to go for a customised ROM/Kernel/Bootloader etc ?
3) If (2) is true and I need a different ROM/kernel etc which is the most reliable ?
I know I need to do the downgrade, root, clockworkmod etc but can probably handle that from other threads.
Many thanks for anyone taking the time to respond.

1: A factory reset *May* help, but there's problems with official ICS anyway.. I haven't tried stock ICS and have no intention of trying it with all the horrid reports I read.
2: I would say this is your best option, put a ROM on, you won't regret it.
3: You will need to flash a ROM, boot it once, then wipe caches again and flash a kernel. As for kernel IMO your best choice is Guevor's kernel, (I'm using v20.6 and it's perfect.) As far as ROM I recommend ARHD or Revolver if you like stock look, and Megatron or AOKP if you like AOSP based roms. (its all preference here)

15 reboots in one day? Have you tried a factory reset yet? That sounds excessive.
But I have zero problems with ARHD 3.4 and Guevors kernel.

As the 2 previous posters suggest - I think a factory reset could possibly help.
If not then I would root, and install a custom ROM. I'm using Revolver and stock kernel with zero RR or SOD. I tried Guevor's kernel and it just didn't agree with my particular TF-101. I also tried ARHD and it worked great but I just prefer the aesthetics of Revolver. Good luck and I sure hope you get your reboot issues fixed soon.

Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.

rege0039 said:
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
Click to expand...
Click to collapse
As you have had the unit over a year --> old serial# --> it has to be nvflash-able. So you have an option for an easy one-step installation.

Erm, OK - now I am a bit lost !
I want a rooted machine, Clockwork mod and a chance to try custom roms and kernels.
I seem to be able to find instructions for one but not the others, some want to put back stock rom but I am don't want that.
Sorry to be thick, and maybe I'm looking in a panic and getting lost but is there some instructions to follow to take it from 0.24 to being rooted and able to load custom roms. If I get to Clockwork mod I know how to use that to flash etc as I had it on my touchpad before I want completely to Android.
nv-flasable - what does that mean ? Can I check my serial number to know I can do it ? Stickers seems to have come off so not sure I know serial
Sorry for sounding confused and not looking enough - I really have tried but can't seem to get instructions that go from where I am to where I need to be !!!
Thanks again.

NvFlash
NvFlash is a utility that older tabs (With Sbkv1) can use to easily flash a recovery on the system. ASUS has basically two passkeys for the TF101 to get into APX mode, Sbkv1, and Sbkv2. Sbkv1 is the passkey everyone has, and Sbkv2 is currently unknown/locked. What Sbk you have is based on the serial number of your tablet (you can look at the box if you still have it, or find the stickers, also when did you purchase the tab, if it was before July 2011 then you for sure have Sbkv1, if not it may be Sbkv2) If your serial number starts with B60 or below (B50 B40 etc...) it has Sbkv1, if it has B70 or higher, it has Sbkv2. Find out what Sbk you have (it should be version one) then download NvFlash from Rayman's thread. Search nvflash unbricking released in the development forum. Once you have that get an NvFlashable recovery (I recommend Rouge XM touch recovery 1.5, since it reads from internal and external memory, again search in development.) Boot your tablet into APX mode and connect to your computer (Turn off, hold Volume-UP and power.) Install the driver, then follow instructions from NvFlash thread to flash the new recovery. Once you have this, you can place a ROM on your tab (All roms are pre-rooted, no need to install superuser) boot into your new CWM recovery with Power + Volume-DOWN, then press Volume-Up after a few seconds. Wipe data/factory reset, wipe cache, wipe Dalvik-cache, install zip from... find your ROM.zip (don't extract it) and install! Then reboot and let it install, after booting once, you can go back into CWM recovery to install a kernel.zip that you also place on your tab (I recommend Guevor's kernel, make sure you wipe cache and dalvik-cache again.) Then you're all set!
Any other Q's?

Ok. I think I follow all that. Many, many thanks.
I will go to work tomorow and look for the box, but I'm pretty sure it was bought before July 2011.
Need to do something, sure it's cos I am now counting but today held the record at 29 reboots ! Four within 8 minutes at one point.
I think I will go Android Revolution and the kernel you mentioned.
Would be great to bo rooted as I have Titanium license as well.
Thanks again. webOS forums were always good, XDA proving so as well.

Nvflash was just released for Sbkv2, so just use NvFlash, it's easiest good luck!

Thanks for following this up with the latest news !
As far as I can see the wheelie setup is for LINUX only ?
I'm on Windows 7, I could set it up as a dual boot but am complete newbie at Linux !

It's not that bad to set up, just download virtualbox from Oracle, then an ubuntu.iso installation, and run it as a virtual machine within windows. Easier than dual boot. It isn't too hard to set up, essentially download and extract.

So ...
Good news is got it rooted, clockworkmod installed (using the Rogue version that was suggested) and then went installed Android Revolution latest version. Did all the required resets, dalvik and cache wipes etc.
Great I, thought, until ...
All day to day it has rebooted frequently even though I installed no other s/w - just what comes with Android Revolution. It seems to more frequent when the device has powered down after a period of inactivity.
Is it now time to start thinking this is a h/w problem ?
Will a different custom ROM be worth a go or would a different kernel help (which I haven't tried yet) ? If so I wasn't sure which version of the suggested kernel (Guevors) I should go for as there seemed to a lot of them.
Once again, thanks for any and all time. NVFlash was a revelation and really not that hard once I had the drivers installed.

Have now installed v21 of the kernel and got CPU tuner to change minimum cpu speed, wasn't sure about voltages.
Is there a recommended way to set cpu speed, governors and voltages ?
At the point of thinking this will never be stable again. Not even getting 30 minutes without a random reboot.

Try version 17c of guevor's if 21 is giving you issues, and any Cm9 based build will have overclock change built in. I don't use overclock apps, they give me problems. Make sure you SuperWipe, then try reinstalling ARHD (or a aosp/aokp/etc rom) flash either 20.1version6 guevor or 17c and don't overclock (default it overclocks a bit to 1200). See if it is finally stable, if not you might have borked hardware :/

It's charging at the moment, after I night of rebooting I presume.
I've got the SuperWipe zip so I will run that (which I didn't before but did do a reset, cache and dalvik wipe) and then put Revolution on after that.
I looked at Megatrons ROM as well - any comments on its reliability ?
I've not noticed it only does it when the device has been left for a few minutes. If I keep using it and don't let it sleep then things seems OK.

Megatron is really stable, I've found. I like aosp better too.

Those who experience rr or SoD can downgrade via nvflash to Any custom rom , prime 1.4 for example, and then upgrade by way of cwm to an ics aopk to make those problems disappear?
EDIT: megatron is very stable and have an awesome battery life. And the pop ups telling us there's a new update is great too
Sent from my Transformer TF101 using XDA Premium HD app

Hi,
Have been away with unreliable internet access but am now back.
I'm starting to think there must be a h/w problem as nothing seems to make the thing stop rebooting. The only pattern I can see is that if the device is being charged (either from the mains or by being plugged in to the keyboard) then it seems to stay up. Not sure if a certain battery level makes a difference.
I went through the whole SuperWipe clean and Revolution install, then put on the 17c kernel (At least I think I did About shows 2.6.39.4-g8fc25a9-dirty for the kernel, is that right ?) and am still have lots of reboots.
Tried Megatron with the same kernel and couldn't get wifi but still got a couple of reboots.
Any other suggestions ?
Or does anyone know a way of getting repairs done on this in the UK ?

You'll want to RMA to ASUS if nothing works :/

Kernel not flashing with revolver 4.2

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: