Jump to content

[ROM] : Stock ROMs for ZTE Blade 2/Orange San Francisco II/T-Mobile Vivacity


Guest Sebastian404

Recommended Posts

Guest Russ_uk

The update tool gave me the following P736EV1.0.0B13.zip which I assume is new, can anyone dig up info on it?

I keep getting lost on the zte site!

http://www.mediafire...b9d38933nmxwrp1

I did the upgrade and all worked fine. As for any info there isn't any as far as i can see regarding a change log etc.

It's funny that the Vivacity upgrade tool gave you:

P736EV1.0.0B13

As it gave me:

P736EV1.0.0B04

I've just double checked the tool again and it's showing 'B04' as being the latest version ??

Be interesting to see what anyone else got!

MCZQ - Wanna double check yours again to compare ?

Thanks in advance

Link to comment
Share on other sites

I did the upgrade and all worked fine. As for any info there isn't any as far as i can see regarding a change log etc.

It's funny that the Vivacity upgrade tool gave you:

P736EV1.0.0B13

As it gave me:

P736EV1.0.0B04

I've just double checked the tool again and it's showing 'B04' as being the latest version ??

Be interesting to see what anyone else got!

MCZQ - Wanna double check yours again to compare ?

Thanks in advance

Strange, as even http://blog.podtwo.com/android/rom/ZTE%20Blade2%20Stock%20ROMs.html has b12 listed.I do note when I go to "about" in settings it shows as b04, but this may be ZTE being lazy as the kernel version never changes even when a custom compile is used. Can you do a md5 sum for your b4.zip?

Link to comment
Share on other sites

Guest Russ_uk

Strange, as even http://blog.podtwo.c...ock%20ROMs.html has b12 listed.I do note when I go to "about" in settings it shows as b04, but this may be ZTE being lazy as the kernel version never changes even when a custom compile is used. Can you do a md5 sum for your b4.zip?

Very strange indeed, My TMV came with B03 pre installed and a single update gave me B04 - I've never come across B12/B13 at all.

fDu3.jpeg

Leave it with me and I'll upload my B04.zip + the md5 sum when I get time.

I'm far from being an expert but I've got a feeling this might be why some people are have different issues with certain custom/de-branded ROM's and others aren't ??

(No message sound, not sleeping properly, compass errors etc etc - Nothing major but bugs all the same)

Think a bit detective work is called for, I'll see if I can come up with any answers but preferably someone with some more experience than me can look into this and/or do a few comparisons?

Link to comment
Share on other sites

I just re-ran the update tool to double check for you.

It states I am currently running B03 (Actually a ICS mashup so that will be misleading), and the latest update is B04. After clicking update, I check C:\Program Files (x86)\Handset software update tool\Handset software update tool\FirmwareVersion and note B13.zip is downloading again.

That folder of yours actually contains a B04? It would make sense at this stage if it contained a B13 on your end and we are just dealing badly named versions.

Link to comment
Share on other sites

Guest Sebastian404

Strange, as even http://blog.podtwo.com/android/rom/ZTE%20Blade2%20Stock%20ROMs.html has b12 listed.I do note when I go to "about" in settings it shows as b04

notice in the about box..

ro.build.version.release=2.3.5

ro.build.sw_internal_version=P736EV1.0.0B12

ro.build.display.id=P736EV1.0.0B03

the INTERNAL version is B12... the DISPLAY version is B03

The internal version tracks the development of the image, if it fails testing and/or needs more work its internal version number will increment, so that is telling you there has been 12 internal builds of that image, but only 3 of them have been promoted to being 'final'..

Of course, that's only if ZTE follow their own rules, there are a number of different images with the same DISPLAY version, when someone 'forgot' to update it... for this reason the update images are always based on the INTERNAL version as that seems to be the only thing that consistently changes

Link to comment
Share on other sites

Guest Sebastian404

Oh also, I've got two newer update images to upload, Im not sure they is anything major different with them tho...

OUK_P736VV1.0.0B12.zip

P736EV1.0.0B13.zip

I'll be uploaading them later

Link to comment
Share on other sites

Guest Russ_uk

I check C:\Program Files (x86)\Handset software update tool\Handset software update tool\FirmwareVersion and note B13.zip is downloading again.

I've got nothing like FirmwareVersion (or anything relating to firmware at all) in my 'Handset software update tool' folder. (I'm running Windows 7 x64)

In fact when i used the tool to do my upgrade It didn't download anything as a .zip file, it just sent all the necessary files directly to my phone.

Where are you guys getting these zip files from - ClockworkMod ?

Edited by Russ_uk
Link to comment
Share on other sites

  • 3 weeks later...
  • 2 weeks later...
Guest fr0do

Just flashed P736EV1.0.0B13 to my TMV and it wouldn't boot. Goes to the blue themed CWM v3 (after a 2nd vibrate) that doesn't work with the capacitive buttons. Vol- gets you into FTM mode.

Is this the right rom or should I be installing this some other way?

(Got back working ok BTW ;))

.

Edited by fr0do
Link to comment
Share on other sites

Guest tommies1

Hello,

initialy i made a mistake and installed blade GEN2 rom cyanogen.

my Blade S (french blade 2)

Hopefully, there is the TPT method.

then i put in image folder the original rom for my device P771FV1.0.0B05.zip (tried orange stock TPT too)

sound up + power up, TPT begins and stays on

load /mmc1/image/qcsblhd_cfgdata.mbn

I don't understand because il can install without errors by this methode CM7.0.2-Gen1-to-Gen2-TPT.zip or cm-7.1.0-RC1-Blade-TPT.zip

that are not good TFT rom for me

any idea ?

sorry for my poor english

Link to comment
Share on other sites

Guest Titas

Are you holding power and volume+ and MENU?

Instructions: (from Amorphas)

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 image.bin file and a nandroid.md5 file inside it.

Check the md5sum of the image.bin file matches the one written 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 (probably, if this doesn't work then you can use the system update option from the settings menu in your rom).

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.

Edited by Titas
Link to comment
Share on other sites

Guest tommies1

TPT didn't recognized image.bin.

clockwork didn't flash good rom.

what could i do ?

my first error was to use fastboot to flash a wrong rom.

the ZTE windows tool recognised my blade Crescent as a Blade 1

the TPT didn't recognize blade S image format imagine.bin in image folder (just blade format withe several files in image folder)

Then i used TPT mode to flash a blade 1 stock rom to recover FTM. i couldn't use the phone but i recovered the FTM mode.

then used fastboot to flash good rom.

done

Link to comment
Share on other sites

  • 2 weeks later...
Guest domenico lamberti

hey guys, i need do i need to have the Stock TPT to run the Stock ROM ? because i am going to shoot my review of the phone and it would be fair if i reviewed it with Fish n chips first off, so will i need to tpt back to stock or can the rom go over any tpt ?

Link to comment
Share on other sites

  • 2 weeks later...
  • 1 month later...
Guest KonstaT

Orange San Francisco II/T-Mobile Vivacity stock TPTs in ZTE website.

http://wwwen.zte.com...data/mobile/UK/

San Francisco II SD card upgrading instruction & software

http://wwwen.zte.com...11756049474.zip


ro.build.display.id=OUK_P736VV1.0.0B04
ro.build.version.release=2.3.5
ro.build.date=Wed Feb 15 18:50:49 CST 2012
ro.com.google.gmsversion=2.3_r9
ro.build.sw_internal_version=OUK_P736VV1.0.0B13
[/CODE] Vivacity SD card upgrading instruction & software http://wwwen.zte.com...14731386512.zip
[CODE]
ro.build.display.id=P736EV1.0.0B05
ro.build.version.release=2.3.5
ro.build.date=Wed Feb 15 01:49:09 HKT 2012
ro.com.google.gmsversion=2.3_r9
ro.build.sw_internal_version=P736EV1.0.0B14
Most recent/interesting is this one. It seems that this Optimus Barcelona = ZTE Atlas W = some Vivacity variation. http://wwwen.zte.com...obile/Portugal/ http://wwwen.zte.com...31844117591.zip

ro.build.display.id=OPTIMUS_P736EV1.0.0B02
ro.build.version.release=2.3.5
ro.build.date=Thu Mar 15 01:03:41 CST 2012
ro.com.google.gmsversion=2.3_r9
ro.build.sw_internal_version=OPTIMUS_P736EV1.0.0B02
[/code]

Link to comment
Share on other sites

  • 4 weeks later...
Guest app10336

Somebody has link for this stock rom ?

n81x1113600.jpg

Or how to make it myself ?

Edit: Blade S = Crescent/OSF II

Edited by app10336
Link to comment
Share on other sites

  • 2 weeks later...
Guest iharrybao

Somebody has link for this stock rom ?

n81x1113600.jpg

Or how to make it myself ?

Edit: Blade S = Crescent/OSF II

Blade S = Crescent/OSF II?

maybe you can use OSF II

Edited by iharrybao
Link to comment
Share on other sites

  • 1 month later...
Guest KEZZY1965

Hi Guys,

I am after a stock Kernel & ROM for Vivacity. Would the above TPT's provide both or just the ROM ?

(I have loaded fish n chips to a locked phone and now need to revert to stock build to run an unlock)

Thanks for your help in advance.

Link to comment
Share on other sites

  • 4 weeks later...
Guest lohtse

Most recent/interesting is this one. It seems that this Optimus Barcelona = ZTE Atlas W = some Vivacity variation.

http://wwwen.zte.com...obile/Portugal/

http://wwwen.zte.com...31844117591.zip


ro.build.display.id=OPTIMUS_P736EV1.0.0B02

ro.build.version.release=2.3.5

ro.build.date=Thu Mar 15 01:03:41 CST 2012

ro.com.google.gmsversion=2.3_r9

ro.build.sw_internal_version=OPTIMUS_P736EV1.0.0B02

could this be used to flash on to the vivacity as its just a vivacity debranded?

if so anyone able to root it and apply app2sd?

Link to comment
Share on other sites

  • 2 weeks later...

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.