Mod Version Of ClockWorkMod Recovery for Racer

[Guest jm888]

Brilliant! :D

That's great - what screen resolution is that handset? 320x240 - its just the naming of the handset is what lead me to ask if there's any differences with the official ZTE Racer handset.... :)

Thanks a million for your feedback ... will look into this :)

Cheers, B)

Hi, it's the ZTE Racer equivalent phone sold through Telstra in Australia. It is 320x240, and as far as I can tell has identical specs to the Racer. All roms that I've loaded have worked without any problem.

[Guest t0mm13b]

heres mine finally, 3uk ZTE Racer ROM 2.3.5 4pda #179, kernal 2.6.32.9#64 by deadlink

# ./evtest /dev/input/event0

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "msm-touchscreen"

Supported events:

Event type 0 (sync)

Event type 1 (key)

Event code 330 (touch)

Event type 3 (Absolute)

Event code 0 (X)

Value 887

Min 69

Max 959

Event code 1 (Y)

Value 723

Min 0

Max 846

Event code 24 (Pressure)

Value 313

Min 0

Max 255

# ./evtest /dev/input/event1

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "mooncake_keypad"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 59 (F1)

Event code 102 (Home)

Event code 107 (End)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 158 (BAck)

Event code 231 (?)

# ./evtest /dev/input/event2

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "compass"

Supported Events:

Event type 0 (sync)

Event type 3 (Absolute)

Event code 0 (X)

Value -39

Min -5760

Max 5760

Event code 1 (Y)

Value 13

Min -5760

Max 5760

Event code 2 (Z)

Value -727

Min -5760

Max 5760

Event code 3 (Rx)

Value 0

Min 0

Max 23040

Event code 4 (Ry)

Value 0

Min -11520

Max 11520

Event code 5 (Rz)

Value 0

Min -5760

Max 5760

Event code 6 (Throttle)

Value 33

Min -30

Max 85

Event code 7 (Rudder)

Value 0

Min 0

Max 3

Event code 8 (Wheel)

Value 3

Min 0

Max 3

Event code 10 (Brake)

Value 0

Min -2048

Max 2032

Event code 16 (Hat0X)

Value 0

Min -2048

Max 2032

Event code 17 (Hay0Y)

Value 0

Min -2048

Max 2032

# ./evtest /dev/input/event3

Input driver version is 1.0.0

Input driver ID: bus 0x0 vendor 0x1 product 0x1 version 0x1

Input device name: "7k_handset"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 114 (volumeDown)

Event code 115(Volume Up)

Event code 116 (Power)

Event code 142 (Sleep)

Event code 143 (WakeUp)

Event code 226 (Media)

Again, brilliant stuff - well done! :D

Now we have the info required so its a matter of time ;)

Cheers,

B)

[Guest equiliym]

wow ive been away for a day and this.. :D sweet, good job guys.. t0mm13b, mind if i ask you a question related to your kernel git? i know this isnt a related topic, i could msg you tho when i get some more free time etc etc

[Guest Phoenix Silver]

heres mine finally, 3uk ZTE Racer ROM 2.3.5 4pda #179, kernal 2.6.32.9#64 by deadlink

# ./evtest /dev/input/event0

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "msm-touchscreen"

Supported events:

Event type 0 (sync)

Event type 1 (key)

Event code 330 (touch)

Event type 3 (Absolute)

Event code 0 (X)

Value 887

Min 69

Max 959

Event code 1 (Y)

Value 723

Min 0

Max 846

Event code 24 (Pressure)

Value 313

Min 0

Max 255

# ./evtest /dev/input/event1

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "mooncake_keypad"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 59 (F1)

Event code 102 (Home)

Event code 107 (End)

Event code 114 (VolumeDown)

Event code 115 (VolumeUp)

Event code 158 (BAck)

Event code 231 (?)

# ./evtest /dev/input/event2

Input driver version is 1.0.0

Input device ID: bus 0x0 product 0x0 version 0x0

Input device name: "compass"

Supported Events:

Event type 0 (sync)

Event type 3 (Absolute)

Event code 0 (X)

Value -39

Min -5760

Max 5760

Event code 1 (Y)

Value 13

Min -5760

Max 5760

Event code 2 (Z)

Value -727

Min -5760

Max 5760

Event code 3 (Rx)

Value 0

Min 0

Max 23040

Event code 4 (Ry)

Value 0

Min -11520

Max 11520

Event code 5 (Rz)

Value 0

Min -5760

Max 5760

Event code 6 (Throttle)

Value 33

Min -30

Max 85

Event code 7 (Rudder)

Value 0

Min 0

Max 3

Event code 8 (Wheel)

Value 3

Min 0

Max 3

Event code 10 (Brake)

Value 0

Min -2048

Max 2032

Event code 16 (Hat0X)

Value 0

Min -2048

Max 2032

Event code 17 (Hay0Y)

Value 0

Min -2048

Max 2032

# ./evtest /dev/input/event3

Input driver version is 1.0.0

Input driver ID: bus 0x0 vendor 0x1 product 0x1 version 0x1

Input device name: "7k_handset"

Supported events:

Event type 0 (Sync)

Event type 1 (Key)

Event code 114 (volumeDown)

Event code 115(Volume Up)

Event code 116 (Power)

Event code 142 (Sleep)

Event code 143 (WakeUp)

Event code 226 (Media)

Great :)

So it's event0 we have to read and event1 we have to write

Sub event 0 1 and 24

[Guest plegdroid]

Great :)

So it's event0 we have to read and event1 we have to write

Sub event 0 1 and 24

can I say a really big thank you to you guys/gal's for really taking the time out to make this happen for us racer guys. :)

[Guest Racerboy]

thx t0mm13b & Phoenix Silver your project here will be appreciated, keep us posted on any developments and if you need any more info i`m sure the Racer community here can help some more, if you need any beta testers ;) i and others will happily help.......

[Guest t0mm13b]

thx t0mm13b & Phoenix Silver your project here will be appreciated, keep us posted on any developments and if you need any more info i`m sure the Racer community here can help some more, if you need any beta testers ;) i and others will happily help.......

Of course, uhmmm... am keeping tab on this kernel source and will inform you of the progress over the weekend. :)

We are trying to find and figure out a way to test it privately before issuing it to beta testers :)

Can one of you guys point me in the direction for the clockwork mod recovery linky for your racers so that I can look into the kernel source and investigate further? :)

Cheers,

B)

[Guest Krste]

Of course, uhmmm... am keeping tab on this kernel source and will inform you of the progress over the weekend. :)

We are trying to find and figure out a way to test it privately before issuing it to beta testers :)

Can one of you guys point me in the direction for the clockwork mod recovery linky for your racers so that I can look into the kernel source and investigate further? :)

Cheers,

B)

Here is the ClockworkMod Recovery by Sebastian404

http://android.modaco.com/topic/331762-recovery-clockworkmod-recovery-for-zte-racer/

And here is the source code

https://github.com/sebastian404/android_device_zte_mooncake

[Guest plegdroid]

iam not sure if this is the same as what krstep has posted, but may still be helpful ,

http://apicdn.viglink.com/api/click?key=a7e5ffb24b9e84f4f4f6bbd88aa4e5b8&out=http%3A%2F%2Fandroid.podtwo.com%2Frecovery%2Farchived%2Frecovery-clockwork-4.0.1.4-mooncake-gen1-update_signed.zip&loc=http%3A%2F%2Fandroid.modaco.com&subid=bb9866cabf57950faff6a0f8c26c9e0c

[Guest Racerboy]

Exact CWM we use (gen1 for both) HERE .zip file and HERE .img file

[Guest t0mm13b]

Okie, this is beta!! So be warned! :D

Be prepared to have a working clockworkmod that you can flash if this fails :)

(I do not know if there's a fastboot mode available on the Racer...)

Go to Phoenix's Server here.

Download the file photom_cwm_update_racer.zip and put onto your sdcard.

Boot into your working ClockworkMod.

Choose that file and flash it and reboot.

Let me know how it goes.

(Am playing blind here so do not know what will happen!)

Edited September 6, 2011 by t0mm13b

[Guest Racerboy]

ok flashed CWM mod update, but does not boot into recovery, red led goes off and stays on green droid picture, nor does it carry on with boot, i restarted afew times to make sure but still same results.........

[Guest t0mm13b]

ok flashed CWM mod update, but does not boot into recovery, red led goes off and stays on green droid picture, nor does it carry on with boot, i restarted afew times to make sure but still same results.........

Okie - thanks for the feedback... am looking into this :)

It should be noted - that no changes was made to the entire device tree for the racer... unless there's an updated version lying around... am using sebastian404's version... am wondering.... :)

Will keep digging ... B)

Edited September 6, 2011 by t0mm13b

[Guest Racerboy]

no probs, i`ll test whatever you create :D

[Guest t0mm13b]

Okie, Have updated and fingers crossed. :)

Refer back to post #36 above and try again :)

Let me know how it goes.

Cheers,

B)

Edited September 8, 2011 by t0mm13b

[Guest Racerboy]

morning tommy, still the same results as before :( can you create an .img file of this latest version to see if works through fastboot?

[Guest t0mm13b]

morning tommy, still the same results as before :( can you create an .img file of this latest version to see if works through fastboot?

Hi! :)

Okie... uhmmm try this file photom_cwm_fastboot_racer.zip that can be flashed with fastboot from Phoenix's server. :)

Cheers,

B)

Edited September 8, 2011 by t0mm13b

[Guest Racerboy]

lol i could have extracted that from the update :rolleyes: nvm, same result red led goes off then just stays on green droid picture (fastboot method)

[Guest t0mm13b]

lol i could have extracted that from the update :rolleyes: nvm, same result red led goes off then just stays on green droid picture (fastboot method)

Hmmm.... either the kernel has booted but not launched recovery?

When you plug in the cable, does adb devices return the appropriate said device name for the racer?

This device tree I got from sebastians404 .... am not sure... btw - that's a gen1 recovery.... you're not on gen2 (is there such a thing?)

B)

[Guest Racerboy]

yes i have adb fully functional :)

adb devices: Racer

and mine is gen1 only (never upgraded to gen2 at all) their is gen2 but through tpt method from different operator other than mine (3uk)

Edited September 8, 2011 by Racerboy

[Guest t0mm13b]

yes i have adb fully functional :)

adb devices: Racer

and mine is gen1 only (never upgraded to gen2 at all) their is gen2 but through tpt method from different operator other than mine (3uk)

Okie....at least it's recognizing the device...

Can you adb shell into it?

Do a ls in the /temp directory - there should be a log in there (cat /temp/recovery.log) - can you pastebin it? Also can you pastebin in the contents of dmesg output as well to confirm please? :)

Cheers,

B)

[Guest Racerboy]

sry i thought you meant is adb functioning ok to install recovery via fastboot, but it does`nt recognise the phone now with your cwm mod

adb devices: BLANK

[Guest t0mm13b]

sry i thought you meant is adb functioning ok to install recovery via fastboot, but it does`nt recognise the phone now with your cwm mod

adb devices: BLANK

okie, np :)

Is deadlink's kernel a gen1? could try that one.... and see.... will be back to you in a while :)

[Guest Racerboy]

okie, np :)

Is deadlink's kernel a gen1? could try that one.... and see.... will be back to you in a while :)

ok i rebooted phone and it recognises my device now lol, can you give exact commands on cmd for what you want plz

yes it is gen1 (racer-kernel-2.6.32.9#64)

Edited September 8, 2011 by Racerboy

[Guest t0mm13b]

ok i rebooted phone and it recognises my device now lol, can you give exact commands on cmd for what you want plz

yes it is gen1 (racer-kernel-2.6.32.9#64)

Uhmm... its when booting into the ClockWorkMod, it should be recognized by adb devices command.

I was really hoping that you could shell into the recovery with the green android logo, after booted it into recovery...

Can you confirm that you've booted into recovery, the android logo is there, and that adb devices can recognize the handset?