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

[tpaine]

Gotcha. Very cool. When I get some time I'll do a restore, tho I have no doubts.

Now I see how to test the bootloader, so lots to test. Have you tried the CT bootloader method yet ? I'm stiil looking it over, but I don't speak Spanish. Just a joke , folks...

 

[vampirefo.]

I don't see the difference on the two methods so haven't tried it. He uses one step that is different, he edits the bootloader before flashing, at this point I am not sure why.

After reading his last comment about partition table, I don't plan on using his method, however people can make their own choice.

Sent from my SPH-D710 using Android Tablet

 

[bludot]

fake recovery boots (after update install via the 8065 stock recovery) still not able to boot tablet normally. I tried via a restore and via a update to get back the 8065 dump posted by @tpaine. There are still errors with the data partition.

 

[vampirefo.]

fake recovery boots (after update install via the 8065 stock recovery) still not able to boot tablet normally. I tried via a restore and via a update to get back the 8065 dump posted by @tpaine. There are still errors with the data partition.

Post out from

cat /proc/mtd

Your problems are your data partition, it's corrupt.

You can run from sdcard if your have one, then try to
Sent from my SPH-D710 using Android Tablet

 

[bludot]

I cant. wont boot. i can use the other boot.img(7065) to boot and then post or use the twrp recovery and use the terminal option. What shall I do?

I posted it before and found it:

export PATH=/data/local/bin:$PATH
app_67@android:/ $ export PATH=/data/local/bin:$PATH
app_67@android:/ $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: 20000000 00200000 "system"
mtd6: 08000000 00200000 "factory"
mtd7: 20000000 00200000 "cache"
mtd8: 90000000 00200000 "userdata"
mtd9: 124000000 00200000 "NFTL_Part"
app_67@android:/ $ 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
none /acct cgroup rw,relatime,cpuacct 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
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
ubi0_0 /system ubifs ro,relatime 0 0
/dev/block/mtdblock6 /factory yaffs2 rw,nosuid,nodev,relatime 0 0
ubi1_0 /data ubifs rw,nosuid,nodev,relatime 0 0
/dev/block/mtdblock7 /cache yaffs2 rw,nosuid,nodev,relatime 0 0
none /proc/bus/usb usbfs rw,relatime 0 0
/dev/block/vold/250:37 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/250:37 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/vold/253:1 /mnt/sdcard/external_sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1000,g id=1015,fmask=0002,dmask=0002,allow_utime=0020,cod epage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
app_67@android:/ $

 

[tpaine]

Can you use fake recovery ? What about specially formatted sdcard?

 

[bludot]

fake recovery works(but doesnt fix the tablet). Didnt try the specially formated sdcard yet. will do it tonight i think.

 

[tpaine]

What about formatting sdcard ?

Added:

Just checking out fake recovery. Seems to have all the bells and whistles (save ADB). This is great stuff !

 

[vampirefo.]

What about formatting sdcard ?

Added:

Just checking out fake recovery. Seems to have all the bells and whistles (save ADB). This is great stuff !

It has adb as well.

Sent from my SPH-D710 using Android Tablet

 

[bludot]

It can format the internal sdcard

 

[vampirefo.]

It can format the internal sdcard

If you set up the sdcard, and have another android and a sdcard reader, you can run your tablet from sdcard.

Sent from my SPH-D710 using Android Tablet

 

[bludot]

How? I have an android phone (froyo )

 

[vampirefo.]

How? I have an android phone (froyo )

That is what this whole thread is about.

Sent from my SPH-D710 using Android Tablet

 

[tpaine]

It has adb as well.

After a bit more testing, The fake recovery is very cool. Can not get it to work in ADB in either linux or windows.

Here is a pic



Below is the stock recovery without any ext-sd





And below is Stock recovery with ext-sd or uImage of vampirefo's modified 8065 stock recovery.



Note the E:bootloader errors in both cases. This is not an error of the bootloader, but the bootloader reporting normal argument errors. (at least it looks that way).

These results were the same with the specially prepared card with bootloader, and a simple fat32 16gb card. Too bad we can't buy micro-sd's like we used to buy floppies- 50 at a time for about $5- (showing my age).

You can tell the difference between stock and modified stock by a very short flash just before the recovery screen appears on modified stock from ext-sd.

Am I missing something for ADB to work in fake recovery? My next step is to continue researching the rescue method and work on kernel mods.

@vampirefo did your get your new HD installed ?

 

[bludot]

did you try factory reset to see if the data error comes?