[FIX] Fix Status 7 error on assert raw write

Search This thread
By:
Advanced…
geoffcorey

geoffcorey

Senior Member
Apr 24, 2010
2,156
484
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
 

Attachments

  • insercure-kernel.zip
    3.9 MB · Views: 3,380
  • Like
Reactions: reynard80, Levanthan, lykosha and 18 others
P

pedroflovera

Senior Member
Apr 4, 2010
167
30
New York
Thanks

geoffcorey said:
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
Click to expand...
Click to collapse

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

T-Macgnolia

Senior Member
Sep 30, 2010
3,796
2,023
Shannon, Ms.
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.
 
  • Like
Reactions: BanB
Keupie

Keupie

Senior Member
May 12, 2010
175
38
Apeldoorn
Very usefull!! Thanks a lot!!

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

mohammadx

Member
Jan 6, 2012
23
0
geoffcorey said:
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
Click to expand...
Click to collapse

no any chenge (status 7) :(
 
Uchiha_GT

Uchiha_GT

Senior Member
Dec 18, 2012
187
11
This is exactly what I need! Thank you!!!!

Sent from my HTC Sensation Z710e using xda premium
 
Uchiha_GT

Uchiha_GT

Senior Member
Dec 18, 2012
187
11
Where can i find the boot.img that ro.secure=1. I need to flash it back because I believe it may be linked to wifi issues on the stock ics rom...
 
kalrocking

kalrocking

Senior Member
Nov 12, 2012
70
12
34
Goa
Still the same error not working

i have successfully flashed the insercurekernel.zip but still i am getting the same error ..

Please help me ..
 
rzr86

rzr86

Senior Member
May 21, 2012
8,106
2,455
38
Nafpaktos
kalrocking said:
error 7

write raw image failed some assert failed ...
trying to install sebastian overclocked kernel.. tried few others also still not working ...
Click to expand...
Click to collapse

are you sure you flashed the insecure kernel.zip successfully?
because its job is to fix status 7

reflash again the insecure kernel and then flash sebastian's kernel
 
You must log in or register to reply here.

Similar threads

shnizlon
[ROM][Sense 4.0][FINISHED] OrDroid 9.0.0 | EQS | APM | Tweaks | Fast & Stable
Replies
17K
Views
3M
dodge67
dodge67
mike1986.
[ROM] Android Revolution HD 7.3 | ICS | High Quality & Performance | Legendary
Replies
81K
Views
16M
Ulumia
Ulumia
xl VipeR lx
  • Poll
[Guide] to Installing S-off, Unlocking, ClockWork, Root, SuperCID & S-on
Replies
5K
Views
2M
H
htcuser445
mike1986.
[DEV] HTC Sensation & HTC Sensation XE firmware | Partitions Info | [11.07.2012]
Replies
2K
Views
1M
M
murchz
A
[ROM] CM-10.1 AOSP 4.2.2 Jellybean [KANG] [Aug-6]
Replies
13K
Views
3M
Lamiszcze
Lamiszcze

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 21
    geoffcorey
    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
    View
    1
    T-Macgnolia
    T-Macgnolia
    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.
    View

New posts