AMLogic Tablets, 7033, 7035, 7065, 7060, and So On: Repair Tablet from SD Card

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
If you have a AMLogic, make and upload your dumps, In the coming weeks I will start modify uploaded recovery.img for these devices so they can be used to recovery the tablet, testers will be needed as I don't have all of these type of tablets, I am hoping one method will cover them all, this is going to be via sdcard.

Aditya Gilra: Unbricking & Upgrading the Gadmei E8HD

Please read and understand above link,

Before you do anything, tablet needs to be rooted.

adb shell

cat /proc/mtd

post outpout include device name eg 7065

to dump tablet

adb shell

su

mkdir /sdcard/dump

cat /dev/mtd/mtd4 > /sdcard/dump/boot.img
cat /dev/mtd/mtd3 > /sdcard/dump/recovery.img
cat /dev/mtd/mtd0 > /sdcard/dump/bootloader.img
busybox tar -czvf /sdcard/dump/coby33_system.tgz /system
#note change to your device.
#note also check your cat /proc/mtd output and adjust backup commands to your tablet if different than mine.

if you have a problem with making system backup you will need to replace busybox.

The goal here is to get these tablets to boot from sdcard.

In the above blog it states this sudo dd if=u-boot.bin of=/dev/sdb

It has came to my attention some users don't know where or what u-boot.bin is, this is just your bootloader.img

so you can rename bootloader.img to u-boot.bin, or change the command to sudo dd if=bootloader.img of=/dev/sdb


Scripts I use to unpack boot.img and recovery.img for 7065

7065 boot/recovery unpack scripts


to flash recovery.img

download

flash_image


Code:
adb push flash_image /data/local/tmp/flash_image
adb push recovery.img /data/local/tmp/recovery.img

adb shell
su

chmod 755 /data/local/tmp/flash_image
/data/local/tmp/flash_image recovery /data/local/tmp/recovery.img

reboot recovery
 
Last edited:

tpaine

Senior Member
Aug 18, 2012
525
130
This is very good news for us Coby owners. Is the system acutally running on the sdcard ? Here's my 8065 output.

shell@android:/ $ cat /proc/mtd
cat /proc/mtd
dev: size erasesize name
mtd0: 00800000 00200000 "bootloader"
mtd1: 00800000 00200000 "logo"
mtd2: 00800000 00200000 "aml_logo"
mtd3: 00800000 00200000 "recovery"
mtd4: 00800000 00200000 "boot"
mtd5: 20400000 00200000 "system"
mtd6: 08000000 00200000 "factory"
mtd7: 20000000 00200000 "cache"
mtd8: 90000000 00200000 "userdata"
mtd9: 123c00000 00200000 "NFTL_Part"
shell@android:/ $

Any help with modified recovery would be appreciated.
 
Last edited:

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
Yes I am currently running from sdcard, below is output.

using same as above method to make sdcard, all I did was add two ext4 partitions one for data other for system, due to time limit in recovery, i just put the sdcard in my lenovo a 2109 booted into recovery, no time limit in that recovery, then mounted sdcard, and and installed the 7065 system dump.

then removed sdcard put into 7065, on the fat32 partition I have boot.img renamed to uImage_recovery and also 7065_system.tgz eg my dump.

Code:
root@android:/ # busybox df -h
Filesystem                Size      Used Available Use% Mounted on
tmpfs                   427.1M     80.0K    427.0M   0% /dev
tmpfs                   427.1M         0    427.1M   0% /mnt/asec
tmpfs                   427.1M         0    427.1M   0% /mnt/obb
/dev/block/mtdblock6    127.9M     25.4M    102.5M  20% /factory
/dev/block/cardblksd2
                       1007.9M    401.9M    554.8M  42% /system
/dev/block/cardblksd3
                          5.1G    217.9M      4.6G   4% /data
/dev/block/mtdblock7    511.5M     36.5M    475.0M   7% /cache
/dev/block/vold/250:37
                          4.1G      1.3G      2.8G  32% /mnt/sdcard
/dev/block/vold/250:37
                          4.1G      1.3G      2.8G  32% /mnt/secure/asec
/dev/block/vold/253:1
                        998.0M    248.9M    749.1M  25% /mnt/sdcard/external_sdcard
root@android:/ #
 

mcclain_ts

Senior Member
Aug 29, 2013
120
42
Does the MID7033 with it's ViMicro fall in here too? I have one with a cracked digitizer,(dis-assembled) and one fully functional.(rooted using the MID7035 method) I've had both units opened up, but didn't notice any chips tagged as "AMLogic". Thanks!(warm smilz)
Both have: ViMicro VC0882BXSA TS0820A 0251118, ViMicro VA7882FL CS0510F 0601228,(GPU) (1) Micron 29F32G08CBACA C, (nand chip on bottom of board) and (4) Hynix DDR3 RAM chips(2on top/2 on bottom of board) The resistive screen/touch I believe might be integral to the main chip.(as I can't locate a separate chip for that, not even with the LCD/digitizer) The WiFi is an Atheros chipAR63020-AL 1B. Sorry, I know this is WAY more info. than necessary.(smilz)

MID7033 -

cat /proc/mtd
dev: size erasesize name
mtd0: 00a00000 00100000 "SysInfo"
mtd1: 00c00000 00100000 "Uboot"
mtd2: 02000000 00100000 "kernel"
mtd3: 01600000 00100000 "RKer"
mtd4: 18200000 00100000 "System"
mtd5: 68100000 00100000 "Data"
mtd6: 20000000 00100000 "Cache"
mtd7: 5b000000 00100000 "user"

Hope your day is going fine too.(smilz)


Okay, did...

mkdir /sdcard/dump
cat /dev/mtd4 > /sdcard/dump/boot.img
cat /dev/mtd3 > /sdcard/dump/recovery.img
cat /dev/mtd0 > /sdcard/dump/bootloader.img
busybox tar -czvf /sdcard/dump/coby33_system.tgz /system


and output was:

# mkdir /sdcard/dump
cat /dev/mtd4 > /sdcard/dump/boot.img
cat /dev/mtd3 > /sdcard/dump/recovery.img
cat /dev/mtd0 > /sdcard/dump/bootloader.img
busybox tar -czvf /sdcard/dump/coby33_system.tgz /systemmkdir /sdcard/dump
mkdir: can't create directory '/sdcard/dump': No space left on device
1|uid=2000 gid=2000 groups=1003,1004,1007,1009,1011,1015,3001,3002,3003,3006@android:/ # cat /dev/mtd4 > /sdcard/dump/boot.img
sh: cannot create /sdcard/dump/boot.img: No such file or directory
1|uid=2000 gid=2000 groups=1003,1004,1007,1009,1011,1015,3001,3002,3003,3006@android:/ # cat /dev/mtd3 > /sdcard/dump/recovery.img

sh: cannot create /sdcard/dump/recovery.img: No such file or directory
1|uid=2000 gid=2000 groups=1003,1004,1007,1009,1011,1015,3001,3002,3003,3006@android:/ # cat /dev/mtd0 > /sdcard/dump/bootloader.i
mg
sh: cannot create /sdcard/dump/bootloader.img: No such file or directory

------------------------------------------------------------------------------------------

Guess I'll need to update "busybox"!LOL


------------------------------------------------------------------------------------------

Okay, tried:

" busybox tar -czvf /sdcard/coby33_system.t
gz /system "

busybox tar -czvf /sdcard/coby33_system.tgz /system
tar: removing leading '/' from member names
system/
system/app/
system/app/NetworkLocation.apk
gzip: short write
tar: write error: Broken pipe

(scratching my head on this one)
 
Last edited:

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
@ mcclain_ts
the bootloader you uploaded is almost the same as the 7065, so it should be able to boot from sdcard, like I posted I don't have all theses tablets, so can only go off of whats uploaded. trial and error, lol.
I have no ideal if you can run sdcard or not, but should be able to boot.
to run from sdcard requires kernel source, then build ext4 modules as the 7065 kernel doesn't support ext4, i was able to patch together a source code to build the modules for my device.
 
Last edited:

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
@mcclain_ts

your dump is different, what commands did you use last time to dump your recovery.img, boot.img and bootloader.img, they were correct just system was wrong, this method your dump will be wrong, one has to look at cat /proc/mtd to see where and what their partitions are.

so for you use the dd commands you used last time, for recovery.img, boot.img, bootloader.img use the tar for system though.
 
Last edited:

mcclain_ts

Senior Member
Aug 29, 2013
120
42
Don't have gapps on this thing yet so I can't get it from googleplay.(sighs)
I guess I'm-a-huntin' APKs boyz! FRESH busybox kind.LOL
 

mcclain_ts

Senior Member
Aug 29, 2013
120
42
" so for you use the dd commands you used last time, for recovery.img, boot.img, bootloader.img use the tar for system though. "

--------------------

Gotcha! Ya, I did use that/those "dd" commands last time. So maybe I don't have to update that busybox and superuser then, after all huh?(smilz) Well, I just hope if I do, it won't foobar the ADB su access I get now. I ran a root check from on the tablet, but it says I don't have root access, and it is not set up correctly. ADB sure allows access though. and rootexplorer has no problems either.

-------------------------I gotta go help my dad put some trim on the house next door, I'll be back in a while my friend.-------------

Thanks for all your patience with me. And ALL the work/time/assistance you devote to all us dummies!LOLLLLL
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
Busy day for me today, working on it.

Same here busy day, much going on trying to do this and work around house, lol.
Hopefully we can get this working on most of these tablets, running from sdcard isn't that important here, the important part it getting theses tablets to boot from sdcard, so they can either be repaired via adb or install zip.
 
Last edited:

tpaine

Senior Member
Aug 18, 2012
525
130
Same here busy day, much going on trying to do this and work around house, lol.
Hopefully we can get this working on most of these tablets, running from sdcard isn't that important here, the important part it getting theses tablets to boot from sdcard, so they can either be repaired via adb or install zip.

I like the lenovo touch. Does the system.tar need to be zipped without boot and recovery ?
 

vampirefo.

Senior Member
Developer
Nov 8, 2011
3,836
1,394
I like the lenovo touch. Does the system.tar need to be zipped without boot and recovery ?

yes this is just a backup, you can use your backup you already made from your 8065, I think you just used .tar not .tgz doesn't really make a difference as long as you use the correct decompression.

Now your modified boot.img would go on the small fat32 partition, the burned in bootloader will look here to see what it needs to load, either boot or recovery, which ever you use must be named uImage_recovery as that is the only name the bootloader will accept.

But before you do any of that make sure you can burn your bootloader to sdcard, and boot either into recovery or regular mode.
 
Last edited:

mcclain_ts

Senior Member
Aug 29, 2013
120
42
Burning the midnight oil, almost!LOL

Alright, finished trimming that other house for the day, and I think (I THINK!) I might have finally nailed this sucker down! Uploading the file to GoogleDocs now...

ADB commands used:

su

dd if=/dev/mtd/mtd2 of=/external_sd/boot.img bs=4096
dd if=/dev/mtd/mtd1 of=/external_sd/bootloader.img bs=4096
dd if=/dev/mtd/mtd3 of=/external_sd/recovery.img bs=4096

busybox tar -czvf /external_sd/system.tgz /system

Zipped, I have a file size of 143,533KB. I tested the zip for any corruption before the upload, and it was all good.
Have a look if you wouldn't mind,(and when you have some free time) and let me know what you think.
Thanks Bud'!(warm smilz) 6:30PM Pacific Standard Time now - 62%. Hey, how do I test this without CWM and your scripts?LOL DOHHHH! LOL

Toddman

-----------------Here's the link: mid7033_dump_test -------------------
 
Last edited:

mcclain_ts

Senior Member
Aug 29, 2013
120
42
On another not, you have any ideas of which tablet maker is second/similar to Coby and it's tablet hardware/internals/systems? Affordability wise too? These Coby tablets are already starting to "dry up", now that they've cleared the shelves, and emptied out the warranty/repair centers to the liquidators. We need to find an alternate. Hopefully a manufacturer that will not be going out of business in the near future!(warm smilz)

----------------------------------------------------------

I guess the next thing for the 7033, is to try and build a working CWM recovery. I bet you're already working on that.(or already got it tucked up your sleeve)
(warm smilz) Damn you're GOOD!!!
 
Last edited:
Top