HD2 sprawdzanie bad blocków

Witam was, gdzieś wpadłem na temat o tym że bad blocki najłatwiej sprawdzić przy pomocy recovery - zapisany plik z poziomu cwm

wpis prezentuje się tak:
Starting recovery on Mon Mar 11 18:44:25 2013
framebuffer: fd 4 (480 x 800)
ClockworkMod Recovery v4.0.0.0
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot yaffs2 boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 /dev/block/mmcblk0

I:Completed outputting fstab.
I:Processing arguments.
mtd: successfully wrote block at 0
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GRJ22
ro.build.version.incremental=eng.root.20110609.211 932
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Thu Jun 9 21:19:44 BST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=root
ro.build.host=sahang
ro.build.tags=test-keys
ro.product.model=HTC HD2
ro.product.brand=htc_wwe
ro.product.name=passion
ro.product.device=leo
ro.product.board=htcleo
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=qsd8k
ro.build.product=leo
ro.build.description=passion-user 2.3.3 GRI40 102588 release-keys
ro.build.fingerprint=google/passion/passion:2.3.3/GRI40/102588:user/release-keys
ro.sf.lcd_density=240
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.ecc.HTC-WWE=999
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.enable.dtm=1
ro.ril.gprsclass=12
ro.ril.hsdpa.category=8
ro.ril.hsupa.category=5
ro.ril.hsxpa=2
mobiledata.interfaces=rmnet0,rmnet1,rmnet2,ppp0
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.telephony.default_network=0
ro.ril.enable.prl.recognition=1
ro.opengles.version=131072
ro.media.dec.jpeg.memcap=20000000
dalvik.vm.heapsize=32m
dalvik.vm.dexopt-data-only=1
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=1
keyguard.no_require_sim=true
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.ril.enable.managed.roaming=1
ro.ril.oem.nosim.ecclist=911,112,113,115,117,999,0 00,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.modversion=CyanogenMod-7.1.0-RC0-LEO-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
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=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=htcleo
ro.revision=0
init.svc.choice_fn=stopped
init.svc.offmode_charging=running
init.svc.detect_key=running
init.svc.adbd=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
mtd: successfully wrote block at 0
I:Set boot command ""



Mam jakieś bad sectory w pamięci NAND i czy w ogóle da się to dzięki temu stwierdzić? Pozdrawiam!