31 replies to this topic

[Sebastian404]

I grabbed the update file and took a look at the boot.img..

did you remember to add  usbconfig into sbin (and a service for it in init.rc)...

tho looking at it they seem to be just writting to the registers directly from init.rc now

	write /sys/class/android_usb/android0/enable 0
	write /sys/class/android_usb/android0/idVendor 18d1
	write /sys/class/android_usb/android0/idProduct 2d00
	write /sys/class/android_usb/android0/enable 1

I'd do both to be sure.

[KonstaT]

Yeah, there even seems to be a separate init script for USB in the stock recovery image. Also usbconfig and usbchangemode are in /sbin but there is no service created for them anywhere. And I indeed am missing idVendor/idProduct/etc in init.rc. It looks like this in the stock recovery:

on property:sys.usb.config=diag
	write /sys/class/android_usb/android0/enable 0
	write /sys/class/android_usb/android0/idVendor 19D2
	write /sys/class/android_usb/android0/idProduct 0112
	write /sys/class/android_usb/android0/f_diag/clients diag
	write /sys/class/android_usb/android0/functions diag
	write /sys/class/android_usb/android0/enable 1
	setprop sys.usb.state $sys.usb.config
on property:sys.usb.config=diag,adb
	write /sys/class/android_usb/android0/enable 0
	write /sys/class/android_usb/android0/idVendor 19D2
	write /sys/class/android_usb/android0/idProduct 0213
	write /sys/class/android_usb/android0/f_diag/clients diag
	write /sys/class/android_usb/android0/functions diag,adb
	write /sys/class/android_usb/android0/enable 1
	setprop sys.usb.state $sys.usb.config
	start adbd
# Restart adbd so it can run as root
on property:service.adb.root=1
	write /sys/class/android_usb/android0/enable 0
	restart adbd
	write /sys/class/android_usb/android0/enable 1

Thanks, I have now few more ideas to sort this out. I'll try to do a new build on the weekend when I have more time to play with kernel and what not...

[KonstaT]

Here is a new build for someone to try. Please test adb and mass storage and report back.

I compiled kernel from source with CONFIG_ZTE_FTM_FLAG_SUPPORT unset. Otherwise I used default config extracted from the regular kernel. Kernel zImage size dropped from 8.3mb to 3.9mb. Someone might assume that kernel source should match the binary shipped with the device, but no - not with ZTE. This is untested of course, so there is a small chance it doesn't even boot.

Also added bunch of stuff for usb and hopefully fixed adb and usb mass storage.

recovery-cwm5028-acqua.img
.
md5:5c5f6b1904690c9a6f0c6a4f54a3d1e5

[Sebastian404]

KonstaT, on 18 August 2012 - 06:37 PM, said:

Here is a new build for someone to try. Please test adb and mass storage and report back.

I compiled kernel from source with CONFIG_ZTE_FTM_FLAG_SUPPORT unset. Otherwise I used default config extracted from the regular kernel. Kernel zImage size dropped from 8.3mb to 3.9mb. Someone might assume that kernel source should match the binary shipped with the device, but no - not with ZTE.

For some reason (probably a typo in the build pipeline) zte are not using ziped kernels, its the same on the blade2 & roamer2, the config produces a ziped kernel images, and the devices will boot with a ziped kernel...  Im going to assume they picked the wrong file out of the kernel build directory and no-one has spotted it.

[Yurbuh Tuggly]

KonstaT, on 18 August 2012 - 06:37 PM, said:

Here is a new build for someone to try. Please test adb and mass storage and report back.

Tested. Both boot-only and flashed...same results.
Upon entering the recovery, Windows found new drivers:
USB Composite Device =Check, ready to use
USB Mass Storage Device =Check, ready to use
Linux File-CD Gadget USB Device =Check, ready to use
$ro.product.model = X, no driver found

USB access--full access to the SD card upon mounting.
ADB......sorry, no .No devices attached.

[KonstaT]

We're getting there. Another one.

recovery-cwm5028-zte-acqua.img
.
md5:63715a21e988f216775284f5ffde8ed5

[Yurbuh Tuggly]

KonstaT, on 18 August 2012 - 07:48 PM, said:

We're getting there. Another one.

Slowly but surely. I have confidence.
Same result as above except now instead of $ro.product.model = X, no driver found:
Android = X No driver found

USB = OK
ADB = No.

Also, (and this is a very minor detail also present in the stock recovery), the text is very tiny. IF there is any EASY way to increase the size of the menu-choice text in the recovery, that would be a fine improvement. If it's a bother, forget about it.

Edited by Yurbuh Tuggly, 19 August 2012 - 05:54 AM.

[KonstaT]

I have high hopes that this has both adb and usb mass storage working (or neither ). Please test and report back.

ADB is not something that a regular user would (probably ever) need on recovery mode, but it would still be nice to have a 100% working cwm. If this doesn't work, I'll probably give up for now. I'll push the sources to my github for the one that worked out the best.

acqua-cwm5028.img
http://www.mediafire...0rc06h90re8azjd
md5:69b4323af736f4f87ca81f32880feffe

[Yurbuh Tuggly]

KonstaT, on 19 August 2012 - 09:16 AM, said:

I have high hopes that this has both adb and usb mass storage working (or neither ). Please test and report back.

ADB is not something that a regular user would (probably ever) need on recovery mode, but it would still be nice to have a 100% working cwm.

BINGO!

ZTE Composite ADB Interface = Check Ready to use.

USB = Good.
ADB = Good

List of devices attached
0123456789ABCDEF     recovery

This one's the keeper. Well done!

[KonstaT]

Great, my job here is done then. ADB device name is of course incorrect but I'll let that one slide. Now you'd just need some custom ROMs...

I pushed the source to my github if someone wants to improve it and I updated my thread with the new version.

[stefdesign]

Where to get some custom ROMs for this device (Coldfusion based on CyanogenMod  9 of 10 for example)?
Or is there somewhere a port-tool (like this one but with porting of zte skate (for example) -> zte skate acqua) to try it safely on this phone?

okay, my last question has already been answered

Edited by stefdesign, 19 August 2012 - 05:05 PM.

[KonstaT]

stefdesign, on 19 August 2012 - 04:55 PM, said:

Where to get some custom ROMs for this device (Coldfusion based on CyanogenMod  9 of 10 for example)?
Or is there somewhere a port-tool (like this one but with porting of zte skate (for example) -> zte skate acqua) to try it safely on this phone?

okay, my last question has already been answered

Does it make CyanogenMod better if it comes re-branded?

No, you can't port ROMs from Skate. It's an ARMv6 device, this has ARMv7 chipset.

You could try porting ROMs from other msm7x27a devices like ZTE N880E, ZTE V889D, ZTE Blade II, Huawei G300, HTC Desire V, Samsung Galaxy Mini 2 and Samsung Galaxy Ace Plus (Samsungs have different screen resolution though). If you ask me, it would be better to start by modifying your current stock ROM at this point. There is no point in porting some half-working CM9/CM10 build from other devices - you should be building it from source for this device yourself.