Jump to content

[RECOVERY] : ClockworkMod Recovery for ZTE Blade [OLED+TFT]


Recommended Posts

Posted

WAIT, SO IF I HAVE A VERSION OF clockwork recovery 2.5.1.8 I can't use the update.zip method with 3.0.0.6?!

Posted

Also, how do I direct comand promt into a directory, sorry... I kind of forgot, so I open command promt I have the blade.img file and fast boot on my desktop... then what?

And fastboot won't open for some reason. please help.

Guest Ricksy75
Posted

i updated mine with the update zip, i went from 2518 straight to 3006 and it works fine so far, made a backup and did a recovery all ok.

Guest lizhihuaxia
Posted

who can tell me which is better between RA-recovery and clockworld

Posted (edited)

I have ClockworkMod Recovery 2.5.0.9 (modaco r2) - can I update this latest version using the zip method?

Sorted - it worked!

Edited by Ash.UK
Guest jasonXXx
Posted
Usb mounting not working for me in recovery 3.0.0.6.

Edit 1

Ok i have a log now im using a uk white tft with de_crossed r0.2 and clockwork 3.0.0.6 i flashed this via fastboot all seems to work nice but not mount usb storage please can you look at this seb?

Log: http://pastebin.com/j16RSBym

Guest fineking
Posted
Ah, yes, sorry I got the file name wrong... however I did build a version 3.0.0.6 that should work, can you check it out and let me know if it works?

recovery-clockwork-3.0.0.6-x880.img - MD5 : 0448e6286240afefccc469ce4e7e4a80

I seem to remember that was a 'feature' of some of the other European devices, there is a thread somewhere that tells you how to modify the phone.apk so it is unlocked, I will try and track that down and see what I can find out when I'm back in the US

Hi, Sebastian

I have tested the new "recovery-clockwork-3.0.0.6-x880.img ". It is also successful!

(ClockworkMod Recovery v3.0.06 is displayed)

Good Job, Thank you very much!

Guest southeastblue
Posted (edited)

Not sure if anyone can help but I'm a bit stuck...

I had a San Francisco Blade since release, but it started to reboot itself randomly. I got a replacement from Orange really quickly, but now I'm stuck in my attempts to install Clockwork Mod as when I hold down the up volume key and the power key nothing happens - the phone just boots like normal.

Is there some kind of work around here? It's an OLED one still like my original so I assumed since it was an earlier model it would be act the same as my last phone. Also holding down power, volume up, and home doesn't do anything either.

Any help appreciated.

EDIT: Holding volume down shows the white FTM screen, is this any use to me?

EDIT AGAIN: Managed to install it using recovery manager instead! :D

Edited by southeastblue
Guest logicalextreme
Posted

Cheers Sebastian. Think your site's getting hammered at the moment as it's taken me half an hour to get 17% of 2.5.1.8! For anyone else interested, I Googled the filename and got one of 4shared. MD5 checks out.

Guest JimJam707
Posted

Are their any benefits of using your build of ClockworkMod over the official one(s) by Koush on Rom Manager?

Posted (edited)

If I want to install CM7 do I need 2.5.1.8 or 3.0.0.6? I already have this 2.5.1.8 installed, but I'm little confused what are benefits of this new 3 version? And is it mandatory to install CM7 or can I install CM7 just by using this 2.5.1.8?

Edited by Oyorf
Posted
If I want to install CM7 do I need 2.5.1.8 or 3.0.0.6? I already have this 2.5.1.8 installed, but I'm little confused what are benefits of this new 3 version? And is it mandatory to install CM7 or can I install CM7 just by using this 2.5.1.8?

Upgrade to 3.0.0.6 just to be sure!

Guest limawhiskey
Posted
If I want to install CM7 do I need 2.5.1.8 or 3.0.0.6?
I found CM7 would not install with 2.5.1.8. Once I updated to 3.0.0.6 it installed fine.
Guest Sebastian404
Posted
Are their any benefits of using your build of ClockworkMod over the official one(s) by Koush on Rom Manager?

officially none, the official one is the one you officially should be using, since it it 'official', officially

Guest hecatae
Posted

strange thing is that rom-manager recognises neither seb or koush's version until it flashes recovery with a version it has downloaded, found this out on a re-install of cm7.

I think recovery manager has the same issue occuring

Posted
Not sure if anyone can help but I'm a bit stuck...

I had a San Francisco Blade since release, but it started to reboot itself randomly. I got a replacement from Orange really quickly, but now I'm stuck in my attempts to install Clockwork Mod as when I hold down the up volume key and the power key nothing happens - the phone just boots like normal.

Is there some kind of work around here? It's an OLED one still like my original so I assumed since it was an earlier model it would be act the same as my last phone. Also holding down power, volume up, and home doesn't do anything either.

Any help appreciated.

EDIT: Holding volume down shows the white FTM screen, is this any use to me?

EDIT AGAIN: Managed to install it using recovery manager instead! :huh:

I also had a replacement TFT was changed to OLED, but holding volume up key do not provide the "green android" screen. I install clock work via Rom Manager, but I would like to have alternative install clockwork from PC. How to do this?

Posted (edited)
I also had a replacement TFT was changed to OLED, but holding volume up key do not provide the "green android" screen. I install clock work via Rom Manager, but I would like to have alternative install clockwork from PC. How to do this?

If you're running flb-froyo (i think modaco r12 too) there's a reboot app, select reboot to bootloader & you can use fastboot. If you're running any other rooted rom, then get/use android terminal & type these commands


su
reboot bootloader
[/codebox]

you can also do it with adb, adb reboot bootloader

Edited by wbaw
Guest dj_pirtu
Posted

I'm getting pissed off cause my Blade dont like Clockwork 2.5.0.9/2.5.1.3/2.5.1.8 versions at all, endless boot loop. 3.0.0.6 works well but cant install any addons with that. Same thing with fastboot or recovery manager. What next?

Guest jasonXXx
Posted

@Seb have you managed to check the usb storage mounting via the recivery yet? The log is posted above.

Guest Sebastian404
Posted
@Seb have you managed to check the usb storage mounting via the recivery yet? The log is posted above.

Im catching up after being away from home for about 3 months....

1) does it work under 3.0.0.5?

2) have you got the latest ZTE drivers installed?

3) can you mount your android device as a USB device in normal operation?

Guest jasonXXx
Posted
Im catching up after being away from home for about 3 months....

1) does it work under 3.0.0.5?

2) have you got the latest ZTE drivers installed?

3) can you mount your android device as a USB device in normal operation?

Yes to all thanks.

Guest limawhiskey
Posted (edited)

It works ok for me with 3.0.0.6.

My log is the same as yours, except I don't get the write error:

E:Unable to write to ums lunfile (No such file or directory)

or the mount error:

W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)

I flashed 3.0.0.6 via Recovery Manager, don't know if this will help though.

Edited by limawhiskey
Guest jasonXXx
Posted
It works ok for me with 3.0.0.6.

My log is the same as yours, except I don't get the write error:

E:Unable to write to ums lunfile (No such file or directory)

or the mount error:

W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)

I flashed 3.0.0.6 via Recovery Manager, don't know if this will help though.

Hmm strange were did you get your drivers?

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...

Important Information

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