168 replies to this topic

[StevenHarperUK]

Hi Guys,

Great work on unlocking the full 512MB of these 256MB Phones.

However the solution to this seems to start and page 4 and spread all the way up to here.

Can someone who will take ownership of a nice clear new thread please make one - and we can get it stickied.

I don't mind this being me - but if someone else wants it thats good.

The new thread should include all the models that can be done and have been confirmed.
It should all be clear in the first post, and kept up-to date.

Again well done.

[oh!dougal]

StevenHarperUK, on Dec 28 2010, 14:23, said:

Hi Guys,

Great work on unlocking the full 512MB of these 256MB Phones.

However the solution to this seems to start and page 4 and spread all the way up to here.

Can someone who will take ownership of a nice clear new thread please make one - and we can get it stickied.

I don't mind this being me - but if someone else wants it thats good.

The new thread should include all the models that can be done and have been confirmed.
It should all be clear in the first post, and kept up-to date.

Again well done.

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.


This update should also have great value to devs/crackers wanting to understand preboot (pre-linux) processes, (and linux-unreadable partitions) on the Blade.

AND it demonstrates ZTE's inbuilt method of flashing in new roms (and maybe patches?)

[fonix232]

oh!dougal, on Dec 28 2010, 17:38, said:

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.
This update should also have great value to devs/crackers wanting to understand preboot (pre-linux) processes, (and linux-unreadable partitions) on the Blade.

AND it demonstrates ZTE's inbuilt method of flashing in new roms (and maybe patches?)

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).

[StevenHarperUK]

oh!dougal, on Dec 28 2010, 14:38, said:

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.
This update should also have great value to devs/crackers wanting to understand preboot (pre-linux) processes, (and linux-unreadable partitions) on the Blade.

AND it demonstrates ZTE's inbuilt method of flashing in new roms (and maybe patches?)

I agree; that's why whoever makes this thread will have to be VERY clear on who should be doing this update and be willing to keep it upto date.
And possibly get translations done for languages pertenant to the devices country of origin.

[StevenHarperUK]

fonix232, on Dec 28 2010, 14:41, said:

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).

Wow this is rather a big development.

It means that we can produce a single ZIP for a full phone update, no fastboot - very neat.

[oh!dougal]

fonix232, on Dec 28 2010, 14:41, said:

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 ...

[fonix232]

oh!dougal, on Dec 28 2010, 17:56, said:

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).

[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

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.

[gusthy]

oh!dougal, on Dec 28 2010, 14:38, said:

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.

[hecatae]

fonix232, on Dec 27 2010, 22:06, said:

Not a minute more

http://fonix232.co.c...?dir=/blade/b03

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

[fonix232]

hecatae, on Dec 28 2010, 18:05, said:

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!

[StevenHarperUK]

hecatae, on Dec 28 2010, 15:05, said:

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 by StevenHarperUK, 28 December 2010 - 03:11 PM.

[hecatae]

fonix232, on Dec 28 2010, 15:08, said:

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

[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?

[gusthy]

StevenHarperUK, on Dec 28 2010, 15:12, said:

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.

[Phoenix Silver]

StevenHarperUK, on Dec 28 2010, 16:12, said:

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 ?

[oh!dougal]

StevenHarperUK, on Dec 28 2010, 15:12, said:

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?

[Sebastian404]

StevenHarperUK, on Dec 28 2010, 15:01, said:

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

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

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

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

[Phoenix Silver]

oh!dougal, on Dec 28 2010, 16:28, said:

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  

[oh!dougal]

Phoenix Silver, on Dec 28 2010, 15:30, said:

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?