[FIX] Fix Status 7 error on assert raw write

---

I see a few people asking the question about status 7 error when trying toflash a custom kernel on their sensation.

Here is a quick breakdown of a boot.img

boot.img = zimage (the kernel) + ramdisk.

ona stock sensation or a boot.img taken from an ruu, the ramdisk has a protection flag set (ro.secure=1 in default.prop needs to be changed to ro.secure=0).

The kernel devs here, package their kernel updates in a way that copies the current ramdisk, and then comines them with their compiled zimage to make a boot.img which is then flashed. This method is actually the preferred way, and causes the least amount of issues/errors.

But this method fails with a protected ramdisk, which results in the status 7 error about write_raw failed. So to get around this, you must first flash an insecure boot.img.

Most (if not all) custom roms provide you with an insecure boot.img to begin with.

but to shroten the process, i'm going to link an insecure boot.img for those who don't want to change/install a custom rom.

MD5: 36d3e33740dc5799a5b53ee42d579e81

I'm sure this will come in handy for a lot of people. Good job!

Excellent man, don't need but thanks for thinking for people with issue

Really well appreciated in a community

Thanks

---

Originally Posted by geoffcorey

I see a few people asking the question about status 7 error when trying toflash a custom kernel on their sensation.

Here is a quick breakdown of a boot.img

boot.img = zimage (the kernel) + ramdisk.

ona stock sensation or a boot.img taken from an ruu, the ramdisk has a protection flag set (ro.secure=1 in default.prop needs to be changed to ro.secure=0).

The kernel devs here, package their kernel updates in a way that copies the current ramdisk, and then comines them with their compiled zimage to make a boot.img which is then flashed. This method is actually the preferred way, and causes the least amount of issues/errors.

But this method fails with a protected ramdisk, which results in the status 7 error about write_raw failed. So to get around this, you must first flash an insecure boot.img.

Most (if not all) custom roms provide you with an insecure boot.img to begin with.

but to shroten the process, i'm going to link an insecure boot.img for those who don't want to change/install a custom rom.

MD5: 36d3e33740dc5799a5b53ee42d579e81

Thank you very very very much, finally i able to flash my favorite kernel!..

This is a quick and easy way to fix the problem. But for those that don't mind getting their hands dirty can change the ro.secure=1 to ro.secure=0 manually using Dixda's Kitchen from here on XDA. Just thought I would through that out there.

Doesn't work on SGS plus. Status 7 remain and bootloop in recovery mode.

Originally Posted by sabian01

Doesn't work on SGS plus. Status 7 remain and bootloop in recovery mode.

i'm not sure for my answer but i think it fails because of different software or some kind of kernel code
different devices
or i'm telling bull****s

Originally Posted by sabian01

Doesn't work on SGS plus. Status 7 remain and bootloop in recovery mode.

What's an "SGS plus"? This is only for HTC sensation.

Sent from my Galaxy Nexus using Tapatalk 2

Very usefull!! Thanks a lot!!

Sent from my HTC Sensation XE with Beats Audio using xda app-developers app

Originally Posted by geoffcorey

I see a few people asking the question about status 7 error when trying toflash a custom kernel on their sensation.

Here is a quick breakdown of a boot.img

boot.img = zimage (the kernel) + ramdisk.

ona stock sensation or a boot.img taken from an ruu, the ramdisk has a protection flag set (ro.secure=1 in default.prop needs to be changed to ro.secure=0).

The kernel devs here, package their kernel updates in a way that copies the current ramdisk, and then comines them with their compiled zimage to make a boot.img which is then flashed. This method is actually the preferred way, and causes the least amount of issues/errors.

But this method fails with a protected ramdisk, which results in the status 7 error about write_raw failed. So to get around this, you must first flash an insecure boot.img.

Most (if not all) custom roms provide you with an insecure boot.img to begin with.

but to shroten the process, i'm going to link an insecure boot.img for those who don't want to change/install a custom rom.

MD5: 36d3e33740dc5799a5b53ee42d579e81

no any chenge (status 7)