Jump to content

Mod Version Of ClockWorkMod Recovery for Racer

Guest Racerboy

By Guest Racerboy
in ZTE Racer - ROMs & ROM customisation

 Share

Recommended Posts

Guest Racerboy

Guest Racerboy

Posted
Posted

Okie.... something is blocking in there somewhere that is conflicting....

Please bear with me as this is going to be very tedious in finding the right kernel config ... and of course, experiment with the different config options to get it right... :unsure:

no probs :)

patience is a virtue

Link to comment
Share on other sites
  • Replies 239
  • Created
  • Last Reply

Popular Days

Popular Days

Popular Posts

Guest Dario93
Guest Dario93

Locked as requested by the OP. D.

Guest Racerboy
Guest Racerboy

Hi guys, how does the possibility of having touch screen options aswell as normal vol- vol+ make call end call buttons to control CWM sound? The guys in the Blade section have created a Gen2 version f

Guest Krste
Guest Krste

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/a

Posted Images

Guest Racerboy

Guest Racerboy

Posted
Posted

Any idea where the 4pda kernel sources is? :unsure:

you know more than me on github, if hes actually released the source code it should be their: version 2.6.32.9#64

HERE is his thread on 2.6.32.9#64 with good old bing translate lol, it does give instructions on how to build kernal and parameters he`s used on the top spoiler, i dont know if you have compiled it the same way

other than that i cant help :unsure:

Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted

you know more than me on github, if hes actually released the source code it should be their: version 2.6.32.9#64

HERE is his thread on 2.6.32.9#64 with good old bing translate lol, it does give instructions on how to build kernal and parameters he`s used on the top spoiler, i dont know if you have compiled it the same way

other than that i cant help :unsure:

Okie, thanks for that... :)

Am very blind on this for now... so... not sure, have sebastian's sources, used the config from his recovery gen1 and added touchscreen, other than that - I know you've tried it and it does not boot for some reason or another... am recompiling it again to make sure nothing is amiss...

Will keep trying

Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted (edited)

Not giving up on this little kernel f..ker... there is one clue though - 4pda's base address used for booting is this as per on the russian forum linky that you gave me...

~ / Bin / boot / mkbootimg - kernel arch / arm / boot / zImage - ramdisk ~ / bin / boot.img-ramdisk.gz-o ~ / bin / boot / boot.img - base 0x02e00000

The base address looks "unusual" to me. :blink:

As for his kernel, as this is gen1 which boots off 0x02a00000... :huh:

Why booting off 0x02e00000.... I don't understand that!

Will try deadlink's kernel again and use that boot address (I know you tried that one but was using 0x02a... which is what you've witnessed...)

Edit: Have pm'd Sebastian over on github as his modaco account disables messaging...

Edited by t0mm13b
Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted

thx tigtex, maybe you can lend a hand here with this problem

RESULT: 0x02e00000.... no go same as other 2

Okie... there's something funny going on...

This is the scenario I am thinking,

When using the beta version with 4pda's cm7 kernel, cold booting, the recovery is fixed to boot at 0x02a00000, for some reason, it gets ignored and bypassed and go straight to rom. That's correct yes? Now, when in the ROM, it reboots in warm boot, picks up the address and recovery starts okie.. either its FTM or the base address (from cold boot) is clashing

There's something peculiar going on...

Okie.. Racerboy, a suggestion - can you flash on the original CWM by sebastian and do this for me:


adb shell

dmesg > /sdcard/dmesg_log.txt

cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Hit Ctrl+D or 
exit
. Then pull it down 

adb pull /sdcard/dmesg_log.txt ./dmesg_log.txt

adb pull /sdcard/last_kmsg.log ./last_kmsg.txt

Now, from what I understand, Sebastian's recovery works from cold-boot and in warm boot also... attach them and I'll see if I can find the address of booting

This is annoying :lol:

Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted (edited)

ok here you go but "adb pull /sdcard/last_kmsg.log ./last_kmsg.txt" command returns with "does not exist

dmesg_log.txt

Okie,

Reboot again into sebastian's clockwork and 


adb shell

cat /proc/last_kmsg > /sdcard/last_kmsg.txt
Then hit Ctrl+D or 
exit

adb pull /sdcard/last_kmsg.txt ./last_kmsg.txt

Edited by t0mm13b
Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted

ok worked this time

last_kmsg.txt

Thanks for that.... Interesting... that boots from 0x2a00000

welcome to lk

calling constructors

initializing heap

initializing threads

initializing dpc

initializing timers

creating bootstrap completion thread

top of bootstrap2()

initializing platform

platform_init()

lcdc_ic_lead:9325

lcd_panel_id=1

[hp@lcd&fb]:lcd module init exit

!initializing target

target_init()

0: 0:MIBIB offs=0x00000000 size=0x0000000a attr: 0x00ffffff

1: 0:QCSBL offs=0x0000000a size=0x00000002 attr: 0x00ffffff

2: 0:OEMSBL1 offs=0x0000000c size=0x00000005 attr: 0x00ffffff

3: 0:OEMSBL2 offs=0x00000011 size=0x00000005 attr: 0x00ffffff

4: 0:AMSS offs=0x00000016 size=0x000000d4 attr: 0x00ffffff

5: 0:APPSBL offs=0x000000ea size=0x00000003 attr: 0x00ffffff

6: 0:FOTA offs=0x000000ed size=0x00000002 attr: 0x00ffffff

7: 0:EFS2 offs=0x000000ef size=0x00000060 attr: 0x00ffffff

8: 0:APPS offs=0x0000014f size=0x00000002 attr: 0x00ffffff

9: 0:FTL offs=0x00000151 size=0x00000005 attr: 0x00ff0101

10: 0:EFS2APPS offs=0x00000156 size=0xffffffff attr: 0x00ffffff

smem ptable found: ver: 3 len: 11

nandcfg: 0 0 (initial)

nandcfg(Apps): a85408c0 4745e (used)

nandcfg(Modem): aa5400c0 4745e (used)

ptn 0 name='recovery' start=00000156 len=00000024 flags=00000000 type=Apps Writable=Yes

ptn 1 name='boot' start=0000017a len=00000024 flags=00000000 type=Apps Writable=Yes

ptn 2 name='misc' start=0000019e len=00000003 flags=00000000 type=Apps Writable=Yes

ptn 3 name='cache' start=000001a1 len=00000064 flags=00000000 type=Apps Writable=Yes

ptn 4 name='system' start=00000205 len=000004b0 flags=00000000 type=Apps Writable=Yes

ptn 5 name='userdata' start=000006b5 len=0000093f flags=00000000 type=Apps Writable=Yes

ptn 6 name='persist' start=00000ff4 len=0000000c flags=00000000 type=Apps Writable=Yes

ptn 7 name='MIBIB' start=00000000 len=0000000a flags=00000000 type=Modem Writable=Yes

ptn 8 name='QCSBL' start=0000000a len=00000002 flags=00000000 type=Modem Writable=Yes

ptn 9 name='OEMSBL1' start=0000000c len=00000005 flags=00000000 type=Modem Writable=Yes

ptn 10 name='OEMSBL2' start=00000011 len=00000005 flags=00000000 type=Modem Writable=Yes

ptn 11 name='AMSS' start=00000016 len=000000d4 flags=00000000 type=Modem Writable=Yes

ptn 12 name='APPSBL' start=000000ea len=00000003 flags=00000000 type=Modem Writable=Yes

ptn 13 name='FOTA' start=000000ed len=00000002 flags=00000000 type=Modem Writable=Yes

ptn 14 name='EFS2' start=000000ef len=00000060 flags=00000000 type=Modem Writable=Yes

ptn 15 name='APPS' start=0000014f len=00000002 flags=00000000 type=Modem Writable=Yes

ptn 16 name='FTL' start=00000151 len=00000005 flags=00000000 type=Modem Writable=Yes

ptn 17 name='EFS2APPS' start=00000156 len=ffffffff flags=00000000 type=Modem Writable=Yes

calling apps_init()

[ZYF.BOOT] FTM NV = 2

jiangfeng: g_boot_key_exit_ftm = 0, first time

flash_read_image: success (0 errors)

flash_read_image: success (0 errors)

flash_read_image: success (0 errors)

kernel @ 2a08000 (2558960 bytes)

ramdisk @ 3a00000 (1337750 bytes)

cmdline = 'rdinit=/init console=ttyDCC0 console=ttyMSM2,115200'

Booting Linux

booting linux @ 0x2a08000, ramdisk @ 0x3a00000 (1337750)

cmdline: rdinit=/init console=ttyDCC0 console=ttyMSM2,115200

If you don't understand - lk is known as Little Kernel, which is the boot code, it checks if power up and volume down key is pressed, lk then chain boots into recovery, otherwise it boots normally into the ROM, that is what you're seeing in the above...

I wonder if it can be done to replace the recovery binary file in that original cwm, and re-pack it once again....using original kernel, with modified binary image.... hmmmm ?

Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted

its definately worth shot :D keeping the main structure of the original recovery and replacing only code you use for cwm-mod......go for it :lol:

Okie, what I've done here, used original recovery, replaced cwm-mod binary and added the images in place and repacked it - note: did not specify base address...

Let me know how that goes... :S

recovery_racer_experiment.zip

Link to comment
Share on other sites
Guest Racerboy

Guest Racerboy

Posted
Posted

recovery_racer_experiment

on both cold boot and reboot from desktop into recovery it sticks on green droid pic, no connection to comp so no adb reboot, had to take battery out....:unsure:

Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted

recovery_racer_experiment

on both cold boot and reboot from desktop into recovery it sticks on green droid pic, no connection to comp so no adb reboot, had to take battery out....:unsure:

Okie, could be that there's no base address specified...

try this version... bad news or good news either way... something is amiss... :unsure:

recovery_racer_experiment.zip

Link to comment
Share on other sites
Guest Racerboy

Guest Racerboy

Posted
Posted (edited)

results

GOOD NEWS, boots from cold yay and also reboots into recovery from the desktop BAD NEWS: only vol- and vol+ (to move up and down) and power button when pressed and held down will selects thing that are highlighted on the menu......so we have more progress :lol:

EDIT end call hard key acts as back button (to go up a level)

Edited by Racerboy
Link to comment
Share on other sites
Guest t0mm13b

Guest t0mm13b

Posted
Posted (edited)

results

GOOD NEWS, boots from cold yay and also reboots into recovery from the desktop BAD NEWS: only vol- and vol+ (to move up and down) and power button when pressed and held down will selects thing that are highlighted on the menu......so we have more progress :lol:

EDIT end call hard key acts as back button (to go up a level)

/me facepalms....

Oh! Just realized....

There's no touchscreen support in that kernel!!!!!! :blink:

FFFFFFuuuuuuuuu

Edit: I have Sebastian's sources but it does not reflect the configuration of what's in the kernel config... wonder if its a very old kernel.... need to dig around on this and try using the existing cwm recovery layout and shove in the kernel into that - have done this a few pages back and it hung.... :blink: :unsure:

Edited by t0mm13b
Link to comment
Share on other sites
Guest Racerboy

Guest Racerboy

Posted
Posted

BaD NeWs : no recovery either from cold or from reboot into recovery from phone desktop, sticks on green droid screen until i either plug usb in or i take battery out................................................:mellow:

Link to comment
Share on other sites
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.

  I accept