[Q] assert failed: write_raw_image("tmp/boot.img","boot") - Android Q&A, Help & Troubleshooting

i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.

---

chchia said:
i believe this question is asked before, but the search function is not working at the moment.
I am using a Incredible S with S-OFF, installed with a custom recovery that confirm working with some other rom.
i decided to make one rom my self, i setup the Kitchen enviroment, and extracted the official RUU follow the tutorial, everything goes fine.
until i copied it to my SD card and trying to flash, i will get the following messsage
assert failed: write_raw_image("tmp/boot.img","boot")
can anyone help me? i had tried different setting for and make about 10 rom but all return the same message.
thank you.
Click to expand...
Click to collapse
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...

---

You can send the "update-script" to me,then let me give a look.
My email addrress:[email protected]

---

Or just paste it here so that it can help everyone.

---

dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Well.Take it onder in the web,let me try to download it.
So,I can take a look.

---

dsixda said:
Or just paste it here so that it can help everyone.
Click to expand...
Click to collapse
Maybe it is this:"write_raw_image tmp/boot.img boot"

---

zeaxion said:
Maybe it is this:"write_raw_image tmp/boot.img boot"
Click to expand...
Click to collapse
No .... that is wrong syntax. Won't even work in an update-script. For the Incredible S you need an updater-script (not update-script). Commands are followed by parentheses, with each parameter followed by a comma, and then a semi-colon at the very end. Run the kitchen on your ROM to get the proper syntax.
Anyways, nothing can be done at this point unless the original poster provides more detail, like at least posting his updater-script.

---

I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App

---

Mattix724 said:
I'm no developer but I believe it should be write_raw_image BOOT:boot.img
Correct me if I'm wrong
Sent from my Zio using XDA App
Click to expand...
Click to collapse
That's correct syntax, but it doesn't work on newer htc devices because of the new filesystem formats. Boot.img has to be copied to /tmp folder before it can be flashed to device. You have to use updater-script to accomplish that.

---

dsixda said:
The same problem happened on the myTouch 4G but works with this:
package_extract_file("boot.img", "/dev/block/mmcblk0p22");
Let us know if it works...
Click to expand...
Click to collapse
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way

---

I never had any issues using
assert(package_extract_file("boot.img", "/tmp/boot.img"),
write_raw_image("/tmp/boot.img", "boot"),
delete("/tmp/boot.img"));
in my updater-script for Incredible S.

---

lars.oakland said:
That's from ADB? My MT4G is stuck at:
Flashing Kernal ...
assert failed: write_raw_image("/tmp/boot.img","boot")
E:Error in /sdcard/download/virtuous_fusion-glacier-rom-v1.0.9.zip
(Status 7)
Installation aborted
Any help is greatly appreciated. Stuck on a bootscreen in a bad way
Click to expand...
Click to collapse
Status 7 usually means you are using the wrong update-binary.

---

dsixda said:
Status 7 usually means you are using the wrong update-binary.
Click to expand...
Click to collapse
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.

---

chchia said:
assert failed: write_raw_image("tmp/boot.img","boot")
Click to expand...
Click to collapse
Should tmp/boot.img be /tmp/boot.img?

---

Mioze7Ae said:
Should tmp/boot.img be /tmp/boot.img?
Click to expand...
Click to collapse
Good catch!

---

rsxtypes72 said:
For us that know little can you elaborate and what that means exactly?
Per your previous answer I tried using an updater based on other devs work and I still get the same error on my g2.
I just wanted to add that I do run the error check and it says the update binary fine. No errors.
Click to expand...
Click to collapse
Update-binary is not the update-script.
The update-binary file is supposed to be included with the updater-script and contains all the command implementations that are used in the script... however there are three main types of update-binary and you have to know which one to include. They are mostly differentiated by the number of parameters supported for the 'mount' command for your updater-script.

---

All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App

---

rsxtypes72 said:
All I the roms I have made have both the update and updater scripts included. That's why I'm stumped. I am using the leaked gb rom for g2. Oh well. Thank you for everything.
I'm gonna try to do and root the boot.img myself. Decompile and compile.
Sent from my T-Mobile G2 using XDA App
Click to expand...
Click to collapse
On your G2 you should have only an update-script in the ROM, or else the two other files (updater-script and update-binary), not both at the same time. The updater-script is a more advanced script than the update-script yet very similar.
The new versions of ClockworkMod only support the updater-script + update-binary however.

---

dsixda said:
The new versions of ClockworkMod only support the updater-script + update-binary however.
Click to expand...
Click to collapse
This is why the roms have both. I have not come across a single htc vision rom that only has an update-binary in it. They all have both
Sent from my T-Mobile G2 using XDA App
Update.
I just wanted to add that I have tried countless times to make a rom. I check that update script has no error and still I get the same error.
The weird thing is if I use a custom rom from one of the devs that does boot and I use the kitchen to go from edify to amend and then try to
convert it back later after I have made changes using the kitchen it wont boot and results in same write error.
Has anyone been able to make a bootable vision rom using the kitchen? If you have can you tell me where I can look or can you give me some answers. Yes I have checked google. No luck. Thanks
Im almost ready to give up.
I did make one rom that booted up and worked fine. Except when i went thru the steps to make the zip I removed the updater-script and update-binary created by the kitchen and replaced them with the udpater-script and update binary from one of the dev roms I use. This is the only way I have gotten a rom to flash and boot.

---

Just a thought. I know you said the htc vision is supported but would adding an edify_def for it help solve the problem?
Sent from my T-Mobile G2 using XDA App