help needed A20 stuck on logo ADB shell not working - GSM-Forum

Insomniacno1 · 01-07-2021, 08:48

Unfortunately my Minami M-750 Tablet got stuck on logo again and this time the solution from my previous post on slatedroid is not working, because it seem some of the system folders are empty and ADB shell is not functioning correctly!
https://www.slatedroid.com/topic/110.../?hl=allwinner

I'm now running Xubuntu 16.04 64bit and have newest Android SDK, android tools and fastboot installed I also have Qtadb. I have a second SSD with windows 7 Pro 64bit.

For the last 3 months on and off I have tried to revive my old Minami A20 tablet that is stuck on logo. From recovery I can factory reset it and wipe data cache, but no matter how many times I try it is still stuck on logo.

Btw, it came rooted from the factory, but su had to be re-installed, I later made su system file.

Stericsson busybox is installed too I just don't know which version after all the factory reset.

I did enable usb debug when the tablet was working, but don't know if that is still enabled after factory reset.

I have a full Uberizer firmware backup rom dump but I can't get it recognized in Windows 7 Pro 64bit as other than Alcatel ADB interface and that is not enough for Uberizer to recognize it, I have tried all sorts of usb drivers from Alwinner stock to Google to alcatel and even some generic ones, Also tried the Composite drivers and going to recovery on the tablet to see if that would help uberizer recognize it, to no avail.

Uberizer for Windows firmware backup(I can run Uberizer in Wine but it does not have access to the tablet), (There is no working Uberizer for linux), the Rom dump files are:

boot.img
bootloader.img
data.img
recovery.img
system.img

My problems are the following:

I can't get it recognized correctly in windows due to stuck on logo and incorrect usb drivers / linux(here i can browse some folders but not all and QtADB is not recognizing the tablet correctly nor do ADB from terminal only serial number).

I can't seem to find the correct firmware for this model.

In stock recovery windows 7 recognizes this as Alcatel ADB interface, Uberizer can't see anything.

In stock recovery on the top of everything else it reads:

SDK : MID-A20-Android4.2-V1.3
Android system recovery <3e>
Volume up/down to move highlight;
enter button to select (The interface is touch based scrolling and
Power is enter, the tablet only have Power and Home button, no volume buttons)

The options are:
- reboot system now
- apply update from ADB (also known as sideload)
- wipe data/factory reset
- wipe cache partition
- apply update from internal storage
- apply update from cache

Some research seem to indicate that this is part of the multiple devices called K70 or A70X or A70XH

Ok, I'm not a shark on how to do this so need some guidance, could someone help me out?

adb in linux can show me files by adb ls / but some folders are not opening like:

/vendor
/etc
/system
/init

The rest open:
/config
/cache
/acct
/d
/sdcard
/mnt
/sys
/sbin
/proc
/data
/root
/dev

Funny thing is that Qtadb shows all partitions as empty and can't find any files. I tried Mydroid but that one doesn't even find the device.

adb can find the device and list it as

adb devices
List of devices attached
20080411 device

Qtadb logcat shows:

10:57:42.693 exec '/system/bin/sh' failed: No such file or directory 2 2) -

adb shell shows :
- exec '/system/bin/sh' failed: No such file or directory (2) -

So none of the shell commands are working

Device spec and OS iinfo:
http://specdevice.com/showspec.php?i...3-c58700000000

Hope someone can help me out - thank you

Jan

adb ls /.*.*
000041ed 00000000 5e6ee094 .
000041ed 00000000 5e6ee094 ..
00004140 00000000 5e6ee093 config
000041f8 00000000 5e6ee094 cache
000041ed 00000000 5e6ee093 acct
0000a1ff 0000000e 5e6ee093 vendor
0000a1ff 00000011 5e6ee093 d
0000a1ff 0000000b 5e6ee093 etc
0000a1ff 0000000b 5e6ee093 sdcard
000041fd 00000000 5e6ee093 mnt
000081a4 0004c3ae 00000000 zet622x.ko
000081a4 000003ec 00000000 ueventd.sun7i.rc
000081a4 00000fb8 00000000 ueventd.rc
000081a4 00000110 00000000 ueventd.goldfish.rc
000041ed 00001000 576be140 system
000041ed 00000000 5e6ee093 sys
000081a4 000248d4 00000000 ssd253x-ts.ko
000081a4 00028660 00000000 sis925x.ko
000041e8 00000000 00000000 sbin
0000416d 00000000 00000000 proc
000081a4 0009f1fd 00000000 nand.ko
000081a4 0003c142 00000000 lcd.ko
000081e8 00258000 00000000 initlogo.rle
000081e8 00000f4b 00000000 init.usb.rc
000081e8 00000703 00000000 init.trace.rc
000081e8 00000d75 00000000 init.sun7i.usb.rc
000081e8 00001746 00000000 init.sun7i.rc
000081e8 00004f9b 00000000 init.rc
000081e8 000009b7 00000000 init.goldfish.rc
000081e8 0001bc68 00000000 init
000081a4 00006ef3 00000000 inet_ctp.ko
000081a4 00075788 00000000 hdmi.ko
000081a4 00020cc1 00000000 gt9xx.ko
000081a4 00020874 00000000 gt82x.ko
000081a4 000215a2 00000000 gt801_2plus1.ko
000081a4 00078435 00000000 gslX680new.ko
000081a4 000d5ee3 00000000 gslX680.ko
000081a4 00050f85 00000000 ft5x06_ts.ko
000081a4 00046dcb 00000000 ft5x02.ko
000081a4 0007699b 00000000 ft5402.ko
000081a4 00351e78 00000000 disp.ko
000081a4 00000074 00000000 default.prop
000041f9 00000000 5e6ee094 data
000081a4 0002a66f 00000000 ct36x_ts.ko
000081a4 00020655 00000000 byd693x-ts.ko
000041c0 00000000 52189ece root
000041ed 00000c30 5e6ee094 dev

cat /proc/partitions
major minor #blocks name

7 0 2111 loop0
7 1 5229 loop1
7 2 4190 loop2
7 3 11466 loop3
7 4 2111 loop4
7 5 2111 loop5
7 6 3150 loop6
7 7 11466 loop7
93 0 16384 nanda
93 8 16384 nandb
93 16 16384 nandc
93 24 638976 nandd
93 32 1048576 nande
93 40 16384 nandf
93 48 32768 nandg
93 56 524288 nandh
93 64 262144 nandi
93 72 4882432 nandj
179 0 30760960 mmcblk0
179 1 30756411 mmcblk0p1
254 0 2110 dm-0
254 1 5229 dm-1
254 2 4189 dm-2
254 3 11466 dm-3
254 4 2110 dm-4
254 5 2110 dm-5
254 6 3150 dm-6
254 7 11466 dm-7
7 8 21861 loop8
254 8 21861 dm-8
7 9 4190 loop9
254 9 4189 dm-9
7 10 6269 loop10
254 10 6268 dm-10
7 11 3150 loop11
254 11 3150 dm-11
7 12 2111 loop12
254 12 2110 dm-12
7 13 7308 loop13
254 13 7308 dm-13
7 14 32256 loop14
254 14 32256 dm-14
7 15 2111 loop15
254 15 2110 dm-15
7 16 3150 loop16
254 16 3150 dm-16
7 17 45770 loop17
254 17 45769 dm-17
7 18 2111 loop18
254 18 2110 dm-18
7 19 2111 loop19
254 19 2110 dm-19
7 20 19782 loop20
254 20 19782 dm-20
7 21 28098 loop21
254 21 28098 dm-21
7 22 15624 loop22
254 22 15624 dm-22
7 23 6269 loop23
254 23 6268 dm-23
7 24 14585 loop24
254 24 14584 dm-24
7 25 6269 loop25
254 25 6268 dm-25
7 26 2111 loop26
254 26 2110 dm-26
7 27 37454 loop27
254 27 37453 dm-27
7 28 23940 loop28
254 28 23940 dm-28
7 29 8348 loop29
254 29 8347 dm-29
root@android:/ #

root@android:/ # cat /proc/cmdline
console=ttyS0,115200 root=/dev/system init=/init loglevel=4 partitions=bootloader@nanda:env@nandb:boot@nandc:s ystem@nandd:data@nande:misc@nandf:recovery@nandg:c ache@nandh:databk@nandi:UDISK@nandj
root@android:/ #

01-07-2021, 08:48	#1 (permalink)
Insomniacno1 Junior Member Join Date: Jan 2009 Posts: 16 Member: 952897 Status: Offline Thanks Meter: 2	help needed A20 stuck on logo ADB shell not working Unfortunately my Minami M-750 Tablet got stuck on logo again and this time the solution from my previous post on slatedroid is not working, because it seem some of the system folders are empty and ADB shell is not functioning correctly! https://www.slatedroid.com/topic/110.../?hl=allwinner I'm now running Xubuntu 16.04 64bit and have newest Android SDK, android tools and fastboot installed I also have Qtadb. I have a second SSD with windows 7 Pro 64bit. For the last 3 months on and off I have tried to revive my old Minami A20 tablet that is stuck on logo. From recovery I can factory reset it and wipe data cache, but no matter how many times I try it is still stuck on logo. Btw, it came rooted from the factory, but su had to be re-installed, I later made su system file. Stericsson busybox is installed too I just don't know which version after all the factory reset. I did enable usb debug when the tablet was working, but don't know if that is still enabled after factory reset. I have a full Uberizer firmware backup rom dump but I can't get it recognized in Windows 7 Pro 64bit as other than Alcatel ADB interface and that is not enough for Uberizer to recognize it, I have tried all sorts of usb drivers from Alwinner stock to Google to alcatel and even some generic ones, Also tried the Composite drivers and going to recovery on the tablet to see if that would help uberizer recognize it, to no avail. Uberizer for Windows firmware backup(I can run Uberizer in Wine but it does not have access to the tablet), (There is no working Uberizer for linux), the Rom dump files are: boot.img bootloader.img data.img recovery.img system.img My problems are the following: I can't get it recognized correctly in windows due to stuck on logo and incorrect usb drivers / linux(here i can browse some folders but not all and QtADB is not recognizing the tablet correctly nor do ADB from terminal only serial number). I can't seem to find the correct firmware for this model. In stock recovery windows 7 recognizes this as Alcatel ADB interface, Uberizer can't see anything. In stock recovery on the top of everything else it reads: SDK : MID-A20-Android4.2-V1.3 Android system recovery <3e> Volume up/down to move highlight; enter button to select (The interface is touch based scrolling and Power is enter, the tablet only have Power and Home button, no volume buttons) The options are: - reboot system now - apply update from ADB (also known as sideload) - wipe data/factory reset - wipe cache partition - apply update from internal storage - apply update from cache Some research seem to indicate that this is part of the multiple devices called K70 or A70X or A70XH Ok, I'm not a shark on how to do this so need some guidance, could someone help me out? adb in linux can show me files by adb ls / but some folders are not opening like: /vendor /etc /system /init The rest open: /config /cache /acct /d /sdcard /mnt /sys /sbin /proc /data /root /dev Funny thing is that Qtadb shows all partitions as empty and can't find any files. I tried Mydroid but that one doesn't even find the device. adb can find the device and list it as adb devices List of devices attached 20080411 device Qtadb logcat shows: 10:57:42.693 exec '/system/bin/sh' failed: No such file or directory 2 2) - adb shell shows : - exec '/system/bin/sh' failed: No such file or directory (2) - So none of the shell commands are working Device spec and OS iinfo: http://specdevice.com/showspec.php?i...3-c58700000000 Hope someone can help me out - thank you Jan adb ls /.. 000041ed 00000000 5e6ee094 . 000041ed 00000000 5e6ee094 .. 00004140 00000000 5e6ee093 config 000041f8 00000000 5e6ee094 cache 000041ed 00000000 5e6ee093 acct 0000a1ff 0000000e 5e6ee093 vendor 0000a1ff 00000011 5e6ee093 d 0000a1ff 0000000b 5e6ee093 etc 0000a1ff 0000000b 5e6ee093 sdcard 000041fd 00000000 5e6ee093 mnt 000081a4 0004c3ae 00000000 zet622x.ko 000081a4 000003ec 00000000 ueventd.sun7i.rc 000081a4 00000fb8 00000000 ueventd.rc 000081a4 00000110 00000000 ueventd.goldfish.rc 000041ed 00001000 576be140 system 000041ed 00000000 5e6ee093 sys 000081a4 000248d4 00000000 ssd253x-ts.ko 000081a4 00028660 00000000 sis925x.ko 000041e8 00000000 00000000 sbin 0000416d 00000000 00000000 proc 000081a4 0009f1fd 00000000 nand.ko 000081a4 0003c142 00000000 lcd.ko 000081e8 00258000 00000000 initlogo.rle 000081e8 00000f4b 00000000 init.usb.rc 000081e8 00000703 00000000 init.trace.rc 000081e8 00000d75 00000000 init.sun7i.usb.rc 000081e8 00001746 00000000 init.sun7i.rc 000081e8 00004f9b 00000000 init.rc 000081e8 000009b7 00000000 init.goldfish.rc 000081e8 0001bc68 00000000 init 000081a4 00006ef3 00000000 inet_ctp.ko 000081a4 00075788 00000000 hdmi.ko 000081a4 00020cc1 00000000 gt9xx.ko 000081a4 00020874 00000000 gt82x.ko 000081a4 000215a2 00000000 gt801_2plus1.ko 000081a4 00078435 00000000 gslX680new.ko 000081a4 000d5ee3 00000000 gslX680.ko 000081a4 00050f85 00000000 ft5x06_ts.ko 000081a4 00046dcb 00000000 ft5x02.ko 000081a4 0007699b 00000000 ft5402.ko 000081a4 00351e78 00000000 disp.ko 000081a4 00000074 00000000 default.prop 000041f9 00000000 5e6ee094 data 000081a4 0002a66f 00000000 ct36x_ts.ko 000081a4 00020655 00000000 byd693x-ts.ko 000041c0 00000000 52189ece root 000041ed 00000c30 5e6ee094 dev cat /proc/partitions major minor #blocks name 7 0 2111 loop0 7 1 5229 loop1 7 2 4190 loop2 7 3 11466 loop3 7 4 2111 loop4 7 5 2111 loop5 7 6 3150 loop6 7 7 11466 loop7 93 0 16384 nanda 93 8 16384 nandb 93 16 16384 nandc 93 24 638976 nandd 93 32 1048576 nande 93 40 16384 nandf 93 48 32768 nandg 93 56 524288 nandh 93 64 262144 nandi 93 72 4882432 nandj 179 0 30760960 mmcblk0 179 1 30756411 mmcblk0p1 254 0 2110 dm-0 254 1 5229 dm-1 254 2 4189 dm-2 254 3 11466 dm-3 254 4 2110 dm-4 254 5 2110 dm-5 254 6 3150 dm-6 254 7 11466 dm-7 7 8 21861 loop8 254 8 21861 dm-8 7 9 4190 loop9 254 9 4189 dm-9 7 10 6269 loop10 254 10 6268 dm-10 7 11 3150 loop11 254 11 3150 dm-11 7 12 2111 loop12 254 12 2110 dm-12 7 13 7308 loop13 254 13 7308 dm-13 7 14 32256 loop14 254 14 32256 dm-14 7 15 2111 loop15 254 15 2110 dm-15 7 16 3150 loop16 254 16 3150 dm-16 7 17 45770 loop17 254 17 45769 dm-17 7 18 2111 loop18 254 18 2110 dm-18 7 19 2111 loop19 254 19 2110 dm-19 7 20 19782 loop20 254 20 19782 dm-20 7 21 28098 loop21 254 21 28098 dm-21 7 22 15624 loop22 254 22 15624 dm-22 7 23 6269 loop23 254 23 6268 dm-23 7 24 14585 loop24 254 24 14584 dm-24 7 25 6269 loop25 254 25 6268 dm-25 7 26 2111 loop26 254 26 2110 dm-26 7 27 37454 loop27 254 27 37453 dm-27 7 28 23940 loop28 254 28 23940 dm-28 7 29 8348 loop29 254 29 8347 dm-29 root@android:/ # root@android:/ # cat /proc/cmdline console=ttyS0,115200 root=/dev/system init=/init loglevel=4 partitions=bootloader@nanda:env@nandb:boot@nandc:s ystem@nandd:data@nande:misc@nandf:recovery@nandg:c ache@nandh:databk@nandi:UDISK@nandj root@android:/ # Last edited by Insomniacno1; 01-07-2021 at 08:56.