90 replies to this topic

[theparasol]

Seems to me that you are simply unable to read the help output.

 

Yes, I tried that already too but same (strange) result, I cant find any obvious error in my command!

 

root@xp1000:~# nanddump -f dump0 /dev/mtd0
nanddump: invalid option -- 'f'
BusyBox v1.21.1 (2014-02-04 22:29:25 CET) multi-call binary.

Usage: nanddump [-o] [-b] [-s ADDR] [-f FILE] MTD_DEVICE

Dump the specified MTD device

        -o      Dump oob data
        -b      Omit bad block from the dump
        -s ADDR Start address
        -l LEN  Length
        -f FILE Dump to file ('-' for stdout)

[Lost in Space]

Looksl ike you have already a problem to read a 3 line post of gutemine up to the end

 

>>> Try mtd-utils-nanddump ipk for a better one.

 

I would not spend any more time on the busybox version of the mtd-utils as they are old and cripled in functionality  too.

 

Amd if they are not on the PLi feed - not my fault.

 

I was maybe just lucky that my tester still had the full tools on his box from the fgwrite tests.

Edited by gutemine, 8 February 2014 - 16:35.

[theparasol]

Indeed... but my more basic question is why is the busybox outputting help that isnt valid... its misleading if you ask me...

[Lost in Space]

To be honest - this is YOUR sofware feed as I asume you have OpenPLi on your box.

 

And it depends on the version of busybox how big the problem is, check if you applied all the relevant patches and complain at the busybox mailing list - not at my place.

 

If I climb a mountain I get proper tools and lates mtd-utils are really hight quality as they are the de-facto standard for Linux Flash tools.

Edited by gutemine, 8 February 2014 - 16:39.

[theparasol]

To be honest - this is YOUR sofware feed as I asume you have OpenPLi on your box.

 

I never had to use this tool before, and since I'm no expert on this material either I just was wondering what am I doing wrong in the first place.

Seems nothing but just the next stupid *dontcare* bug I stumbled over

[Lost in Space]

I normally use personally either self compiled ones from a current mtd-utils snasphot or you can try the ones from
here:

 

http://www.dreamboxu...m4_mips32el.ipk

 

My own versions of the mtd-util binaries are evil as they contain usefull extensions which make the live of my plugins easier.

 

But your naddump problems should not be the inhibitor to the real search for the bootlogo in flash.

Edited by gutemine, 8 February 2014 - 16:54.

[theparasol]

My own versions of the mtd-util binaries are evil as the contain usefill extensions which make the live of my plugins easier.

 

And besides that lets not forget your usual timebomb code...

As I have personal no interrest in changing a manufacturer logo this is were my journey ends.

 

P.S. mtd-utils-nanddump are in the openpli feeds, so no need for external packages.... but thanks anyway for wasting your time to assist me

[Lost in Space]

As I have to re-compile them regulary to fix bugs, add features and and use latest sources as basis, yes they have expiry dates (which means they simply stop operation, the are not bombing anything until now) so that I don't neet to fiddle around with old bugs and need to support only the latest version.

 

This means your old OE and feeds are also timebombed as they expire and cann't be used to build images from the stone age anymore.

 

But this discussion if OT here, hopefully somebody more motivated to really solve the problem will find something usefull in my hints, because as I explained this is not really that difficult to figure out.

Edited by gutemine, 8 February 2014 - 17:06.

[theparasol]

...hopefully somebody more motivated...

 

Just do for a change the simple steps yourself too and post the results to amaze the lazy, dumb and ignorant crowd

[Lost in Space]

Not that you say it ...

 

But the others in this thread at least contributed something usefull or tried to give the OP a solution.

[theparasol]

Problem of topicstarter is already solved, but you yourself opened up a more general approach where the user isnt relaying on bootloader support to change the manufacturer image.

You already sketched in draft how to find and change the manufacturer image. Now you have to wait for a user that takes up the challenge and decides to carry out the tasks on his device.

 

After all proof is in tasting the pudding

[Lost in Space]

If you consider using an old bootloader whcih make system crash a good solution ... yes I agree it is 'solved'

 

But my hints where no challenge, just hints.

 

Good that we talked about your understanding of how a form works

Edited by gutemine, 8 February 2014 - 17:36.

[theparasol]

If you consider using an old bootloader whcih make system crash a good solution ... yes I agree it is 'solved'

 

Merely temporarly (mis)use old bootloader that still has manufacturer logo flash support, after that replace it with latest bootloader again. Nothing wrong in doing such a thing.

[Lost in Space]

maybe yes, but if you then boot your box the newer kernel and drivers will maybe not like this old bootloader, so you would need to instantly flash the new bootloader again.

 

But once again if somebody wants a better and more generic solution and understand your box better ... there is now room to improve instead of shrugging your shoulders.

 

I simply cann't hep any further then what I did already, as my dreamboxes all have their bootlogos neatly in the filesystem

[theparasol]

Dreamboxes have their own challenges. If you ask me far more daring

[Lost in Space]

I'm sorry, this is OT and will not go back to the pimps and their cars discussion

[theparasol]

Well thanks again for sharing your interesting thoughts and view about the matter!

Edited by theparasol, 8 February 2014 - 18:01.

[ajeeb]

Problem of topicstarter is already solved, but you yourself opened up a more general approach where the user isnt relaying on bootloader support to change the manufacturer image.

You already sketched in draft how to find and change the manufacturer image. Now you have to wait for a user that takes up the challenge and decides to carry out the tasks on his device.

 

After all proof is in tasting the pudding

 

anyway ! button line I revert to old bootloader  ... update splash.bin ... update again to new bootloader no harm done !

-

BTW latest pli update cause problem with tunerA  ... so I copy satellites.xml back it's solve the problem .

 

cheers 

[malakudi]

Please add "ignore user's post" option in forum. We desperately need this.

[dAF2000]

[modbreak=Modbreak]Let's keep it on-topic and just find the answer on how to remove the logo. Discussions about why there's a logo seem to lead to nothing.[/modbreak]