31 replies to this topic

[Yurbuh Tuggly]

Opened this up for further discussion of ClockworkMod for this device since the "Root" thread is no longer about Root, really:
http://www.modaco.co...ot/page__st__20

Edited by Yurbuh Tuggly, 13 August 2012 - 12:12 PM.

[KonstaT]

Another build for you to test. Used custom graphics for this one and added few more keys to the list to act as select key.

acqua-cwm5504.img
.
md5:5c9245b09b7e004b7f154c10a694c69f

[Yurbuh Tuggly]

KonstaT, on 13 August 2012 - 10:24 AM, said:

Another build for you to test. Used custom graphics for this one and added few more keys to the list to act as select key.

First of all, thank you for the effort and time you are putting into this (for a seemingly limited audience at this point).
Tested:
Graphics = good. No more shifting around when scrolling through the menu.
Selection key = still no go. No way to select anything from the main menu

Interesting sub-note: briefly tapping the Power button on the top of the device, puts it into some kind of pause/suspend mode with just the 'hat' CWM logo in the middle. Quickly tapping Power again brings back the main menu.

PS..I don't know if this will help, but booted into the "touch" recovery/Advanced/Key Test and came up with this:
Menu = Key 139
Home = Key 102
Back = Key 158
Search = Key 217

Edited by Yurbuh Tuggly, 13 August 2012 - 11:37 AM.

[SMHenryT]

Yurbuh Tuggly, on 13 August 2012 - 11:32 AM, said:

First of all, thank you for the effort and time you are putting into this (for a seemingly limited audience at this point).

The limited audience is developer KonstaT very thankfull!

[KonstaT]

Yurbuh Tuggly, on 13 August 2012 - 11:32 AM, said:

First of all, thank you for the effort and time you are putting into this (for a seemingly limited audience at this point).

PS..I don't know if this will help, but booted into the "touch" recovery/Advanced/Key Test and came up with this:
Menu = Key 139
Home = Key 102
Back = Key 158
Search = Key 217

No problem, I see this more as a challenge and a chance to teach myself something new (this device is quite different from what I currently play with). That said, here are the last two builds. I really can't do much more without actually having the device. It's really a pain not being able to test any of this myself...

Info about the keycodes brings a bit of bad news. Those cases should already be handled and I have no idea why select key is not working but rest of the buttons are (volumes, power, back). First build has few tweaks here a there and it shouldn't be too different from previous build. Second one is compiled with BOARD_HAS_NO_SELECT_BUTTON and you should be able to use power key as select button.

acqua-recovery1.img
.
md5:b51f0d721e911965f4ea0fec022e23de

acqua-recovery2.img
http://www.mediafire...t6ddvs9cr4312dn
md5:49348a49ad9a5526304240223c01ec7c

Now that you have a backup of your stock recovery partition and you know how to restore it, you might want to test flashing one of these to the actual recovery partition. After that, try booting into recovery with the key combination (vol down + power?, which is it btw?) or using 'adb reboot recovery' and see if it makes any difference.

[Yurbuh Tuggly]

KonstaT, on 13 August 2012 - 02:15 PM, said:

No problem, I see this more as a challenge and a chance to teach myself something new (this device is quite different from what I currently play with)..

Info about the keycodes brings a bit of bad news. Those cases should already be handled and I have no idea why select key is not working but rest of the buttons are (volumes, power, back). First build has few tweaks here a there and it shouldn't be too different from previous build. Second one is compiled with BOARD_HAS_NO_SELECT_BUTTON and you should be able to use power key as select button.

Now that you have a backup of your stock recovery partition and you know how to restore it, you might want to test flashing one of these to the actual recovery partition. After that, try booting into recovery with the key combination (vol down + power?, which is it btw?) or using 'adb reboot recovery' and see if it makes any difference.

Challenge it is, indeed. And I feel your pain. I recently had to recompile/edit an APK for somebody that, at the time, I could not even run on my phone (Galaxy Mini). So it was about a million back and forths to get it right.
Results of testing:
R-1 = same...looks good, but no selections possible
(and a slight misunderstanding...Back button has not worked either..only in the semi-working Touch version from builder)
R-2 = good to go! Power as select works just fine.
Did a nandroid and it looks complete and normal: all files present and accounted for in one backup folder with expected sizes.
The only 'mistake' I made was to go into Advanced/Key test to see if I could pick up any more clues for you, and I was stuck. LOL! Had to do a Hold-Power hard reset to get out.
I will be flashing this one since it all seems to work (minus the 4 dead keys).
Great job!

Oh and PS: it's Power and VOL+ to get to normal recovery.

Update:
Flashed R-2, works just fine, rebooted into phone and used Rom Toolbox to do another nandroid (just to see if RT could 'communicate' with it OK)--no problems at all. It's a keeper. IF you want to fiddle more with it to see if you can get the key bindings, I would be happy to be the Guinea Pig...otherwise Job Done as far as I'm concerned.

Edited by Yurbuh Tuggly, 13 August 2012 - 04:30 PM.

[KonstaT]

Yurbuh Tuggly, on 13 August 2012 - 04:11 PM, said:

R-2 = good to go! Power as select works just fine.
Did a nandroid and it looks complete and normal: all files present and accounted for in one backup folder with expected sizes.
The only 'mistake' I made was to go into Advanced/Key test to see if I could pick up any more clues for you, and I was stuck. LOL! Had to do a Hold-Power hard reset to get out.
I will be flashing this one since it all seems to work (minus the 4 dead keys).
Great job!

Oh and PS: it's Power and VOL+ to get to normal recovery.

Update:
Flashed R-2, works just fine, rebooted into phone and used Rom Toolbox to do another nandroid (just to see if RT could 'communicate' with it OK)--no problems at all. It's a keeper. IF you want to fiddle more with it to see if you can get the key bindings, I would be happy to be the Guinea Pig...otherwise Job Done as far as I'm concerned.

Great. Now the "Back menu button enabled" thing you figured out comes in handy.

Can you test if adb works while in recovery mode? Also could you test if you can you mount your device as usb storage (mounts & storage -> mount usb storage)? There's some logs in /cache/recovery/ that might have some useful info.

There's been some compiling issue with some devices that breaks input keys, but iirc it killed all keys - not just some (had it with Blade at one point too). I might try again with gingerbread branch and cwm 5.0.2.8, but I'm occupied with other things for rest of this week. Of course I'm not perfectly happy with it yet since it doesn't still quite work like it should...

I'd still suggest you'd tried contacting sebastian404. He's got tons of experience on making recoveries. He's done cwm for pretty much every ZTE and Huawei device on this forum.

[Yurbuh Tuggly]

KonstaT, on 13 August 2012 - 06:55 PM, said:

Can you test if adb works while in recovery mode? Also could you test if you can you mount your device as usb storage (mounts & storage -> mount usb storage)? There's some logs in /cache/recovery/ that might have some useful info.

1) No ADB in recovery mode...no devices listed.
2) No USB mount either..E: Unable to open ums lunfile (no such file or di <text cutoff>
3) Scrolling to get "Back menu button enabled/disabled" has no real effect except to change the text...no actual hardware (soft buttons) are usable.

No rush to do anything. The minor issues still present are not deal breakers for me. Just happy to have options like nandroid finally available.
I don't need it, but for any others that may have this device, do you have a 'zip install' version that may work from the stock recovery? Just thinking that not everybody will be able to deal with ADB on some computers. Lack of drivers, no SDK,.........

Off topic, but one thing I have noticed with this phone..sometimes (usually but not always) on a reboot, the clock is set back to February (don't remember the day) @ 9:00 am. It's inconsistent, but certainly a bit annoying. Common to ZTE's or just odd with this one?

If sebastion404 sees this and wants to do something, I would be happy to assist/test, but otherwise I am more likely not to bother anybody. Yourself included..you have been an enormous help with this, and I do not expect any more.

[KonstaT]

Yurbuh Tuggly, on 13 August 2012 - 07:58 PM, said:

1) No ADB in recovery mode...no devices listed.
2) No USB mount either..E: Unable to open ums lunfile (no such file or di <text cutoff>
3) Scrolling to get "Back menu button enabled/disabled" has no real effect except to change the text...no actual hardware (soft buttons) are usable.

I don't need it, but for any others that may have this device, do you have a 'zip install' version that may work from the stock recovery? Just thinking that not everybody will be able to deal with ADB on some computers. Lack of drivers, no SDK,.........

1) Too bad, adb shell could have been useful.
2) lunfile path is probably incorrect, I might have picked the wrong one from the usual two (/sys/devices/platform/usb_mass_storage/lun vs. /sys/devices/platform/msm_hsusb/gadget/lun). Could check which one exists?
3) When enabled, that actually adds a new option to bottom of every menu to go back one level higher in the menu structure. You can now use your power key to select it  to go back in the menus. Otherwise it would be difficult without a working hardware back key. That's what I meant.

I don't think I can make a stock recovery flashable zip. It should be signed with ZTE key or it fails to install (lol, this might be where they failed their own update too). Making it into a clockworkmod flashable zip won't help much.

[Yurbuh Tuggly]

KonstaT, on 13 August 2012 - 08:49 PM, said:

1) Too bad, adb shell could have been useful.
2) lunfile path is probably incorrect, I might have picked the wrong one from the usual two (/sys/devices/platform/usb_mass_storage/lun vs. /sys/devices/platform/msm_hsusb/gadget/lun). Could check which one exists?
3) When enabled, that actually adds a new option to bottom of every menu to go back one level higher in the menu structure. You can now use your power key to select it  to go back in the menus. Otherwise it would be difficult without a working hardware back key. That's what I meant.

I don't think I can make a stock recovery flashable zip. It should be signed with ZTE key or it fails to install (lol, this might be where they failed their own update too). Making it into a clockworkmod flashable zip won't help much.

Actually:
/sys/devices/platform/msm_hsusb/gadget/lun0 and ...../lun1

Duh. Of course. I did not even notice that, but I certainly was going <Back> a lot.

No zippy = no biggie.

[KonstaT]

Ok, one more for you to try. This is cwm 5.0.2.8 compiled from CM7 sources. If the harware select keys don't work in this one, I'm going to give up until/if I can get my hands on the actual device.

acqua-cwm5028.img
.
md5:c60e49696b6290c35ee237329043fe63

[Yurbuh Tuggly]

KonstaT, on 14 August 2012 - 08:03 AM, said:

Ok, one more for you to try. This is cwm 5.0.2.8 compiled from CM7 sources. If the harware select keys don't work in this one, I'm going to give up until/if I can get my hands on the actual device.

Well.......guess what?

....wait for it.......KEYS WORK!!!!!!!
Menu key= pause/suspend
Home key = select!!
Back key = back!!

It even vibrates on selection which is a nice (and new) confirmation of a key press.
The ONLY thing that does not work (and I am not bothered by this in the least) is USB Mount:
E: Unable to open ums lunfile (is a directory)

Excellent work. Now get busy on your other things.

[KonstaT]

Great, this should fix the usb storage mounting. Does adb work? Please report any other issues you come across. That vibrating thing can be annoying in the long run too.

zte-acqua-cwm5028.img
http://www.mediafire...615lw1m3yp3ab8h
md5:231d6dca718bb922029acd8f889caec6

I'll probably start a new thread with instructions/links to drivers/etc for this when I have time to write. I'll also add instructions on how to root via recovery. I also pushed the sources for the recovery to my github.

[Yurbuh Tuggly]

KonstaT, on 14 August 2012 - 08:42 AM, said:

Great, this should fix the usb storage mounting. Does adb work? Please report any other issues you come across. That vibrating thing can be annoying in the long run too.

No errors anywhere.
But no ADB and no actual USB mount--nothing shows up on the PC. But both of these may be more due to Win7-64 and this particular phone. It has always been that (even with the stock recovery) when recovery mode is invoked on this phone, it loses connection to the PC.
With a Galaxy Mini I had, this was not the case..so I blame this phone.

[KonstaT]

Could be a driver issue or could be something else.

I opened a new thread here. Suggestions on making the instructions better are welcome.

[Yurbuh Tuggly]

KonstaT, on 14 August 2012 - 09:41 AM, said:

I opened a new thread here. Suggestions on making the instructions better are welcome.

Looks good. I don't see anything missing.
(and thanks for the Nod..glad to help)
This, of course, is what I was trying to do before I got into my Recovery Nightmare with bad CWMs and a million other things I tried...now it will be SO much easier for others just starting out.
And if anybody has any questions later on, glad to help with those too.

[Sebastian404]

I just spotted this thread, good work so far...

Im not sure if its the fcase, with with a lot of ZTE devices they have a 'special' FTM mode to install updates from the USB Card and or use the updater program.

FTM mode does not bother to do somethings like initialize USB and the keyboard (depending on the device), with the other ZTE devices we are replacing FTM with recovery, as there is no way into recovery using a key combination..

Entering recovery via 'adb reboot recovery' leaves the device in a different state from booting the device with VOL+ (or -) held down.

So the way around this is either to re-build the kernel (if the source is available) with CONFIG_ZTE_FTM_FLAG_SUPPORT unset, or to make a little script to check if USB is enabled, and if not do a 'reboot recovery' to get the device into the right mode.

This could be what going on here...

[KonstaT]

Yeah, I remember reading something about CONFIG_ZTE_FTM_FLAG_SUPPORT in Blade forum. There is a kernel source available for this device here. I tried compiling it with default config from ZTE N880E (basically this device but with CDMA radio) when the source was initially released. Being a ZTE kernel source, it didn't compile of course. I'll probably give it now another shot when I get around. There's probably bunch of other stuff that can also be disabled from recovery kernel?

Issue with input keys is a problem with cwm 5.5.0.4, few other devices seem to suffer from it as well. Remaining issue with the cwm 5.0.2.8 build seems to be the USB connectivity - no adb, no mass storage. Maybe Yurbuh Tuggly or someone else who actually has a device could test if booting into recovery mode with 'adb reboot recovery' makes any difference in this matter? Making a postboot script to reboot the recovery would be a really simple solution for this problem.

[Sebastian404]

Your right, the kernel wont compile due to a typo, but its fairly easy to fix.

edit arch/arm/mach-msm/board-msm7x27a-zte.c

edit line 45, change it from:

#include <proc_comm.h>

to:

#include "proc_comm.h"

And that will then compile

As for scripts, here is mine:

#!/sbin/sh
#
##########################################
#History:
#when	   whom			what, where, why
#--------   ----			---------------------------------------------------
#2010-12-08 sebastian404	horrible, horrible hack
#2011-08-09 sebastian404	slighty better hack, but still horrible
##########################################
FTM_MODE=`/sbin/busybox cat /sys/devices/platform/android_usb/functions/ftm_mode`
if [[ $FTM_MODE = "disable" ]]
then
/sbin/recovery
else
/sbin/reboot recovery &
fi

[Yurbuh Tuggly]

KonstaT, on 14 August 2012 - 08:57 PM, said:

Maybe Yurbuh Tuggly or someone else who actually has a device could test if booting into recovery mode with 'adb reboot recovery' makes any difference in this matter?

Tested.
No difference, I'm afraid.
As soon as recovery starts to appear on the phone, all connectivity to the PC is lost.