Kobo Original N416 SD Card Image

[tonyyng]

Same behaviour:

tony@tony-Vostro-2520:/mnt/sd/ddrescue$ sudo tar -xvf ddrescue-1.24-gnueabi.tar.gz
ddrescue
ddrescuelog
libstdc++.so.6
libstdc++.so.6.0.24
tony@tony-Vostro-2520:/mnt/sd/ddrescue$ file ddrescue
ddrescue: ELF 32-bit LSB executable, ARM, version 1 (SYSV), dynamically linked (uses shared libs), for GNU/Linux 3.2.0, BuildID[sha1]=0x1d59210c917bd755e14b41c6be47f82b14abaf2e, not stripped
tony@tony-Vostro-2520:/mnt/sd/ddrescue$ ldd ddrescue
        not a dynamic executable
tony@tony-Vostro-2520:/mnt/sd/ddrescue$ cd /mnt
tony@tony-Vostro-2520:/mnt$ sudo umount /dev/sdc1


# mount /dev/mmcblk0p1 /mnt/sd
kjournald starting.  Commit interval 5 seconds
EXT3 FS on mmcblk0p1, internal journal
EXT3-fs: mounted filesystem with ordered data mode.
# cd /mnt/sd/ddrescue/
# ls -ltr
-rwxr-xr-x    1 root     root      9372840 Jan 22  2019 libstdc++.so.6.0.24
-rwxrwxr-x    1 root     root       115248 Mar 22  2019 ddrescue
-rwxrwxr-x    1 root     root        62772 Mar 22  2019 ddrescuelog
lrwxrwxrwx    1 root     root           19 Mar 22  2019 libstdc++.so.6 -> libstdc++.so.6.0.24
-rw-rw-r--    1 root     root      3292105 Mar 22  2019 ddrescue-1.24-gnueabi.tar.gz
# ./ddrescue --force /dev/zero /dev/mtdblock6 --log-events=log.txt
./ddrescue: line 1: syntax error: unexpected word (expecting ")")

[RandomInsano]

Hey guys, just some clarifying stuff on the errors. This one:

> # ./flash_erase
> /bin/sh: ./flash_erase: not found

Means the program loader wasn’t able to find libraries needed to start the app. This usually happens when the app is compiled for one distro and is used on another. The program is good, the library versions aren’t.

> Unexpected word bracket thing (on my cell phone where copy + paste is bad)

I had this last week while trying to run binaries on the Kobo Touch. I’m fairly certain this was due to the ARM binaries being built for an unmatching architecture and the program loader once again giving unhelpful text.


Those I/O errors are not promising at all. That Flash chip is done done. I’m hoping it survives a little longer but I’ve got little hope.


For the system not booting on its own, there should be a variable U-boot uses when it starts up. It should be “bootcmd”. You can dump the value using “printenv” and you can likely find a tutorial on how to save it yourself. You’re so used to U-boot at this point that the commands will be obvious (it’s what you’ve been typing over and over to load and boot the kernel).

[tonyyng]

Originally Posted by RandomInsano

For the system not booting on its own, there should be a variable U-boot uses when it starts up. It should be “bootcmd”. You can dump the value using “printenv” and you can likely find a tutorial on how to save it yourself. You’re so used to U-boot at this point that the commands will be obvious (it’s what you’ve been typing over and over to load and boot the kernel).

This value is set. I haven't been typing it. I have to hit a key (from Tera Term window connected through FTDI) or it autoboots. What is strange is that it does autoboot when it isn't connect.

eBR-1A # printenv
bootcmd=nandr 80000 200000 31000000 m;bootm 31000000
bootdelay=0
baudrate=115200
ethaddr=08:00:3e:26:0a:5b
ipaddr=192.168.0.100
serverip=192.168.0.254
netmask=255.255.255.0
bootfile="uImage"
device_name=EB600EM
device_code=5
NAND_Blocks=0x00002000 8192
base_uboot=0x00000000
size_uboot=0x00080000 4
base_kernel=0x00080000
size_kernel=0x00260000 19
base_pic=0x002e0000
size_pic=0x000c0000 6
base_param=0x003a0000
size_param=0x00020000 1
base_RootFS=0x003c0000
size_RootFS=0x0a000000 1280
base_app=0x0a3c0000
size_app=0x00100000 8
base_Disk=0x0a4c0000
size_Disk=0x35b40000 6874
lgo=loadum 31880000;go 31880000
bootargs=noinitrd root=/dev/mtdblock4 rw rootfstype=yaffs init=/linuxrc console=ttySAC0 controller=2 PA_BB=29 PA_BT=1 FS_BB=30 FS_BT=1280 AP_BB=1310 AP_BT=8 US_BB=1318 US_BT=6874 UVer=ntx-600em-v2.6
PexilFormat=0
PexilWidth=1
ImgBase=30000000
Rotate=0
brd=0
WaveForm=3
ltupipe=15

Environment size: 888/65532 bytes

Thanks to everyone for their help. I've learned a lot from your suggestions.

I'm going to give it up and consign this Kobo to the scrap pile.

[BloodRagg]

could you post a #cat /proc/cpuinfo

im in toolchain hell atm, but this came out properly