dheen

[RECOVERY] Rcovery For ZTE Link

20 posts in this topic

Hello,

i've made a recover.img for ZTE Link that don't seems to have the same kernel as racer

So let's test it (don't forget to have the proper fastboot and made save of your recovery before !!!)

Edit : test the backup mode. the Img are valid and extractable by unyaffs \o/

recoverylink.img

fastboot.zip

Edited by dheen
0

Share this post


Link to post
Share on other sites

Yes it ran !!!

All extract are good.

Thanks.

Edited by Mytriox
0

Share this post


Link to post
Share on other sites

Ok, i try to compile a kernel for the ZTE Link .... but i've got some problem doing it, it appears that the size of the kernel in LINK was limited.

It explained why the racer and the link have different base address for boot and recovery (0X02E00000 for racer and 0x03600000 for the link)

So i cannot compile a good kernel for the Link ..... it appears that the firmware for the racer is not the same :) ....

The kernel size for the link is 1,7 Mo and when i compile a 2.1 version with minimum driver the size is 1,9 mo....

In conclusion, in france we-re doomed :lol: but you could do you're personnal rom in 1.6 :(

( ..... i regret not to wait for the Blade :) ....)

i suppose we have to pray for an update by ZTE or Bouygues ( ..... or to start make some money to buy a new phone :P)

0

Share this post


Link to post
Share on other sites

And from this link : http://ensupport.zte.com.cn/OldEnSupport/H...010-5/105.shtml

Or here : http://support.zte.com.cn/support/news/New...?newsId=1000303

Or here : http://ensupport.zte.com.cn/OldEnSupport/H...010-7/105.shtml

Or here : http://www.gomonews.com/zte-quietly-releas...ir-source-code/

Any hope ?

Or any chance to upgrade the firmware before using recovery with 2.1 image ?

(another french guy with bouygues operator and a fuc... donut phone.....)

Edited by Barbatos
1

Share this post


Link to post
Share on other sites

Just a little question.

Did we can change the base address when you flash?

Edited by Mytriox
0

Share this post


Link to post
Share on other sites

Barbatos > already try this, by as i say, when i try to compile the source kernel 2.1 i got a file with 1,9 Mo size and it appears that it's to big for the link

The firmware have to be flash before .... and i don't know how (I might be wrong, and i'd love to hear here that someone have a solution :))

Mytriox > the base address is program in the firmware of the phone (upper that kernel) so even if you change the base address in boot.img ou recovery.img the phone don't mind.

(you can try to change this in the perl script by adding --base )

0

Share this post


Link to post
Share on other sites

Thanks for the reply.

Another dumb question

In this case how bouygue will do for updating the link?

0

Share this post


Link to post
Share on other sites
Thanks for the reply.

Another dumb question

In this case how bouygue will do for updating the link?

Maybe they just won't update it... :)

0

Share this post


Link to post
Share on other sites

I have tested to compile an android 2.1.

No problem to compile, with cross_compilation and all option to rum "make".

But when i must create the boot.img with the file zImage, i use this command :

./mkbootimg --kernel omap/arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=ttyS2,115200n8 rw [email protected] init=/init ip=off brdrev=P3A_CDMA mtdparts=omap2-nand.0:[email protected](mbm),[email protected](cdt),[email protected](lbl),[email protected](misc),3584k(boo

),4608k(recovery),143744k(system),94848k(cache),268032k(userdata),2m(kpanic)" -o boot.img

The memorys values "[email protected](mbm),[email protected](cdt),[email protected](lbl),[email protected](misc),3584k(boot)

4608k(recovery),143744k(system),94848k(cache),268032k(userdata),2m(kpanic)" are good or not ?

Best Regards !

0

Share this post


Link to post
Share on other sites
I have tested to compile an android 2.1.

No problem to compile, with cross_compilation and all option to rum "make".

But when i must create the boot.img with the file zImage, i use this command :

./mkbootimg --kernel omap/arch/arm/boot/zImage --ramdisk boot.img-ramdisk.gz --cmdline "console=ttyS2,115200n8 rw [email protected] init=/init ip=off brdrev=P3A_CDMA mtdparts=omap2-nand.0:[email protected](mbm),[email protected](cdt),[email protected](lbl),[email protected](misc),3584k(boo

),4608k(recovery),143744k(system),94848k(cache),268032k(userdata),2m(kpanic)" -o boot.img

The memorys values "[email protected](mbm),[email protected](cdt),[email protected](lbl),[email protected](misc),3584k(boot)

4608k(recovery),143744k(system),94848k(cache),268032k(userdata),2m(kpanic)" are good or not ?

Best Regards !

I have tested to compile kernel,too. ( android 2.1 and 1.6),sourece code from ZTE website。

No problem to compile,but when flash-image into the phone ,the screen turn to colourful point.

I thought LCD drivers has some problem.

I hope somebody could test to compile android 1.6 kernel.

0

Share this post


Link to post
Share on other sites

Same thing with the 1.6 kernel, i try to compile it a while ago.

i don't know if it's a LCD driver problem or a memory problem, cause the phone just freeze or flash, but nothing happens, no welcome sound.

The src was not proper to work .....

0

Share this post


Link to post
Share on other sites

Hi all !

I need your recovery img, because my ZTE Link is locked on the unlocking scheme and my phone asks me my google account (i lost it).

But i dont know how to install it.

Can anyone tell me how i can install the recovery img on my ZTE ?

0

Share this post


Link to post
Share on other sites

Hi dheen,

I know that that's an old topic but I'd like to know how did you manage to change the recovery for ZTE Racer to have a working recovery for the ZTE Link?

0

Share this post


Link to post
Share on other sites

Has anyone tried the gen1/gen2 versions of clockwork with the Link?

I found the source for the Link, but I cant get it to compile there seems to be some issues with lots of ZTE's source code releases.

0

Share this post


Link to post
Share on other sites

NEED HELP URGENT

Hi i am just a newbe (sory for my english) i have ZTE-LINK after many days of search i found a customer upgrade tool & drivers for zte link on their Handsets Services & Support page (on this address)

http://wwwen.zte.com.cn/en/products/mobile/handset_services/index.jsp?stateId=1385&state=France&chnlid=5352

i download it run on xp but the problem is its interface language is French which i can't understand kindly someone translate it.

another thing my phone (zte-link)is not going in FTM mode or in Recovery mode with any key combination or battery removel & insurtion.

Please help m in this matter

Thanks in advance.

Tool img. is attched. zte.bmp

0

Share this post


Link to post
Share on other sites

NEED HELP URGENT

Hi i am just a newbe (sory for my english) i have ZTE-LINK after many days of search i found a customer upgrade tool & drivers for zte link on their Handsets Services & Support page (on this address)

http://wwwen.zte.com...nce&chnlid=5352

i download it run on xp but the problem is its interface language is French which i can't understand kindly someone translate it.

another thing my phone (zte-link)is not going in FTM mode or in Recovery mode with any key combination or battery removel & insurtion.

Please help m in this matter

Thanks in advance.

Tool img. is attched. zte.bmp

Hi !

Can you upload this program here please ? (no acces error 500)

Translate :

the phone will be updated in version : P726GV1.0.0B03

*Chinese language*

d. Install driver BEFORE start update (USB driver ??)

e. Save your contacts and personnals data before start update

f. The phone must switch to download mod before update: stop your device. remove the battery. press volume key. connect your device to PC with USB cable and start device(always volume key pressed)

The rest is in chinese language...

Volume up I think...

Sorry for my english :P

Thanks

Edited by St3phen
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.