There are several wrong things in the first version, some still in the second one...
First, the type of the function is Boolean, which correct syntactically, but sub-optimal, as it encloses a simple boolean in an object. Use boolean instead, the primitive type.
Second, the temp variable is totally useless... Use toTest directly.
Last, in the first version, the loop isn't really useful, as you return on the first iteration, whatever the result! And thus, the break after the return is never reached.
The second version is better with this point, but can be still improved: no need to assign true each time.
A better version could be:
Or just return false; in the test.
Without intermediary array, and a variant on the test, and on the result:

phi.lho thanks a lot for helping me again. I have already noticed that the temp was useless, and have no idea why i came up with object Boolean instead of the primitive... maybe it was late :-) But the loop in the first try returning from the first iteration gets me confused. (of course i could not try as it wont compile)

Indeed, I edited too fast. I replaced above the letras.length with toTest.length() (the () is necessary...).

About the first issue: think about it: if condition is true, you return true and exit the function. If it is false, you return false, and exit the function. No other loop is run.

Even in a for loop? I thought it would go until the second condition "for( 1st; 2nd; 3d)" was met... So u don't need the break statement? Right?