MEIZU MX ROOT

HelloI boughttheMXMEIZUChina
IcandoaRothwithSuperUserOneClick?
Would that work?Is it dangerous?
Thank you

I did not find Edit

HelloI boughttheMXMEIZUfrom China
IcandoaRootwithSuperUserOneClick?
Would that work?Is it dangerous?
Thank you

Hope they can fix the space bar in the next firmware.

Originally Posted by chengdude

Hope they can fix the space bar in the next firmware.

That was mean chengdude

Back on topic, you probably won't be able to root the Meizu MX China version, because it has been blocked by Meizu. Hong Kong version is rootable because it has different software.

Originally Posted by nice2know_u

That was mean chengdude

Back on topic, you probably won't be able to root the Meizu MX China version, because it has been blocked by Meizu. Hong Kong version is rootable because it has different software.

any possibility that meizu has unblocked CN Ver. for root in future? one another question that why meizu do this? cn or hk must be a same..
what you think.

As Meizu stated about M9, I think the same is about MX. This is because of the patent rules in china ( ? haven't found anything about that... ) that they can't sell unlocked version in China, because of the Flyme OS designers. BUT, if they are truly going to launch plain ICS for MX CN version, then the root should be allowed

Soyou tell methat it is impossibleto doRootdevicefrom China?

Originally Posted by Barak Shem-Tov

Soyou tell methat it is impossibleto doRootdevicefrom China?

Yes, most likely. As you know only temp-root is available for the M9 too, but I have not seen a solution for the MX yet.

Whydid they do thatImustrootdevice

Originally Posted by Barak Shem-Tov

Whydid they do thatImustrootdevice

then you should have read the posts here before your purchase to know that you need the HK version for rooting. But so far I saw no one with a MX-HK who has successful rooted it.

how to root mx hong kong version

I believe SuperOneClick works on the MX HK. [LINK]

Does this work with 4-core HK version?

Originally Posted by birginioss

Does this work with 4-core HK version?

Superoneclick root is only suitable for mx dual core hk ver with Hong Kong firmware

With mx quad core hk ver with Hong Kong firmware. Please search tpsparkyroot in Google.

For mx dual or mx quad with China fw even you are hk ver mx, you are no way to root that except using uart as xda mentioned.

Originally Posted by hackarchive

how to root mx hong kong version

Sent from my M032 using Tapatalk 2

Originally Posted by kedros5

Superoneclick root is only suitable for mx dual core hk ver with Hong Kong firmware

With mx quad core hk ver with Hong Kong firmware. Please search tpsparkyroot in Google.

For mx dual or mx quad with China fw even you are hk ver mx, you are no way to root that except using uart as xda mentioned.






Sent from my M032 using Tapatalk 2

WAIT, WHAT????

Superuseronclick can root the Honkong MeizuMX 4-Core with Android 4.0.3 and flyme os??


10char

Originally Posted by Nexus S

WAIT, WHAT????

Superuseronclick can root the Honkong MeizuMX 4-Core with Android 4.0.3 and flyme os??


10char

No it's not possible.

Originally Posted by datagutt

Good news! We might be able to root using https://github.com/saurik/mempodroid. Im currently asking Saurik how to figure out the memory addresses needed.

Originally Posted by datagutt

SuperOneClick uses Zergrush IIRC (which is 2.2 and 2.3 only). No exploits i tried work, the best bet is the one i linked too, but Saurik doesnt seem to have answered (probably busy).

I can say that mempodroid does not work either. I got someone to find the right memory addresses needed, but it still segfaulted.
EDIT: I can post it if anybody wants to give a go, or see if they can fix it.

The TPSparkyRoot method (ro.kernel.qemu=1) works for me on the HK 4-core.
Won't it work on the CN version?

PHP Code:

> adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
MX21..................      device 


> adb shell

Code:

shell@android:/ $ cd  /data/local/
cd  /data/local/
shell@android:/data/local $ ls -al
ls -al
drwxrwx--x shell    shell             2012-07-05 06:39 tmp
shell@android:/data/local $ mv tmp tmp.old
mv tmp tmp.old
shell@android:/data/local $ ln -s /data /data/local/tmp
ln -s /data /data/local/tmp
shell@android:/data/local $ ls -al
ls -al
lrwxrwxrwx shell    shell             2012-07-20 20:25 tmp -> /data
drwxrwx--x shell    shell             2012-07-05 06:39 tmp.old

(At this point, reboot)

Code:

shell@android:/data/local/tmp $ echo "ro.kernel.qemu=1" > /data/local.prop
echo "ro.kernel.qemu=1" > /data/local.prop
shell@android:/data/local/tmp $ cat /data/local.prop
cat /data/local.prop
ro.kernel.qemu=1

(Reboot a second time)

Code:

root@android:/ # id
id
uid=0(root) gid=0(root)

then do whatever to install su, etc.

Then when you reboot, su disappears from /system. This is tested on Flyme OS 1.0.1, M030 dual-core HK version​.

How weird.
Can you try pushing this version of su (su_ics_v3.1_wraithdu_installer_v7.zip) in /system/bin/su after the "adb remount" step ?
su_ics_v3.1_wraithdu_installer_v7.zip (from supercharger xda thread)