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

Root Testers required

S

Sebastian404

Member
So I have made a build of Clockwork Mod Recovery for the ZTE Warp Sequent..

http://android.podtwo.com/beta/b1_recovery-clockwork-4.0.1.5s-warp2.img

I have no idea if it will work since I have not been able to find a device, but it has a good chance.

I'm deliberately not going to give you any in depth instructions, since I'm only looking for someone who knows what they are doing..

you should have the USB drivers installed, and be able to get the device into fastboot mode.. and then use the traditional:

fastboot flash recovery b1_recovery-clockwork-4.0.1.5s-warp2.img

any/all feedback welcome.
 
I got the recovery on it but the screen is all garbled and green. I can see that it responds to scrolling and there is txt back there but no go. Ill post a screen.
 

Attachments

  • IMG_20121008_204956.jpg
    IMG_20121008_204956.jpg
    462.5 KB · Views: 136
ok it works but there are problems with mounting /cache , /cache/recovery/log , and /cache/recovery/last_log. Errors show when I try show log. idk what else to do to check for integrity. Where do I go from here?
 
peasarecool said:
ok it works but there are problems with mounting /cache , /cache/recovery/log , and /cache/recovery/last_log. Errors show when I try show log. idk what else to do to check for integrity. Where do I go from here?
Click to expand...

when you say there are problems with mounting? is that something that comes up on screen when its booting?

What exactly does it say when you try to show the log?

as for testing it, if you try a backup does it actually do anything?
 
ill reflash it and be detailed with the errors. backup gave me boot, data, recovery and system. and the controls are just off. Ill explain when im in it again. can you possibly compile from source for us since we have a boot and recovery img floating around here now? im reading up but ive never compiled a thing in my life
 
peasarecool said:
ill reflash it and be detailed with the errors. backup gave me boot, data, recovery and system. and the controls are just off. Ill explain when im in it again. can you possibly compile from source for us since we have a boot and recovery img floating around here now? im reading up but ive never compiled a thing in my life
Click to expand...

Do you mean ClockWorkMod Recovery? I always build it from source. I managed to get a ROM dump a few weeks ago, that I've been using for the kernel, there is currently no kernel source available, I have emailed my contact at ZTE to get them to post it, hopefully it wont take as long as it did with the original Warp.

I've made a couple of changes, rather that leave the cache file system at 'auto' I'll make it 'ext4' in-case that is confusing it, otherwise this is the same as the last:

http://android.podtwo.com/beta/b3_recovery-clockwork-4.0.1.5s-warp2.img
 
oooh ok. I was wondering how you were coming up with cwms to try. I assumed you were using one from a different device modified for ours. Ill see in about an hour if I can be detailed about my problems
 
on main screen of cwm I see at the bottom
Code: 
E:Cant mount /cache/recovery/command
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log

First time I tried I swear power buttin was the select button, now it toggles the screen blank (with logo) and back. At some point the home button stops selecting anything at all while the up/down still works. Sometimes if I fiddle with buttons enough I get something like "back menu button enabled" (although its not) but then power or home may work again to select. Just now, as I type this (fiddling around to give an acurate descrition) hitting power to toggle text on and off, and volume keys to try to make home work again( this worked before) now its stuck at blank with little logo. Pull battery.....

trying again, I go to wipe cache, hit home, it goes to standard
Code: 
no
no
no
etc
yes
no
screen.... home doesnt respond. power selects no.
try again, still no home, (im on home screen) power toggles text. with no method to madness, button mashing sometimes results in "back button enabled" allowing power to select again...if not battery pull..

try again.. yes on clear cache says
Code: 
E:Cant mount /cache/recovery/log
E:Cant open /cache/recovery/log
E:Cant mount /cache/recovery/last_log
E:Cant open /cache/recovery/last_log

pull batt...install zip from sd card...same error..backup worked first time with boot.img, system.img, recovery.img, and data.img. mount usb storage...same error. show log, same error. im not going to try every opton. to sum up the pattern, on home screen of cwm home button is key, any other screen power button is. If it goes bact to home because of error...no select button


AHA....up,up up up up a few times ALWAYS makes "back menu button enabled..then POWER button is select key without EVER messing up ( I have a headache now)

Mount usb storage: E:Unable to open ums lunfile (sys/devices/platform/usb_mass_storage/lun0/file) ---well thats different than last time...Now choose zip from sd card browses the sd card(getting somewhere!)
wipe cache works, dalvik cache works...report error makes a file...ill send it. So up up up up up up up fixes everything I guess.
Key test: power-116, up-115, down-114, back, home, menu do nothing...
Im done...sorry for the headache
 
up or down about 10 timea prompts back menu button enabled, allowing power button to control properly and stops errors at show log, mount from sd, etc....

log: ro.bootloader=0.85.0000
ro.hardware=warp2
ro.revision=0
ro.emmc=1
...usbconfig=stopped
...rmt_storage=running
...recovery=running
...adbd=running
checking for extended command...
skipping.....file not found
 
AHA....up,up up up up a few times ALWAYS makes "back menu button enabled..then POWER button is select key without EVER messing up ( I have a headache now)
Click to expand...


I had cwm installed on an htc one that you had to use the up up up up up cycle thing to enable power button select. It drove me nuts till I figured it out. I think it is supposed to be a safety feature or made for devices with limited hardware buttons?
 
yaggermr said:
I had cwm installed on an htc one that you had to use the up up up up up cycle thing to enable power button select. It drove me nuts till I figured it out. I think it is supposed to be a safety feature or made for devices with limited hardware buttons?
Click to expand...

i dont believe this could be so...I was getting errors before i did it. It has too much of a pattern to the madness. Hard to explain but I feel this is a configuration problem. I'd like to hear what sebastoan has to say about using an older cwm
 
Ah, thanks for the feedback, your right, the UP,UP,UP thing is a feature for devices that don't have any other physical buttons, that can be fixed in the config tho, it should default to POWER now

the USB mount thing should be easy to fix too, it just depends on the type of USB device used, I'll try the other path for that, see if that fixes it, if not can you look in your /sys/devices/ for a directory called 'lun0'

I stuck with the v4.1.0.5 build since from v5 onwards Koush initially withheld the source, and then changed the Licence, and I don't agree with the new licence so I'm sticking with 4.1.0.5 for now..

However I always publish my device config (once I have it working) so anyone can use it to build more recent versions.

so here we go with the next build :

http://android.podtwo.com/beta/b4_recovery-clockwork-4.0.1.5s-warp2.img
 
Code: 
Starting recovery on Wed Oct 10 21:01:56 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.
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/command
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=GINGERBREAD
ro.build.display.id=generic_warp2-eng 2.3.7 GINGERBREAD eng.sebastian.20121010.132143 test-keys
ro.build.version.incremental=eng.sebastian.20121010.132143
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Oct 10 13:29:04 PDT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=sebastian
ro.build.host=linux
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=generic_warp2
ro.product.device=warp2
ro.product.board=warp2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7630
ro.build.product=warp2
ro.build.description=generic_warp2-eng 2.3.7 GINGERBREAD eng.sebastian.20121010.132143 test-keys
ro.build.fingerprint=Android/generic_warp2/warp2:2.3.7/GINGERBREAD/eng.sebastian.20121010.132143:eng/test-keys
ro.cm.device=warp2
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
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...
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
I like the lime green on black better than the colors on shabbypenguins version. Heres a log. There's no lun0 in there, unless its in a subfolder of a subfolder
 
peasarecool said:
Code:
I like the lime green on black better than the colors on shabbypenguins version. Heres a log. There's no lun0 in there, unless its in a subfolder of a subfolder
Click to expand...

That not being able to mount the cache partion is very odd, can you mount other partions from the menu without any errors?

yeah its probably a few directorys deep, if you try something like

find /sys/devices |grep lun0

that should give you a path to it..
 
find /sys/devices |grep lun0
/sys/devices/platform/msm_hsusb/gadget/lun0
/sys/devices/platform/msm_hsusb/gadget/lun0/uevent
/sys/devices/platform/msm_hsusb/gadget/lun0/power
/sys/devices/platform/msm_hsusb/gadget/lun0/power/
/sys/devices/platform/msm_hsusb/gadget/lun0/power/
/sys/devices/platform/msm_hsusb/gadget/lun0/power/
/sys/devices/platform/msm_hsusb/gadget/lun0/power/
/sys/devices/platform/msm_hsusb/gadget/lun0/power/
/sys/devices/platform/msm_hsusb/gadget/lun0/ro
/sys/devices/platform/msm_hsusb/gadget/lun0/file
/sys/devices/platform/msm_hsusb/gadget/lun0/nofua

I believe the cache problem wasnt showing when I did the up up up up up on the other one. Not sure though. Ill see whats mounting later
 
Same errors---cant mount /cache/recovery/command, log, and last_log
Went to try mounting and unmounting everything like u asked ans system worked cache failed to mount, then whatever was next made the menu go blank but the bottom txt was still there that has the version and log...first time for that

edit: second time, no freeze or dissapperating txt. everything but cache mounts

Code: 
Starting recovery on Thu Oct 11 01:44:29 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.
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/command
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=GINGERBREAD
ro.build.display.id=generic_warp2-eng 2.3.7 GINGERBREAD eng.sebastian.20121010.175405 test-keys
ro.build.version.incremental=eng.sebastian.20121010.175405
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Oct 10 17:58:40 PDT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=sebastian
ro.build.host=linux
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=generic_warp2
ro.product.device=warp2
ro.product.board=warp2
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7630
ro.build.product=warp2
ro.build.description=generic_warp2-eng 2.3.7 GINGERBREAD eng.sebastian.20121010.175405 test-keys
ro.build.fingerprint=Android/generic_warp2/warp2:2.3.7/GINGERBREAD/eng.sebastian.20121010.175405:eng/test-keys
ro.cm.device=warp2
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
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...
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
Error mounting /cache!
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p17 (Invalid argument)
W:Can't unlink /cache/recovery/command
 
You must log in or register to reply here.
Back
Top Bottom