WelcomeWelcome | FAQFAQ | DownloadsDownloads | WikiWiki

Author Topic: [Project cancelled] my microsd card and my failures  (Read 16577 times)

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #15 on: November 24, 2012, 06:13:38 PM »
roberts

thankyou for your link and questions I will answer them soon

2) just to complete my current issues here is what I did immediately after multicard reading report with fdisk showing no partition

I pulled micro out of multi reader and into single SD reader with adaptor etc

Code: [Select]
ls -al /dev/disk/by-path
total 0
drwxr-xr-x 2 root root 180 Nov 25 07:06 .
drwxr-xr-x 6 root root 120 Nov 25 06:55 ..
lrwxrwxrwx 1 root root   9 Nov 25 06:55 pci-0000:00:1d.7-usb-0:7.4:1.0-scsi-0:0:0:0 -> ../../sdb
lrwxrwxrwx 1 root root   9 Nov 25 07:06 pci-0000:00:1d.7-usb-0:8:1.0-scsi-0:0:0:0 -> ../../sdc
lrwxrwxrwx 1 root root  10 Nov 25 07:06 pci-0000:00:1d.7-usb-0:8:1.0-scsi-0:0:0:0-part1 -> ../../sdc1
lrwxrwxrwx 1 root root   9 Nov 25 06:55 pci-0000:00:1f.1-scsi-0:0:0:0 -> ../../sr0
lrwxrwxrwx 1 root root   9 Nov 25 07:02 pci-0000:00:1f.2-scsi-0:0:0:0 -> ../../sda
lrwxrwxrwx 1 root root  10 Nov 25 06:55 pci-0000:00:1f.2-scsi-0:0:0:0-part1 -> ../../sda1
lrwxrwxrwx 1 root root  10 Nov 25 06:55 pci-0000:00:1f.2-scsi-0:0:0:0-part2 -> ../../sda2

new VERDICT

Can not use micro sd direct into multi reader

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #16 on: November 24, 2012, 07:26:54 PM »
ok lets see what I have

connect lead to OTG port and connect usb to PC running TC and run lsusb
Code: [Select]
lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 1bcf:0007 Sunplus Innovation Technology Inc. Optical Mouse
Bus 002 Device 002: ID 046d:c315 Logitech, Inc. Classic New Touch Keyboard
Bus 001 Device 011: ID 18d1:0003 Google Inc.

ok we have 18d1:0003 Google Inc. but google search suggests thats just a Chinese company

2) so went into android and looked but could not see anything but I am not an android expert
so downloaded an app called elixir2 which can generate a report and email you (me)

here are some contents

Quote
Processor

Processor:   ARMv7 Processor rev 2 (v7l)
Freq range:   30 MHz - 960 MHz
Current freq:   912 MHz
BogoMIPS:   906.46
Available processors:   1
Available processors:   1

Build

Board:   crane
Bootloader:   unknown
Brand:   softwinners
CPU ABI:   armeabi-v7a
CPU ABI2:   armeabi
Device:   apollo-mele
Display:   apollo_mele-eng 4.0.4 IMM76D 20120910 test-keys
Hardware:   sun4i
Host:   pqlabs
Id:   IMM76D
Manufacturer:   unknown
Model:   SoftwinerEvb
Product:   apollo_mele
Radio:   
SDK version:   15
Serial:   unknown
Tags:   test-keys
Time:   Sep 10, 2012 9:46:33 PM
Type:   eng
User:   lixg
Version:   4.0.4
Version codename:   REL
Version incremental:   20120910

EDIT a quick google shows
http://en.wikipedia.org/wiki/AllWinner_A1X  mentions mele sunxi etc
http://en.wikipedia.org/wiki/Rockchip   mentions variious processor specs

verdict....I do not have the rockchip so must have the allwinner?
« Last Edit: November 24, 2012, 07:36:50 PM by aus9 »

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: investigating my microsd card and my failures
« Reply #17 on: November 24, 2012, 08:42:57 PM »
sun4i, You have an allwinner. It should boot from a properly prepared sd card with an appropriate script.bin.
10+ Years Contributing to Linux Open Source Projects.

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #18 on: November 24, 2012, 08:52:54 PM »
yeah that is what I hope too

1) Have I tried other distro images yes no success

2) Just did a rather strange test but it might lead me to believe its my android card slot that might be faulty?

Back in TC, check device pathway
dd image onto microsd
Instead of over-writing the script.bin  .....which is what I have always done
I elected this test....to place my true script.bin as extra file called script0.bin

3) light tests with current sd card were
no lights for kb so ignored and mouse is as follows
power cord in...mouse on
when screen goes "blank"....mouse goes off
when android splashes re-apppear....mouse is on

4) reboot into TC with microsd card
I have lost the extra script bin

OK not much of test but something funny is happening

redo the overwrite to put correct (my) script.bin into folder
ensure umount yes

redo the tests............same negative result

Each time android completes boot....it claims usb storage is damaged

I now wonder if I have been lucky enough to get a lemon?

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #19 on: November 25, 2012, 12:32:43 AM »
ok last test for today

I amended my "alternative way to get script.bin" post to include a md5sum check
before you copy to usb stick
after you copy to usb stick
and
after you have made a dd image to microsd carrd

Therefore I can eliminate a bad copy of the script.bin

In that other post I also copied over a number of files including one called magic.bin

Code: [Select]
file magic.bin
magic.bin: ASCII text, with very long lines, with no line terminators

strings magic.bin
a1sp9maKde37ee6c-6dc4-4d74-86f0-db32116efb53e0e40ccf-7a66-406b-88c3-415b4a62a8f7777622ab-6bd0-464f-9da5-4cc203e855ea8ce5671f-e8b5-442e-9300-2ee6836c538aabf5f481-c961-4895-8245-631f74851d0c2bbb4229-55a8-4929-a165-3f406f0ee441ab5d09a9-c4dc-44bb-a175-cfb7c978a062329ea51e-1ddc-44ff-ac09-9ef7b64e0c52a712e47d-13f7-4490-9fea-bdcd587b8a4a5ed4d4e6-0ba3-45c5-a778-3232a42d4d960a9b7466-d7b3-4087-b8ff-c51763b852a50cd78bb6-a6d5-43a8-8661-fb91abd346433e8a86ee-711e-49c1-ad54-b59dd01fe513e22b0d8b-647f-4417-a115-9806c5d64eec

I wonder if this acts like a magic cookie that some distros have?

I have just spotted its size its 512 bytes....the same size of a stage1 grub bootloader file, in other words a MBR
« Last Edit: November 25, 2012, 12:37:57 AM by aus9 »

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #20 on: November 25, 2012, 02:46:09 AM »
I am (almost) glad others seem to have similar issue now to peek further
http://forum.doozan.com/read.php?6,9762,9762

it concerns "MK802 - Cannot boot anything but Android"

http://comments.gmane.org/gmane.comp.hardware.netbook.arm/4181
« Last Edit: November 25, 2012, 02:47:53 AM by aus9 »

Offline roberts

  • Retired Admins
  • Hero Member
  • *****
  • Posts: 7361
  • Founder Emeritus
Re: investigating my microsd card and my failures
« Reply #21 on: November 25, 2012, 09:52:23 AM »
I suppose an alternative would be to flash nand.
Have you explored LiveSuite ? Have you download your MK802's firmware in case you needed to re-flash via LiveSuite? If so, and are familiar with the procedure then might to possible to flash linux. I recall, some at Miniand were atempting such.

I hope that this is not a trend with other, newer, Allwinner devices. Locked down to only Android.
10+ Years Contributing to Linux Open Source Projects.

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #22 on: November 25, 2012, 07:42:45 PM »
I have not had a chance to do it yet

thanks for thinking of me

I have one last test, I should have done this earlier but can't report the results to after work day

each time I have let android boot....every time in fact, it says usb storage is damaged and to reformat it
but does not give me an option in the android system settings according to my eyesight

I found this site mentioning the size limits of fat/vfat
http://www.genie9.com/support/kb/KnowledgeArticle.aspx?KBID=113+

and this link says android only supports fat32
http://www.envythisstuff.com/techtalk/mk802faq.html#microsdcard

and mentions firmware
a little bit below

as you can see the fat32 test will be easy but the firmware may bork my device

below in above link is the firmware instruction you click a button in a hole etc

2) if fat32 test fails.....I might just give this to my dad as his wife has some memory issues and I have already downloaded some free apps on android to see if they are suitable

eg
memory training games
sudoku

but will decide later

thanks for reading
« Last Edit: November 25, 2012, 07:45:55 PM by aus9 »

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #23 on: November 26, 2012, 02:51:02 AM »
ok before I start to test if android knows I have a working microsd slot lets format the microsd card to fat32 as per above post

Initially I got some codepage error but maro already had a work-a-round as per
http://forum.tinycorelinux.net/index.php/topic,11128.msg58340.html#msg58340

I also had some other errors saying missing files fixed in below command
so as I prefer gparted my new command is

Code: [Select]
tce-load -i gparted dosfstools mtools glibc_gconv
sudo gparted

microsd formatted as fat32 ending in cylinder boundary
with no files on storage card, boot up of android has no reports of damaged storage device for sandisk 8G microsd
« Last Edit: November 26, 2012, 02:53:30 AM by aus9 »

aus9

  • Guest
Re: investigating my microsd card and my failures
« Reply #24 on: November 26, 2012, 03:36:26 AM »
ok so I add in linux some media files ....mp3  wav  mp4 flv

repower the microsd card.....and it says damaged

I give up

I won't try the firmware as the firmware rev2 does not state any thing that might resolve issues with the microsd slot
it does mention shutdown but not as Official firmware
http://liliputing.com/2012/08/uberoid-custom-rom-for-the-mk802-android-4-0-without-any-bloat.html

does not matter as I give up

this becomes a xmas pressie for daddy