ClockWork problems

[Guest deksman2]

Ok,

I don't know why, but CWM versions above 3.0.15 (I think) refuse to work on my Blade (they always hang at the green Android image after pressing the - button... I tried + as well),

It's Gen2 btw with ginger stirFry b21 so I have no idea what's happening.

I cannot use newest CWM's and it's frustrating.

Anyone else has these issues?

Also do you happen to know how to resolve them?

Also, it's become very difficult to find Recovery Manager online for the Blade (I'm using 0.37 beta version) along with the CWM itself.

So what's going on?

P.S. Recovery Manager keeps saying: 'Unrecognized' under 'Currently installed Recovery', and I cannot restore older CWM versions either (all now hang at green Android Icon).

Installing new ROM's via PC is not an option since the ZTE Blade drivers simply refuse to be accepted by my Win 7 x64 Ultimate.

Edited September 24, 2011 by deksman2

[Guest shmizan]

try installing Rom Manager app, and flash CWM from it.

also find the right drivers for your Windows in the drivers thread. see which works for the x64 users.

I'm running Windows 7 x64 Enterprise and I have the drivers working properly.

it's one of these 3:

ZTE_HS_Driver_Setup.exe / ZTE Android USB Driver for Microsoft PC_5.2066.1.8.zip / 64bit-Win7.zip

[Guest deksman2]

try installing Rom Manager app, and flash CWM from it.

also find the right drivers for your Windows in the drivers thread. see which works for the x64 users.

I'm running Windows 7 x64 Enterprise and I have the drivers working properly.

it's one of these 3:

ZTE_HS_Driver_Setup.exe / ZTE Android USB Driver for Microsoft PC_5.2066.1.8.zip / 64bit-Win7.zip

How did you install the drivers in question?

Via Device Manager?

Because I tried.

When the Blade is on, Windows detects it properly and installs proper drivers, however, when it's off, Windows detects it as an Unknown device, and I cannot update it's drivers regardless of how I try.

I point it to the installed directory and Windows keeps complaining that the drivers aren't right and that I must need x64 version (regardless that they ARE).

I'm fairly proficient with computers but the install procedure for this little piece is annoying at best. So much resistance.

Nothing helps.

I tried the Rom Manager.

I have bad news.

Android Market prohibits me from installing the said application because I'm in Croatia.

I was able to find the 3.0.0.0 version though, and it installed ClockworkMod 3.0.1.4. if I'm not mistaken, but my Blade keeps hanging on the Green Android pic if it attempts to go into ClockWorkMod.

I don't get it.

Is it possible the SD card got damaged from when I dropped the phone on the floor twice?

though, the old ClockworkMod worked afterwards just fine.

It wasn't until today when I tried updating the CWM with the newest version that the mobile keeps freezing at the Green Android bit (irrespective of the CWM being installed).

[Guest muller37]

you could backup, try a new tpt of gsf then reinstall backup maybe.

[Guest deksman2]

you could backup, try a new tpt of gsf then reinstall backup maybe.

Can you be (much) more specific?

With what will I back up the ROM if the smartphone cannot access CWM?

Regarding the TPT... I could try that, but doesn't that convert GEN1 to GEN2 for the most part?

I hadn't found instructions on the GEN2 to GEN2 (or just installing a GEN2 ROM from an older GEN2 ROM).

The current ROM is running fine, but I wanted to upgrade to the newest version because of Burstlam kernel.

And the instructions I found are confusing because they imply doing other things and access to CWM (which I don't have).

Still, I don't have any kind of a safety net if something goes wrong. I could in essence end up easily with a bricked phone with no way of restoring it.

[Guest deksman2]

RESOLVED!!! - at least for now.

I was able to find proper drivers for my ZTE blade and update them via Device manager.

It was a combination of 2 different driver sets.

Strange.

Anyway, I was able to install CWM 4.0.0.5 using the Fastboot method.

Lol... I think I can try installing the latest one as well... though for now I'm gonna try to install the ROM I wanted to put.