root.txt

Unzip chaindsdd-su.zip and then get a shell with adb

Code:

adb shell

Set up the dirs, so shell owns them prior to logging. If shell does not own them then we can not control them. If the logs dir already exists, you may have to do a factory reset to remove them. They should not exist unless someone attempted this previously.

Code:

mkdir /data/local/logs
mkdir /data/local/logs/kernel

Open emode's logset activity. First button should be for enabling log set, enable it. Do not exit the activity, but if you do just repeat the below command.

Code:

am start -a android.intent.action.MAIN -n com.zte.emode/.logset

Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.

Code:

ls -l /data/local/logs/kernel/log_kernel.txt

If it exists, delete it and immediately symlink it to /data/local.prop, logset may recreate it, if it does delete and try symlinking again.

Code:

rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /data/local/logs/kernel/log_kernel.txt

Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.

Code:

ls -l /data/local.prop

Now once /data/local.prop exists, go back to the logset activity and disable logset. If you don't disable it, it will slowly eat away at all the disk space, and possibly overwrite the local.prop before you get root. Now lets set qemu=1 then reboot.

Code:

echo 'ro.kernel.qemu=1' > /data/local.prop
exit
adb reboot

Once you have rebooted, remount, install su.

Code:

adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su

Clean up your mess!

Code:

adb shell rm /data/local.prop
adb shell rm -r /data/local/logs

Reboot, install the Superuser app from the market and enjoy

Code:

adb reboot