Can't Root MID9740

[j2m_andro]

hey there, i recently received a mid9740 and the first thing i wanted to do is to root it and install gapps.. ive been googling for days now and always find myself reading read first development index root utility and ive been doing the steps stated there to root my c(rap)oby mid9740.. ive installed adb drivers following instructions from here and made sure it works, i even got myself prepared, downloaded cwm and read this topic a couple of times now.. but even after being that worked up, i still can't root it.. followinf the instructions for mid9740, RootUtility says it is successfully rooted (for everytime now since 2days ago), but it is (always) not.. not even the slightest sighting of superuser in appdrawer.. even asking adb shell then su says su: not found.. i am working on windows 8 64bit os and i thought that might be the problem. so i dual booted into windows 7, installed every driver and repeated the sam procedure but nothing works.. not to mention i also do a factory reset every time i try to root it..

please help me before i offer that tab's life to livesuit..
p.s ive been reading/googling threads here and it seems like iam the first one to encounter this. and please excuse my grammar abuse.xD and that i just made this account today just for this..

 

[Traveller]

The root utility is a batch file, which is why it always reads that the root is successful. The file structure on a 9740 is sufficiently different that the root utility may not work on it. You'll need to search the forums, because if I recall correctly there is another root method possible for the 9740 that doesn't use the root utility.

 

[tpaine]

The OP could also use vampirefo's manual root method thru adb for allwinner tabs. Any of his 7042, 8042 or 9042 root thread methods would work.

 

[j2m_andro]

im soory for not going back so soooon.. >_< took me, obviously, a long time to find an alternative to this.. but finally, i have rooted my mid9740.. though i did not found it here, i still wanna ask..

i used the batch file provided here, and it successfully rooted my tab.. but i used the root utility here to dump my tablet and uploaded it here. (buildnumber: 20130226.185145) My question is that, can i install gapps using it? using the root utility you have provided?? ) i want to know anything just before i start installing em.. thanks very much.. )

 

[j2m_andro]

i used the batch file provided here, and it successfully rooted my tab.. but i used the root utility here to dump my tablet and uploaded it here. (buildnumber: 20130226.185145) My question is that, can i install gapps using it? using the root utility you have provided?? ) i want to know anything just before i start installing em.. thanks very much.. )

okay. so answering my own question.. you can't, or i did it wrong, use the root utility if rooted that way.. my tablet is now under a bootloop.. it is stuck in recovery mode.. and always says

E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't mount /cache/recovery/last_log

and any command i tried- back up- wipe everything - mount everything --- ends up in error.

any help???


edit: i still have the dump files with me

 

[vampirefo.]

I take it, you didn't read this http://www.androidtablets.net/forum...evelopment-index-root-utility.html#post234276

I download your dump just now, took it apart, your tablet has nand lock, had you provided the dump first and gave me time to take it a part I could have saved your tablet.

 

[Traveller]

Given how old my 9742 is, it's no surprise I keep forgetting about the nand lock, despite posting that warning in large, red letters at the top of the post.

 

[vampirefo.]

Given how old my 9742 is, it's no surprise I keep forgetting about the nand lock, despite posting that warning in large, red letters at the top of the post.

Well this is the first full dump of any Coby tablet with nand lock that we have, no other person has made a dump and uploaded.

looking at this dump, the testkey is 4.0.4 while our roms are 4.0.3

ro.build.description=crane_MID9742_TianMa_sc3052-user 4.0.4 IMM76D 20130220 test-keys
ro.build.fingerprint=sc/crane_MID9742_TianMa_sc3052/crane-MID9742-TianMa-sc3052:4.0.4/IMM76D/20130220:user/test-keys

ro.build.date=Wed Feb 20 18:51:54 CST 2013

ro.build.id=IMM76D

ro.build.version.release=4.0.4

I will be able to make a cw recovery from this dump that will now work on the 9740 nand locked tables, but unlikely to help OP. The recovery would need be be installed before the nand becomes locked.

 

[j2m_andro]

I take it, you didn't read this http://www.androidtablets.net/forum...evelopment-index-root-utility.html#post234276

I download your dump just now, took it apart, your tablet has nand lock, had you provided the dump first and gave me time to take it a part I could have saved your tablet.

im so sorrrrryy i made a wrong move.. but i said it, i've been reading it.. the thing is, i found it toooo late when i remembered what i shouldn't have done, since ive got this tablet with builddated in 2013.. >_< but then i had it dumped, so i thought you guys could help me get through this..

so.. can my tablet still be saved???

im so sorry for causing you guys trouble..

--and i just got home earlier..

 

[j2m_andro]

Well this is the first full dump of any Coby tablet with nand lock that we have, no other person has made a dump and uploaded.

...

I will be able to make a cw recovery from this dump that will now work on the 9740 nand locked tables, but unlikely to help OP. The recovery would need be be installed before the nand becomes locked.

and here i am thinking my dumps were just complemented.. >_<

so please please..

 

[j2m_andro]

i found this topic similar to mine.. http://www.androidtablets.net/forum/coby-generation-3/60076-solved-coby-kyros-9740-stuck-cwm.html thread's op said it was solved but didn't saw how he'd done it.. i tried loading the updates provided there to wipe cache partition but no luck.. tried loading the nand.ko file but still no luck..

D:\CobyADB>adb shell
~ # busybox cp /sdcard/nand.ko /tmp/nand.ko
busybox cp /sdcard/nand.ko /tmp/nand.ko
~ # chmod 644 /tmp/nand.ko
chmod 644 /tmp/nand.ko
~ # insmod /tmp/nand.ko
insmod /tmp/nand.ko
insmod: can't insert '/tmp/nand.ko': File exists
~ # lsmod
lsmod
nand 105401 0 - Live 0xbf000000
~ # mount -t ext4 /dev/block/nandh /cache
mount -t ext4 /dev/block/nandh /cache
mount: mounting /dev/block/nandh on /cache failed: No such file or directory
~ # rm -r /cache/*
rm -r /cache/*
rm: can't remove '/cache/*': No such file or directory

and this must have been because of that nand lock right??? will there be no way of saving ma tab?

 

[vampirefo.]

At this time there is no known way to fix your tablet, perhaps liivesuit could fix it, I don't provide livesuit images or support for them. My guess the OP of the thread you referred to either returned his tablet, or built a livesuit image on his own and fixed his tablet.

I have no time frame for when I will build a recovery or look into fixing a tablet with nand lock. This would be a time consuming project that I am just not willing to put much time into right now.

 

[vampirefo.]

Ok after looking through the bootloader, I might have an ideal might work might not.

Sent from my SPH-D710 using Android Phone

 

[vampirefo.]

I can't duplicate this problem on my test tablet.

What I have tried?

I installed your full dump onto my 1042 test tablet, rebooted, edit the screen size, installed my 9740 recovery from stock recovery, no nand lock recovery working as it should.

I then installed your stock recovery again, rooted and installed my cwm 9740 recovery via adb, booting into recovery, no nand lock recovery working as it should.

I then built a recovery based on your stock recovery kernel, removed the nand.ko to force the tablet into a boot loop, but a simple adb push of nand.ko and insmod the nand.ko fixed the problem.

I then built a livesuit image using your dump, flashed my test tablet with the image, resized the screen, repeated all of the above still no nand lock.

So I have no clue on what's triggering nand lock on your tablet, it's not the recovery, bootloader, system, boot.img.

Could be a hidden partition or hardware, if hardware there will never be a fix unless you disassemble the tablet and remove the hardware component that is causing the problem.

If hidden partition, which is most likely the cause, My guess nandj partition, then livesuit would most likely fix your tablet, as it would wipe out all partitions.

 

[dir]

@vampirefo

I'm having the same problem. What I did was:

1) Download and install the CWM recovery you posted here: http://www.androidtablets.net/forum...lopment/58222-cm9-coby-9740-new-recovery.html
2) Download and install CM9 from the same link above, and were getting Can't mount /cache/ issues.

And now the device is on CWM loop. I tried to insmod the nand.ko file you posted from here http://www.androidtablets.net/forum/coby-generation-3/60076-solved-coby-kyros-9740-stuck-cwm.html which loads, but having errors on dmesg. Here are the errors:

/sdcard # lsmod
lsmod
nand 105401 0 - Live 0xbf000000
/sdcard # ls -l /dev/block/
ls -l /dev/block/
brw------- 1 root root 7, 0 Jan 1 17:31 loop0
brw------- 1 root root 7, 1 Jan 1 17:31 loop1
brw------- 1 root root 7, 2 Jan 1 17:31 loop2
brw------- 1 root root 7, 3 Jan 1 17:31 loop3
brw------- 1 root root 7, 4 Jan 1 17:31 loop4
brw------- 1 root root 7, 5 Jan 1 17:31 loop5
brw------- 1 root root 7, 6 Jan 1 17:31 loop6
brw------- 1 root root 7, 7 Jan 1 17:31 loop7
brw------- 1 root root 179, 0 Jan 1 17:31 mmcblk0
brw------- 1 root root 179, 1 Jan 1 17:31 mmcblk0p1
-rw-rw-rw- 1 root root 1088 Jan 1 17:31 nandf
drwxr-xr-x 3 root root 60 Jan 1 17:31 platform
brw------- 1 root root 1, 0 Jan 1 17:31 ram0
brw------- 1 root root 1, 1 Jan 1 17:31 ram1
/sdcard #

<7>[ 291.855256] hello:init_nand_libmodule,21
<7>[ 291.859187] hello:init_nand_libmodule,22
<7>[ 291.863191] [NAND]nand driver, init.
<7>[ 291.866769] [NAND] nand driver version: 0x2, 0x11, data: 20121102
<7>[ 291.872885] [NAND] nand clk request start
<7>[ 291.876908] [NAND] nand clk request ok!
<7>[ 291.880781] [NAND] nand gpio_request
<7>[ 291.884387] [NAND] nand gpio_request fail
<7>[ 291.888406] NAND_RequestDMA ok
<7>[ 291.891806] [NAND] nand driver version: 0x2 0x11
<3>[ 291.896514] IRQ handler type mismatch for IRQ 37
<3>[ 291.901127] current handler: nand
<7>[ 291.901552] [<c003aa64>] (unwind_backtrace+0x0/0x11c) from [<c0091ce8>] (__setup_irq+0x318/0x3c4)
<7>[ 291.901552] [<c0091ce8>] (__setup_irq+0x318/0x3c4) from [<c0091e58>] (request_threaded_irq+0xc4/0x110)
<7>[ 291.901552] [<c0091e58>] (request_threaded_irq+0xc4/0x110) from [<bf00127c>] (nand_init+0xa4/0x18c [nand])
<7>[ 291.901552] [<bf00127c>] (nand_init+0xa4/0x18c [nand]) from [<bf01b02c>] (init_nand_libmodule+0x2c/0x3c [nand])
<7>[ 291.901552] [<bf01b02c>] (init_nand_libmodule+0x2c/0x3c [nand]) from [<c002f490>] (do_one_initcall+0x94/0x164)
<7>[ 291.901552] [<c002f490>] (do_one_initcall+0x94/0x164) from [<c008b7c4>] (sys_init_module+0x164c/0x1810)
<7>[ 291.901552] [<c008b7c4>] (sys_init_module+0x164c/0x1810) from [<c0035100>] (ret_fast_syscall+0x0/0x30)
<7>[ 291.971304] nand interrupte register error
<7>[ 291.975401] [NAND]init_blklayer fail

Could it be a not supported/outdated nand.ko module?