Coby 9742 stuck installing gapps

[3d12]

I am still not following why you can't use hardware keys to boot into recovery, the reason you can't with adb is you have no root.

On my grandson's 9742, to get into recovery from poweroff.

press and release at same time both power and volume down, as soon as you see the word Coby press and hold both power and volume down for 3 seconds, release power, keep holding volume down til you are in recovery.

Oh my god, I love you. This worked. This is the first time I've seen the cwm screen in 12 hours, and I've never been so happy to see it. A suggestion to Traveller, it might be worth putting this method in the rooting sticky along with the others.

EDIT: To clarify, the previous method I was using was, from poweroff, to hold the power and volume down buttons continuously. I just tested it again, and I can reliably boot into recovery using the "press, release, hold" method instead.

If you have adb working, post a few results.

Yes, sir:

adb shell

shell@android:/ $

mount

shell@android:/ $ mount
mount
rootfs / rootfs ro,relatime 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/nande /data ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journal
_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandh /cache ext4 rw,nosuid,nodev,noatime,user_xattr,barrier=0,journa
l_checksum,data=ordered,noauto_da_alloc 0 0
/dev/block/nandi /mnt/private vfat ro,relatime,fmask=0000,dmask=0000,allow_utime
=0022,codepage=cp437,iocharset=ascii,shortname=mixed,errors=remount-ro 0 0
shell@android:/ $

busybox df -h

shell@android:/ $ busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 252.0M 8.0K 100% /system
/dev/block/nande 2.0G 170.2M 1.8G 8% /data
/dev/block/nandh 503.9M 8.4M 495.5M 2% /cache
/dev/block/nandi 988.0K 988.0K 0 100% /mnt/private
shell@android:/ $

Dunno what that'll tell you, but there you are. Do either of you have any other recommendations/suggestions based on these outputs before I re-flash to my last backup in cwm?

 

[vampirefo.]

your system is full you need room in your system for the OS to move, during boot the system need to write logs and such, having 100% full prevents the system from doing anything.

I would just restore a working backup, then boot into it once you have a working tablet then post the busybox df -h output so we can see how much room is in system and what we need to remove before you add anything else.

Both your outputs are good, just system is full, so no partition damage, restoring a backup is the best thing to do at this point, then build from it. I like to have 10MB or more free space once everything is in system.

 

[3d12]

I would just restore a working backup, then boot into it once you have a working tablet then post the busybox df -h output so we can see how much room is in system and what we need to remove before you add anything else.

shell@android:/ $ busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 252.0M 4.0K 100% /system
/dev/block/nande 2.0G 170.0M 1.8G 8% /data
/dev/block/nandh 503.9M 8.4M 495.5M 2% /cache
/dev/block/nandi 988.0K 988.0K 0 100% /mnt/private
/dev/block/vold/179:1 3.7G 706.9M 3.0G 19% /mnt/extsd
/dev/block/vold/93:80 4.6G 219.7M 4.4G 5% /mnt/sdcard
df: /mnt/secure/asec: Permission denied
1|shell@android:/ $

Hrm, it seems system is still at 100%. Could this be leftover bloatware from before installing gapps? The backup I restored was from after confirming gapps worked and before applying the tweaks. I've loaded the backup and the above-posted output is from the tablet sitting idle at the desktop after booting as normal. (Even loaded a program and played around a bit to make sure, and everything is back to working condition so far.)

 

[vampirefo.]

shell@android:/ $ busybox df -h
busybox df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 407.1M 44.0K 407.1M 0% /dev
tmpfs 407.1M 0 407.1M 0% /mnt/asec
tmpfs 407.1M 0 407.1M 0% /mnt/obb
/dev/block/nandd 252.0M 252.0M 4.0K 100% /system
/dev/block/nande 2.0G 170.0M 1.8G 8% /data
/dev/block/nandh 503.9M 8.4M 495.5M 2% /cache
/dev/block/nandi 988.0K 988.0K 0 100% /mnt/private
/dev/block/vold/179:1 3.7G 706.9M 3.0G 19% /mnt/extsd
/dev/block/vold/93:80 4.6G 219.7M 4.4G 5% /mnt/sdcard
df: /mnt/secure/asec: Permission denied
1|shell@android:/ $

Hrm, it seems system is still at 100%. Could this be leftover bloatware from before installing gapps? The backup I restored was from after confirming gapps worked and before applying the tweaks. I've loaded the backup and the above-posted output is from the tablet sitting idle at the desktop after booting as normal. (Even loaded a program and played around a bit to make sure, and everything is back to working condition so far.)

go to /system/vendor/modules delete below files and the one folder, should give you more than enough room.

ath6k
8192cu.ko
ar6003.ko
ar6302.ko
bcm4330.bin
bcm4330.hcd
bcm4330.ko
bcm4330_nvram.txt
bcm40183.hcd
bcm40183_dhd.ko
bcm40183_fw.bin
bcm40183_nvram.txt

 

[3d12]

go to /system/vendor/modules delete below files and the one folder, should give you more than enough room.

Wow, even I'm impressed with how noob this sounds, but how exactly do I go about doing that? I tried ES File Explorer, and it gave me "Operation not Permitted" (even though it started with Superuser permissions and is approved within Superuser) and when I tried using adb, I got "rm failed, read-only file system." So I tried "adb remount" and it tells me the same thing from before, when my tablet wasn't booting: "Remount failed, operation not permitted," and "adbd cannot run as root in production builds."

Should I try mounting /system in cwm and run adb while on the recovery screen? Would that work any better?

EDIT: Also, why those files specifically? Are they just drivers I'm never going to use or something? It only totaled to 14 or so MB, so I'm just curious.

 

[vampirefo.]

ES file explorer > tools > rootexplorer > mount r/w > /system rw

or

adb shell

su

busybox mount -o remount,rw /system

rm -r /system/vendor/modules/ath6k

and so on.

Only my repacked boot.img allow adb remount, default boot.img has adb remount disabled.

These are wifi modules for non Coby devices so not needed, you need at least 10MB free I showed you how to get 14MB