• Announcements

    • Reminder - MoDaCo position on illegal content   07/30/15

      ILLEGAL CONTENT I'd like to just reaffirm MoDaCo's position regarding piracy and illegal content in the light of some recent questions / postings. Posts will be censored by myself or my moderation team if the contain or link to: Illegal / pirated / cracked software or sites that host such softwareNintendo emulators / ROMs or sites hosting them (in light of Nintendo's legal stance)CUSTOM ROMS You may discuss and post links to custom device ROMs on MoDaCo, provided the following rules are adhered to: ROMs must not contain any illegal 3rd party software (this includes trial versions included without permission)ROMs must give full credit to the original authorISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • Reminder: Selling items on the forum directly is not allowed   07/30/15

      Please note that selling items on the forum directly is not allowed by the forum rules. There is a forum for eBay auctions whereby you can list the items on eBay and link to them there. This is the ONLY forum for this type of activity. You may also advertise links to the eBay forum in your signature. Please note that selling directly in contravention of these rules will result in a warning / suspension / ban.

[RECOVERY] ClockworkMod Recovery v6.0.0.8

82 posts in this topic

Posted

any idea about the TMV‘s?

0

Share this post


Link to post
Share on other sites

Posted

Reverted to Flibbesan's 5.0.2.7. until there is a version which works with TMV's soft keys

0

Share this post


Link to post
Share on other sites

Posted (edited)

hi guys

i have just to flash this with Terminal Emulator (as i could not fast boot v5.0.2.7) using the command,

flash_image recovery recovery-clockwork-5.5.0.4-blade2.img

and got,

imgfailed with error: -1

as always an help would be gratefully appreciated.

recovery-clockwork-5.5.0.4-blade2.img is on my SD card is this the correct location?

Edited by plewis1981
0

Share this post


Link to post
Share on other sites

Posted

Are you in that directory in Terminal Emulator?

"cd /sdcard"

0

Share this post


Link to post
Share on other sites

Posted (edited)

?? this is the first time i have used terminal emulator i will have a look see what i can fined

do i have to change initial command to cd /sdcard?

Edited by plewis1981
0

Share this post


Link to post
Share on other sites

Posted (edited)

Flashed a rom with this recovery. work nice. usb mounting and adb too.

Nice job, again, Dazzozo.

(French Blade S)

Edited by app10336
0

Share this post


Link to post
Share on other sites

Posted (edited)

Flashed successfully using Terminal Emulator following this guide

http://androidforums...l-emulator.html

Works like a dream.

Grate work Dazzozo.

Edited by plewis1981
0

Share this post


Link to post
Share on other sites

Posted

Just put a flashable zip up. I'll look in to the touch buttons another time.

0

Share this post


Link to post
Share on other sites

Posted

Thanks Daz - nice to know a TMV compatible version is on your To Do list

0

Share this post


Link to post
Share on other sites

Posted

TPT version ? :blush:

0

Share this post


Link to post
Share on other sites

Posted

j

0

Share this post


Link to post
Share on other sites

Posted

Bump! v6, probably tied in to Jelly Bean and CM10 in some way, now has some strange background image and might work on the Vivacity devices with touch buttons!

1

Share this post


Link to post
Share on other sites

Posted

Thanks daz just flashed the zip all seams to be working on sf2

0

Share this post


Link to post
Share on other sites

Posted (edited)

There a way to do it a TPT like v4.0 / v5.0 ?

Tested too, seam to work fine.

Edited by app10336
0

Share this post


Link to post
Share on other sites

Posted

More branches!

https://github.com/D...2/tree/recovery

I just pushed all my recovery stuff to GitHub.

TPTs - is there much point? There's a zip here, is that not easy enough?

0

Share this post


Link to post
Share on other sites

Posted

TPTs - is there much point? There's a zip here, is that not easy enough?

For me yes, of course. You're doing an amazing job for this device.

I'm just thinking that for new users, flash the best recovery as possible at first time. (this one should be the best ^^)

I maintain tutorials for French community. I think is useful to have last version for every things.

Anyway, if it's not possible, it's not possible, sorry for request

0

Share this post


Link to post
Share on other sites

Posted

It's possible, I just wondered what the reasoning was.

When I get word that it's good on the Vivacity side I'll consider TPTs.

0

Share this post


Link to post
Share on other sites

Posted

Thanks, I hope this will vork for T-Mobile.

0

Share this post


Link to post
Share on other sites

Posted (edited)

Just tried this on my Vivacity, the touch buttons do not work, however pressing the top power button allows me to select an option, I cannot go back once an option is selected. It also seems like after rebooting from Clockworkmod I must do a battery pull, if I don't do this the phone stays on the boot screen.

Edited by nbrasso
0

Share this post


Link to post
Share on other sites

Posted

If you navigate to advanced -> key test do the touch buttons respond?

0

Share this post


Link to post
Share on other sites

Posted

Image: recovery-clockwork-6.0.0.8-blade2.img 4,046 KB - MD5: 7087abb11cc3e721db8ef5c6b7913cc8

ZIP: recovery-clockwork-6.0.0.8-blade2.zip 4,308 KB - MD5: 42146e7ab10624430595a6a04553aec2

Don't think it's now better to name these files as Blade S or Crescent Daz? :) To avoid possible confusion and/or not let Blade II users mess up their phones?

Blade2 - ZTE naming fail

1

Share this post


Link to post
Share on other sites

Posted

blade2 = internal name. I don't download things with "Nexus 7" in their name for my tablet, I download things with "grouper".

It is indeed a naming fail but it is wrong for me to name it otherwise. I will add a warning to the first post, though.

Regarding Vivacity; I need someone I can work with to get this sorted out.

First: run a key test, does it report keys for the capacitive buttons?

If not: try rebooting from Android in to recovery, do the buttons now work?

0

Share this post


Link to post
Share on other sites

Posted

Can a Vivacity user test this: http://crescent.theb...ivacitytest.img

Edit: apparently Vivacity users no longer exist :P

0

Share this post


Link to post
Share on other sites

Posted (edited)

I will test it, and report back here. When i navigated to advanced -> key test the buttons still did not respond the same with rebooting to recovery from Android.

Touch buttons still don't seem to be working with the Vivacity test image.

Edited by nbrasso
0

Share this post


Link to post
Share on other sites

Posted

Makes absolutely no sense. We're now using flibblesan's kernel, too. There appears to be literally nothing different between the two images in terms of keys, especially in the Vivacity test image.

I'll keep looking, but...

I have no idea, honestly.

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-2015. MoDaCo uses IntelliTxt technology.