Coby Kyros MID1042 Problem

[vampirefo.]

We still have yet to hit on anything I didn't already know.

drop the attitude, I am not required to offer you any help, an wont help people with attitudes.

 

[mvancil]

The "No space left" error is it being unable to overwrite existing files...

C:\coby_root3>adb push data /data/local/tmp/
push: data/Superuser.apk -> /data/local/tmp/Superuser.apk
push: data/su -> /data/local/tmp/su
push: data/root.sh -> /data/local/tmp/root.sh
push: data/recovery.img -> /data/local/tmp/recovery.img
push: data/reboot-recovery -> /data/local/tmp/reboot-recovery
push: data/mempodroid -> /data/local/tmp/mempodroid
push: data/install-recovery.sh -> /data/local/tmp/install-recovery.sh
7 files pushed. 0 files skipped.
3310 KB/s (10797409 bytes in 3.185s)


C:\coby_root3>adb shell
shell@android:/ $ chmod 0777 /data/local/tmp/mempodroid
chmod 0777 /data/local/tmp/mempodroid
shell@android:/ $ /data/local/tmp/mempodroid 0xd7cc 0xad27 sh /data/local/tmp/ro
ot.sh
7cc 0xad27 sh /data/local/tmp/root.sh <
rooting...
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
shell@android:/ $ su
su
Segmentation fault
139|shell@android:/ $

 

[mvancil]

This is why I was asking if anyone has a signed recovery file that I can use with the native recovery.

 

[vampirefo.]

The "No space left" error is it being unable to overwrite existing files...

C:\coby_root3>adb push data /data/local/tmp/
push: data/Superuser.apk -> /data/local/tmp/Superuser.apk
push: data/su -> /data/local/tmp/su
push: data/root.sh -> /data/local/tmp/root.sh
push: data/recovery.img -> /data/local/tmp/recovery.img
push: data/reboot-recovery -> /data/local/tmp/reboot-recovery
push: data/mempodroid -> /data/local/tmp/mempodroid
push: data/install-recovery.sh -> /data/local/tmp/install-recovery.sh
7 files pushed. 0 files skipped.
3310 KB/s (10797409 bytes in 3.185s)


C:\coby_root3>adb shell
shell@android:/ $ chmod 0777 /data/local/tmp/mempodroid
chmod 0777 /data/local/tmp/mempodroid
shell@android:/ $ /data/local/tmp/mempodroid 0xd7cc 0xad27 sh /data/local/tmp/ro
ot.sh
7cc 0xad27 sh /data/local/tmp/root.sh <
rooting...
cp: write error: No space left on device
cp: write error: No space left on device
cp: write error: No space left on device
shell@android:/ $ su
su
Segmentation fault
139|shell@android:/ $

ok your system is full no room to write, your su is corrupt not Superuser.apk,

Do you already have cw recovery installed?

 

[vampirefo.]

This is why I was asking if anyone has a signed recovery file that I can use with the native recovery.

ok so you don't have cw recovery installed?

 

[mvancil]

No. Just the native recovery.

 

[vampirefo.]

No. Just the native recovery.

ok I am making you a zip that will root your device

This will replace su and Superuser.apk and set permission for root.

just flash via stock recovery.

http://www.mediafire.com/?bsgczf2bdw32o1q

 

[mvancil]

Attempting now...

 

[mvancil]

It all appeared to go ok....but I don't think that did it. Trying to test now.

 

[vampirefo.]

It all appeared to go ok....but I don't think that did it. Trying to test now.

adb shell
su
Post output.

 

[mvancil]

This is still progress...I'm hoping this means I just go back and re-root

shell@android:/ $ su
su
/system/bin/sh: su: not found
127|shell@android:/ $

 

[mvancil]

Nope...re-root fails...then I get the segmentation fault again....re-applying the zip.

 

[mvancil]

Oh this is neat....in the /system/bin I see 2 entries for su

 

[vampirefo.]

Nope...re-root fails...then I get the segmentation fault again....re-applying the zip.

Yes it fails cause no remove left your system is full, it will be a few hours. I will fix this for you with the next zip.

 

[vampirefo.]

adb shell

busybox df -h