[FIX] for Status 7 Error in Nexus S 2.3.1 Upgrade

[Amin Sabet]

Those of us who flashed rootboot.img to install a rooted/insecure boot image were unable to update via the 2.3.1 OTA (Status 7 Error). A few different solutions have been posted. Here's one which worked for me, courtesy of momohammed20 and Luxferro:

Step 1: Restore the "2010-12-22.21.06.07" Nandroid backup which momohammed20 shared in this thread. That wipes your phone completely and gives you stock 2.3.1 without root.

Step 2: Follow the steps provided by Luxferro in this post. That gets you back root along with ClockworkMod Recovery.

Worked perfectly for me. Again, the solution is already out there in a few other threads, but I thought this deserved its own thread since a lot of folks have been stuck with the Status 7 error when trying to update.

Thanks again to momohammed20 and Luxferro!

 

[petep86]

Umm if we have 2.3 we can't nandroid a 2.3.1 backup. Ull get an error every time.

Sent from my Nexus S using XDA App

 

[Amin Sabet]

I followed these steps, and they worked nicely with no errors whatsoever. Others have done the same.

 

[petep86]

U were runninr2.3 rooted and then nandroid the 2.3.1 and u didn't get a MD5 error? Hard to beloved BC I've tried 5 times. Can anyone else try this out n let us know? ?

Sent from my Nexus S using XDA App

 

[petep86]

EDIT: just got it to work.. I re-downloaded it and it loaded. Seems the nandroid I dl from that thread the first time got renamed n it had a "(" in it, and recovery couldn't read the file...
Thanks alot tho, u were right!!

Sent from my Nexus One using XDA App

 

[TheBiles]

So will this allow the future flashing of OTAs without issue?

 

[nsavani]

i also want to know if this will allow for future updates. i dont want to be reflashing my phone for every minor update.

 

[petep86]

Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR

Oh btw there's no root, in case u didn't understand what Stock 2.3.1 meant.

Sent from my Nexus S using XDA App

 

[TheBiles]

Yes it will. The bootloader remains unlocked. But it restores everything to stock 2.3.1, and will have stock recovery, so next time there's a OTA it won't get an error when Its flashing BC u will be using the stock recovery n not CWR

Sent from my Nexus S using XDA App

From what I understand, the problem lies in the boot.img and not ClockworkMod.

 

[petep86]

From what I understand, the problem lies in the boot.img and not ClockworkMod.

What problem are u referring to?
That u can't ota the update??


Sent from my Nexus S using XDA App

 

[TheBiles]

What problem are u referring to?
That u can't ota the update??


Sent from my Nexus S using XDA App

"Status 7" is the result of a rooted boot.img. It has nothing to do with ClockworkMod Recovery.

 

[Amin Sabet]

So will this allow the future flashing of OTAs without issue?

I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.

 

[demo23019]

Wish this was posted this morning before i gave up

between some people getting it to work and other not working. People posting methods with stock boot.img but come to find out it wont work with rootboot....ect
Then realizing some people are on one root method while other used another...too confusing and i gave up after countless tries and gave and flashed modaco GRH78 r2 and glad i did because its pretty good..

IMO guys if this is going to require to you wipe your data save your self from headaches and just flash modaco GRH78 r2 with supercurio's EXT4 tweak it also rooted has new market and other fun stuff

 

[Amin Sabet]

demo, that's a good point. I'm using the r2 MoDaCo ROM now - it seems very good!

 

[Luxferro]

I don't know about that. For this particular OTA, it seems that the problem was the root boot. The method in the OP addresses that. However, I wouldn't assume that the next OTA will be compatible with a rooted device. My understanding (and I am no authority) is that the only way to know you're going to be getting OTAs is to revert to full stock. My intent was to have root and recovery in 2.3.1, not to get back to stock and stay there.

Nope, that is false. I had initially used superboot to root my phone when I first got it (w/ the pre-rooted modified boot.img). And I still got the prompt for the update. It will just give you a MD5 mismatch error when you accept the prompt and try to update.

 

[Amin Sabet]

deleted (accidental double post)

 

[Amin Sabet]

Luxferro, I think you misunderstood what I wrote. I too was rooted and got the prompt for this particular OTA, and some folks who were rooted (without root boot) were able to apply the OTA without an error. What I was trying to say was that the only way to be sure that they can receive and apply all future OTA updates would be to revert to stock (or have a means to revert to stock).

 

[godsfilth]

the status 7 error is a result of the patch process not finding a proper checksum for the things its patching if you have deleted system/framework apk's/odex's de-odexd the system/framework themed the system/framework changed the kernel this will cause status 7 error and will give you a hint on where the issue lies i.e. it will say somthing about calculator not match if you deleted it and error code 7