Database Users

[Q] Help, stuck in bootloader

I have two Defys. One flashed ok and works fine. But not the other one. I flashed stock 2.2 (can't remember which exactly), but on the second phone it was somewhat unstable, slow, throwed UUID inconsistency errors... It was rooted just after flashing, so I don't know exactly if it was problem of sbf or root. And I couldn't get into recovery menu to wipe. Since on the first phone everything worked fine, I thought something went wrong and re-flash will help. So I flashed the same sbf, and it didn't boot at all =| It always boots into bootloader, which says
Code:
Bootloader
09.10
Code Corrupt
Battery OK
Ok to Program
Transfer Mode:
USB
Tried other firmwares, but RSD Lite says
Code:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File: 0x9D6, Phone: 0x4805
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
While on the phone's screen there is the following message:
Code:
SW Update
In progress...
Tried to flash just bootloader, same errors... Tried to change cable and even computer — no luck =[
So I'm pretty confused =| Is it software or hardware problem? Can I send it back to seller to fix it? What can be done?

Hey me too!
I'm also stuck in here...
I hope that there are some method to solve this ploblem

If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz

ifu said:
If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
Click to expand...
Click to collapse
nothing happens here pressing vol+/- at the same time... if I tap the lower right corner I see the normal recovery, it's what you're referring to?
ifu said:
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse

ifu said:
If something went wrong and you stuck in a bootloop etc, shutdown the system (if possible) or pull out the battery.
-Go into the system recovery with "vol down + power".
-Then when you see the android update guy press vol down + vol up at the same time.
-Wipe your phone + factory reset.
-Reboot and hold "vol up + power"
-You are now into bootloader mode, reflash the system with RSD Lite and a sbf you like
-Your Defy is back in biz
Click to expand...
Click to collapse
This act I know...but not in this case
Firstly I can't go to recovery mode moreover..(even I hold vol down + power how long..)
Then I can't go on the step as you listed...
I just stuck in Bootloader mode automatically when i put in the battery..
Is there any reset solution or some method to fix the "Error verifying Code Group xx checksums"?
Thanks

kix_k9 said:
This act I know...but not in this case
Firstly I can't go to recovery mode moreover..(even I hold vol down + power how long..)
Then I can't go on the step as you listed...
I just stuck in Bootloader mode automatically when i put in the battery..
Click to expand...
Click to collapse
Exactly. It does not boot, going straight to bootloader and no futher, regardless of the buttons I'm pressing.
But one day the miracle has happened I routinely connected the phone to my laptop, preparing to flash it one more time. Inserted half-charged battery from my second phone, just as usual. But before I started RSD I was shocked by vibration meaning my "bricked" phone had booted just fine!
I launched Clockwork recovery and installed its recovery system. However, when I tried to boot into it, it didn't and booted as usual. I tried once more with the same result. Then I tried to boot into default recovery menu (power + volume down) and succeded. As I had those UID errors messages, I decided to wipe as those messages suggested. After that completed and my phone booted successfully (being a triumph as I considered it to be dead), I still got those UID errors =\
I booted into bootloader to see if there is still "Code corrupt" error, and to my pleasure, it wasn't. Nothing to lose, I thought, and tried to flash 3.4.3-11 SBF. And... now I'm back in bootloader with "Code corrupt" error and without any idea what's happening =| But at least I know the phone can boot (and can't figure out how to make it do so =)) Will do more research soon.
P.S. Curiously, RSD couldn't detect "resurrected" phone unless in bootloader (my second phone is deteted even being not in bootloader), and I don't remember exactly, but I think I couldn't turn it into USB mass storage mode — it just reverted back to Motorola Phone Portal mode.
Any ideas?

Hi Shevchuk
I had the same problem a couple of weeks ago that my defy stuck on that screen and I wasn't able to flash it.
As my Defy was rooted I tried it to fix it at my own. I tried a lot, different PCs with different OS and different versions of RSD but nothing worked. So I decided one day to call the motorola support hotline and told them that it got stuck on that screen without mentioning that it was rooted and that I tried to flash it. Finally, they told me to send it in.
After two weeks I got my Defy back and it was working. They said that something was broken and exchanged that part

Code Corrupt is not a pds problem... but a simple "bad flash" problem
pds one will reboot the device after logo...
for pds problem :
if you have 2 defys you can maybe do it...
first you need to flash the same SBF on both devices
then with adb shell (as root) you need to extract the fully working system partition (with the signature flag) :
dd if=/dev/block/system of=/sdcard/CG39.ext3.smg
this image will be mountable (and modifiable) on a linux machine :
mkdir ~/system
mount -o loop -t ext3 CG39.ext3.smg ~/system
cd ~/system
you will be able to install bootmenu inside the image, then repack a sbf with this "tuned" CG39... and to lock boot before the /pds check, which can reboot device
and with bootmenu, you can flash cm7 with the recovery

I have the same problem code corrupt but nothing to ay

crub55 said:
I have the same problem code corrupt but nothing to ay
Click to expand...
Click to collapse
Did anyone of you ever find a solution I have the exact same problem.

I have same problem
Epsylon3 said:
Code Corrupt is not a pds problem... but a simple "bad flash" problem
pds one will reboot the device after logo...
for pds problem :
if you have 2 defys you can maybe do it...
first you need to flash the same SBF on both devices
then with adb shell (as root) you need to extract the fully working system partition (with the signature flag) :
dd if=/dev/block/system of=/sdcard/CG39.ext3.smg
this image will be mountable (and modifiable) on a linux machine :
mkdir ~/system
mount -o loop -t ext3 CG39.ext3.smg ~/system
cd ~/system
you will be able to install bootmenu inside the image, then repack a sbf with this "tuned" CG39... and to lock boot before the /pds check, which can reboot device
and with bootmenu, you can flash cm7 with the recovery
Click to expand...
Click to collapse
I have same problem and i can't slove it please help me follow this quote.
I have one defy and I don't know how to do it.

Please ask all questions in the Q&A section. Thread moved there.

Worked For Me
Shevchuk said:
I have two Defys. One flashed ok and works fine. But not the other one. I flashed stock 2.2 (can't remember which exactly), but on the second phone it was somewhat unstable, slow, throwed UUID inconsistency errors... It was rooted just after flashing, so I don't know exactly if it was problem of sbf or root. And I couldn't get into recovery menu to wipe. Since on the first phone everything worked fine, I thought something went wrong and re-flash will help. So I flashed the same sbf, and it didn't boot at all =| It always boots into bootloader, which says
Code:
Bootloader
09.10
Code Corrupt
Battery OK
Ok to Program
Transfer Mode:
USB
Tried other firmwares, but RSD Lite says
Code:
Phone[0000]: Code Group 32 checksums match.
Phone[0000]: Error verifying Code Group 33 checksums. File: 0x9D6, Phone: 0x4805
[...]
Failed flashing process. Phone[0000]: Error getting subscriber unit checksum. Device API Error: 0xE003003F. Command: RQRCS (0xE403203F); phone connected
While on the phone's screen there is the following message:
Code:
SW Update
In progress...
Tried to flash just bootloader, same errors... Tried to change cable and even computer — no luck =[
So I'm pretty confused =| Is it software or hardware problem? Can I send it back to seller to fix it? What can be done?
Click to expand...
Click to collapse
I know i might sound stupid. But i had the same problem, i kept my phone untouched for a few days. And after that i usually came to try another SBF file but my phone Turned on magically, I still dont know how it happened, but it did. There is some way to fix it, but cant figure out how.

Did anyone find a solution to this problem??

[Q] Pure root script, problems & questions

Hi all gurus,
please forgive the noobiness but the task is quite urgent and actually, since I'm a new, noob user, I can't post in the dev section.
Well... my need was to install a fixed wpa_supplicant on a stock WW ROM in order to manage ad hoc wifi connections. In order to do so, I tried the Pure Root script (APK mode correctly up & running)
Did as follows:
- I did a complete backup of both boot.img and recovery.img from my stock Transformer using the "Backup current Boot.img and/or Recovery.img" option ; everything went fine... but under the directory /images/backup I can't see any file
- i tried to install a root WW using the first option of the script; I choose to install recovery too (CWM?). Everything fine; I rebooted the tablet but Root Explorer tells me I'm not root ... Am I missing something?
(tried then to install the modified wpa_supplicant via CWM... but again, installation done with success, reboot -> no ad-hoc connection management )
I decided then to revert back to the original Asus stock version (option 4: " Install Stock ww Boot.img and/or Recovery.img").
Everything goes fine and actually I thing now I'm running with the stock worldwide version... But there's a thing I don't understand: I tried to boot in recovery mode to verify that CWM is not present anymore: so pressing ON + volume down, this is what I see:
"Android ww_epad-user bootloader ( e) released by "WW_epad-8.4.4.11-20110711"
Checking for android ota recovery
Checking for RCK... Press key <VOL_UP> in 5 sec to enter RCK "
If I don't press VOL_UP I get the wiping data option: " press <VOL_UP> to execute or <VOL_DOWN> to cancel wiping data". It is not the one of CWM.
BUT if I press VOL_UP ... an Android robot with an exclamative marks appear.
So... what am I missing? What's the actual status of the device? My guess is that stock rom is ok but recovery don't. How can I restore completely the situation to the stock one (or also, previous backups)?
Thanks in advance mates, unfortunately I have to add support for ad-hoc connection in 24 hours (to bring my tablet with me on holiday, otherwise I have no way to connect to the net and the device is quite useless ).
Understanding how to flash to stock version both boot and recovery is quite a nice way to start modding from scratch, having the knowledge that no matter what a mess I can do, there's always a way to repair to original, asus stock version

[Q] Please help

Story : Stock zte blade gets in the hands of a hasty noob
i flash CWM 6.x.x.and a rom
bootloop
i flash CWM 5.x.x and reboot
tries to boot again same non working rom and ends in bootloop again
after flashing the new cwm i cant get in any recovery mode
i tried to power on with vol up + menu or simply with vol up and nothing happens it just passes straight to the stuck rom boot loop
power on and vol down stuck on ZTE image and nothing happens until i remove battery
pls help me to recover my blade
Thank you in advance

Use adb to flash recovery again. Then power on with volume- pressed
Asus TF300T | ZTE Blade

it sais waiting for device ...

ssx2 said:
it sais waiting for device ...
Click to expand...
Click to collapse
Did you switch on the device?
Asus TF300T | ZTE Blade

yes ... i used fastboot to flash the recovery and it sais waiting or device
or pls tell me the right procedure

ssx2 said:
yes ... i used fastboot to flash the recovery and it sais waiting or device
Click to expand...
Click to collapse
There's an unbricking guide on modaco. Read it
Asus TF300T | ZTE Blade

QuantumFoam said:
There's an unbricking guide on modaco. Read it
Asus TF300T | ZTE Blade
Click to expand...
Click to collapse
solved thank you

ssx2 said:
solved thank you
Click to expand...
Click to collapse
Please post how you solved it so tthat future users with similar problems too can solve them
Asus TF300T | ZTE Blade

QuantumFoam said:
Please post how you solved it so tthat future users with similar problems too can solve them
Asus TF300T | ZTE Blade
Click to expand...
Click to collapse
All credits for the tutorial goes to "hedgepigdanie" who wrote the original post in modaco
The dodgy ZTE firmware flasher
This method can help if your blade cannot boot at all. Consider it a LAST RESORT - people do this all the time and only make their situation worse. Only use it if all the above methods fail or if your IMEI is corrupt. Your IMEI will be lost in the process and you will need to use hex editing to fix it up afterwards. This method also requires windows. Most of this is taken from burstlam’s thread here, which you can also refer to (burstlam has posted screenshots which also help to show what to do). Do the following in order:
Boot into download mode and set up connection
Download and install the ZTE USB driver.
Put your phone in download mode by turning it on with both volume buttons held down at the same time. The screen will remain black, but the notification LED should briefly flash red.
Plug it into your computer. The phone should be recognised in windows device manager under “Ports (COM & LPT)” as “ZTE Handset Diagnostic Interface(DFU) (COMxx)”. Take note of the port number (xx). If your phone cannot turn on at all and the LED doesn’t flash, it is dead. Sorry about that.
Flash firmware
Download this file, which contains the ZTE flasher along with firmware to flash your phone with, and unzip it somewhere convenient.
Run “Flasher.exe” from the extracted folder. Press the exclamation mark and login as administrator with the password “ZTEsmt123”.
Under “SW Directory”, select the correct firmware folder inside the extracted folder (European Gen1 firmware or Chinese v880 Gen2 firmware). ONLY flash the one appropriate for your phone.
Leave the default settings as they are – “download cefs” ticked, “no backup restore” selected, and “download” selected.
Go to the “Option” menu and select “Port Config”. Set line 1 to the COM port that you observed in step 3, then press OK.
Press the purple arrow next to line 1 and wait for your phone to be flashed. When finished it should boot into FTM mode.
Edit "channel1.nvm" to hold IMEI
In the flasher folder, open the file “channel1.nvm” with HxD, or a hex editor of your choice.
Go to offset 0x1215. The IMEI is stored between offset 0x1215 and 0x121C. You need to read your correct IMEI from behind your battery and enter it here like this:
In 0x1215 put the first digit of your IMEI followed by A. For each successive pair of digits, enter the second digit followed by the first digit. For example: and IMEI of 123456789012345 would be recorded at 0x1215 as 1A 32 54 76 98 10 32 54. When done, save this file.
Restore channel1.nvm to your phone
Make sure channel1.nvm is in the folder next to the flasher with the correct IMEI.
Connect your phone to your computer and turn on your phone with volume down held. It should boot into FTM mode.
In the flasher, select “restore NV” and “RF/BT/IMEI/unLock info”, and press the purple arrow next to line 1. Your IMEI will now be restored to your phone.
Put clockworkmod in the recovery partition
Take out the battery and turn on the phone. Clockworkmod should load.
Clockworkmod is now installed to your phone’s boot partition. This means that if you install a ROM at this point you will overwrite clockworkmod. You must now flash the correct version of clockworkmod to the recovery partition.
Go to “mounts and storage”, and select mount USB storage. Connect the phone to your computer and copy the correct version of clockworkmod as a zip file (Gen1 for European Gen1 firmware, Gen2 for Chinese firmware) to your SD card, then install it using clockworkmod.
Restart your phone with volume down held. It should boot into clockworkmod. If it boots into FTM mode or does not progress pass the green android, reboot normally and make sure you flashed the correct version of clockworkmod.
You can now flash a ROM (If you flashed Gen1 firmware you can also upgrade to Gen2 via TPT). When you do, check your IMEI. If it is wrong, flash stock recovery in clockworkmod, boot into FTM mode, and repeat (correctly) above from editing channel1.nvm onwards.
Personally i had countered the following situations that put me in difficulty for a few moments:
as put in the download mode the led didnt blinked or turned red as it said it should behave in the tut
and the second part ... after checking the port in Device Manager i didnt noticed the exclamation mark on the driver that meant the driver should be updated ... so when i had to pres the purple arrow nothing happen as actually the flasher didnt recognized the Blade so i chose to update drive from the net and everything went just fine

Please put this thread into stickies section. Going to be very help full for future users
Sent from my Blade using xda app-developers app

[GUIDE]Unbrick the ZTE Blade

Unbricking the ZTE Blade / Dell XCD35 / Orange San Francisco​
Foreword
First off, I have NOT written this guide. Credits go to hedgepigdaniel for composing this guide. I have merely tweaked the language and brought it to XDA for those of us that do not frequent the MoDaCo forums, and frankly, I was sick of answering every "Bricked Blade" question with a "Go to MoDaCo" answer. This guide is meant to help you to recover from a bad flash. It assumes at the very least that you cannot boot android, and can help you as long as your phone can boot into download mode. I have described many ways to unbrick in order of increasing difficulty and risk. Use only the first method that works. These instructions will wipe everything on your phone’s internal memory. Before you follow any of them, charge your battery and have a good night’s sleep. For the purposes of this guide, a Dell XCD35 is a European GSM Blade.
Hard Brick vs Soft Brick
If your phone is soft-bricked, it has a software problem which is rendering it only as useful as a paperweight (i.e. there is nothing physically wrong with it). If it is hard-bricked, it has a physical problem which is rendering it only as useful as a paperweight. The recovery methods below can only help you to recover from a soft-brick because they do not involve any physical repairs. 99% of bricked phones are soft-bricked, and to my knowledge it is always possible to recover a soft-bricked ZTE Blade of the variants this guide is written for. I can't help you much with hard-bricked phones, but I will say this: batteries break before phones. Your Blade may have an old or damaged battery if it displays any of the following symptoms:
-Does not turn on at all, even into download mode as per method 5
-Turns on initially but does not successfully boot android without repeatedly rebooting or turning off, even after recovery using the methods below
-Boots successfully but regularly reboots or turns off, even after recovery using the methods below
- Especially if its behavior is different depending on whether a charger is connected and/or depending on which charger is connected
If you suspect that your phone has a bad battery, you may be interested in buying a new battery from eBay, since it's cheaper than buying a new phone. Sometimes the angle at which the battery is inserted can have an impact: moving the battery from side to side or inserting blu-tak to hold the battery closer to the terminals can sometimes fix the problem.
Corrupt NV memory
If your phone was flashed via windows and will not boot into anything except recovery mode (i.e. FTM mode or clockworkmod), even if you install a compatible ROM and boot normally, then the problem is usually corrupt NV memory. You must use method 4 to solve this problem. You can often solve it by following only the instructions to restore your IMEI (skipping the flashing part), but you may need to do the whole lot.
Method 1 : ClockWorkMod
1. Turn your phone on with volume down held. If it boots into clockwork, then you should be able to fix it from there. In clockworkmod:
2. Go to “backup and restore” and perform a backup of your current setup.
3. Go to “mounts and storage” and select mount USB storage. Connect the phone to a computer and copy your backup from the clockworkmod directory to your computer. Download a Gen1 or Gen2 ROM and copy it to your SD card (not a stock ROM, since it will overwrite clockworkmod). If you are not sure, try installing both Gen1 and Gen2 ROMs.
4. Go to “mounts and storage” and format boot, system, data, cache, and sd-ext.
5. Go to “install zip from SD card” and install the ROM you have downloaded. Restart your phone when it is finished.​
Method 2 : Fastboot
Fastboot is a method of flashing a recovery image to your phone from a computer (which can be running Windows, Linux, or OSX). It does not work with Blades that are running stock Gen2 firmware (i.e. upgraded to stock Gen2 via windows or upgraded to android 2.2 by an official update) unless both the recovery and boot partitions are completely unbootable.
For all platforms
Download and extract this file, which contains both fastboot and clockworkmod for Gen1 and Gen2.
Turn on your phone with volume up held and connect it to your computer. It should not progress beyond the green android. Sometimes you have to wait a few minutes for the computer to recognise it.
For Windows
Download and install the ZTE Handset drivers. Your phone should be listed as "Fastboot Interface" under "ADB Interfaces".
Run windows-flash-gen1-recovery.bat to flash Gen1 clockworkmod, or windows-flash-gen2-recovery.bat to flash gen2 clockworkmod.
After rebooting with volume down held, you should be able to flash a ROM in clockworkmod.
For Linux
Navigate to the extracted folder and run one of the following commands.
To flash Gen1 clockworkmod:
Code:
sudo ./fastboot-linux flash recovery recovery-clockwork-4.0.0.8-blade-gen1.img
To flash Gen2 clockworkmod:
Code:
sudo ./fastboot-linux flash recovery recovery-clockwork-4.0.0.8-blade-gen2.img
After rebooting with volume down held, you should be able to flash a ROM in clockworkmod.
For Mac
I don't know the command but it is probably similar to linux. you need to run fastboot-mac instead of fastboot-linux and flash the appropriate .img file.​
Method 3 : TPT
TPT is a way of flashing part of the low-level firmware on your phone. After successfully flashing the files below you will regain access to clockworkmod. You need a different type of TPT depending on what variant of the Blade you have. If you have a China Unicom v880 or any other Chinese variant then you must not flash a TPT designed for European Blades, and vice versa. Be aware that flashing a modified or corrupt TPT can permanently brick your phone. Choose the appropriate file below.
European Gen1 TPT
Use this if your phone is a European GSM variant and if it is Gen1 or has been upgraded to Gen2 via TPT. This will flash stock Gen1 firmware.
European Gen2 TPT
Use this if your phone is a European GSM variant and if it was sold as Gen2 or upgraded to stock Gen2 via windows. This will flash stock Gen2 firmware.
China Unicom v880 Gen2 TPT
Use this if your phone is a China Unicom v880 (unsure, but may work on Chinese u880/x880). This will flash the stock Gen2 firmware taken from the B15 android 2.2.2 update.
Flashing the TPT
-Download the applicable TPT file from above.
-Unzip and put the “image” folder onto the root directory of your SD card.
-Disconnect and reconnect your SD card and check the integrity of the TPT files. There is a file called "image.hash" in the image folder which contains all the files' md5 hashes in plain text. Make sure that the md5 of all the files match, or you may brick your phone.
-Turn on your phone with the SD card inserted and with menu and volume up held.
-The screen will either stay black or show green text (if you see the green android immediately then it didn't work), and will restart into clockworkmod when done. Wait at least 5 minutes for it to restart if you don’t see anything.
-When it is finished (even if it didn't work), then remove the image directory from the SD card to prevent accidental flashing later on.
-You can now flash a ROM using ClockWorkMod. If it doesn't work, then using a different SD card may help. If you have a European variant then it is safe to try both Gen1 and Gen2 TPTs separately in case you have made a mistake.​
Method 4 : Windows Upgrader
This method flashes the entire low-level firmware and maintains the correct IMEI automatically. To use this method you need to be able to boot into stock recovery. This means that when you turn your phone on with volume down held, the words “FTM” must appear on the screen. If you can access clockworkmod then you don't need to use this method - see above. This method requires windows.
For European Blades, follow this guide and flash any firmware package linked in the guide.
For Chinese Blades, you must follow the same guide but flash this firmware package instead.
If your provider/country is listed here then you can also flash your stock firmware instead, and optionally the stock ROM aswell.​
Method 5 : ZTE Firmware Flasher
This method can help if your blade cannot boot at all. Consider it a LAST RESORT - people do this all the time and only make their situation worse. Only use it if all the above methods fail or if your IMEI is corrupt. Your IMEI will be lost in the process and you will need to use hex editing to fix it up afterwards. This method also requires windows. Most of this is taken from Burstlam’s thread here, which you can also refer to (Burstlam has posted screenshots which also help to show what to do). Do the following in order:
Boot into download mode and set up connection
-Download and install the ZTE USB driver.
-Put your phone in download mode by turning it on with both volume buttons held down at the same time. The screen will remain black, but the notification LED should briefly flash red.
-Plug it into your computer. The phone should be recognised in windows device manager under “Ports (COM & LPT)” as “ZTE Handset Diagnostic Interface(DFU) (COMxx)”. Take note of the port number (xx). If your phone cannot turn on at all and the LED doesn’t flash, it is dead.
Flash firmware
-Download this file, which contains the ZTE flasher along with firmware to flash your phone with, and unzip it somewhere convenient.
-Run “Flasher.exe” from the extracted folder. Press the exclamation mark and login as administrator with the password “ZTEsmt123”.
-Under “SW Directory”, select the correct firmware folder inside the extracted folder (European Gen1 firmware or Chinese v880 Gen2 firmware). ONLY flash the one appropriate for your phone.
-Leave the default settings as they are – “download cefs” ticked, “no backup restore” selected, and “download” selected.
-Go to the “Option” menu and select “Port Config”. Set line 1 to the COM port that you observed in step 3, then press OK.
-Press the purple arrow next to line 1 and wait for your phone to be flashed. When finished it should boot into FTM mode.
Edit "channel1.nvm" to hold IMEI
-In the flasher folder, open the file “channel1.nvm” with HxD, or a hex editor of your choice.
-Go to offset 0x1215. The IMEI is stored between offset 0x1215 and 0x121C. You need to read your correct IMEI from behind your battery and enter it here like this:
-In 0x1215 put the first digit of your IMEI followed by A. For each successive pair of digits, enter the second digit followed by the first digit. For example: and IMEI of 123456789012345 would be recorded at 0x1215 as 1A 32 54 76 98 10 32 54. When done, save this file.
Restore channel1.nvm to your phone
-Make sure channel1.nvm is in the folder next to the flasher with the correct IMEI.
-Connect your phone to your computer and turn on your phone with volume down held. It should boot into FTM mode.
-In the flasher, select “restore NV” and “RF/BT/IMEI/unLock info”, and press the purple arrow next to line 1. Your IMEI will now be restored to your phone.
Put clockworkmod in the recovery partition
-Take out the battery and turn on the phone. Clockworkmod should load.
-Clockworkmod is now installed to your phone’s boot partition. This means that if you install a ROM at this point you will overwrite clockworkmod. You must now flash the correct version of clockworkmod to the recovery partition.
-Go to “mounts and storage”, and select mount USB storage. Connect the phone to your computer and copy the correct version of clockworkmod as a zip file (Gen1 for European Gen1 firmware, Gen2 for Chinese firmware) to your SD card, then install it using clockworkmod.
-Restart your phone with volume down held. It should boot into clockworkmod. If it boots into FTM mode or does not progress pass the green android, reboot normally and make sure you flashed the correct version of clockworkmod.
-You can now flash a ROM (If you flashed Gen1 firmware you can also upgrade to Gen2 via TPT). When you do, check your IMEI. If it is wrong, flash stock recovery in ClockWorkMod, boot into FTM mode, and repeat (correctly) above from "editing channel1.nvm" onwards.​
Useful Links
ZTE Blade All In One Rooting Thread : http://forum.xda-developers.com/showthread.php?t=1644220
ZTE Blade FAQ : http://forum.xda-developers.com/showthread.php?t=1600756​

I tried the fastboot method since my zte blade was unable to get into recovery mode so i downloaded a stock rom extracted it and copied the boot.img cache.img and flashed them using fastboot then i flashed the recovery in the blade-fastboot-recovery folder and it rebooted to clockword and i installed the swedish snow rom using clockworkmod and now my blade is running gingerbread 2.3.5

Help unbricking Balde
Hi, I can't get my Blade to boot into either Clockwork Mod or get it to flash via TPT, the only 'mode' it will enter is the vol+ and vol- ZTE low level mode. I've been through all the unbricking guides and have finally ended up using the method 5 ZTE flasher software. I get the firmware flashed OK, but mostly it still will not enter FTM, CWM or TPT modes. i have tried 5 or 6 different firmwares for different Gens (I don't know the gen it should be / originally was).
The only exception to this is if I use the chinese firmware 'unicom gen2' - even though the one thing I know my Blade wasn't originally is the chinese one. (It was originally an Orange San Fran).
With this firmware flashed I can enter FTM, and so reflash Channel1.nvm (I can alter hex 1215 on with correct IMEI, or leave it, it makes no difference to the outcome).
From here it will boot into CWM v. 3.0.2.4, but written in chinese characters. However if I then go to install zip from SD card then CWM just hangs with the RomManager splash screen, but doesn't actually go any further to let me choose a zip.
Other things I've tried are to swap some of the .img files from other firmwares into the chinese firmwere, but this doesn't work. And I've also tried using adb command line, but adb devices lists no devices, even when connected in FTM mode. (even though ZTE flasher recognises the device)
I'm fresh out of ideas - any one offer any help?

Idea ZTE BLADE Totally DEAD
my idea zte blade is totally dead
i have tried all the method on XDA but the window didn't recognize it (Driver installed)
Please help me.

how do i get offset 0x1215? i can find 1215 but NOT 0x1215??? please advise

Great Tutorial and Support
I learned lots of ways about rooting in these explanations above and had great benefit while saving my phone from bricked state.
Still i have big problems which i couldnt find anywhere, is ZTE Atlas W firmware couldnt be installed in my phone, nor any ROMs give me any benefit. ZTE Atlas model is a new name in XDA developers website so there not any ROMs (i guess) about that phone.
My phone (ZTE ATLAS W) always booting to ClockWorkMode and when i try to install from SD card, it is not working or cant find any ROM to boot it in normal way. I really complicated the phone with some other downloads but still i hope i will survive the phone with your helps... Please tell me all i can.

fuzzweed said:
Hi, I can't get my Blade to boot into either Clockwork Mod or get it to flash via TPT, the only 'mode' it will enter is the vol+ and vol- ZTE low level mode. I've been through all the unbricking guides and have finally ended up using the method 5 ZTE flasher software. I get the firmware flashed OK, but mostly it still will not enter FTM, CWM or TPT modes. i have tried 5 or 6 different firmwares for different Gens (I don't know the gen it should be / originally was).
The only exception to this is if I use the chinese firmware 'unicom gen2' - even though the one thing I know my Blade wasn't originally is the chinese one. (It was originally an Orange San Fran).
With this firmware flashed I can enter FTM, and so reflash Channel1.nvm (I can alter hex 1215 on with correct IMEI, or leave it, it makes no difference to the outcome).
From here it will boot into CWM v. 3.0.2.4, but written in chinese characters. However if I then go to install zip from SD card then CWM just hangs with the RomManager splash screen, but doesn't actually go any further to let me choose a zip.
Other things I've tried are to swap some of the .img files from other firmwares into the chinese firmwere, but this doesn't work. And I've also tried using adb command line, but adb devices lists no devices, even when connected in FTM mode. (even though ZTE flasher recognises the device)
I'm fresh out of ideas - any one offer any help?
Click to expand...
Click to collapse
SOLVED! For the record: 1) firmware included with the ZTE firmware flasher only includes unicom and euro gen 1 firmwares. It turns out that my blade is euro gen 2. Found a stock euro gen 2 firmware in another thread and flashed it with the ZTE firmware flasher which worked OK. Having now got the correct firmware for the hardware the NVram update worked OK (previously it had failed) This was the major cause of the phone not booting correctly past CWM or FTM screen. Once these two processes were complete I was able to use the ZTE ROM updater from the ZTE website to identify the phone correctly and download and install the correct stock ROM automatically. Now back up and working beautifully.
Lessons I learnt. 1) It matters what hardware you have (I wasn't able to positively identify mine cos it was bricked) but luckily trying unicom, gen 1 and several gen 2 firmwares didn't cause any lasting damage until I'd got the correct one working.
2) NVram update is important, but won't complete successfully if the wrong firmware for the hardware is installed.
3) Using stock ROMs and firmwares only is an important first step to unbricking the phone. Trying to flash custom ROMs straight to a bricked phone is fraught with problems.

Hi guys..i got issues also on my brothers gen2 blade chinese v880..the probe is i got an error after flashing tpt file,and my blade stuck in airplane mode..i cant get it off even i installed different roms..fyi,i currently running cm 7.2 and able to enter cwm recovery,bootingand playing games on it but cant enter ftm mode..need help..
Sent from my HTC Wildfire using xda premium

Nothing working
My ZTE Blade is not starting up. If I try to enter Recovery Mode, FTM mode opens and nothing works. If I try to normally start the phone, it ends the recovery mode. The recovery mode has very less options. The options are -
-reboot system now
-apply sdcard:update.zip
-wipe data/factory reset
-wipe cache partition.
All these options are in the 180 degree rotated screen. Nothing works here. If I choose "reboot system now", the phone gets rebooted and again, same recovery mode gets opened.
Guys, please help me fast!

HELP
AFTER I DID THE METHOD 5 IT REDUCE MY RAM TO 166mb

ZTE Blade G2 V880H
Can you please add ZTE Blade G2 V880H to your device list ?
It is a new release from ZTE in 2013.
OS: Android 4.2
Chip set: Media tech MT6589 1.2 Ghz
RAM: 512 MB
ROM: 4GB
Camera: 5MP AF with Flash
Display: IPS 4.5“ FWVGA(480*854), 16M color
Battery 2000mAh
ztedevice.in /specification.php?for=specificatrion&type=ZTE-BLADE-G2

zte blade apex dead any solutin please xda team????
zte blad apex dead during bad update can't enter to ftm mode or recovery mode only with vol+ & vol- it become dfu mode

invalid imei forZTE BLADE G2
:crying:I was installing CWMR after flashing the recovery.image from mobile unkle tool when i rebooted my phone then i lost my IMEI- no signal too plzzz help me asap its showing IMEI - UNKNOW:crying::crying::crying::crying::crying::crying::crying::crying:

Help please ((
I bought my ZTE BLADE Q before 4 days.The phone is so cool,so fast and all that...
I want to change my fonts I use app from google play Im tried HiFont,and it says i need to root phone.I have root my phone with app called "KEY ROOT Master" from 4Shared.
When i root my phone I change the fonts to CHOCO COOKY then it said reboot phone to take a effect.I have reboot my phone.When it turns on fonts aren't changed.I have search the internet and i find Font Installer app from google play.When i change fonts in that app it said reboot phone.When i start to reboot phone my phone "STUCK" on the ZTE logo.I think my phone is bricked.Im trying to install CWM but my PC dont recognise my drivers. PLEASE HELP ME HOW TO UNBRICK MY PHONE OR HOW TO INSTALL CWm ON BRICKED ZTE BLADE Q.Sorry for my bad English!! :crying:

Driver not recognised
rmengh0991 said:
my idea zte blade is totally dead
i have tried all the method on XDA but the window didn't recognize it (Driver installed)
Please help me.
Click to expand...
Click to collapse
Other methods are not working so I tried the 5th step but my PC didn't recognize driver for this device. I had installed zte driver provided in this thread and I did it by turning off my phon . Didn't recognize. Is it really dead

Is it for Blade L3 german too? I have a bootloop After factory Reset.

sammy1970 said:
Is it for Blade L3 german too? I have a bootloop After factory Reset.
Click to expand...
Click to collapse
I don't think so. It works on zte blade and its other version like San Francisco, Orange, dell xcd35. But try at least may be you can succeed. But don't forget to check first whether you device is gen1 or gen2 and then flash that appropriate firmware

Wow, I tried your tutorial and it works fine. Great post mate!

Zte Blade A452 4g lte
I ask all users who have this phone that I set backup this model I would appreciate the phone was purchased in the German

I format my Zte Blade A1 c880u with SP Flash Tool and now is Hard bricked.. I not have any backups. And cant flash official rom with Sp Flash Tool ( dram error.. ). My pc detect the phone in Device Manager. Any chance to unbrick phone ?

[Q] Need to unbrick Defy+ - Strange problems

Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis

If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2

Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.