Jump to content

Semi-Bricked my ZTE BLADE. What to do?


Recommended Posts

Guest Ziemba
Posted

Hey, I have a problem with my RedBull Mobile ZTE BLADE gen 2 from Play. I've been running on CM7 till' I crushed my headphones entering. I decided to turn it back to shop to repair it on guarantee so I wanted to flash stock ROM back. I entered clocwork recovery and flashed it with ROM. Then the phone tried to reboot and... stayed in RedBull Mobile logo. I tryed to debrick it using this tutorial:

http://www.modaco.com/topic/343587-guide-de-bricking-a-zte-blade/

but any TPT returns

ERORR!

ERORR!

ERORR!

ERORR!

ERORR!

I also tried fastboot but when I'm connecting phone to computer the computer says that there is error installing drivers. I tried updating drivers, I tried installing many different drivers manualy and failed. When I choose add new hardware, and choose ADB Interface there is no options like fastboot interface like in tutorial. And other options like Composite Interface whatever and single something interface whatever return error number 10. So.. they dont work. And yea, I tried updating drivers through hardware manager. It just doesn't work.

So... I'm still stuck on the RedBull Mobile screen which is more or less the same as Grenn Android screen. Can't get into recovery, and I can't install drivers for any other mode.

I believe that If only I could install the driver which can make me comunicate with phone, I could use one of the method in the de-brick tutorial. Or maybe lack of drivers means that phone is bricked more than i thouht?

Please help..

Posted (edited)

When you bought the device was it Gen 1 or Gen 2? Try using one of the TPT's from http://amphoras.co.u...oads/blade-tpts make sure that you use thes instructions to flash it.

After downloading, check the md5sum.

Unzip the file to the root of your sdcard. You should end up with a folder called "image" on the root of your sdcard with a some files inside.

Check the md5sum of the files match those listed in the nandroid.md5 file.

Turn your phone off and take the battery out.

Put the battery back in and power on holding the vol+ and menu buttons.

You should see green text appear on the screen, then once its finished you should boot into Clockwork recovery.

Flash your chosen rom and reboot.

If the TPT won't start, try using a different sdcard. Some just don't like TPTs.

Warnings:

Delete the image folder once you're done to prevent accidental flashing.

Check the md5sums. If they don't match, delete it and try downloading again.

No guarantees, when flashing a TPT there is always a risk of permentantly bricking your phone.

Any problems post back here :)

Edited by hydo1
Guest Ziemba
Posted (edited)

It was gen2. I'll report back when I'm done with that TPT ;)

thanks

Well, I tried one of these earlier and I chose gen 2 stock, and got

error!

error!

error!

error!

error!

error!

I used different sd card and its still the same. md5 checksum is ok.

Edited by Ziemba
Posted

hmmmmmmmmm.........

This isn't looking good :wacko:.

You definitely can't get fastboot?

Guest Ziemba
Posted

Well.. As I mentioned.. when I use the combination I get into RedBull Mobile and when I connect to comp it can't get any drivers to work. And I tried different drivers.

And I tried "You seen this thread? http://www.modaco.co...rivers-and-adb/ " also, but windows doesn't want to make it happen. When I locate the folder, it says that drivers are up to date, no matter if I install them or uninstall or whatever. It still shows unknown device.

I tried it on windows 7 64x and widnows 8 64x.

By the way, I dont know how to make fastboot work on Linux.

Posted (edited)

Just make sure that your blade is not one of the ones listed under the warnings section. I am not familiar with the Red Bull Mobile Blade (in fact I never even knew that there was a Red Bull mobile network).

Also if you cannot make fastboot work on your PC try another one windows when it comes to drivers is very inconsistent, sometimes it works really well but other times the drivers get corrupted somewhere along the way and then it is a royal pain in the ass to sort it out?

Edited by hydo1
Guest AmbushReality
Posted

Sorry to chip in, but have you considered trying Linux, either by hard install or bootable USB? Linux doesn't require drivers, so you may have a chance there :)

Guest Ziemba
Posted (edited)

Well I connected phone on Ubuntu but nothing happend. I'm not too familiar with Unix/Linux systems so I didn't know where to go next ;) Thanks for replays tho, I'll try them ;)

And RedBull Mobile is a small part of Play mobile network in Poland ;)

Well.. all these TPTs show the same error error error error. Maybe someone familiar with linux/unix may suggest something?

Edited by Ziemba
Guest Ziemba
Posted

Last resort is returning it on guarantee and hoping its to bricked to decide if it was violated :P

Posted

Might work.... Have you tried the windows method mentioned in post 7?

  • 4 weeks later...
Posted (edited)

Yea.. all TPTs say the same thing

have u solved the problem? , is ur mobile 256 or 512 ram?, it is showing error just because all of them are the wronng tpts for your phone.

Edited by alfu

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.