[Q] recovery.img is too large

[da1k]

Hello everybody,

I know that I should put this threat in Development but I have no rights to write there.

I tried to install CM10.1 and everything is going good until I receive such infromation: "recovery.img is too large for partition" and installation is stopped and Streak is bricked. I can repeat installation one more time with the same error.

Is anybody able to help me, what to do. How to reformat partition or change it size?

OK I solved the problem. I installed previous edition and now it works
best regards,

 

[giveen]

Actually a pretty easy fix. I need to adjust that in the scripts.

 

[OpenMinded]

Hello everybody,

I know that I should put this threat in Development but I have no rights to write there.

I tried to install CM10.1 and everything is going good until I receive such infromation: "recovery.img is too large for partition" and installation is stopped and Streak is bricked. I can repeat installation one more time with the same error.

Is anybody able to help me, what to do. How to reformat partition or change it size?

OK I solved the problem. I installed previous edition and now it works
best regards,

I also have this size problem when using the original kernel.
What did you do to fix this? What previous version?\
thanks

 

[giveen]

You have to adjust the flash configuration file. My newest build has this fixed.

 

[OpenMinded]

You have to adjust the flash configuration file. My newest build has this fixed.

i as asking because I try to compile recovery for mtk6589 based phones.
I cannot compile because the size is too large.
When I try to compile the wrong block size is shown, while the parameter is set to the proper value in the board config file.
It seems it is not read somehow.
It is very hard to find this kind of stuff when googling .
well, of to bed now, better luck next time

 

[giveen]

i as asking because I try to compile recovery for mtk6589 based phones.
I cannot compile because the size is too large.
When I try to compile the wrong block size is shown, while the parameter is set to the proper value in the board config file.
It seems it is not read somehow.
It is very hard to find this kind of stuff when googling .
well, of to bed now, better luck next time

Adjust the size in your BoardConfig

 

[OpenMinded]

Adjust the size in your BoardConfig

I did but according to compiler output it is not used.
Maybe some config error in my build setup.
I just followed the cm wiki with no luck.
There is also a message when using lunch,something like device not configured.
I'll muddle on,thanks

 

[giveen]

I did but according to compiler output it is not used.
Maybe some config error in my build setup.
I just followed the cm wiki with no luck.
There is also a message when using lunch,something like device not configured.
I'll muddle on,thanks

You have this in BoardConfig.mk?

BOARD_RECOVERYIMAGE_PARTITION_SIZE := 6042880

Make sure yours is large enough to hold your recovery image size and is smaller than your recovery partition.

 

[OpenMinded]

You have this in BoardConfig.mk?

BOARD_RECOVERYIMAGE_PARTITION_SIZE := 6042880

Make sure yours is large enough to hold your recovery image size and is smaller than your recovery partition.

I have 0x00600000 . I will try your setting.
If I allocate too much, it will overwrite the sec_ro partition.
I have not seen it being used.
I'll report back. the strange thing is also that the compiler reports a blocksize of 135xxx while it is set tot 131xxx.
Thank you for your input, cheers

---------- Post added at 03:46 PM ---------- Previous post was at 03:33 PM ----------

I have 0x00600000 . I will try your setting.
If I allocate too much, it will overwrite the sec_ro partition.
I have not seen it being used.
I'll report back. the strange thing is also that the compiler reports a blocksize of 135xxx while it is set tot 131xxx.
Thank you for your input, cheers

Well just tried it, it now wrongly reports a bigger size for the max 103xxxxx.
It build fine now, it's 6.3 mb, but the bloody piece of crap just does not boot.
I'm pretty much done for the moment.
Following multiple tutorials that lead to all kinds of errors other people lack to have is getting a bit annoying now .
thanks anyway, cheers

 

[giveen]

Try setting it to 6291456
0x00600000 = 6291456

What device are you developing for? What is the partition size?

 

[OpenMinded]

Try setting it to 6291456
0x00600000 = 6291456

What device are you developing for? What is the partition size?

Thanks for explaining. I am developing for Alps e2001v21_v89_gq3008s.
It is sold as Star / Haipai N9599 / N9589 .
The buildprop shows Alps and the string e2001v21_v89_gq3008s.
It is a MTK6589 based device with 1 Gb rom/ 16 gb ram and some kind of screen that supports a pen.

What do you mean with partition size?
I thought it was that 0x00600000.
It was very hard to find out the real device list and partitions, so I extracted it from a working recovery image.
Please find it attached.
Thanks for any help!

I just tried to fix things by fiddling with local_manifest, not sure if it has influence.
It's frustrating not to be able to build this darn thing, your help is greatly appreciated!

I'm trying to recompile now and also attached the scatter file for mtk droid tools.

 

[giveen]

Hex vs Decimal

Local_manifest is just where things download from

 

[OpenMinded]

Hex vs Decimal

Local_manifest is just where things download from

thanks, I know hex/decimal difference.
I am just unable to use the partition size and make a fitting recovery, let alone one that boots .

 

[OpenMinded]

thanks, I know hex/decimal difference.
I am just unable to use the partition size and make a fitting recovery, let alone one that boots .

I finally solved it.
I took the number of bytes from the compiler output that were claimed as reserver.
I added that to the maximum decimal number and all is fine.
Booting also worked, the issue was caused by a problem in the binary kernel I was using, which I found out by extracting it with unpack mtk tools again and comparing it.
So I have a working CWM 6.0 now for my mtk6589 based device.
Yeah!
thanks for the help, cheers

 

[byb4]

Would you share it?

I finally solved it.
I took the number of bytes from the compiler output that were claimed as reserver.
I added that to the maximum decimal number and all is fine.
Booting also worked, the issue was caused by a problem in the binary kernel I was using, which I found out by extracting it with unpack mtk tools again and comparing it.
So I have a working CWM 6.0 now for my mtk6589 based device.
Yeah!
thanks for the help, cheers

I've got a very similar phone, the STAR N9599 and would appreciate it if you could share your work. I'm having trouble with my Camera not auto-focusing and wonder if a ROM upgrade would resolve it.

 

[OpenMinded]

I've got a very similar phone, the STAR N9599 and would appreciate it if you could share your work. I'm having trouble with my Camera not auto-focusing and wonder if a ROM upgrade would resolve it.

This is not the place to discuss that I guess.
Look here:
http://forum.xda-developers.com/showthread.php?p=44216874#post44216874
I will post the CM 6 I compiled there soon, there is a ROM here:
http://www.needrom.com/phone-roms/star/n9599/
Make sure you backup first (google it) and be sure the hardware is identical.
No warranties and of course no one to blame when you brick it, but yourself.
Please remember that before flashing. You might try to find the camera files first to try, or download the ICS camera app from the market, to check if it is a software or hardware problem.

 

[balapradeep.jnvv]

i started working on ubuntu touch every thing is going well up to now :fingers-crossed:
here the problem is with the recovery.img, and boot.img they were too large to flash.... how to change the partition table before flashing ??
i made some changes to partition sizes in bord config finally i built those images ,here my question is how does the remaining partitions adjust AND how to flash
where to adjust all of these


:good: in advance

 

[hahagu]

Hello, same prob here...
Also, do I need the kernel source for this to work? And if so, where do I put it?

 

[giveen]

Hello, same prob here...
Also, do I need the kernel source for this to work? And if so, where do I put it?

Kernel source is on my github

 

[hahagu]

Kernel source is on my github

What's ur github? And what is the kernel src for?