You mean your concern is only the keyboard ? Just open a document , say write a sms - hold down on area you wish to write, select input method - and see what other keyboard choices are there ? If there is a full English one - select it to be your default. You can also check for KB alternatives in the Market. Use VLINGO - is free and plus point it can be voice activated to accept input by voice

---

Added on January 27, 2011, 12:14 am

YES. Strange ? Where is your source of the Roto rom ? It is supposed to remove the protected bootloaders
Anyway, you can now use the patch first before flashing the recovery again

Roto ROM doesn't mention remove protected bootloader. As mentioned on his thread:
"They don't contain and won't install protected bootloaders either"
My another noob question here:
Bootloader is part of the ROM or come with the TAB?

BREAKING NEWS / JAN 15: A fix has been found ! See this post. Also see the bounty thread: http://forum.xda-developers.com/showthread.php?t=906464.

This really applies to other ROMs as well, but the "new" JM6/9/A/C/D/E/F ROMs specifically.

Some of these ROMs include new bootloaders. These bootloaders check checksums/signatures in various parts of the firmwares. The "normal" Samsung ROMs, nor custom ROMs and kernels, have these checksums.

The result is that once flashed, you cannot revert to older/official/custom Samsung ROMs, and you are pretty much stuck using one of these four ROMs, as they are the only ones containing the right checksums.

At least TRIPLE CHECK if you want to flash one of these ROMs, that what you are flashing DOES NOT include the new bootloaders ( boot.bin and sbl.bin ). I know from the CF-Root thread that a fair number of you are already too late, but I thought to warn new users anyways. Some modders (like rotohammer) already usually remove these parts, but still triple check everything to make sure.

There is no known fix. I know, I've tried all of them some people suggested in other threads. None of them really works. Sure, with some effort, you can get a different firmware to somewhat run, but you'll still be using the "checksum" bootloaders and the kernel will not be modified. You will still be running the kernel from the "checksum" firmware you loaded earlier. You will not be able to do full flashes, nor will KIES updates work.

Hopefully somebody will find a real solution for this issue for those already affected. If so, please post it in this thread.