[Thrive General] Natolx:
Someone over at thriveforums.org managed to pull a recovery log

Could the OTA update be located in the staging partition?

Additionally, if Toshiba Service Station.apk can WRITE the OTA update to whatever partition its on(apparently not system/cache) we should be able to pull a copy of it right?

Starting recovery on Fri Jul 15 15:46:21 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /recovery emmc /dev/block/platform/sdhci-tegra.3/by-num/p1 (null) 0
2 /boot emmc /dev/block/platform/sdhci-tegra.3/by-num/p2 (null) 0
3 /system ext4 /dev/block/platform/sdhci-tegra.3/by-num/p3 (null) 0
4 /cache ext4 /dev/block/platform/sdhci-tegra.3/by-num/p4 (null) 0
5 /misc emmc /dev/block/platform/sdhci-tegra.3/by-num/p5 (null) 0
6 /staging emmc /dev/block/platform/sdhci-tegra.3/by-num/p6 (null) 0
7 /data ext4 /dev/block/platform/sdhci-tegra.3/by-num/p7 (null) 0
8 /sdcard vfat /dev/block/mmcblk1p1 (null) 0

Command: "/sbin/recovery"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.build.id=HMJ37
ro.build.display.id=HMJ37.01.5.0018
ro.build.version.incremental=01.5.0018
ro.build.version.sdk=12
ro.build.version.codename=REL
ro.build.version.release=3.1
ro.build.date=Sat Jun 11 15:27:37 JST 2011
ro.build.date.utc=1307773657
ro.build.type=user
ro.build.user=android-toshiba
ro.build.host=dps3build2.local
ro.build.tags=release-keys
ro.product.model=AT100
ro.product.brand=TOSHIBA
ro.product.name=tostab03
ro.product.device=tostab03
ro.product.board=tostab03
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=TOSHIBA
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=tostab03
ro.build.description=tostab03-user 3.1 HMJ37 01.5.0018 release-keys
ro.build.fingerprint=TOSHIBA/tostab03/tostab03:3.1/HMJ37/01.5.0018:user/release-keys
ro.build.characteristics=default
ro.opengles.version=131072
ro.toshiba.device_wwan=0
wifi.interface=wlan0
rild.libpath=/system/lib/libmbm-ril.so
rild.libargs=-d /dev/ttyACM0 -i usb0
ro.sf.broadband=5521gw
ro.sf.hwrotation=0
ro.bootanim.hwrotation=270
mbm.gps.config.gps_ctrl=/dev/cdc-wdm0
mbm.gps.config.gps_nmea=/dev/ttyACM2
mbm.gps.config.gps_pref_mode=MEGPS
mbm.gps.config.supl.enable_ni=yes
mbm.gps.config.supl.username=test
mbm.gps.config.supl.password=test
ro.setupwizard.mode=REQUIRED
ro.com.google.gmsversion=3.1_r1
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
keyguard.no_require_sim=true
ro.com.google.clientidbase=android-toshiba
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
persist.sys.timezone=America/Denver
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=033c2089438154d7
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=unknown
ro.hardware=antares
ro.revision=0
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/dev/block/mmcblk0p7
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_flags=0x00000406
ro.crypto.state=unencrypted
persist.sys.locksw_state=0
persist.sys.profiler_ms=0
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
init.svc.recovery=running
init.svc.adbd=running

E:failed to mount /sdcard (No such file or directory)

-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 1073725440
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4095
Label:
Blocks: 262140
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8535/262140 blocks
Cache wipe complete.