• Announcements

    • PaulOBrien

      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 software Nintendo 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 author ISSUES If you have any issues with this policy, please contact PaulOBrien directly via PM.
    • PaulOBrien

      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.
Sign in to follow this  
Followers 0

Bricked Crescent/SFII

3 posts in this topic


First time poster, long-time lurker.

I bricked my SFII today - I was trying to debrand it and at some point in the process when the phone was linked to my PC there was a "fail" message - I think it was during the part when I was using QPST.

**edit - it failed during the OSF flasher, patched by Radmir

Result: The phone is stuck at the little green android. It will not boot to FTM or anything else. My PC recognises it in Device Manager ("ZTE Handset Diagnostic Interface") but I cannot access it via Windows Explorer.

I have downloaded a firmware flasher USDL_P726CV1.00.00 - (the current ZTE update tool does not recognise the handset) and have found the following files to flash (part of "Unlock OSF2") :


















However, when I try to flash these to the phone, the first few work - it gets to 22/100 then I get an error message "Download fail, please check the log file to get fail information"

This is the logfile:

2012.12.12 21:16:3¡ª¡ªDownload armprg.bin...

2012.12.12 21:16:9¡ª¡ªskip to armprg...

2012.12.12 21:16:15¡ª¡ªenter security mode...

2012.12.12 21:16:15¡ª¡ªDownload partition.mbn...

2012.12.12 21:16:15¡ª¡ªDownload qcsblhd_cfgdataPath.mbn File...

2012.12.12 21:16:16¡ª¡ªDownload OEM bootloader...

2012.12.12 21:16:17¡ª¡ªDownload AMSS...

2012.12.12 21:16:21¡ª¡ª¸ßËÙЭÒéÏ´«ËÍÊý¾Ýʧ°Ü

2012.12.12 21:16:21¡ª¡ªDownload fail, please check the log file to get fail information!

Any ideas on how to revive it or should I just send it back pretending "it's gone a bit funny"? Thanks

Edited by bdw1971

Share this post

Link to post
Share on other sites


I've managed to get the phone back to FTM mode using the instructions here:


I then dumped a CWM image onto the SD card, booted from that and now have CWM 5 installed.

I then went through the wipe cache partition, wipe data, wipe dalvik cache process and installed Fish n Chips (from the SD card). The install reported back OK but every time I reboot, remove battery etc. I boot into CWM.

When I plug the phone into my PC it's recognised in Device Manager but not Windows Explorer -

It feels like I'm nearly there - any ideas of how to get me out of CWM?


Share this post

Link to post
Share on other sites

Aaargh! God knows which of the SF2 roms I tried to install - it looked like it was working really well from CWM - progress bar went across etc. When I rebooted I was stuck in FTM - can't get CWM back on there.

The only upside is the ZTE updater recognises the device but won't download the update - it says it's doing it but after 10 minutes the indicator hasn't shifted from 0% and there's nothing in the download directory but a tiny tmp file.

I think it's time to take it back.


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
Sign in to follow this  
Followers 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2016. MoDaCo uses IntelliTxt technology.