Yes! Yes! We got it! ZTE-U V880 ROM (UNI_CN_V880 1.1)

[Guest MDCFan]

I am attaching SIM lock ignoring Phone.apk for this ROM. Untested (because i don't have this ROM booting ;)), but i think it should work.

Phone_chinese_lock_ignoring_.rar

[Guest DonJamal]

in clockwork with backup or something couldnt be installed?

[Guest rjm2k]

But almost a month older than the Japanese Softbank ROM so it may not be the "perfect" ROM everyone has been waiting for. On the other hand it it's not Wednesday so there is still hope. ;)

I think some people still have it in their head that we needed a chinese production release, as you know that became irrelevant once we got the Japanese release unless the chinese one proved to be newer which it doesn't seem to be.

[Guest fonix232]

I think some people still have it in their head that we needed a chinese production release, as you know that became irrelevant once we got the Japanese release unless the chinese one proved to be newer which it doesn't seem to be.

What I want from this release is multi-lang. Even if the Japanese build is newer, this supposed to have full European language support (Greek, Hungarian, Spanish, etc).

And also, those cool ZTE stuffs too ;)

[Guest Rotmann]

I thought this rom was supost to be perfect

Patience my friend, we still have time till Wednesday ;)

On the other hand, is this chinese version 100% similar to the european blades, on the hardware side?

[Guest fonix232]

Patience my friend, we still have time till Wednesday ;)

On the other hand, is this chinese version 100% similar to the european blades, on the hardware side?

Nope, it has only 256MB of RAM, and a separate OEM partition (built-in SD card?)

[Guest custard tart]

Patience my friend, we still have time till Wednesday ;)

On the other hand, is this chinese version 100% similar to the european blades, on the hardware side?

next wednesday？what does it mean？

[Guest Arr Too]

Here are the interesting bits from build.prop:

ro.build.version.release=2.2

ro.build.date=Tue Nov 16 16:18:16 CST 2010

ro.build.sw_internal_version=P729CUV1.0.0B07

ro.build.display.id=UNI_CN_V880 1.1

There is no "ro.com.google.gmsversion" specified. ;) Stagefright is all off, HW accel off, VM heap 24m.

[Guest Carlos Abel Chavez Slim]

Can't wait for this.

[Guest fonix232]

Here are the interesting bits from build.prop:

ro.build.version.release=2.2

ro.build.date=Tue Nov 16 16:18:16 CST 2010

ro.build.sw_internal_version=P729CUV1.0.0B07

ro.build.display.id=UNI_CN_V880 1.1

There is no "ro.com.google.gmsversion" specified. ;) Stagefright is all off, HW accel off, VM heap 24m.

Except Stagefright, everything is stock... Looks like our chinese friends got the message from the custom ROMs :)

[Guest Arr Too]

From config.gz:

CONFIG_PHYS_OFFSET=0x02600000

Oh dear....

[Guest jdtanner]

next wednesday？what does it mean？

It is an ongoing joke...do a search for Wednesday in the forum ;)

[Guest Sebastian404]

Here are the interesting bits from build.prop:

ro.build.version.release=2.2

ro.build.date=Tue Nov 16 16:18:16 CST 2010

ro.build.sw_internal_version=P729CUV1.0.0B07

ro.build.display.id=UNI_CN_V880 1.1[/code]

There is no "ro.com.google.gmsversion" specified.   ;)   Stagefright is all off, HW accel off, VM heap 24m.


It does only have 256mb....


Tho who knows, maybe its another Hungarian special

[Guest Jekle]

I got it to boot! Sort of. I used a update-script generator from the xda forum the default boot.img is apparently to big, so i used the jj r7 boot.img went through to clockwork process with no errors. But now its stuck at the Green Android Robot. :-(

Edited January 16, 2011 by Jekle

[Guest Arr Too]

the default boot.img is apparently to big

No, it's just a complete dump of the partition (so it needs repacking). But we can't use that kernel as it's built to the wrong address for our Blades (same reason we can't use the Japanese kernel).

[Guest Jekle]

Has anyone else got it to boot?

[Guest whatcolour]

I got it to boot! Sort of. I used a update-script generator from the xda forum the default boot.img is apparently to big, so i used the jj r7 boot.img went through to clockwork process with no errors. But now its stuck at the Green Android Robot. :-(

Thought the MCR kernel from Paul's latest rom should work?

[Guest fonix232]

Has anyone else got it to boot?

Same as yours, not getting past green android (bootloop, before adbd was started).

With JJ7 kernel

[Guest Jekle]

Same as yours, not getting past green android (bootloop, before adbd was started).

With JJ7 kernel

whatcolour suggested MCR Kernel would that work?

Edited January 16, 2011 by Jekle

[Guest fonix232]

whatcolour suggested MCR Kernel would that work?

IDK, it is trial-and-error.

[Guest whatcolour]

IDK, it is trial-and-error.

MCR has the best chance to work since it's based on a previous Chinese leak (P729CUV1.0.0B04)

[Guest daerragh]

Can anyone explain in layman terms why we have to use a different kernel, not the stock one? I thought that both phones are identical.

Edited January 16, 2011 by daerragh

[Guest Sebastian404]

I thought that both phones are identical.

This has been done to death.... you thought wrong

[Guest Jekle]

I'm just downloading MCR r7 now, fingers crossed it'll work

[Guest Arr Too]

Can anyone explain in layman terms why we have to use a different kernel, not the stock one?

Like the Japanese ROM, the kernel seems to be setup for a different RAM layout to the Blade. There might be a way in which our Blades can be reconfigured to a compatible layout (perhaps via something like the Hungarian update), but we just don't have the information on how to make such low-level changes. And kallt_kaffe has looked into hacking the kernel to use our layout and he says it's not feasible (too many changes needed, with no guarantee that we would be able to make only the correct changes).