Root [Boost Mobile] Testers wanted

[attrapp]

Is there now a log file in cache/recovery/log ?

It sounds like its working but the screen is not working... If so nearly there..

Yeah I don't have a log either.

 

[Sebastian404]

Ok, another day another build...

http://android.podtwo.com/beta/ztewarp/b5_recovery-clockwork-4.0.1.5-arthur.img

I'm starting to run out of ideas tho

 

[Woodstock77]

Ok, another day another build...

http://android.podtwo.com/beta/ztewarp/b5_recovery-clockwork-4.0.1.5-arthur.img

I'm starting to run out of ideas tho

Same as b4

 

[Sebastian404]

Same as b4

hmmm

Can you do a dmesg again? see if I can see anything different.


A guy has contacted me about the V9PLUS which is ZTE's latest Tablet, it seems to have the same hardware, I'm just building a recovery for him. it will be interesting to see if it has the same issues :!

 

[Woodstock77]

hmmm

Can you do a dmesg again? see if I can see anything different.


A guy has contacted me about the V9PLUS which is ZTE's latest Tablet, it seems to have the same hardware, I'm just building a recovery for him. it will be interesting to see if it has the same issues :!

I just went to work. It will be late tonight before I can do it.

 

[Sebastian404]

I just went to work. It will be late tonight before I can do it.

ok, I've made another build:

http://android.podtwo.com/beta/ztewarp/b6_recovery-clockwork-4.0.1.5-arthur.img

I'm not expecting it to be any different, but I've added in code that should mount /cache can you check it and see there anything in there at all? there should be a /cache/recovery/log file.


The other thing you could try doing is re-flash the stock recovery, then reboot into it, pick the reboot option and when you end up in android have a look in the /cache/ directory then...

 

[Woodstock77]

ok, I've made another build:

http://android.podtwo.com/beta/ztewarp/b6_recovery-clockwork-4.0.1.5-arthur.img

I'm not expecting it to be any different, but I've added in code that should mount /cache can you check it and see there anything in there at all? there should be a /cache/recovery/log file.


The other thing you could try doing is re-flash the stock recovery, then reboot into it, pick the reboot option and when you end up in android have a look in the /cache/ directory then...

Should I pull a dmesg and mount from stock as well just to see whats different? I was hoping someone else might step in and help here since Im stuck at work until 2am (about 6 more hrs).

 

[Woodstock77]

With b6 it boot loops in recovery. Every time it gets to the hardware buttons lighting up it restarts. What now?

 

[Sebastian404]

With b6 it boot loops in recovery. Every time it gets to the hardware buttons lighting up it restarts. What now?

argh! sorry thats my fault, typo.

can you try this verison :

http://android.podtwo.com/beta/ztewarp/b6_recovery-clockwork-4.0.1.5-arthur.img

Im going to assume that the screen still wont work, but it hopefully should create a log file in /cache


once you've done that, can you then reflash the original stock recovery:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

reboot into recovery, then reboot back to normal and then see if it created a recovery log in /cache


and the post the log files (if any exist)

 

[Woodstock77]

argh! sorry thats my fault, typo.

can you try this verison :

http://android.podtwo.com/beta/ztewarp/b6_recovery-clockwork-4.0.1.5-arthur.img

Im going to assume that the screen still wont work, but it hopefully should create a log file in /cache


once you've done that, can you then reflash the original stock recovery:

http://android.podtwo.com/beta/ztewarp/stock_recovery.img

reboot into recovery, then reboot back to normal and then see if it created a recovery log in /cache


and the post the log files (if any exist)

Ok in b6 there is still no recovery log found.
In stock the device is not found and there is no unknown devices in the system. For some reason it doesnt use diag drivers in stock recovery.

 

[Sebastian404]

Ok in b6 there is still no recovery log found.
In stock the device is not found and there is no unknown devices in the system. For some reason it doesnt use diag drivers in stock recovery.

if you reboot the device back into android is there anything in the /cache/recovery dir?

 

[Woodstock77]

if you reboot the device back into android is there anything in the /cache/recovery dir?

No nothing

 

[Woodstock77]

I decided to look for it using root explorer. What I found was a file called last_log. Here is what is in it. I need to try using it with b6 next but this is after stock.

Starting recovery on Tue Dec 13 17:43:49 2011
framebuffer: fd 4 (480 x 800)
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /dbl emmc /dev/block/mmcblk0p1 (null)
  2 /osbl emmc /dev/block/mmcblk0p2 (null)
  3 /cefs emmc /dev/block/mmcblk0p5 (null)
  4 /adsp emmc /dev/block/mmcblk0p8 (null)
  5 /amss emmc /dev/block/mmcblk0p9 (null)
  6 /emmcboot emmc /dev/block/mmcblk0p11 (null)
  7 /boot emmc /dev/block/mmcblk0p12 (null)
  8 /recovery emmc /dev/block/mmcblk0p13 (null)
  9 /splash emmc /dev/block/mmcblk0p14 (null)
  10 /system ext4 /dev/block/mmcblk0p15 (null)
  11 /misc emmc /dev/block/mmcblk0p16 (null)
  12 /cache ext4 /dev/block/mmcblk0p17 (null)
  13 /data ext4 /dev/block/mmcblk0p18 (null)
  14 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

Command: "/sbin/recovery"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.build.id=GINGERBREAD
ro.build.display.id=N860V1.0.0B06
ro.build.version.incremental=eng.tanbaihua.20110926.163948
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 26 16:48:06 CST 2011
ro.build.date.utc=1317026886
ro.build.type=user
ro.build.user=tanbaihua
ro.build.host=zhangchun-desktop
ro.build.tags=release-keys
ro.product.model=N860
ro.product.brand=ZTE
ro.product.name=ZTE_Warp
ro.product.device=arthur
ro.product.board=arthur
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ZTE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=arthur
ro.build.description=ZTE_Warp-user 2.3.5 GINGERBREAD eng.tanbaihua.20110926.163948 release-keys
ro.build.fingerprint=ZTE/ZTE_Warp/arthur:2.3.5/GINGERBREAD/eng.tanbaihua.20110926.163948:user/release-keys
ro.setupwizard.mode=DISABLED
ro.product.board_name=arthur
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV
DEVICE_PROVISIONED=1
debug.egl.hw=1
debug.sf.hw=1
dalvik.vm.heapsize=32m
ro.dev.dmm=1
dev.dmm.dpd.trigger_delay=30
ro.sf.lcd_density=240
ro.sf.hwrotation=180
persist.cne.UseCne=false
persist.cne.loadVendorCne=true
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=true
persist.cne.snsr.based.rat.mgt=true
persist.cne.bat.based.rat.mgt=true
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
lpa.decode=true
ro.use_data_netmgrd=true
ro.emmc.sdcard.partition=16
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.opengles.version=131072
ro.qualcomm.bluetooth.dun=true
ro.build.baseband_version=N860B01
ro.build.software_version=N860V1.0.0B06
ro.build.sw_internal_version=N860V1.0.0B12
ro.camera.video.size.mms=1048576
ro.camera.video.duaration.mms=40
ro.config.ringtone=Ring_Synth_04.ogg
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-zte
ro.com.google.clientidbase.am=android-boost-us
ro.com.google.clientidbase.ms=android-boost-us
ro.com.google.clientidbase.gmm=android-zte
ro.build.hardware_version=c4tB
ro.build.pri.version=61007
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.gmsversion=2.3_r6
persist.sys.usb.enable_switch=1
persist.sys.usb.linux_switch=1
persist.sys.usb.switch_pid=0x1351
persist.sys.usb.linux_pid=0x1350
persist.sys.usb.default.pid=0x83
persist.sys.sdcard.mount=1
persist.sys.usb.unique_sn=1
persist.sys.usb.enable_cdrom=0x5656
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=recovery
ro.baseband=msm
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
ro.emmc=1
ro.gcftest=0
init.svc.rmt_storage=running
init.svc.recovery=running
init.svc.diagtest=running
init.svc.adbd=stopped

 

[Woodstock77]

This is the b6 last_log

Starting recovery on Tue Dec 13 17:43:49 2011
framebuffer: fd 4 (480 x 800)
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /dbl emmc /dev/block/mmcblk0p1 (null)
  2 /osbl emmc /dev/block/mmcblk0p2 (null)
  3 /cefs emmc /dev/block/mmcblk0p5 (null)
  4 /adsp emmc /dev/block/mmcblk0p8 (null)
  5 /amss emmc /dev/block/mmcblk0p9 (null)
  6 /emmcboot emmc /dev/block/mmcblk0p11 (null)
  7 /boot emmc /dev/block/mmcblk0p12 (null)
  8 /recovery emmc /dev/block/mmcblk0p13 (null)
  9 /splash emmc /dev/block/mmcblk0p14 (null)
  10 /system ext4 /dev/block/mmcblk0p15 (null)
  11 /misc emmc /dev/block/mmcblk0p16 (null)
  12 /cache ext4 /dev/block/mmcblk0p17 (null)
  13 /data ext4 /dev/block/mmcblk0p18 (null)
  14 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

Command: "/sbin/recovery"

ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=0
ro.build.id=GINGERBREAD
ro.build.display.id=N860V1.0.0B06
ro.build.version.incremental=eng.tanbaihua.20110926.163948
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Sep 26 16:48:06 CST 2011
ro.build.date.utc=1317026886
ro.build.type=user
ro.build.user=tanbaihua
ro.build.host=zhangchun-desktop
ro.build.tags=release-keys
ro.product.model=N860
ro.product.brand=ZTE
ro.product.name=ZTE_Warp
ro.product.device=arthur
ro.product.board=arthur
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=ZTE
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=arthur
ro.build.description=ZTE_Warp-user 2.3.5 GINGERBREAD eng.tanbaihua.20110926.163948 release-keys
ro.build.fingerprint=ZTE/ZTE_Warp/arthur:2.3.5/GINGERBREAD/eng.tanbaihua.20110926.163948:user/release-keys
ro.setupwizard.mode=DISABLED
ro.product.board_name=arthur
rild.libpath=/system/lib/libril-qc-1.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
ril.subscription.types=NV
DEVICE_PROVISIONED=1
debug.egl.hw=1
debug.sf.hw=1
dalvik.vm.heapsize=32m
ro.dev.dmm=1
dev.dmm.dpd.trigger_delay=30
ro.sf.lcd_density=240
ro.sf.hwrotation=180
persist.cne.UseCne=false
persist.cne.loadVendorCne=true
persist.cne.bat.range.low.med=30
persist.cne.bat.range.med.high=60
persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
persist.cne.bwbased.rat.sel=true
persist.cne.snsr.based.rat.mgt=true
persist.cne.bat.based.rat.mgt=true
persist.cne.rat.acq.time.out=30000
persist.cne.rat.acq.retry.tout=0
lpa.decode=true
ro.use_data_netmgrd=true
ro.emmc.sdcard.partition=16
media.stagefright.enable-player=true
media.stagefright.enable-meta=false
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
ro.opengles.version=131072
ro.qualcomm.bluetooth.dun=true
ro.build.baseband_version=N860B01
ro.build.software_version=N860V1.0.0B06
ro.build.sw_internal_version=N860V1.0.0B12
ro.camera.video.size.mms=1048576
ro.camera.video.duaration.mms=40
ro.config.ringtone=Ring_Synth_04.ogg
ro.com.google.clientidbase=android-zte
ro.com.google.clientidbase.yt=android-zte
ro.com.google.clientidbase.am=android-boost-us
ro.com.google.clientidbase.ms=android-boost-us
ro.com.google.clientidbase.gmm=android-zte
ro.build.hardware_version=c4tB
ro.build.pri.version=61007
ro.config.notification_sound=F1_New_SMS.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.gmsversion=2.3_r6
persist.sys.usb.enable_switch=1
persist.sys.usb.linux_switch=1
persist.sys.usb.switch_pid=0x1351
persist.sys.usb.linux_pid=0x1350
persist.sys.usb.default.pid=0x83
persist.sys.sdcard.mount=1
persist.sys.usb.unique_sn=1
persist.sys.usb.enable_cdrom=0x5656
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=recovery
ro.baseband=msm
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
ro.emmc=1
ro.gcftest=0
init.svc.rmt_storage=running
init.svc.recovery=running
init.svc.diagtest=running
init.svc.adbd=stopped

They are the same so I assume from stock and not b6
I have to go to work now.

 

[Woodstock77]

If anyone else wants to get in on the fun and see whats happenning try these things. Some of the instruction here is assuming that you have a little more understanding so I kind of want to clarify it a little. When you download the support files unzip them to a an easy location on you hard drive. Lets say your HD is C:\ make a folder there called zte or something easy (c:\zte\) then unzip the support files into it. Then put your recovery image in there as well http://android.podtwo.com/beta/ztewarp/stock_recovery.img
. Go to the start menu and run type cmd and enter and the command prompt window will open. Type "cd c:\zte" or whatever you named the file and press enter. Then enter these commands (WAIT FOR EACH TO COMPLETE) After bootloader you will just see the green andoid, After flashing recovery you will see when its done. After reboot you will be back in android. After reboot recovery you will see the recovery console.

adb-windows.exe reboot bootloader
fastboot-windows.exe flash recovery stock_recovery.img
fastboot-windows.exe reboot
adb-windows.exe reboot recovery

That should get you into the stock recovery. You wont be able to copy any files from here because for some reason the diag comms dont work with the stock recovery. But if you did one of the other stock recovery files you could do a few more things. This is just to get you familiar with what we're doing. Just reboot into android from here.
Now once android starts back up type

adb-windows.exe pull /cache/recovery/last_log recovery_log.txt

It should make a text file called recovery_log.txt in your folder where you put the support files. You can name it anything you want for example if you wanted pink_elephants.txt type in

adb-windows.exe pull /cache/recovery/last_log pink_elephants.txt

.

I didnt get into drivers and all that but I wanted to give you some ideas of what to do.

 

[Sebastian404]

Ok, I've been doing some looking around and I found some mention of a fix for a 'blank screen' that I've now applied the recovery source...

http://android.podtwo.com/beta/ztewarp/b7_recovery-clockwork-4.0.1.5-arthur.img

maybe 7th time lucky?

 

[Woodstock77]

Ok, I've been doing some looking around and I found some mention of a fix for a 'blank screen' that I've now applied the recovery source...

http://android.podtwo.com/beta/ztewarp/b7_recovery-clockwork-4.0.1.5-arthur.img

maybe 7th time lucky?

I cant wait to test it out. But I have to wait until I get off work. 7 more hours. I work too much.

 

[Sebastian404]

I cant wait to test it out. But I have to wait until I get off work. 7 more hours. I work too much.

it seems that way

Im hoping to be back in the US for Christmas, I might look into picking one up for myself, the hardware seems to be the way forward for ZTE since I'm now aware that other devices in their range use the same hardware..

 

[jessesigmon]

First time posting been lurking since the prevail was rooted. Shabby interdpth you guys are that ish. Lil question Sebastian, my basband is n860b01 kernel 2.6.35.7-perf+ zte-kernel@zdroid-smt build b07 hardware version c4tb . Is that the same as yours? If not would that even make a difference? Great job so far muchos gracias can't wait to see the cwm up and running on the warp.

 

[Woodstock77]

First time posting been lurking since the prevail was rooted. Shabby interdpth you guys are that ish. Like question Sebastian, my baseman is n860b01 kernel 2.6.35.7-perf+ zte-kernel@zdroid-smt build b07 hardware version c4tb . Is that the same as yours? If not would that even make a difference? Great job so far muchos gracias can't wait to see the Candice up and running on the warp.

My build is b06 everything else is the same. Sebastian doesnt have a warp thats why all this back and forth here. I wouldnt think there would be a difference when it comes to this.

 

[Woodstock77]

it seems that way

Im hoping to be back in the US for Christmas, I might look into picking one up for myself, the hardware seems to be the way forward for ZTE since I'm now aware that other devices in their range use the same hardware..

Well. Custom recovery shows up. But iys tiny and shows up 4 times. I can only see 2 whole and two halves though. Also I cannot move up and down or make a selection.
Getting closer. Ohh also it showed up as unknown device and wouldnt take any drivers.

 

[Woodstock77]

Also it did create a last_log and here is whats in it.

Starting recovery on Wed Dec 14 07:41:09 2011
framebuffer: fd 4 (480 x 800)
active fb swap failed: Invalid argument
CWM-based Recovery v4.0.1.5
active fb swap failed: Invalid argument
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /boot emmc /dev/block/mmcblk0p12 (null)
  2 /recovery emmc /dev/block/mmcblk0p13 (null)
  3 /splash emmc /dev/block/mmcblk0p14 (null)
  4 /system ext4 /dev/block/mmcblk0p15 (null)
  5 /misc emmc /dev/block/mmcblk0p16 (null)
  6 /cache ext4 /dev/block/mmcblk0p17 (null)
  7 /data ext4 /dev/block/mmcblk0p18 (null)
  8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.modversion=clockwork-4.0.1.5-arthur
ro.product.device=arthur
ro.product.name=N860
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Tue Dec 13 16:20:32 PST 2011
ro.build.datei.utc=1323645223
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
init.svc.usbconfig=stopped
init.svc.recovery=running
init.svc.adbd=running

I:Checking for extendedcommand...
active fb swap failed: Invalid argument
I:Skipping execution of extendedcommand, file not found...

 

[Sebastian404]

Well. Custom recovery shows up. But iys tiny and shows up 4 times. I can only see 2 whole and two halves though. Also I cannot move up and down or make a selection.
Getting closer. Ohh also it showed up as unknown device and wouldnt take any drivers.

interesting, from the sound of it, the Kernel only supports a 32bit Framebuffer... not come across one of those before, been looking around other devices that have those and I've 'borrowed' some code from there...

http://android.podtwo.com/beta/ztewarp/b8_recovery-clockwork-4.0.1.5-arthur.img

8th time lucky?

 

[Woodstock77]

interesting, from the sound of it, the Kernel only supports a 32bit Framebuffer... not come across one of those before, been looking around other devices that have those and I've 'borrowed' some code from there...

http://android.podtwo.com/beta/ztewarp/b8_recovery-clockwork-4.0.1.5-arthur.img

8th time lucky?

It works as far as I can tell. One screen and you can select things. I did see an error message at the bottom and I'm posting the log.

Starting recovery on Wed Dec 14 16:22:00 2011
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /boot emmc /dev/block/mmcblk0p12 (null)
  2 /recovery emmc /dev/block/mmcblk0p13 (null)
  3 /splash emmc /dev/block/mmcblk0p14 (null)
  4 /system ext4 /dev/block/mmcblk0p15 (null)
  5 /misc emmc /dev/block/mmcblk0p16 (null)
  6 /cache ext4 /dev/block/mmcblk0p17 (null)
  7 /data ext4 /dev/block/mmcblk0p18 (null)
  8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
  9 /sd-ext auto /dev/block/mmcblk1p2 (null)

I:Completed outputting fstab.
I:Processing arguments.
E:Can't open /dev/block/mmcblk0p16
(No such file or directory)
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.modversion=clockwork-4.0.1.5-arthur
ro.product.device=arthur
ro.product.name=N860
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Wed Dec 14 05:35:47 PST 2011
ro.build.datei.utc=1323645223
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
init.svc.usbconfig=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

So I looked for E:Cant open /dev/block/mmcblk0p16 and found mmcblk0p16 at dev/block/platform/msm_sdcc2/mmcblk0p16. All files of that type are in that directory (dev/block/platform/msm_sdcc2/).
So I think all these should be looking in that directory like
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/platform/msm_sdcc2/mmcblk0p12 (null)
2 /recovery emmc /dev/block/platform/msm_sdcc2/mmcblk0p13 (null)
3 /splash emmc /dev/block/platform/msm_sdcc2/mmcblk0p14 (null)
4 /system ext4 /dev/block/platform/msm_sdcc2/mmcblk0p15 (null)
5 /misc emmc /dev/block/platform/msm_sdcc2/mmcblk0p16 (null)
6 /cache ext4 /dev/block/platform/msm_sdcc2/mmcblk0p17 (null)
7 /data ext4 /dev/block/platform/msm_sdcc2/mmcblk0p18 (null)
8 /sdcard vfat /dev/block/platform/msm_sdcc4/mmcblk1p1 /dev/block/platform/msm_sdcc4/mmcblk1
9 /sd-ext auto /dev/block/mmcblk1p2 (null)<<cannot find!

 

[Sebastian404]

It works as far as I can tell. One screen and you can select things. I did see an error message at the bottom and I'm posting the log.

Starting recovery on Wed Dec 14 16:22:00 2011
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v4.0.1.5
recovery filesystem table
=========================
  0 /tmp ramdisk (null) (null)
  1 /boot emmc /dev/block/mmcblk0p12 (null)
  2 /recovery emmc /dev/block/mmcblk0p13 (null)
  3 /splash emmc /dev/block/mmcblk0p14 (null)
  4 /system ext4 /dev/block/mmcblk0p15 (null)
  5 /misc emmc /dev/block/mmcblk0p16 (null)
  6 /cache ext4 /dev/block/mmcblk0p17 (null)
  7 /data ext4 /dev/block/mmcblk0p18 (null)
  8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
  9 /sd-ext auto /dev/block/mmcblk1p2 (null)

I:Completed outputting fstab.
I:Processing arguments.
E:Can't open /dev/block/mmcblk0p16
(No such file or directory)
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"

ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.modversion=clockwork-4.0.1.5-arthur
ro.product.device=arthur
ro.product.name=N860
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Wed Dec 14 05:35:47 PST 2011
ro.build.datei.utc=1323645223
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=arthur
ro.revision=0
init.svc.usbconfig=running
init.svc.recovery=running

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

So I looked for E:Cant open /dev/block/mmcblk0p16 and found mmcblk0p16 at dev/block/platform/msm_sdcc2/mmcblk0p16. All files of that type are in that directory (dev/block/platform/msm_sdcc2/).
So I think all these should be looking in that directory like
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/platform/msm_sdcc2/mmcblk0p12 (null)
2 /recovery emmc /dev/block/platform/msm_sdcc2/mmcblk0p13 (null)
3 /splash emmc /dev/block/platform/msm_sdcc2/mmcblk0p14 (null)
4 /system ext4 /dev/block/platform/msm_sdcc2/mmcblk0p15 (null)
5 /misc emmc /dev/block/platform/msm_sdcc2/mmcblk0p16 (null)
6 /cache ext4 /dev/block/platform/msm_sdcc2/mmcblk0p17 (null)
7 /data ext4 /dev/block/platform/msm_sdcc2/mmcblk0p18 (null)
8 /sdcard vfat /dev/block/platform/msm_sdcc4/mmcblk1p1 /dev/block/platform/msm_sdcc4/mmcblk1
9 /sd-ext auto /dev/block/mmcblk1p2 (null)<<cannot find!

Cool, can you try a backup and restore see if there's any problems with that?

its possible the device does not have a /misc partition, from looking at the mount list normally, it seems it does not.

the sd-ext mount will only appear if you partition your SDcard, some people like to create a 2nd parition on there for swap, but I dont think you really need that with this device.

if you cant find anything wrong with it, I'll fix the /misc partion and promote it to final