Getting Dreaded 'write_raw_image' failure on boot.img

Discussion in 'ChevyNo1' started by ChevyNo1, May 27, 2011.

  1. ChevyNo1
    Offline

    ChevyNo1 Premium Member Premium Member Developer

    Joined:
    Dec 28, 2009
    Messages:
    5,354
    Likes Received:
    5
    Trophy Points:
    0
    So I've been doing my research - and from what I've gathered - the boot.img is too large, or there are corrupt blocks in the boot partition. However - what I've tested thus far makes me think this is not the case.

    I am able to install 5.3 just fine. I have built 5.4 and was to start testing it myself when I came upon this error. It IS a fresh pull from CM which brought in a few fixes. However - I do not use any part of their boot stuff, as you know I create my own kernels.

    I have taken the 5.3 zipfile that installs, and put the 5.4 boot image in it, and it installs just fine. This is what leads me to believe that it's not the boot.img itself.

    I've also seen a few posts that blamed the recovery (I'm using RZR 2.0.3). However - again, my test should rule this out. updater_binary is the same between 5.3/5.4, so it's not that.

    Sooooo - I know a few of you have faced this. Did you ever get it resolved?
  2. NicoleNXD
    Offline

    NicoleNXD New Member

    Joined:
    Sep 7, 2010
    Messages:
    344
    Likes Received:
    1
    Trophy Points:
    0
    Location:
    Livermore, CA
    Chevy, winner00 in the cm section has the same issue and was trying to figure it out. Maybe he could be of some help to you.

    Sent from my Droid using DroidForums
  3. ChevyNo1
    Offline

    ChevyNo1 Premium Member Premium Member Developer

    Joined:
    Dec 28, 2009
    Messages:
    5,354
    Likes Received:
    5
    Trophy Points:
    0
    Thanks Nicole I'll check that out - been beating my head against the wall on this for some time today ...
  4. NicoleNXD
    Offline

    NicoleNXD New Member

    Joined:
    Sep 7, 2010
    Messages:
    344
    Likes Received:
    1
    Trophy Points:
    0
    Location:
    Livermore, CA
    No problem. Hope he can help. =)

    Sent from my Droid using DroidForums
  5. spc_hicks09
    Offline

    spc_hicks09 Premium Member Premium Member Developer

    Joined:
    Nov 7, 2010
    Messages:
    1,156
    Likes Received:
    33
    Trophy Points:
    48
    Location:
    Marion, OH
    Stupid question I know but, are you putting this in a "update script" or "updater script." Lol nevermind I just reread your post where you say "updater_binary" haha. What's the exact syntax you have in there because it should be something like:

    write_raw_image BOOT:boot.img
    Last edited: May 28, 2011
  6. hrdnhvy
    Offline

    hrdnhvy New Member

    Joined:
    Mar 13, 2010
    Messages:
    613
    Likes Received:
    0
    Trophy Points:
    0
    Location:
    WI
    Interesting, I to have gotten this error the last two roms i tried to flash & im using clockwork recovery, I was begining to wonder/worry if it was my phone or sd card...
  7. spc_hicks09
    Offline

    spc_hicks09 Premium Member Premium Member Developer

    Joined:
    Nov 7, 2010
    Messages:
    1,156
    Likes Received:
    33
    Trophy Points:
    48
    Location:
    Marion, OH
    Too many bad partition blocks maybe? I have never had this issue but I wish I would so I could try to figure it out.
  8. ChevyNo1
    Offline

    ChevyNo1 Premium Member Premium Member Developer

    Joined:
    Dec 28, 2009
    Messages:
    5,354
    Likes Received:
    5
    Trophy Points:
    0
    After several hours of debugging - I believe I have it figured out - will report back later!
  9. liquid0624
    Offline

    liquid0624 Premium Member Premium Member Developer

    Joined:
    Mar 24, 2010
    Messages:
    584
    Likes Received:
    5
    Trophy Points:
    0
    Chevy I'm having same issue pm me plz if u figured it out bro thanks
  10. ChevyNo1
    Offline

    ChevyNo1 Premium Member Premium Member Developer

    Joined:
    Dec 28, 2009
    Messages:
    5,354
    Likes Received:
    5
    Trophy Points:
    0
    PM sent bro!
  11. winner00
    Offline

    winner00 Premium Member Premium Member Developer

    Joined:
    Nov 15, 2009
    Messages:
    1,112
    Likes Received:
    10
    Trophy Points:
    0
    Location:
    Utah
    What was causing it? I know it been fixed now but curious to what was causing it.
  12. ChevyNo1
    Offline

    ChevyNo1 Premium Member Premium Member Developer

    Joined:
    Dec 28, 2009
    Messages:
    5,354
    Likes Received:
    5
    Trophy Points:
    0
    PM sent! :)
  13. claaaaayz
    Offline

    claaaaayz New Member

    Joined:
    Jun 6, 2011
    Messages:
    1
    Likes Received:
    0
    Trophy Points:
    0
    Glad you figured it out!

    I'm having a similar problem and was wondering if you could post here to help myself and the others who come across this forum looking for the answer. Much appreciated!
Search tags for this page

assert failed write raw image( /tmp/boot.img boot )

,

boot.img: updated is too big for the boot image

,
how to fix boot img too large