18 replies to this topic

[hecatae]

anyone want to see if we can use an amss.mbn from another msm7227 device, we would have to change a few libs as well.

reasons I want to do this, see if we can enable different radio bands like 850, see if we can improve the reception quality

there is a tpt for the zte v9 here http://www.device.be...tware/m2/m2.zip

if the amss.mbn files match I'd be willing to see if the amss updates my radio image

alternatively we could extract lg firmwares and look at the amss.mbn contained within those firmwares for their msm7227 chipsets

alternatively, does anyone know the partition layout for the zte v9 light, does it match the zte x880 libra?

edit: http://forum.xda-dev...mp;postcount=30

zte v9 partition layout

Quote

# cat mtd
dev: size erasesize name
mtd0: 00500000 00020000 "recovery"
mtd1: 00500000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00080000 00020000 "misc"
mtd4: 02800000 00020000 "cache"
mtd5: 0ef00000 00020000 "system"
mtd6: 0a280000 00020000 "userdata"
mtd7: 00200000 00020000 "oem"
mtd8: 00180000 00020000 "persist"

zte x880 partition layout

Quote

# cat /proc/mtd
dev: size erasesize name
mtd0: 00500000 00020000 "recovery"
mtd1: 00500000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00080000 00020000 "misc"
mtd4: 02580000 00020000 "cache"
mtd5: 0dc00000 00020000 "system"
mtd6: 0a280000 00020000 "userdata"
mtd7: 01500000 00020000 "oem"
mtd8: 00180000 00020000 "persist"

zte blade partition layout

Quote

Factory MTD layout
$ cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00480000 00020000 "recovery"
mtd1: 00480000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00060000 00020000 "misc"
mtd4: 02940000 00020000 "cache"
mtd5: 0cf80000 00020000 "system"
mtd6: 0d020000 00020000 "userdata"
mtd7: 00180000 00020000 "persist"

is it me or are the zte v9 partition layouts the same as the x880?

I'll flash the amss.mbn first and report back

I can use the boot.img for gen2 from swedish spring by kallt_kaffe, recovery.img for x880 by sebastian404, system.img from swedish spring, splash.img is the same as previously

Edited by hecatae, 25 March 2011 - 05:25 PM.

[fonix232]

The /proc/mtd will not be enough, you have to see the partition.mbn layout of the given devices, it contains the offsets and length of these partitions!

[hecatae]

fonix232, on Mar 25 2011, 17:46, said:

The /proc/mtd will not be enough, you have to see the partition.mbn layout of the given devices, it contains the offsets and length of these partitions!

like this from the blade?

Quote

Factory partition layout
/dev: 212440K total, 12K used, 212428K available (block size 4096)
/system: 212480K total, 142456K used, 70024K available (block size 4096)
/data: 213120K total, 46764K used, 166356K available (block size 4096)
/persist: 1536K total, 1156K used, 380K available (block size 4096)
/sqlite_stmt_journals: 4096K total, 0K used, 4096K available (block size 4096)
/cache: 42240K total, 1416K used, 40824K available (block size 4096)

[fonix232]

hecatae, on Mar 25 2011, 20:57, said:

like this from the blade?

Still not the one, use the TPT included partition.mbn! It includes the hidden RADIO partitions too, so you can see if another one is fitting the size etc!

[hecatae]

fonix232, on Mar 25 2011, 18:11, said:

Still not the one, use the TPT included partition.mbn! It includes the hidden RADIO partitions too, so you can see if another one is fitting the size etc!

ok, I'll pull it apart later and compare to the v9 partition.mbn

the partition.mbn is identical, the partition_zte.mbn is different as it shows the oem partition on the v9

and the amss.mbn is identical

Edited by hecatae, 25 March 2011 - 11:14 PM.

[leromarinvit]

I just flashed the GEN2 amss.mbn on my GEN1 phone. The good news is that everything still works. The bad news is that it hasn't given me HSUPA. It's definitely the new radio, since it needs the new ril libs to work. I've seen some reports that not everybody has HSUPA after the GEN2 update - might this be the same problem here? Anyone willing to test? There shouldn't be any risk of bricking, just a few minutes of work.

Unfortunately, I can't test the 850 MHz band, since no network uses it here. Can anyone here test that? I'm sort of hesitant to do the full GEN2 update, since the only way back currently seems to eat IMEIs for breakfast (or so I heard). I managed to snatch the downgrade file from Google's cached results page, but I don't really want to risk bricking my phone right now if I can avoid it.

Here's what I did:

• download the JJ RLS9 TPT image
  
• download the gen1 -> gen2 update
  
• replace amss.mbn & amsshd.mbn in JJ with the gen2 ones, then flash that
  
• flash Swedish Spring (probably not necessary)
  
• replace libcm.so & libril-qc-1.so with the gen2 ones

[Sebastian404]

Keep in mind there is is a Gen1 & Gen2 version of the V9 out there, and the guys from ZTE.AU are VERY keen to point out that the Optus version of the V9 has hardware differences to the other versions...

but from *MY* (Optus) gen1 v9:

cat /proc/mtd
dev:	size   erasesize  name
mtd0: 00500000 00020000 "recovery"
mtd1: 00500000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00080000 00020000 "misc"
mtd4: 02800000 00020000 "cache"
mtd5: 0ef00000 00020000 "system"
mtd6: 0a280000 00020000 "userdata"
mtd7: 00200000 00020000 "oem"
mtd8: 00180000 00020000 "persist"

and from a (Telenor) gen2 v9:

dev:	size   erasesize  name
mtd0: 00500000 00020000 "recovery"
mtd1: 00500000 00020000 "boot"
mtd2: 00180000 00020000 "splash"
mtd3: 00080000 00020000 "misc"
mtd4: 02580000 00020000 "cache"
mtd5: 0dc00000 00020000 "system"
mtd6: 0a280000 00020000 "userdata"
mtd7: 01500000 00020000 "oem"
mtd8: 00180000 00020000 "persist"

[leromarinvit]

Sebastian404, on Apr 7 2011, 00:54, said:

Keep in mind there is is a Gen1 & Gen2 version of the V9 out there, and the guys from ZTE.AU are VERY keen to point out that the Optus version of the V9 has hardware differences to the other versions...

Just so there are no misunderstandings: I was talking about the Gen2 Blade radio, not the V9.

[wbaw]

Has anybody noticed any differences between the different blade gen2 amss.mbn files? As far as I know so far we have Comviq (Sweden), TeliaSonera (Sweden), Wind (Greece), Softbank (Japan) & China Unicom versions. Are there any others? Any noticeable differences?

appsboot.mbn varies between networks too, it's probably a bad idea to flash the Greek, Chinese or Japanese versions of that.

[unrandomsam]

wbaw, on May 3 2011, 19:15, said:

Has anybody noticed any differences between the different blade gen2 amss.mbn files? As far as I know so far we have Comviq (Sweden), TeliaSonera (Sweden), Wind (Greece), Softbank (Japan) & China Unicom versions. Are there any others? Any noticeable differences?

appsboot.mbn varies between networks too, it's probably a bad idea to flash the Greek, Chinese or Japanese versions of that.

comviq and teliasoneria are identical

softbank is different.

Its possible that the softbank amss.mbn has 3g at 850mhz instead of 900mhz (I have no way to test this)

(not sure about the others)

[hecatae]

unrandomsam, on May 3 2011, 19:37, said:

comviq and teliasoneria are identical

softbank is different.

Its possible that the softbank amss.mbn has 3g at 850mhz instead of 900mhz (I have no way to test this)

(not sure about the others)

the softbank amss.mbn has caused issues for a user in the UKraine who could not find their operator, but could find another provider, somewhere in the gen2 windows flashing guide

[unrandomsam]

I am interested in trying the gen3 files when they become available.

[wbaw]

comviq & teliasonera are not identical!

Anyway, I found the build dates for 3 of the European gen2 files, simply

strings ./amss.mbn | grep "2011"

Quote

[john@peach amss]$ strings ./amss.comviq | grep "2011"
Feb 10 2011
[john@peach amss]$ strings ./amss.sonera | grep "2011"
Mar 11 2011
20110106
[john@peach amss]$ strings ./amss.t-hun | grep "2011"
Mar 14 2011
20110118
[john@peach amss]$ strings ./amss.wind | grep "2011"
Mar 24 2011

Comviq is the oldest of these, Feb 10 2011 & the Greek Wind is the newest with Mar 24 2011. The second date is only in the middle two.

Further testing seems to show that the T-Mobile Hungary & TeliaSonera amss.mbn files are very similar, there were a lot of changes between comviq & teliasonera, and a lot of changes again for greek wind.

So I'm going to try out the greek wind gen2 amss.mbn on my phone, combined with the hacked gen2 teliasonera appsboot.mbn & hungarian gen1 oemsbl.mbn ... see if i can get the perfect combination & if theres any noticebale difference between wind & teliasonera amss.mbn

that combination works, i get 512mb ram, etc, however i actually seem to be getting slower mobile data speeds, certainly no hsupa ... not noticed any real difference at all yet. maybe gps is a bit improved, or maybe it's just because of the updates to cm7.

Edited by wbaw, 16 May 2011 - 05:44 AM.

[shmizan]

wbaw are you able to test 850 MHz band reception?

[wbaw]

shmizan, on May 16 2011, 08:04, said:

wbaw are you able to test 850 MHz band reception?

No, they don't use that frequency in my country.

I'm getting normal hsdpa, no hsupa, seems to be no noticeable difference between greek wind & swedish teliasonera. I've included the greek version in my latest tpt anyway.

[hedgepigdaniel]

I've tested the Comviq, TeliaSonera, and T-Mobile Hungary amss.bin and none of them enables HSUPA (which is supported on my network/SIM)

[shmizan]

so I wonder how this guy got it working!

[wbaw]

I think he got the upload & download speeds confused.

[shmizan]

ok so I asked him how he enabled HSUPA, this is his answer:

Quote

Hi
I upgraded to Gen2 using the Geni to Gen2 upgrade via Win7 PC. Upload speed correct using Speedtest software. I checked on 2 different
servers here in Ireland North and South Derry (fastest) and Dundalk (slightly slower). Ran the test 3 times on each and obtained the figure posted
on each occasion.

Oldbarzo
(Douglas)

guys how is the windows flashing different? did it flash different files?

Edited by shmizan, 17 May 2011 - 06:54 PM.