Welcome to XDA

Search to go directly to your device's forum

Register an account

Unlock full posting privileges

Ask a question

No registration required
Post Reply

[FIX] Fix Status 7 error on assert raw write

OP geoffcorey

20th March 2012, 08:03 PM   |  #1  
geoffcorey's Avatar
OP Senior Member
Thanks Meter: 479
 
2,157 posts
Join Date:Joined: Apr 2010
More
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
Attached Files
File Type: zip insercure-kernel.zip - [Click for QR Code] (3.87 MB, 2356 views)
The Following 20 Users Say Thank You to geoffcorey For This Useful Post: [ View ]
20th March 2012, 08:11 PM   |  #2  
EddyOS's Avatar
Recognized Contributor
Flag Liverpool, Merseyside
Thanks Meter: 3,241
 
13,616 posts
Join Date:Joined: Jan 2010
More
I'm sure this will come in handy for a lot of people. Good job!
20th March 2012, 08:13 PM   |  #3  
Bluewall's Avatar
Senior Member
Flag Sion
Thanks Meter: 869
 
2,128 posts
Join Date:Joined: Apr 2010
More
Excellent man, don't need but thanks for thinking for people with issue

Really well appreciated in a community
18th July 2012, 07:45 AM   |  #4  
Senior Member
Flag New York
Thanks Meter: 17
 
146 posts
Join Date:Joined: Apr 2010
Donate to Me
More
Thumbs up Thanks
Quote:
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!..
18th July 2012, 12:17 PM   |  #5  
T-Macgnolia's Avatar
Senior Member
Flag Shannon, Ms.
Thanks Meter: 1,897
 
3,708 posts
Join Date:Joined: Sep 2010
Donate to Me
More
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.
The Following User Says Thank You to T-Macgnolia For This Useful Post: [ View ]
16th September 2012, 10:47 PM   |  #6  
Junior Member
Flag Bucharest
Thanks Meter: 0
 
20 posts
Join Date:Joined: Dec 2010
More
Doesn't work on SGS plus. Status 7 remain and bootloop in recovery mode.
16th September 2012, 11:58 PM   |  #7  
rzr86's Avatar
Senior Member
Flag Nafpaktos
Thanks Meter: 2,203
 
7,281 posts
Join Date:Joined: May 2012
More
Quote:
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
17th September 2012, 04:05 AM   |  #8  
geoffcorey's Avatar
OP Senior Member
Thanks Meter: 479
 
2,157 posts
Join Date:Joined: Apr 2010
More
Quote:
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
10th October 2012, 10:31 AM   |  #9  
Keupie's Avatar
Senior Member
Flag Apeldoorn
Thanks Meter: 38
 
151 posts
Join Date:Joined: May 2010
More
Very usefull!! Thanks a lot!!

Sent from my HTC Sensation XE with Beats Audio using xda app-developers app
10th October 2012, 12:11 PM   |  #10  
Junior Member
Thanks Meter: 0
 
23 posts
Join Date:Joined: Jan 2012
Quote:
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)

Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes