MP 809T

[MKKLR21]

There is also MT6592 model with 2GB RAM.
What do you mean swap support? Does it use a swap partition in the internal nand?
Anyone knowing what happens with NFC? Does it exist?

I've seen informations about the mentioned variety, often callen "809t plus". I think all the other versions are the same (MTK6582, 1/4GB, 720x1280) with fake specs.
I don't know, where the swap partition is located in file system. When i fire the command "free" in terminal emulator, the mentioned values are displayed.

[MKKLR21]

I found out how to get rid of fake hardware specs.

You'll have to edit two files in /system/etc, agold_cheat_evaluating_software.xml and changeram.xml

In agold_cheat_evaluating_software.xml remove all lines between and .

In changeram.xml change these lines to:



Reboot yout phone and you're done.

I ran Antutu benchmark from Play Store. Here is the result:
   
   

[gerstavros]

Wtf, it is so easy to cheat the Antutu ?

EDIT: Tried to change the files, but system partition is read-only on mine, although i have root access . I use xplore, and adb. Can anybody find a solution to my problem?

[MKKLR21]

Tried to change the files, but system partition is read-only on mine, although i have root access .

You'll have to edit build.prop. Find to.secure, change value to 0, save and reboot. After that, you're able to mount system partition r/w.

[gerstavros]

You'll have to edit build.prop. Find to.secure, change value to 0, save and reboot. After that, you're able to mount system partition r/w.

actually the ro.secure is in /default.prop. And i cannot obviously edit any file in root partition.
I ll try the hard way, read back the system partition, edit the image at pc, and reflash it
But am i the only one with this problem??

[MKKLR21]

In my ROM version 109_v82_hydy_hd_20131225 there's a setting "to.secure" in build.prop. It's set to 1 by default. When I set it to 0, I'm able to mount /system r/w (there's "ro.secure" in default.prop, which is set to 1).

[gerstavros]

In my ROM version 109_v82_hydy_hd_20131225 there's a setting "to.secure" in build.prop. It's set to 1 by default. When I set it to 0, I'm able to mount /system r/w (there's "ro.secure" in default.prop, which is set to 1).

I have the same rom, there is no to.secure in build.prop (which line is in yours?), and i cannot anyway edit this file as system is not writable even if i have root access, and i am not crazy

[gerstavros]

In my ROM version 109_v82_hydy_hd_20131225 there's a setting "to.secure" in build.prop. It's set to 1 by default. When I set it to 0, I'm able to mount /system r/w (there's "ro.secure" in default.prop, which is set to 1).

I read back the system partition with flash tool, mounted it but it was still read only even on pc.
Finally i made a backup from cwm, edited the build.prop in system.tar.a, by adding the to.secure=0, and restored it. After boot, i checked the build.prop and it was still stock! "to.secure=0" wasn't there, but system is writable now.
Odd enough

[MKKLR21]

OK, I did some investigation on this topic. Looks like I added this line in build.prop (it was some time ago and I could't remember) and I made a typo (must be ro.secure).

Now I wonder why I could gain write access to /system. I made quite a lot of modifications and I can't say which one had this effect.

[gerstavros]

OK, I did some investigation on this topic. Looks like I added this line in build.prop (it was some time ago and I could't remember) and I made a typo (must be ro.secure).

Now I wonder why I could gain write access to /system. I made quite a lot of modifications and I can't say which one had this effect.

I was sure it was ro.secure :p
I don't either know how now i have writable system