DroidForums.net is the original Verizon Android Forum! Registered Users do not see these ads. Please Register - It's Free!
Page 1 of 2 12 LastLast
Results 1 to 10 of 15

Thread: Getting write_raw_image status 7 error

  1. Senior Droid
    Demolition Man's Avatar
    Member #
    64601
    Join Date
    May 2010
    Location
    Pawnee, IN
    Posts
    246
    Liked
    1 times
    Twitter
    DemoManMLS
    Phone
    Droid RAZR
    #1

    Getting write_raw_image status 7 error

    I tried to install several ROMs tonight including the latest LFY and getting the write_raw_image status 7 error when it gets to the boot part of the ROM install. Here's what the recovery log shows on the issue:

    Installing Boot Image...
    mtd: not writing bad block at 0x00280000
    mtd_write_data to boot failed: No space left on device
    write_raw_image: error erasing blocks of boot
    write_raw_image: error closing write of boot
    failed to write boot partition from /tmp/boot.img
    script aborted: assert failed: write_raw_image("/tmp/boot.img", "boot")
    assert failed: write_raw_image("/tmp/boot.img", "boot")
    E:Error in /sdcard/clockworkmod/download/android.markjohnston.us/DL/LFY/RELEASES/LFYv1.95.zip
    (Status 7)
    Installation aborted.
    Failure at line 7:
    install_zip SDCARD:/clockworkmod/download/android.markjohnston.us/DL/LFY/RELEASES/LFYv1.95.zip

    Any idea on how I can fix this?
  2.  
     
     
     
  3. Droid Ninja
    teddyearp's Avatar
    Member #
    27105
    Join Date
    Jan 2010
    Location
    Randle, WA
    Posts
    1,801
    Liked
    19 times
    Phone
    SamsungŪ SCH-I515
    #2
    Two ways. I think it is a corrupted download. So either download it via your pc and xfer it to your sdcard, or clean the download cache in Rom Manager and try again.

    good luck
  4. Senior Droid
    Demolition Man's Avatar
    Member #
    64601
    Join Date
    May 2010
    Location
    Pawnee, IN
    Posts
    246
    Liked
    1 times
    Twitter
    DemoManMLS
    Phone
    Droid RAZR
    #3
    I've downloaded a number of ROMs manually along with using ROM Manager to download them. Same thing. However a few ROMs such as Ultimate Droid install just fine. Right now I have ClockworkMod 2.5.0.1 installed for my recovery.
  5. Droid Ninja
    teddyearp's Avatar
    Member #
    27105
    Join Date
    Jan 2010
    Location
    Randle, WA
    Posts
    1,801
    Liked
    19 times
    Phone
    SamsungŪ SCH-I515
    #4
    Hmmm, got me wondering. Maybe try installing one by manually booting into CMRecovery. Do the backup, then go to the partitions menu and format your /system, /data, /cache, NOT YOUR SDCARD!!, etc., then try installing the rom. On another note, I've got a fellow who's been contacting me via e-mail through my site that is having trouble with LFY as well. It seems as though it corrupted his custom recovery.

    good luck
  6. Droid Sensei
    Dave12308's Avatar
    Member #
    4889
    Join Date
    Nov 2009
    Posts
    3,274
    Liked
    209 times
    Phone
    Droid Bionic
    #5
    You've got bad memory blocks in your boot partition, and now it isn't large enough to hold the boot image. This is a hardware problem, and in the wrong partition can be fatal. As a last resort you could try using RSDLite to flash an SBF file, but this doesn't look promising:

    Installing Boot Image...
    mtd: not writing bad block at 0x00280000
    mtd_write_data to boot failed: No space left on device

    The problem is, certain partitions on the DROID are exactly the size they need to be to hold the image.
  7. Senior Droid
    Demolition Man's Avatar
    Member #
    64601
    Join Date
    May 2010
    Location
    Pawnee, IN
    Posts
    246
    Liked
    1 times
    Twitter
    DemoManMLS
    Phone
    Droid RAZR
    #6
    What's weird is that some ROMs install fine on my Droid (ie: Ultimate Droid). I tried formatting everything but the SD card as well. So my thoughts are it has to be something with the particular boot files used with certain ROMs such as LFY that are causing this to happen since obviously other ROMs are installing on my device just fine.
  8. Droid Ninja
    teddyearp's Avatar
    Member #
    27105
    Join Date
    Jan 2010
    Location
    Randle, WA
    Posts
    1,801
    Liked
    19 times
    Phone
    SamsungŪ SCH-I515
    #7
    And it may well be related to LFY. Like I said I was helping a guy through email who finally had to use MC1's SPRecovery only .sbf file to be able to get a custom recovery on his phone, and then go about restoring his CMRecovery nandroid backup.
  9. Droid Sensei
    Dave12308's Avatar
    Member #
    4889
    Join Date
    Nov 2009
    Posts
    3,274
    Liked
    209 times
    Phone
    Droid Bionic
    #8
    Quote Originally Posted by Demolition Man View Post
    What's weird is that some ROMs install fine on my Droid (ie: Ultimate Droid). I tried formatting everything but the SD card as well. So my thoughts are it has to be something with the particular boot files used with certain ROMs such as LFY that are causing this to happen since obviously other ROMs are installing on my device just fine.
    I do know that some kernels use a different ramdisk image, and if I recall some of them were slightly larger than stock. It could be that LFY's kernel is just big enough to not fit if there are any bad blocks at all.

    I will say that a bad MTD block error is definitely on the hardware level and not the software; MTD stands for Memory Technology Device; and the block remapping is similar to the way bad sectors are marked unusable on a PC hard drive.

    This link explains how the MTD block project enables flash memory capabilities in embedded Linux OSes (such as Android on a kernel level):

    http://www.righthandtech.com/embedde...ing-memory.php
  10. Senior Droid
    Demolition Man's Avatar
    Member #
    64601
    Join Date
    May 2010
    Location
    Pawnee, IN
    Posts
    246
    Liked
    1 times
    Twitter
    DemoManMLS
    Phone
    Droid RAZR
    #9
    Found a fix. I replaced the boot.img file on LFY 1.95 with the one used with UD 2.1. LFY 1.95 installed perfectly on my Droid with this fix. Thanks everyone for the help.
  11. Droid Ninja
    teddyearp's Avatar
    Member #
    27105
    Join Date
    Jan 2010
    Location
    Randle, WA
    Posts
    1,801
    Liked
    19 times
    Phone
    SamsungŪ SCH-I515
    #10
    Good! But just curious, does your WiFi still work? Usually all kernels have to have the twilan.drv.ko file compiled with them.
Page 1 of 2 12 LastLast

Links

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. Status 7 error + sbf file please
    By Rider003 in forum Android Hacks and Help
    Replies: 10
    Last Post: 11-12-2010, 11:06 AM
  2. Error: Nandroid exited with status 31
    By insult in forum Android Hacks and Help
    Replies: 28
    Last Post: 08-03-2010, 08:04 PM
  3. Error: nandroid exited with status 20 -PLEASE HELP
    By joander7 in forum Android Tech Support
    Replies: 2
    Last Post: 06-22-2010, 07:06 PM
  4. ERROR: Nandroid exited with status 28
    By cb3FSU in forum Android Hacks and Help
    Replies: 1
    Last Post: 03-12-2010, 06:37 PM
  5. Update to 2.0.1 - Error status 7
    By psufan5 in forum Android Tech Support
    Replies: 4
    Last Post: 12-23-2009, 07:56 AM

Search tags for this page

android write raw image no space left on device
,
assert failed write raw image /tmp/boot.img
,

assert failed write raw image status 7

,
assert failed write raw image tmp boot img boot status 7
,
assert failed: write raw image status 7
,
assert failed: write-raw-image (/tmp/boot.img, boot) and e:e
,
boot.img status 7
,
clockworkmod assert failed write raw image
,
write raw image
,
write raw image status 7
Click on a term to search our site for related topics.
Find us on Google+