MobileRead Forums - View Single Post

hieronymos · 11-17-2011, 09:02 AM

Maybe I have a very special device then. *shrugs*.

The log for the reset however contains the explanations for your image; the mount table. I'll just dump the whole log here if I may.
Somehow it explains the unallocated space. /tmp could probably be on the SD instead of the RAM without any problem - maybe they're still working on that.

Spoiler:

I'll go and see what's inside that recovery_backup_signed.zip - maybe I can simply replace a few of the contents with Clockworkmod.

P.S.: stevebiggs, probably the internal SD card is too slow to play back 3GB / (the seconds your film takes). Try streaming it from another computer - a 1.8GB file from my UPnP server worked fine here.

P.S2: Turn out the recovery .zip is particularly interesting. The only file I can mount is system.img - the other files are in some other format than ext or yaffs or simply are corrupt. System.img contains a bluetooth.apk (indicating it might be the freescale image) and no bloat. Just two kobo files.

11-17-2011, 09:02 AM	#46
hieronymos Groupie Posts: 186 Karma: 45172 Join Date: Nov 2011 Device: Kobo Vox	Maybe I have a very special device then. shrugs. The log for the reset however contains the explanations for your image; the mount table. I'll just dump the whole log here if I may. Somehow it explains the unallocated space. /tmp could probably be on the SD instead of the RAM without any problem - maybe they're still working on that. Spoiler: Build: freescale/imx51_bbg/imx51_bbg:2.3.3/GRI40/eng.CAN.20111027.172304.39765:eng/test-keys Hardware: BBG Bootloader: unknown Radio: unknown Kernel: Linux version 2.6.35.3 (victor@vgonzalez-ubuntu) (gcc version 4.4.3 (GCC) ) K01.01.20110801 Factory data reset 0:Install Success Starting recovery on Wed Nov 16 14:52:16 2011 framebuffer: fd 4 (1024 x 600) recovery filesystem table ========================= 0 /tmp ramdisk (null) (null) 1 /system ext4 /dev/block/mmcblk0p1 (null) 2 /recovery ext4 /dev/block/mmcblk0p2 (null) 3 /sdcard vfat /dev/block/mmcblk0p4 (null) 4 /data ext4 /dev/block/mmcblk0p5 (null) 5 /cache ext4 /dev/block/mmcblk0p6 (null) 6 /misc emmc /dev/block/mmcblk0 (null) 7 /extsd vfat /dev/block/mmcblk1p1 (null) I:Got arguments from boot message Command: "recovery" "--wipe_data" Checking Sideload : E:failed to mount /extsd (No such file or directory) file is not exist Wipe data/cache ro.sf.lcd_density=240 ro.tether.denied=1 ro.config.notification_sound=Razzle.ogg ro.secure=0 ro.allow.mock.location=1 ro.debuggable=0 persist.service.adb.enable=0 ro.factorytest=0 ro.calibration=0 ro.serialno= ro.bootmode=unknown ro.baseband=unknown ro.carrier=unknown ro.bootloader=unknown ro.hardware=freescale ro.revision=332080 init.svc.recovery=running init.svc.boot_count=stopped init.svc.adbd=stopped BATTERY = 100 (0) Formatting /data... format_root return :0Formatting /cache... format_root return :0 I'll go and see what's inside that recovery_backup_signed.zip - maybe I can simply replace a few of the contents with Clockworkmod. P.S.: stevebiggs, probably the internal SD card is too slow to play back 3GB / (the seconds your film takes). Try streaming it from another computer - a 1.8GB file from my UPnP server worked fine here. P.S2: Turn out the recovery .zip is particularly interesting. The only file I can mount is system.img - the other files are in some other format than ext or yaffs or simply are corrupt. System.img contains a bluetooth.apk (indicating it might be the freescale image) and no bloat. Just two kobo files. Last edited by hieronymos; 11-17-2011 at 09:47 AM.