Opera Mini in Landscape with CORRECT arrow keys

Nice.  You're on Rogers, right?  Does Opera Mini prompt you when it wants to access the network?

Interesting, thanks for the update.

Hey Cathy,

Welcome back.

You want to grab the signed JAD from mini.opera.com and open the JAD file in Wordpad or your favorite text editor (that supports LF-only linebreaks).

I had to cheat the system a bit by going to m.opera.com with my PC's browser user-agent set to the Xenon's, then take the JAD download link
/mini.jad?act=dl&tag=mini5&cert=none&region=en-us&rnd=2533806554

and change it to a full, Verisign-certified link
http://m.opera.com/mini.jad?act=dl&tag=mini5&cert=verisign&region=en-us&rnd=2533806554

and download the resulting JAD to my PC to make sure I got a VeriSign-signed JAD.

Yeah, I'm sneaky like that.

Then I take the JAD and add/change the lines listed at the beginning of the thread in the JAD.  Download the JAD to your phone, it should show Verisign signature and download the JAR.

For AT&T folks, the Verisign signature makes sure it only prompts for web access the first time, and not every time it accesses.

Do it slowly (start off with just the unaltered signed version, then start modifying) and you'll get it.
Just be sure to delete the app from your phone before reloading it to ensure your JAD changes apply.

More general background info follows...

JAD files are text files that describe to the Java environment how an application should be installed.
JAR files are zip archives that contain the actual executable Java bytecode.

The JAD contains various parameters along with the digital signature information, if the application is signed.
The digital signature for a signed Java application is stored in the JAD, so if you don't install a Java application using a JAD, it will not be signed, even if the application was signed.

For the curious wondering if you could sign the application in the JAR itself, well, you could put the signature in there, but the authentication requires both the size of the JAR and the SHA-1 hash.  Storing the hash in the JAR archive would then change the content of the archive and therefore its hash, so the hash stored in the archive would be incorrect, not to mention its size might also change.  It's a chicken-and-egg scenario, so the size, size, hash and signature are stored in the JAD.

Which brings up the next point...
Modifying the JAR will break the digital signature, if the JAD/JAR is signed to begin with.
On the other hand, modifying the JAD alone does not break the digital signature, as long as the JAR does not change.

If you can copy/paste text, you can edit JAD files.  It's that simple.


That link should get you a signed version of the JAD.

Then you open the JAD file.
Go to the end, and paste this text in:


You can compare the two attached - the original mini.jad and the mini-modified.jad to see the difference.

Save the JAD, delete Opera Mini from your phone if it's already installed, then load the modified JAD on your phone.

The JADs I post as attachments have limited lifespans because when Opera updates the version, the signature and size information in the JAD no longer apply to the new binary file.  Then you get Certificate Error messages.

I have the patched 5.1 Opera Mini