• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Another JB Update?!

Error 7 means something in the system files has been changed. Are you running a custom Rom? If I recall, you might be running Party Time JB. If so you'll have to flash a stock Rom first before the update will take.

ZJones' cwm-flashable stock Rom will work (use the non deodexed one).
Or Tyler's stock JB backup which can be restored with cwm.

Just flashed stock rom, still a no go. do I need to clear my data?
 
I followed the directions (i think i did it correctly) and I get a status 7 error when flashing the MD6 to MD12
can i get some help?

FWIW, I got that error when I tried to flash the update using the older 6.0.2.3 CMW recovery. If you're using that version, you might try installing the newer 6.0.3.6 CWM recovery and try flashing the update using that.
 
Still not working for me. Tried to restore stock jellybean and it takes. Tells me to update but i keep getting error 7 and update fails
 
What I did was clear the data from Google Services Framework and then checked for updates, per the advice of Sanjuro. (Check out my "New plan!" thread for details.)


This actually got the update downloading, thanks! I'll install it after school and see if it works.
 
I hit install when it finished downloading and it booted into CWM
It started to install but I got an error 7 and it rebooted
 
I hit install when it finished downloading and it booted into CWM
It started to install but I got an error 7 and it rebooted

Copy the update file to your sdcard or another location, boot to cwm and try it again from the new location. I've read others doing this in the past and having it work. Is worth a try.
 
Okay. So. I had busy box and superuser on my SD card already so I decided to root my phone, move the update and install it. I'm still getting error 7!
 
This is a shot in the dark, but maybe try disabling signature certification , in cwm? - toggle sig verification in cwm

Any bloatware or stock apps frozen or disabled with Titanium backup or similar app? - defrost/enable

Is your phone currently updated to MD6, or is it running something before that? - get and install previous update

Status 7 definitely means there is something on your phone "incompatible" with the new install. It's like a safeguard to keep you from hard bricking your phone. That said, it also sometimes keeps you from updating if you've modded something. There's workarounds for that too but it's a lot more involved.

Can you take and post a screenshot of your device info page?
 
This is a shot in the dark, but maybe try disabling signature certification , in cwm? - toggle sig verification in cwm

Any bloatware or stock apps frozen or disabled with Titanium backup or similar app? - defrost/enable

Is your phone currently updated to MD6, or is it running something before that? - get and install previous update

Status 7 definitely means there is something on your phone "incompatible" with the new install. It's like a safeguard to keep you from hard bricking your phone. That said, it also sometimes keeps you from updating if you've modded something. There's workarounds for that too but it's a lot more involved.

Can you take and post a screenshot of your device info page?

I previously had mirage kernel
no apps frozen or anything like that
turning off signiture verification didn't help.
So here is the screenshot you asked for:
tCR0Ed3.png
 
I'm also having the same issue with the status 7. I'm running rooted stock jb with stock kernel MD6. I've tried everything from flashing the MI2 thru cwmt, to a factory reset then flashing, to doing a wipe and reinstalling my backup with all bloatware and no mods and still a no go. The last time there was an update I just had to restore the phone with kies then update then odin and root again but this time kies fails to restore my phone, after the download progress finishes, it just shuts kies down and nothing happens. I have not flashed any roms or kernels at all, ever, I'm stock rooted.
 
I previously had mirage kernel
no apps frozen or anything like that
turning off signiture verification didn't help.
So here is the screenshot you asked for:
tCR0Ed3.png


I'm looking at your screenshot wondering if that mb3 baseband is causing your problems. Shouldn't it be md6?
Anyone know for sure?
 
I'm looking at your screenshot wondering if that mb3 baseband is causing your problems. Shouldn't it be md6?
Anyone know for sure?

I don't think it would be because it's MB3, mine says MD6 and phil and I have the same problem.


I will give this a try later tonight or tomorrow, depending if my kids give me the time, lol
 

Attachments

  • 2013-10-02 19.58.59.png
    2013-10-02 19.58.59.png
    76 KB · Views: 82
Hi all. I joined just to help out if I can at all.
When I tried to get these updates I ran into mad problems with #7 errors as well.
What ended up working for me was getting the stock rom backup files from post #5 from the Out of the box sticky.
Then I copied them to the ext sdcard in the folder /clockworkmod/backup/StockICS
Rebooted into clockwork and did a restore from external sdcard.
After that finished I was back to everything stock and got the push for the MB3 update.
I flashed back to a stock recovery with Odin, booted up and the update was in the cache folder and it let me apply the update from cache!
Then I kept checking for updates till I got to MI2 baseband.
Once completely updated it was simple enough to reflash clockwork and the oh so sweet kernel from mrg666!
Pretty sure I had flashed MB3 improperly at some point even tho the phone worked fine.

Anyway hope this helps someone.
 
Back
Top Bottom