Search results

Great, and nice workaround on the AOSP keyboard :D

Great :)

The new version will still need this to be done, and every version onwards... at least until guys at MIUI figure out that CWM based recovery returns ro.build.product as "GT-I9300" and start including this by themselves

look at a post above yours

Open MIUI zip and move to META-INF\com\google\android Open updater-script Replace the first few lines with: assert(getprop("ro.product.device") == "m0" || getprop("ro.build.product") == "m0" || getprop("ro.product.device") == "GT-I9300" || getprop("ro.build.product") ==...

Sorry, it should be "getprop"

Well, the workaround of the attachment is to use terminal emulator and enter "getprops"... I really needed MAC address, but hey, it's up to you.... If you use a custom keyboard, you should be fine :)

There is another FC -> Settings -> About -> Status.... Here is a logcat screen from eclipse, you might need to zoom in a bit to see.

There is another FC -> Settings -> About -> Status.... Here is a logcat screen from eclipse, you might need to zoom in a bit to see.

I already told you - it's I9300DDDLJ1

There... right after selecting the default input method, the FC occurs...

i will take it after launch... 30 mins

It's DDDLJ1 and the keyboard is constantly crashing, luckily I use swype keyboard... which then works fine

great news, since dual booting only supports JB ROMS!

maybe I'm wrong, but finally there is JB for S3 so I can once again install miui as my secondary ROM on my dual boot phone :)

this is great news indeed :)

s3 JB update? :/

I think m0 is the one.

I can see that everyone is telling you to use the CF CWM that is n0t touch recovery... See here's the real deal, the best recovery you are currently going to find for you S3 is here (but everyone do read... GSM version only): http://forum.xda-developers.com/showthread.php?t=1719744 Will you be...

i9300 JB update maybe?