I'm not certain whether the title is the right description for this scenario or not. I got my mini a few days ago and very stupidly neglected to make a recovery rom before trying to flash it with the kasty-cube_u30gt_mini-41-104-rooted.zip I downloaded from arctablet.com, using the rkbatchtools 1.5. Here is the log from that:
18:19:06 135 Rockchip Batch Tool v1.5.3.0 start run
18:24:28 990 Rockchip Batch Tool v1.5.3.0 start run
18:35:16 697 **********Upgrade Start Total<1>**********
18:35:16 701 <Layer 2-1-2> Test Device Start
18:35:16 707 <Layer 2-1-2> Test Device Success
18:35:16 710 <Layer 2-1-2> Check Chip Start
18:35:16 714 <Layer 2-1-2> Check Chip Success
18:35:16 719 <Layer 2-1-2> Get FlashInfo Start
18:35:16 720 <LAYER 2-1-2> INFO:FlashInfo: 0 0 0 1 0 10 10 18 1E 4 5
18:35:16 723 <Layer 2-1-2> Get FlashInfo Success
18:35:16 731 <Layer 2-1-2> Prepare IDB Start
18:35:16 732 <LAYER 2-1-2> INFO:CS(1) (8192MB) (MICRON)
18:35:16 733 <LAYER 2-1-2> INFO:CS(3) (8192MB) (MICRON)
18:35:16 746 <Layer 2-1-2> Prepare IDB Success
18:35:16 752 <Layer 2-1-2> Download IDB Start
18:35:17 229 <Layer 2-1-2> Download IDB Success
18:35:17 236 <Layer 2-1-2> Reset Device Start
18:35:18 243 <Layer 2-1-2> Reset Device Success
18:35:18 252 <Layer 2-1-2> Wait For Loader Start
18:35:49 061 <Layer 2-1-2> Wait For Loader Fail
18:35:49 067 **********Upgrade Done Success<0> Fail<1> Time<32355>ms**********
As best I can recall, at that point, the device was no longer recognized by the flashing utility. I tried different cables, different usb ports, and a few different computers, but the utility would not recognize the mini anymore.
I can get to the exceedingly ill android screen, after full power off/on; and from there I can pwr/vol+ into the recovery console. The tablet will not go into flash mode, regardless of various efforts. I understand that some people have had issues with executing the combination and length of button presses and, because of that, I have diligently tried different approaches already.
In the recovery console, wipe data and factory reset does nothing to repair the situation. The other options for updating complain about "unknown volume for [/update.img]; Can't mount /update.img; Can not found firmware image or invalid image." The external storage option also complains of no such file or directory. "Recover system from backup" provides "Checking firmware; E:Invalid image." "Apply update from cache" gives me two directories: "lost+found/" and /recovery/." Both directories appear empty from that screen.
After following various suggestions for getting the tablet properly recognized with drivers in Win7, I gave up and first tried to locate the tablet using lsusb in Linux - there it was as a google device, but I could not properly mount it, despite following a number of how-tos and using adb in Linux looked like a hassle.
I went back to Win7 and used adb and adb drivers to pull it up in an adb console. It is listed as 0123456789ABCDEF recovery. I tried to psuh an update.img file to /sdcard on the mini that I downloaded which was supposed to be the original firmware, minuses the unpleasant metro interface. It appeared to successfully transfer the files. After another attempt to recover and a fail, I tried pushing to the /recovery folder, but it failed due to being out of space. You can imagine my regret and dismay.
I cannot open a shell, because adb reports: "- exec '/system/bin/sh' failed: no such file or directory <2> -" In its current state, could I push the needed files to run a shell, or would that work? If so could someone point me to where to download or provide an attachment?
I did use the "adb pull /" command and got quite a few files in the cache, sys, and tmp directories , but it skipped "special" files. Some files would not copy due to i/o errors, according to what I can still see in the cmd window. "adb pull /sdcard" resulted in "remote object /sdcard does not exist" response.
Command "adb pull /system" and "adb pull /mnt" both gave: "0 files pulled. 0 files skipped." Maybe I am doing that wrong, though.
I have ordered, from Amazon, torx T2 and T3 bits to attempt to open it up and short the pins to perform a hard reset, but I would much prefer to get this thing going without disassembly, if at all possible.
Is there anything I can try to get this tablet running via adb--maybe pushing a recovery.img or update.img to the /cache/recovery folder (just has empty last install, last log, and log files right now)? Or should I just wait for those Torx to arrive? I'm afraid this might be some sort of hardware failure, so am really reluctant to open the mini up, before trying to get a refund or replacement.
18:19:06 135 Rockchip Batch Tool v1.5.3.0 start run
18:24:28 990 Rockchip Batch Tool v1.5.3.0 start run
18:35:16 697 **********Upgrade Start Total<1>**********
18:35:16 701 <Layer 2-1-2> Test Device Start
18:35:16 707 <Layer 2-1-2> Test Device Success
18:35:16 710 <Layer 2-1-2> Check Chip Start
18:35:16 714 <Layer 2-1-2> Check Chip Success
18:35:16 719 <Layer 2-1-2> Get FlashInfo Start
18:35:16 720 <LAYER 2-1-2> INFO:FlashInfo: 0 0 0 1 0 10 10 18 1E 4 5
18:35:16 723 <Layer 2-1-2> Get FlashInfo Success
18:35:16 731 <Layer 2-1-2> Prepare IDB Start
18:35:16 732 <LAYER 2-1-2> INFO:CS(1) (8192MB) (MICRON)
18:35:16 733 <LAYER 2-1-2> INFO:CS(3) (8192MB) (MICRON)
18:35:16 746 <Layer 2-1-2> Prepare IDB Success
18:35:16 752 <Layer 2-1-2> Download IDB Start
18:35:17 229 <Layer 2-1-2> Download IDB Success
18:35:17 236 <Layer 2-1-2> Reset Device Start
18:35:18 243 <Layer 2-1-2> Reset Device Success
18:35:18 252 <Layer 2-1-2> Wait For Loader Start
18:35:49 061 <Layer 2-1-2> Wait For Loader Fail
18:35:49 067 **********Upgrade Done Success<0> Fail<1> Time<32355>ms**********
As best I can recall, at that point, the device was no longer recognized by the flashing utility. I tried different cables, different usb ports, and a few different computers, but the utility would not recognize the mini anymore.
I can get to the exceedingly ill android screen, after full power off/on; and from there I can pwr/vol+ into the recovery console. The tablet will not go into flash mode, regardless of various efforts. I understand that some people have had issues with executing the combination and length of button presses and, because of that, I have diligently tried different approaches already.
In the recovery console, wipe data and factory reset does nothing to repair the situation. The other options for updating complain about "unknown volume for [/update.img]; Can't mount /update.img; Can not found firmware image or invalid image." The external storage option also complains of no such file or directory. "Recover system from backup" provides "Checking firmware; E:Invalid image." "Apply update from cache" gives me two directories: "lost+found/" and /recovery/." Both directories appear empty from that screen.
After following various suggestions for getting the tablet properly recognized with drivers in Win7, I gave up and first tried to locate the tablet using lsusb in Linux - there it was as a google device, but I could not properly mount it, despite following a number of how-tos and using adb in Linux looked like a hassle.
I went back to Win7 and used adb and adb drivers to pull it up in an adb console. It is listed as 0123456789ABCDEF recovery. I tried to psuh an update.img file to /sdcard on the mini that I downloaded which was supposed to be the original firmware, minuses the unpleasant metro interface. It appeared to successfully transfer the files. After another attempt to recover and a fail, I tried pushing to the /recovery folder, but it failed due to being out of space. You can imagine my regret and dismay.
I cannot open a shell, because adb reports: "- exec '/system/bin/sh' failed: no such file or directory <2> -" In its current state, could I push the needed files to run a shell, or would that work? If so could someone point me to where to download or provide an attachment?
I did use the "adb pull /" command and got quite a few files in the cache, sys, and tmp directories , but it skipped "special" files. Some files would not copy due to i/o errors, according to what I can still see in the cmd window. "adb pull /sdcard" resulted in "remote object /sdcard does not exist" response.
Command "adb pull /system" and "adb pull /mnt" both gave: "0 files pulled. 0 files skipped." Maybe I am doing that wrong, though.
I have ordered, from Amazon, torx T2 and T3 bits to attempt to open it up and short the pins to perform a hard reset, but I would much prefer to get this thing going without disassembly, if at all possible.
Is there anything I can try to get this tablet running via adb--maybe pushing a recovery.img or update.img to the /cache/recovery folder (just has empty last install, last log, and log files right now)? Or should I just wait for those Torx to arrive? I'm afraid this might be some sort of hardware failure, so am really reluctant to open the mini up, before trying to get a refund or replacement.
Comment