[Android Software Development] ntn:
Problem with MTK6573 android 2.3.6 but ok with same chip android 2.3.4

Hi I had problems for the root of the Smartphone DAPENG A7 MTK6573 Android 2.36 -Kernel 2.6.35.7! The following log:

Easy rooting toolkit (v4.0)

created by DooMLoRD

using exploit zergRush (Revolutionary Team)

Credits go to all those involved in making this possible!

---------------------------------------------------------------

[*] This script will:

(1) root ur device using latest zergRush exploit (21 Nov)

(2) install Busybox (1.18.4)

(3) install SU files (binary: 3.0.3 and apk: 3.0.6)

(4) some checks for free space, tmp directory

(will remove Google Maps if required)

[*] Before u begin:

(1) make sure u have installed adb drivers for ur device

(2) enable "USB DEBUGGING"

from (Menu\Settings\Applications\Development)

(3) enable "UNKNOWN SOURCES"

from (Menu\Settings\Applications)

(4) [OPTIONAL] increase screen timeout to 10 minutes

(5) connect USB cable to PHONE and then connect to PC

(6) skip "PC Companion Software" prompt on device

---------------------------------------------------------------

CONFIRM ALL THE ABOVE THEN

Premere un tasto per continuare . . .

--- STARTING ----

--- WAITING FOR DEVICE

* daemon not running. starting it now *

* daemon started successfully *

--- creating temporary directory

mkdir failed for tmp, File exists

--- cleaning

rm failed for *, No such file or directory

--- pushing zergRush

720 KB/s (23060 bytes in 0.031s)

--- correcting permissions

--- executing zergRush

[**] Zerg rush - Android 2.2/2.3 local root

[**] (C) 2011 Revolutionary. All rights reserved.

[**] Parts of code from Gingerbreak, (C) 2010-2011 The Android Exploid Crew.

[+] Found a GingerBread ! 0x00000118

[*] Scooting ...

[*] Sending 149 zerglings ...

[*] Sending 189 zerglings ...

[-] Hellions with BLUE flames !

--- WAITING FOR DEVICE TO RECONNECT

if it gets stuck over here for a long time then try:

disconnect usb cable and reconnect it

toggle "USB DEBUGGING" (first disable it then enable it)

--- DEVICE FOUND

--- pushing busybox

2167 KB/s (1075144 bytes in 0.484s)

--- correcting permissions

--- remounting /system

mount: permission denied (are you root?)

--- checking free space on /system

0 KB/s (439 bytes in 1.000s)

df: /mnt/secure/asec: Permission denied

export: 376: bad variable name

--- copying busybox to /system/xbin/

/system/xbin/busybox: cannot open for write: Read-only file system

--- correcting ownership

Unable to chmod /system/xbin/busybox: No such file or directory

--- correcting permissions

Unable to chmod /system/xbin/busybox: No such file or directory

--- installing busybox

/system/xbin/busybox: not found

--- pushing SU binary

failed to copy 'files\su' to '/system/bin/su': Read-only file system

--- correcting ownership

Unable to chmod /system/bin/su: No such file or directory

--- correcting permissions

Unable to chmod /system/bin/su: No such file or directory

--- correcting symlinks

rm failed for /system/xbin/su, Read-only file system

link failed Read-only file system

--- pushing Superuser app

failed to copy 'files\Superuser.apk' to '/system/app/./Superuser.apk': Read-only

file system

--- cleaning

--- rebooting

ALL DONE!!!

Premere un tasto per continuare . . .

P. S. the same procedure with smatphone of my friend (MTK6573 Android 2.3.4) has been positive exist!

can anyone help me?:confused:

thanks in any case