Remove All Ads from XDA

Stock boot.img problems from the factory

141 posts
Thanks Meter: 70
Post Reply Email Thread
I have an Alcatel Pixi3 4.5 4G model 5017O and I'm working on development for this phone.

I did a hexdump on the stock boot.img and was quite surprised to see this:
00004b80 |.......... -- Sy|
00004b90 |stem halted.Atte|
00004ba0 |mpting division |
00004bb0 |by 0!...Uncompre|
00004bc0 |ssing Linux.....|
00004bd0 |decompressor ret|
00004be0 |urned an error..|
00004bf0 | done, booting t|
00004c00 |he kernel...inva|
00004c10 |lid distance too|
00004c20 | far back...inva|
00004c30 |lid distance cod|
00004c40 |e...invalid lite|
00004c50 |ral/length code.|
00004c60 |incorrect header|
00004c70 | check..unknown |
00004c80 |compression meth|
00004c90 |od..invalid wind|
00004ca0 |ow size.invalid |
00004cb0 |block type..inva|
00004cc0 |lid stored block|
00004cd0 | lengths....too |
00004ce0 |many length or d|
00004cf0 |istance symbols.|
00004d00 |invalid code len|
00004d10 |gths set....inva|
00004d20 |lid bit length r|
00004d30 |epeat...invalid |
00004d40 |literal/lengths |
00004d50 |set.invalid dist|
00004d60 |ances set...inco|
00004d70 |rrect data check|
00004d80 |....Out of memor|
00004d90 |y while allocati|
00004da0 |ng output buffer|
00004db0 |....Out of memor|
00004dc0 |y while allocati|
00004dd0 |ng input buffer.|
00004de0 |Out of memory wh|
00004df0 |ile allocating z|
00004e00 |_stream.Out of m|
00004e10 |emory while allo|
00004e20 |cating workspace|
00004e30 |....Not a gzip f|
00004e40 |ile.header error|
00004e50 | error..|
00004e60 |uncompression er|
00004e70 |ror.............|

Does anyone else have an Alcatel, or any MediaTek based phone with a stock boot.img, that they can check to see if all of the phones they release are like this?

You can run a hexdump and check for yourself in Linux and let me know, or post your phone specs (MediaTek based only) here as well as a link to download your stock unmodified boot.img.

To do the hexdump cd into the dir with your stock boot.img and run the following command (in Linux):

hexdump -C "boot image name" | tee boot_dump.txt

where "boot image name" is the name of your boot image (without the quotes) that you made during a readback in SP Flash tools when you did your backup of you stock rom. The hexdump will be saved to a file named boot_dump.txt.

(You may have to run "sudo apt-get install hexdump" (without the quotes) in Ubuntu if you don't already have hexdump installed.)

If this is in the wrong section, please let me know.
Post Reply Subscribe to Thread

alcatel, boot.img, error, hexdump, mediatek

Guest Quick Reply (no urls or BBcode)
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes