• 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.

Devs, any thoughts what so ever on unlocking?

14 posts in this topic

Posted

I have access to windows and Linux machines, i have access to a phone that if it's not unlocked it's going to go to the scrap anyway, the digitzer is partly broken and a new battery is needed so if i manage to unlock it great, if the procedure fails it doesn't matter, i have another one for development of other stuff.

 

Any ideas, i've tried to dd a dump of an unlocked phone to the mmcblk0 which didn't work (probably because of bootloader differences, there seems to be several different ones) and i've tried to just dd just partition 11 and 12 which does absolutely nothing, i've also tried to use cefs files from another phone (which was similar enough) via DFU and that didn't help either, all i got was that NO sim card would work, i tried to make a hex search for the cefs code on a complete dump of mmcblk0 and it seems it's infused as the last part of AMSS.MBN on fat partition 13 but changing that does nothing.

 

I'll all ears for any possible solution you want me to try no matter how surely it will mess up the phone (i've learned by now how to recover it anyway).

 

So, anything?

0

Share this post


Link to post
Share on other sites

Posted

Does this really work? :O

0

Share this post


Link to post
Share on other sites

Posted

Does this really work? :o

It might - it might brick your device for good too. Make sure that you don't skip the NV memory backup with QPST if you're going to try.
 
I guess there's no one who has tried it on a Blade III. There was someone on Acqua forum who had used it successfully. Also another report on XDA with some other Acqua variant (ZTE Urbane?). Then there's of course these people with V889D and V880E in russian forums. These are all atlas40 devices.
1

Share this post


Link to post
Share on other sites

Posted

Hy!

 

Have anyone tried it on blade 3?

I fully bricked one mainboard when i flashed the .MBN files from a stock blade 3 rom with DFU Tool and the pc does not recognize it anymore. In this method you have to tick all the boxes in DFU Tool, and flash the v889d files, so probably it will brick the phone...

I don't want to brick another mainboard 'cause I don't have more

If someone have already tried please write down what happened...

1

Share this post


Link to post
Share on other sites

Posted

Hy!

 

Have anyone tried it on blade 3?

I fully bricked one mainboard when i flashed the .MBN files from a stock blade 3 rom with DFU Tool and the pc does not recognize it anymore. In this method you have to tick all the boxes in DFU Tool, and flash the v889d files, so probably it will brick the phone...

I don't want to brick another mainboard 'cause I don't have more

If someone have already tried please write down what happened...

Did you flash .mbn files from a Blade III update.zip? I'm quite sure they're not even in the same format as the V889D ones that come with the DFU tool.

1

Share this post


Link to post
Share on other sites

Posted (edited)

Did you flash .mbn files from a Blade III update.zip? I'm quite sure they're not even in the same format as the V889D ones that come with the DFU tool.

Yes, I flashed the .mbn files from the hungarian update.zip with the DFU tool. Thanks for the information. If i try it, i'll post the result...

 

Edit 1: The result is ALCATEL HS-USB QDLoader 9008 :D (I have alcatel phone, but this is a zte, my pc went mad :D )

 

Edit 2: QPST&QXDM recognize it, but can't do nv restore 'cause it tells no phone or can't switch to download mode. DFU also recognize, but when i push the left button it shows wait reset, than i just wait, but no reset...

 

Result: I killed another zte blade 3 mainboard :D

 

Hope: I found this thread http://www.modaco.com/topic/365713-zte-blade-iii-can-not-enter-recovery-mode/ where Snap.IT described a linux method... Now i'm installing an ubuntu in wmware. I need a full mmcblk0 dump from a blade 3. Can you upload one for me, because i think you have linux for the rom compile...

 

Edit 3: I can't mount the phone's "storage" under linux, so now i'm workink on winxp with qpst emmc software download. I found the mprg7627a.hex and the 7627a_msimage.mbn files and started to download, but it stucked... Where is Snap.IT? He wrote, that he works on a method to repair the phone from qdloader mode...

Edited by crow89
1

Share this post


Link to post
Share on other sites

Posted (edited)

Hi all,

 

I have tried the method from the Russian forum on my Telstra Urbane (ZTE T22) device.

-DFU Tools flashed the Chinese V889D firmware

-Flashed the Russian 2.3.6 with CWM

-Put back regular recovery file with DFU Tools

-Used Update mode to upgrade to Russian ICS 4.0

-Put back CWM and installed Cyanogenmod 11

 

Unfortunately I do not have a service in Cyanogenmod 11, no network. I noticed that the IMEI was changed when doing the DFU Tools firmware flash. All sim cards were working before the Cyanogenmod 11 update.

Do I have to recover my actual IMEI to the device? Would it be sim locked again if doing so?

 

Edit:

Just tried it again, was planning to use the Russian ICS 4.0 version, but Sim is not working there either. Only in 2.3.6

Edited by Franconian
0

Share this post


Link to post
Share on other sites

Posted

I have successfully recovered my original IMEI with the QPST tool. Unfortunately still no network.

 

Is my only chance to use the phone the flash with V889D firmware 2.3 and live with it?

 

Any other things I can try?

0

Share this post


Link to post
Share on other sites

Posted

Hi all,

 

I have tried the method from the Russian forum on my Telstra Urbane (ZTE T22) device.

-DFU Tools flashed the Chinese V889D firmware

-Flashed the Russian 2.3.6 with CWM

-Put back regular recovery file with DFU Tools

-Used Update mode to upgrade to Russian ICS 4.0

-Put back CWM and installed Cyanogenmod 11

 

Unfortunately I do not have a service in Cyanogenmod 11, no network. I noticed that the IMEI was changed when doing the DFU Tools firmware flash. All sim cards were working before the Cyanogenmod 11 update.

Do I have to recover my actual IMEI to the device? Would it be sim locked again if doing so?

 

Edit:

Just tried it again, was planning to use the Russian ICS 4.0 version, but Sim is not working there either. Only in 2.3.6

Hi!

 

How did you flash the v889d firmware with dfu? I translated the russian method, and it said check all the boxes on the left so i checked, and it killed my blade 3 to qdloader mode. I checked your phone, and it has the same specs as my, so i don't understand why my phone died... Did you check the cefs and cefs_null boxes?

0

Share this post


Link to post
Share on other sites

Posted (edited)

Hi crow89,

 

Everything worked perfectly for me until the Russian 2.3.6 update. The only problem is that my Sim card is not recognised anymore "no service" after upgrading back to 4.0.

 

I downloaded all files from the links provided in the Russian forum. All boxes were ticked in DFU Tools using the v889d Firmware. I even repeated the procedure several times as I was trying to fix the "no sim" problem.

 

It may be because the v889d and 2.3.6 Russian firmware are for a dual sim phone? Sim is still working though, however after upgrading to 4.0.4 it does not recognise any sim cards. I even tried to flash to an orignial stock rom after the 2.3.6 Firmware was installed. Same problem when flashing a Cyanogenmod firmware.

 

Edit:

Were you able to download the 4.0.4 update file (Point 8 on Russian Forum instructions)? I might have used the wrong one...

 

Edit2:

I finally managed to install the Russian 4.0.4 rom on it. I used the wrong one before. As I thought it was connected to the dual sim phone rom. The v889d firmware used with the DFU Tools was for the dual sim phone model. After flashing this there is no way to go back to the regular single sim versions.

I have tried to replace files used from the v889d firmware with the single sim version. Unfortunately this caused an irreparable brick on one of my phones (I have two). It does not even go in DFU mode anymore...:-(

 

The second phone is unlocked now and on the 4.0.4 Russian rom. Unfortunately no Cyanogenmod possible due to the dual sim problem.

Edited by Franconian
0

Share this post


Link to post
Share on other sites

Posted (edited)

Hi crow89,

 

Everything worked perfectly for me until the Russian 2.3.6 update. The only problem is that my Sim card is not recognised anymore "no service" after upgrading back to 4.0.

 

I downloaded all files from the links provided in the Russian forum. All boxes were ticked in DFU Tools using the v889d Firmware. I even repeated the procedure several times as I was trying to fix the "no sim" problem.

 

It may be because the v889d and 2.3.6 Russian firmware are for a dual sim phone? Sim is still working though, however after upgrading to 4.0.4 it does not recognise any sim cards. I even tried to flash to an orignial stock rom after the 2.3.6 Firmware was installed. Same problem when flashing a Cyanogenmod firmware.

 

Edit:

Were you able to download the 4.0.4 update file (Point 8 on Russian Forum instructions)? I might have used the wrong one...

 

Edit2:

I finally managed to install the Russian 4.0.4 rom on it. I used the wrong one before. As I thought it was connected to the dual sim phone rom. The v889d firmware used with the DFU Tools was for the dual sim phone model. After flashing this there is no way to go back to the regular single sim versions.

I have tried to replace files used from the v889d firmware with the single sim version. Unfortunately this caused an irreparable brick on one of my phones (I have two). It does not even go in DFU mode anymore...:-(

 

The second phone is unlocked now and on the 4.0.4 Russian rom. Unfortunately no Cyanogenmod possible due to the dual sim problem.

Hi!

 

I was very stup..id when i flashed with dfu... Now i checked, and in my dfu folder there is a v889d 2.1 firmware...

I had two motherboard for my blade 3, and i killed both...

As far as i know from other phones, the difference between the dual and the single sim is inside the boot.img kernel.

 

Sorry, but i can't help you, i'm "more noob" for that phone than you...

I like mediatek platform more than qualcomm, cause i couldn't brick my mt6573 phone... sp flash tool always review mediatek phones, but qpst is so difficult...

 

I hope you can find a way to flash cyanogen to your phone...

Edited by crow89
0

Share this post


Link to post
Share on other sites

Posted (edited)

It's all there on the Russian forum I think, just a bit difficult for non Russian speakers relying on Google Translate. I just found guidelines there on how to change from dual sim software to single sim. Will take some time to fully understand, but that's probably the way to go. After this cyanogen should be working.

 

Edit:

Successfully flashed CM11 on my phone. I can confirm that the Russian unlock procedure works on the Telstra Urbane (ZTE T22) phone.

It was not easy to fully understand the required steps posted on the Russian website using google translate though.

Edited by Franconian
1

Share this post


Link to post
Share on other sites

Posted

Thanks @Franconian and Crow89 (köszönöm), that you sacrificed some effort in this project!
Its so fantastic you'd found a way unlock ZTE atlas40's!! :)

So if someone wanna give it a try..
Can you explain the step by step method of it for a ZTE BLADE 3 user?

It would be really cool to have an unlocked phone :P :)
Anyways thanks! :)

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.