9042 half way bricked. need help.

svtart

Member
Oct 8, 2012
13
0
I have a 9042 that I managed to brink 1/2 back to life. it turns on, into debugging mode. but It will not boot into recovery no mater what I do. I can access in adb but when I try to:
su it will say permission denied. I try to re-install recovery and also permission denied.
any ideas on how to regain permission?
 

svtart

Member
Oct 8, 2012
13
0
also es file explorer is gone and I can not reinstall because the partition is bad, it is out of space with no apps installed.
 

svtart

Member
Oct 8, 2012
13
0
it was rooted, and I tried re rooting it. I follow all the instruction and when I get to:
/data/local/tmp/install-recovery.sh
it gives me this error: cannot create /dev/block/nandg: permission denied
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
type

adb shell

mount

also post what you did to your tablet to get it into this shape.

"error: cannot create /dev/block/nandg: permission denied"

usually means you are doing this on unrooted tablet.

when you tpye adb commands do you see $ or #?
 
Last edited:

svtart

Member
Oct 8, 2012
13
0
C:\Users\Todito\CobyADB>adb shell
shell@android:/ $ mount
mount
rootfs / rootfs rw 0 0
tmpfs /dev tmpfs rw,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600,ptmxmode=000 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
/dev/block/nandd /system ext4 ro,relatime,user_xattr,barrier=0,data=ordered 0 0
/dev/block/vold/179:1 /mnt/extsd vfat rw,dirsync,nosuid,nodev,noexec,relatime,ui
d=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset=
ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,u
id=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,iocharset
=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/93:64 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relat
ime,uid=1000,gid=1015,fmask=0702,dmask=0702,allow_utime=0020,codepage=cp437,ioch
arset=ascii,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
shell@android:/ $

as you can tell I see$

as far as what happened it auto updated busybox and it started givving me just black screens when I went into apps. I uninstalled busybox and when I rebooted it was stuck on the coby letters. I could not get it to see adb in recovery so i found a zip image on the net and installed it. it brought it back, but only half way and now it will not go into recovery or let me change anything with adb..
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
You have two options,

1. Boot into recovery via hardware key.
2.Livesuite.
 

svtart

Member
Oct 8, 2012
13
0
hardware key will not work. power plus volume will not work. it will boot like normal.

I will try livesuite, but i am unsure if it will work when it is not in recovery.

thanks!!
 

svtart

Member
Oct 8, 2012
13
0
tried livesuite. does not work either. tried both debugging mode and normal. as soon as I hit run livesuite shuts down.:(
 
Top