hungarian ZTE blade sw update to solve memory problem

[Guest oh!dougal]

Well, I guess, as I found no hashes for the original img files in the zip, we can simply replace recovery with our own, and also system and boot too!

So it could be used as a self-flashing package what installs everything needed - custom recovery, our own ROM, overclock kernel, and custom splash (even custom partition layouts if I manage to break it somehow).

IMHO the installer and the insight into pre-linux boot behaviour should be MEGA valuable.

But people like Tom_G (for one example) are not going to notice this buried away in a local-interest section ...

[Guest fonix232]

IMHO the installer and the insight into pre-linux boot behaviour should be MEGA valuable.

But people like Tom_G (for one example) are not going to notice this buried away in a local-interest section ...

I agree, but my first goal is to edit the partition layout, the prebootloader can wait (I guess we can't do anything with it, as it is a 16megs ELF binary).

[Guest StevenHarperUK]

I wounder if we can remove the bits of the update we don't wan't to happen and just apply the Memory Fixing part - and not flash the Recovery etc...

-rw-r--r--  1 steven steven		40 2010-12-08 00:05 amsshd.mbn

-rw-r--r--  1 steven steven  19484672 2010-12-08 00:05 amss.mbn

-rw-r--r--  1 steven steven		40 2010-12-14 17:59 appsboothd.mbn

-rw-r--r--  1 steven steven	 44220 2010-12-14 17:59 appsboot.mbn

-rw-r--r--  1 steven steven   2516992 2009-01-01 00:00 boot.img

-rw-r--r--  1 steven steven	577536 2010-05-05 15:12 cefs.mbn

-rw-r--r--  1 steven steven		40 2010-12-08 00:05 oemsblhd.mbn

-rw-r--r--  1 steven steven	435444 2010-12-08 00:05 oemsbl.mbn

-rw-r--r--  1 steven steven	   464 2010-12-08 00:05 partition.mbn

-rw-r--r--  1 steven steven	   252 2010-12-14 17:59 partition_zte.mbn

-rw-r--r--  1 steven steven	 11412 2010-12-08 00:05 qcsblhd_cfgdata.mbn

-rw-r--r--  1 steven steven	 57328 2010-12-08 00:05 qcsbl.mbn

-rw-r--r--  1 steven steven   2891776 2009-01-01 00:00 recovery.img

-rw-r--r--  1 steven steven	770048 2010-12-08 00:41 splash.img

-rw-r--r--  1 steven steven 139780608 2009-01-01 00:00 system.img[/code]


I wounder if we reduce the ZIP to JUST the files needed to fix the memory problem - is there any way of finding out which ones we need


and if it will work with some missing.

[Guest gusthy]

Agreed.

However, there seems a great probability that greedy fools will try to apply this update to their 512 phones with unpredictable (and likely unwelcome) results.

Well, evolution in work.

[Guest hecatae]

Not a minute more :(

http://fonix232.co.cc/rom/index.php?dir=%2Fblade%2Fb03

Extract image.zip to the root of the SD card and do what I wrote from point 2!

PeaNut:

It is still Éclair, as I know T, we will never get official froyo!

thank you for that, going to see what happens using this on the Softbank custom roms

[Guest fonix232]

thank you for that, going to see what happens using this on the Softbank custom roms

I hope you read the next comments too, EXTRACT THE ZIP TO /IMAGE ON SD CARD!

[Guest StevenHarperUK]

thank you for that, going to see what happens using this on the Softbank custom roms

The instructions have been updated to extract the zip contents into a directory called image on the sdcard

So it should be

/sdcard/image/<FILES>

edit : posted at the same time as the above thread.

Edited December 28, 2010 by StevenHarperUK

[Guest hecatae]

I hope you read the next comments too, EXTRACT THE ZIP TO /IMAGE ON SD CARD!

I intend to, the Softbank rom has a System Updates setting in the Settings menu, going to see if it sees this as a valid update

[Guest StevenHarperUK]

Right I think its time to make a new Thread with the instructions clearly in the first post :

Can I please do this?

Any Objections?

[Guest gusthy]

Right I think its time to make a new Thread with the instructions clearly in the first post :

Can I please do this?

Any Objections?

I guess, it's your turn :(

It would be nice to achieve that this new thread be pinned.

[Guest Phoenix Silver]

Right I think its time to make a new Thread with the instructions clearly in the first post :

Can I please do this?

Any Objections?

no objections :(

about this work if i have understand clearly it could help to take a look at the phone portion that linux can't read ?

[Guest oh!dougal]

Right I think its time to make a new Thread with the instructions clearly in the first post :

Can I please do this?

Any Objections?

As regards the pure 256/512 aspect, please start by insisting on downloading Android System Info, and looking at the "RAM" display.

A 512 ram phone shows "Max 414MB" because of some being reserved for the screen, etc.

What does a 256 ram specimen (needing the fix) show?

[Guest Sebastian404]

I wounder if we can remove the bits of the update we don't wan't to happen and just apply the Memory Fixing part - and not flash the Recovery etc...

-rw-r--r--  1 steven steven		40 2010-12-08 00:05 amsshd.mbn

-rw-r--r--  1 steven steven  19484672 2010-12-08 00:05 amss.mbn

-rw-r--r--  1 steven steven		40 2010-12-14 17:59 appsboothd.mbn

-rw-r--r--  1 steven steven	 44220 2010-12-14 17:59 appsboot.mbn

-rw-r--r--  1 steven steven   2516992 2009-01-01 00:00 boot.img

-rw-r--r--  1 steven steven	577536 2010-05-05 15:12 cefs.mbn

-rw-r--r--  1 steven steven		40 2010-12-08 00:05 oemsblhd.mbn

-rw-r--r--  1 steven steven	435444 2010-12-08 00:05 oemsbl.mbn

-rw-r--r--  1 steven steven	   464 2010-12-08 00:05 partition.mbn

-rw-r--r--  1 steven steven	   252 2010-12-14 17:59 partition_zte.mbn

-rw-r--r--  1 steven steven	 11412 2010-12-08 00:05 qcsblhd_cfgdata.mbn

-rw-r--r--  1 steven steven	 57328 2010-12-08 00:05 qcsbl.mbn

-rw-r--r--  1 steven steven   2891776 2009-01-01 00:00 recovery.img

-rw-r--r--  1 steven steven	770048 2010-12-08 00:41 splash.img

-rw-r--r--  1 steven steven 139780608 2009-01-01 00:00 system.img[/code]




I wounder if we reduce the ZIP to JUST the files needed to fix the memory problem - is there any way of finding out which ones we need



and if it will work with some missing.



To be honest, this file is the most interesting thing I've seen for a while, since its a valid working update.zip :(



some stuff you can discard straght-away..



boot, recovery, system are clear..







looking into partition_zte.mbn



[code]0:RECOVERY	56 01 00 00 - 24 00 00 00 00

0:BOOT	7A 01 00 00 - 24 00 00 00

0:SPLASH	9E 01 00 00 - 0C 00 00 00

0:MISC	AA 01 00 00 - 03 00 00 00

0:CACHE	AD 01 00 00 - 4A 01 00 00

0:SYSTEM	F7 02 00 00 - 7C 06 00 00

0:USERDATA	73 09 00 00 - 81 06 00 00

0:PERSIST	F4 0F 00 00 - 0C 00 00 00

and then in partition.mbn

0:MIBIB

0:QCSBL

0:OEMSBL1

0:OEMSBL2

0:AMSS

0:APPSBL

0:FOTA

0:EFS2

0:APPS

0:FTL

0:EFS2APPS[/code]




TOM_G might have a better idea of this since hes been looking into the other partitions with his RS232 magic ;)

[Guest Phoenix Silver]

As regards the pure 256/512 aspect, please start by insisting on downloading Android System Info, and looking at the "RAM" display.

A 512 ram phone shows "Max 414MB" because of some being reserved for the screen, etc.

What does a 256 ram specimen (needing the fix) show?

416,61 M exactly for me :(

[Guest oh!dougal]

416,61 M exactly for me :(

You have a phone with 512 and your rom is using fractionally less than mine for the etceteras.

What does a 256 phone show --- to show that it needs the fix?

[Guest oh!dougal]

To be honest, this file is the most interesting thing I've seen for a while, since its a valid working update.zip :(

<...>

TOM_G might have a better idea of this since hes been looking into the other partitions with his RS232 magic ;)

I've sent him a PM half an hour ago, so, when dawn gets to Melbourne ... !

[Guest Sebastian404]

I've sent him a PM half an hour ago, so, when dawn gets to Melbourne ... !

I guess a much more interested question is who is going to be brave enough to try flashing it to their device?

I've already ruined a very expensive Cisco device by installing the wrong firmware this month... someone else's turn

[Guest StevenHarperUK]

Ok here we go

http://android.modaco.com/content/zte-blad...vices-to-512mb/

[Guest eLJay]

i'm sure it's true lol

Depends whether that is higher or lower Japanese!

[Guest gusthy]

You have a phone with 512 and your rom is using fractionally less than mine for the etceteras.

What does a 256 phone show --- to show that it needs the fix?

MAX 161 MB

[Guest StevenHarperUK]

Which devices have been confirmed to work?

Which devices Exist (with 256MB) and have not been confirmed?

[Guest bbandi]

Which devices have been confirmed to work?

Which devices Exist (with 256MB) and have not been confirmed?

It's confirmed to work on the UK version too:

post

Edited December 28, 2010 by bbandi

[Guest StevenHarperUK]

It's confirmed to work on the UK version too:

post

Thats a bad link - but I believe you :(

[Guest Bygway]

A big thank you to all who have participated on this thread! I've got my 414 MB back! Wohoo!! Köszönöm srácok!

[Guest Konstant1nos]

Hello from Greece i did the update on my ZTE and now i have

414,81 MB of system memory.

Many thanks to all of you.

:( ;) ;) ;)