• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Testers required

so update on the recovery, error cant mount blah blah blah, usual same error. Backup seems to be working right now its froze on backing up data but we will see. No black screen errors, going to verify size of backup file but not goinng to back up with factory img will pull that when done backing up
 
nah sean I can tho

what does your device manager see your phone as in cwm. I have the same problem with mount usb. It wont find drivers because it doesnt seem to know what it is. Idk. the link i posted works for me
 
no sir, computer doesnt recognize the phone correctly...i said somewhere what device manager sees it as...maybe forcing the right drivers would work but idk

update: i got adb shell working in cwm after installing pdanet for the drivers
 
oh cool,

can you do a couple of things,

dmesg >/sdcard/dmesg.txt
mount >/sdcard/mout.txt

and then send me/post the output of those files.

the other thing, is can you try form the command line:

mount -t ext4 /dev/block/mmcblk0p17 /cache

and then tell me if it does actually mount?
 
everything mounts including cache. i can wipe cache. same errors---cant open(or mount) /cache/recovery/command /cache/recovery/log and /cache recovery/last_log
 
peasarecool said:
everything mounts including cache. i can wipe cache. same errors---cant open(or mount) /cache/recovery/command /cache/recovery/log and /cache recovery/last_log
Click to expand...

hm, just as an experiment, can you mount the cache, then from ADB do a

mkdir /cache/recovery

and then reboot the recovery and see if it's still complaining?
 
2nd time i ran the latest cwm, no more errors. everything mounts so i dont need to try that ^. i think we are golden now. Only thing not working is mount USB
 
Just wondering if this is a solid cwm and could we get the files used and or a brief tutorial. If your not at that point I understand. I have been lurking in this thread but had little to add and didn't want to sidetrack this thread. Have used fastboot before but wasn't a constant need because scripts. I am decent at working from adb commands. I am assuming nandroid backup and restore is now working as well as dalvik cache wipe. I appreciate the work you have done. Sorry not trying to hijack the thread.
 
not at this point. 2 of us with the device and 1 dev without it are working together to get it error free. i retract my last statement. an error free copy was flashed but was not consistent across devices. thats the update so far. hit us up at irc.freenode.net #oudhitsquad if you want to help test.
I/someone will post a thorough tutorial after we are confident it is ready for those who dont already know how to get it up and running. thanks for testing if you welcome the risk.
 
peasarecool said:
ill do that later. im sure theres no error with usb it just doesnt work with windows
Click to expand...

Im wondering if its the drivers, looking at the stock recovery it seems to be setting a USB vendor ID of 19D2 and a device ID of 0213, where the bulk of the other ZTE devices I've seen set a Vendor id of 1354...

If you have the device running normally and use the built in USB mount, do you know what device IDs windows can see?

I dont use windows so I cant tell you how to find those, but I assume they will be in control panel/system/devices... or something like that.

UPDATE:

Ive just been and looked up that vendor/device id and its apparently the mode the device uses for Diagnostics, which is probably why the drivers are not seeing it as a USB device.

Here is a another build this time using the standard ZTE device ID,, see if that helps:


http://android.podtwo.com/beta/b7_recovery-clockwork-4.0.1.5s-warp2.img
 
b7 lost adb, didnt gain usb mount, still no errors. windows device manager sees nothing new. no unknown device, no device without drivers,nothing.


Code: 
Starting recovery on Sun Oct 14 15:10:45 2012
framebuffer: fd 4 (540 x 960)
CWM-based Recovery v4.0.1.5s
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
15 /sd-ext auto /dev/block/mmcblk1p2 (null)
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.5s-warp2
ro.product.name=N861
ro.product.device=warp2
ro.product.board=warp2
usb.default.pid=0x1354
persist.usb.default.pid=0x1354
ro.build.date=Thu Sep 27 11:40:07 PDT 2012
ro.build.date.utc=1348771207
ro.build.owner=sebastian404
ro.build.url=http://android.podtwo.com/
ro.factorytest=0
ro.serialno=6f1e7da4
ro.bootmode=recovery
ro.baseband=msm
ro.carrier=unknown
ro.bootloader=0.85.0000
ro.hardware=warp2
ro.revision=0
ro.emmc=1
init.svc.usbconfig=stopped
init.svc.rmt_storage=running
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
 
per device manager:

In MPT Mode:
Android ADB Interface: USB\VID_19D2&PID_0306&REV_0231&MI_01
USB\VID_19D2&PID_0306&MI_01

N861: USB\VID_19D2&PID_0306&REV_0231&MI_00
USB\VID_19D2&PID_0306&MI_00


In Carge Only Mode:
ZTE Composite ADB Interface: USB\VID_19D2&PID_1351&REV_0231&MI_01
USB\VID_19D2&PID_1351&MI_01
 
You must log in or register to reply here.
Back
Top Bottom