yé! \o/
Le fichier su et com.emode.helper.apk fûrent nécessaires.
=======================================================================
Required files:
http://dl.dropbox.co...chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
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.
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.
Confirm the log_kernel.txt file exists, if it does not wait a minute and check again.
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.
Now we want to wait for /data/local.prop to be created, it may take a minute or two. Keep checking until it exists.
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.
echo 'ro.kernel.qemu=1' > /data/local.prop
Once you have rebooted, remount, install su.
Clean up your mess!
Reboot, install the Superuser app from the market and enjoy
http://dl.dropbox.co...chainsdd-su.zip
Unzip chaindsdd-su.zip and then get a shell with adb
Quote
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.
Quote
mkdir /data/local/logs
mkdir /data/local/logs/kernel
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.
Quote
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.
Quote
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.
Quote
rm /data/local/logs/kernel/log_kernel.txt
ln -s /data/local.prop /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.
Quote
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.
echo 'ro.kernel.qemu=1' > /data/local.prop
Quote
exit
adb reboot
adb reboot
Once you have rebooted, remount, install su.
Quote
adb remount
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
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!
Quote
adb shell rm /data/local.prop
adb shell rm -r /data/local/logs
adb shell rm -r /data/local/logs
Reboot, install the Superuser app from the market and enjoy
Quote
adb reboot
Please don't PM me here, I will not likely read it as I do not check often.
===================================================================
Licence du contenu du site (bla bla bla):
Depuis:
http://wiki.rootzwiki.com/Main_Page
...RootzWiki is dedicated to assisting you in gaining root access on your Android phone.
Une copie exacte de ces instructions se trouve sur XDA.
Articles
