IT'S WEDNESDAY!!! And we all know what that means.

[Guest kallt_kaffe]

EDIT 2011-03-18: Made a more clean and official thread for this ROM here: http://android.modaco.com/content/zte-blad...03-17-oled-tft/

EDIT 2011-03-17: New version here: http://www.swedroid.se/forum/showthread.php?t=36653

http://www.mediafire.com/?7owpldax4gdkz5w

Now what is this?

• Froyo ROM based on CSE_P729VV1.0.0B01 (From Swedish Comviq 2.2 Blade).
  
• RDS Radio enabled and overclockable kernel from Japanese Jellyfish RLS9.
  
• Andorko's RDS capabable FMRadio.apk included.
  
• Several Google apps updated to latest versions (VoiceSource, Gmail, Vending, Maps).
  
• Fits in 128Mb system partition.
  
• Pretty much the same features as JJ but no Facebook integration so far (no joining contacts etc...)
  

Some other information:

Comviq/Tele2 now sells Blades with 2.2. These blades loads their kernel to 0x02600000 just as the other official 2.2 phones. Also the repair center i Sweden have started upgrading phones when they repair them. Likely they are using the "TPT" method. New or officially upgraded 2.2 blades most likely all will use these new baseadress. Also the ril libs and liboemcamera.so are not compatible.

This means the new or upgraded phones can NOT use current Clockwork/RA recoverys and they can NOT use current custom ROMs. They can likely be downgraded to a "2.1-phone" using the TPT-files we currently have but there will then be no way back.

I foresee that this will happen in other contries aswell.

So unless we can get hold if a TPT installation for this new "platform", we will need to create separate versions of custom ROMs for these phones. In the event that we can get hold of the "TPT" files for official 2.2 then I suppose we eventually switch ROM development over to the new "platform"?

Edited March 18, 2011 by kallt_kaffe

[Guest Sebastian404]

Some other information: Comviq/Tele2 now sells Blades with 2.2. These blades loads their kernel to 0x02600000 just as the other official 2.2 phones. Also the repair center i Sweden have started upgrading phones when they repair them. Likely they are using the "TPT" method. New or officially upgraded 2.2 blades most likely all will use these new baseadress. Also the ril libs and liboemcamera.so are not compatible.

funny enough, today is also the day we have been promised a 2.2 rom for the V9... Wednesday is a magical day for all ZTE devices! :D

Swedish_Spring..... you have given up on the animal naming method? :(

BTW, You going to share the stock rom dump... hint, hint, hint :(

Edited March 16, 2011 by Sebastian404

[Guest dmxpowa]

lets try to leak TPT files nao.

[Guest kallt_kaffe]

funny enough, today is also the day we have been promised a 2.2 rom for the V9... Wednesday is a magical day for all ZTE devices! :D

Can't argue with that.

Swedish_Spring..... you have given up on the animal naming method? :(

Well, not all are animal names. I allready have Swedish Snow and French Fries... also the Fillyjonk aren't really a real animal. However, I couldn't think of anything quickly enough to keep it within the Wednesday timeframe. I was considering "The Perfect ROM"... :D (Well I actually also considered "Sodomized Swede" as I once read about a priest from USA calling Sweden something like "the land of the sodomized damned" but I'm not sure everyone shares my humour. :( )

BTW, You going to share the stock rom dump... hint, hint, hint B)

The original dump is here: http://dl.dropbox.com/u/1008610/android/CS...9VV1.0.0B01.zip

I also have made a recovery ROM for it but with the lack of Clockwork based on 0x02600000 kernels it's pretty useless right now.

Edited March 16, 2011 by kallt_kaffe

[Guest dorren]

Can't argue with that.

Well, not all are animal names. I allready have Swedish Snow and French Fries... also the Fillyjonk aren't really a real animal. However, I couldn't think of anything quickly enough to keep it within the Wednesday timeframe. I was considering "The Perfect ROM"... :D (Well I actually also considered "Sodomized Swede" as I once read about a priest from USA calling Sweden something like "the land of the sodomized damned" but I'm not sure everyone shares my humour. :D )

The original dump is here: http://dl.dropbox.com/u/1008610/android/CS...9VV1.0.0B01.zip

I also have made a recovery ROM for it but with the lack of Clockwork based on 0x02600000 kernels it's pretty useless right now.

Please do rename it to Sodomized Swede :(

Now I have something to do tonight :( Flashing a rom that is B)

[Guest Sebastian404]

I also have made a recovery ROM for it but with the lack of Clockwork based on 0x02600000 kernels it's pretty useless right now.

http://android.podtwo.com/recovery/

The x880 version apparently works on the Libero 003Z....

I did once ask about if there was any interest in doing dual versions of the custom ROMS, all you need is an alt boot.img and replace the RIL libs.... but no-one seemed interested.

If could get hold of a device I'd also look into building CM7 for it, it cant be hard, just steal the blade's device tree and make some changes...

[Guest kallt_kaffe]

Please do rename it to Sodomized Swede :D

I'm glad to see that I'm not the only one with a twisted sense of humour.

[Guest kallt_kaffe]

http://android.podtwo.com/recovery/

The x880 version apparently works on the Libero 003Z....

I did once ask about if there was any interest in doing dual versions of the custom ROMS, all you need is an alt boot.img and replace the RIL libs.... but no-one seemed interested.

If could get hold of a device I'd also look into building CM7 for it, it cant be hard, just steal the blade's device tree and make some changes...

Apart from the RIL's this time the liboemcamera.so had to be taken from the Libero ROM. Not doing that resulted in a freeze followed by a reboot.

So the x880 version should work then. And if I restore the ril libs and the camera lib and the original kernel it should be usable on a Swedish 2.2 phone. Still getting the new TPT files would be ideal so that we could all switch to the new "platform".

[Guest whatcolour]

LOL..

Reverting from CM7 to this, just for the sake of the "perfect Wednesday ROM"!!!

[Guest oh!dougal]

Wholly wow, this is The Wednesday!

[Guest Simon O]

So we will need to update our phones to use the new kernel addresses to make this useful. I was looking forward to having a european RIL lib that would work better than the Chinese ones we are currently using.

So it seems we are in the same situation we were in when the new Chinese rom was leaked. A new ROM we can't take full advantage off because of the kernel address.

So by using this 'perfect rom' as a base in any custom roms you need to replace the kernel, camera and ril libs to enable the rom to work. Apart from a few system files which may be slightly newer, there are no advantages to this over the Japanaese/Chinese bases already used.

Now if we had the TPT files to update our phones to use the new kernel addresses it would be a different story. We will be able to use the new RIL libs which may resolve the issues some people are having on custom roms. Actually we really need the TPT files if all the current 2.1 blades are being updated to 2.2 with new addresses as it'll prevent people from using any recovery images, custom roms etc.

Why do ZTE have to be so awkward?

Edited March 16, 2011 by flibblesan

[Guest oh!dougal]

... They can likely be downgraded to a "2.1-phone" using the TPT-files we currently have...

Maybe not.

http://android.modaco.com/content/zte-blad...zte-x880-blade/

Edited March 16, 2011 by oh!dougal

[Guest Simon O]

Maybe not.

http://android.modaco.com/content/zte-blad...zte-x880-blade/

Bugger. Thats not good...

I can see more people bricking these phones in the future :D

[Guest Arr Too]

Can we ask ZTE for a 0x02600000-based image? Perhaps they'd be happy to help with a way to 'recover' a phone that had 'mistakenly' been bricked by that Hungarian update?

[Guest wbaw]

Bugger. Thats not good...

I can see more people bricking these phones in the future :D

I wouldn't want to be the first to try the Swedish TPT & then back again with the Hungarian one. It should work, but I think I was the first non-hungarian to try the original tpt, I already did my bit. I think there could be hardware differences in the chinese vs european phones which caused that brick.

Edited March 16, 2011 by wbaw

[Guest Simon O]

I wouldn't want to be the first to try the Swedish TPT & then back again with the Hungarian one. It should work, but I think I was the first non-hungarian to try the original tpt, I already did my bit. I think there could be hardware differences in the chinese vs european phones which caused that brick.

It would probably work but we don't have the Swedish TPT, or any TPT that will update the phone to accept the new kernel address. If we have that then we can migrate all roms to use the new addressing and everyone can update using TPT. Then all blade phones will be pretty much the same.

[Guest Sebastian404]

Without wanting to distract from the on-going disaster, I was due to goto Toyko in a few weeks, I was going to try and pick up a Softbank device when I was out there... not likely to happen now..

I do wonder why they changed the base address tho, I assume it was something to do with the hardware change to support tri/quad-band hardware...

Unless it was, and ZTE are just too lazy to convert back.

KK, what is the build date for the new Kernel?

[Guest kallt_kaffe]

So we will need to update our phones to use the new kernel addresses to make this useful. I was looking forward to having a european RIL lib that would work better than the Chinese ones we are currently using.

So it seems we are in the same situation we were in when the new Chinese rom was leaked. A new ROM we can't take full advantage off because of the kernel address.

So by using this 'perfect rom' as a base in any custom roms you need to replace the kernel, camera and ril libs to enable the rom to work. Apart from a few system files which may be slightly newer, there are no advantages to this over the Japanaese/Chinese bases already used.

Exactly... It's pretty clean out-of-the-box but it's still 2.2 (FRF91).

Now if we had the TPT files to update our phones to use the new kernel addresses it would be a different story. We will be able to use the new RIL libs which may resolve the issues some people are having on custom roms. Actually we really need the TPT files if all the current 2.1 blades are being updated to 2.2 with new addresses as it'll prevent people from using any recovery images, custom roms etc.

We can always make dual versions of the ROMs but it'll be a pain.

Why do ZTE have to be so awkward?

I expect similar upgrades will show on in more contries so I've sure we'll get the TPT files eventually. Everyone who get's their phones upgraded to 2.2 while on repair (they do this in Sweden allready) should take a close look at their micro-SD card when it gets back. If we are lucky someone leaves the "image" folder on one of them.

[Guest Simon O]

I've compared this ROM with Japanese Jellyfish r9 to find if any files have been updated. Actually very few:

FAIL	MD5	bin\akmd2

FAIL	MD5	bin\athtestcmd

FAIL	MD5	bin\debuggerd

FAIL	MD5	bin\dhcpcd

FAIL	MD5	bin\eeprom.AR6002

FAIL	MD5	bin\em_deblock.sh

FAIL	MD5	bin\hci_qcomm_init

FAIL	MD5	bin\hostapd

FAIL	MD5	bin\hostapd_cli

FAIL	MD5	bin\hostapd_wps

FAIL	MD5	bin\iperf

FAIL	MD5	bin\loc_api_app

FAIL	MD5	bin\mm-qcamera-test

FAIL	MD5	bin\netd

FAIL	MD5	bin\recovery

FAIL	MD5	bin\run-as

FAIL	MD5	bin\updater

FAIL	MD5	bin\upmsg.sh

FAIL	MD5	bin\vold

FAIL	MD5	bin\wmiconfig

FAIL	MD5	bin\wpa_supplicant


FAIL	MD5	etc\apns-conf.xml

FAIL	MD5	etc\gps.conf

FAIL	MD5	etc\init.qcom.post_boot.sh

FAIL	MD5	etc\NOTICE.html.gz

FAIL	MD5	etc\pvplayer.cfg

FAIL	MD5	etc\dhcpcd\dhcpcd-hooks\20-dns.conf

FAIL	MD5	etc\security\otacerts.zip

FAIL	MD5	etc\wifi\hostapd.conf

FAIL	MD5	etc\wifi\wpa_supplicant.conf


FAIL	MD5	framework\am.jar

FAIL	MD5	framework\android.policy.jar

FAIL	MD5	framework\android.test.runner.jar

FAIL	MD5	framework\bmgr.jar

FAIL	MD5	framework\com.google.android.maps.jar

FAIL	MD5	framework\com.qualcomm.location.vzw_library.jar

FAIL	MD5	framework\core.jar

FAIL	MD5	framework\ext.jar

FAIL	MD5	framework\framework-res.apk

FAIL	MD5	framework\framework-tests.jar

FAIL	MD5	framework\framework.jar

FAIL	MD5	framework\ime.jar

FAIL	MD5	framework\input.jar

FAIL	MD5	framework\javax.obex.jar

FAIL	MD5	framework\monkey.jar

FAIL	MD5	framework\pm.jar

FAIL	MD5	framework\qcnvitems.jar

FAIL	MD5	framework\qcrilhook.jar

FAIL	MD5	framework\services.jar

FAIL	MD5	framework\svc.jar


FAIL	MD5	lib\libandroid_runtime.so

FAIL	MD5	lib\libaudio.so

FAIL	MD5	lib\libaudiopolicy.so

FAIL	MD5	lib\libbluedroid.so

FAIL	MD5	lib\libbluetoothd.so

FAIL	MD5	lib\libc.so

FAIL	MD5	lib\libcamera.so

FAIL	MD5	lib\libcameraservice.so

FAIL	MD5	lib\libcamera_client.so

FAIL	MD5	lib\libgsdi_exp.so

FAIL	MD5	lib\libhardware_legacy.so

FAIL	MD5	lib\libloc.so

FAIL	MD5	lib\libmedia.so

FAIL	MD5	lib\libmediaplayerservice.so

FAIL	MD5	lib\libnetutils.so

FAIL	MD5	lib\libomx_avcdec_sharedlibrary.so

FAIL	MD5	lib\libomx_m4vdec_sharedlibrary.so

FAIL	MD5	lib\libopencore_common.so

FAIL	MD5	lib\libopencore_player.so

FAIL	MD5	lib\libopencore_rtsp.so

FAIL	MD5	lib\libril-qcril-hook-oem.so

FAIL	MD5	lib\libril.so

FAIL	MD5	lib\libskia.so

FAIL	MD5	lib\libsonivox.so

FAIL	MD5	lib\libsoundpool.so

FAIL	MD5	lib\libtcmd_pipe.so

FAIL	MD5	lib\libwebcore.so

FAIL	MD5	lib\libwpa_client.so

FAIL	MD5	lib\oprofile.ko

FAIL	MD5	lib\hw\lights.msm7k.so

FAIL	MD5	lib\hw\sensors.default.so


FAIL	MD5	wifi\ar6000.ko[/code]

[Guest Sebastian404]

I've compared this ROM with Japanese Jellyfish r9 to find if any files have been updated. Actually very few:

some of those (a lot maybe) will just be the same just rebuilt, so the date/time stamp will of changed, anything that is signed (all the of the framework direcotry) will have a different cert (for the date/time).

[Guest kallt_kaffe]

KK, what is the build date for the new Kernel?

Dunno, don't have such a phone, only the dump. But the config has this info:

#

# Automatically generated make config: don't edit

# Linux kernel version: 2.6.32.9

# Thu Feb 10 04:52:41 2011

#

So basicly it's not older than that but I can be newer (I think), however build.prop also mentions February the 10th so I guess everything was built then.

I haven't taken the time to compile a new kernel, just reused my JJ kernel and it seems to work fine. However comparing the configs there are some small differences in some places. Seems to run well with my "old" kernel anyway.

[Guest kallt_kaffe]

I've compared this ROM with Japanese Jellyfish r9 to find if any files have been updated. Actually very few:

You should add liboemcamera.so, libril-qc-1.so and libcm.so to that list aswell as I borrowed them from JJ so they were different before that.

[Guest Simon O]

some of those (a lot maybe) will just be the same just rebuilt, so the date/time stamp will of changed, anything that is signed (all the of the framework direcotry) will have a different cert (for the date/time).

Yes, seems like that. Almost all the files are the same size. Wifi files are different (improved?) though.

kk: Any chance of uploading the original kernel config from the Swedish rom please?

Edited March 16, 2011 by flibblesan

[Guest Sebastian404]

You should add liboemcamera.so, libril-qc-1.so and libcm.so to that list aswell as I borrowed them from JJ so they were different before that.

Ah....

So your thinking the TPT will update the baseband... since the device has the same hardware the RIL should not change that much?

The camera lib is a bit more of a puzzle tho... unless the 'new devices' has a different camera from the 'old devices'?

[Guest wbaw]

Probably the wrong thread for it, but while flb seb & kallt are all here...

We have a new hungarian update, posted by fonix232 posted this in IRC - http://www.t-mobile.hu/static/szoftverek/z...29TV1_00_00.zip

It is a new update format, a windows .exe file, needs the stock 'FTM' recovery program. It looks like there may be some hidden functions in the new flash program, if we can unlock them.

Edited March 16, 2011 by wbaw