Database Info

[Q] Status 7 error, CWM 6.0.1.2

I'm trying to flash CM9 or 10, or really any update to what I have now. I'm rooted (verified in titanium backup pro), am on some ICS (It's been months and I don't remember, not stock). I'm running clockworkmod recovery touch 6.0.1.2.
I keep getting "status 7" error messages when I try to install the cyanogen mod zips. I've tried the latest stable release of 9, and a nightly of 10. I've done the recommended formatting/wipes from team chopstick's page, also tried wiping davlik. I had previously tried the wiping everything three times, that also did not work. The radio/modem installs fine, but I always get the status 7 when I try installing a different rom zip via CWM recovery.
In googling status 7, I came across several suggestions (for other phone models) that updating CWM should help, but Vincom's sticky suggests I should not update CWM.
I know I did update CWM following advice from here, I initially didn't have touch recovery, but that was months ago and I can't find the instructions to update to the latest CWM.
I'd also like to verify that status 7 can be solved by updating CWM before actually doing it. And what the heck is status 7 anyway?
Apologies in advance, I keep forgetting what I've read, as it's been months since I last did surgery on my phone.

Could be because of a md5 mismatch, check that first. Otherwise, time to upgrade cwm. Personally, i'd upgrade to the latest anyway.

I did check the MD5 sums and they matched.
I'm a little nervous about upgrading CWM since again, vincom's post says not to. I'm pretty sure last time I just ran the zip from inside CWM 4 or so, is that safe to do this time?

interkin3tic said:
I'm trying to flash CM9 or 10, or really any update to what I have now. I'm rooted (verified in titanium backup pro), am on some ICS (It's been months and I don't remember, not stock). I'm running clockworkmod recovery touch 6.0.1.2.
I keep getting "status 7" error messages when I try to install the cyanogen mod zips. I've tried the latest stable release of 9, and a nightly of 10. I've done the recommended formatting/wipes from team chopstick's page, also tried wiping davlik. I had previously tried the wiping everything three times, that also did not work. The radio/modem installs fine, but I always get the status 7 when I try installing a different rom zip via CWM recovery.
In googling status 7, I came across several suggestions (for other phone models) that updating CWM should help, but Vincom's sticky suggests I should not update CWM.
I know I did update CWM following advice from here, I initially didn't have touch recovery, but that was months ago and I can't find the instructions to update to the latest CWM.
I'd also like to verify that status 7 can be solved by updating CWM before actually doing it. And what the heck is status 7 anyway?
Apologies in advance, I keep forgetting what I've read, as it's been months since I last did surgery on my phone.
Click to expand...
Click to collapse
my sticky states not to use rom manager to update cwm, but its ok to update sk8's cwm from his op

Status 7 is md5 mismatch. Try downloading the rom again. And yes, use sk8's recovery rather than rom manager.
Sent from my CvD Nibbled Skyrocket
Quando Omni Flunkus Moritati

Apologies, I found that information eventually, updated via CWM, and was able to install cm9

[Q] [Ques] Unable to flash any rom via CWM after installing XXLSJ with Phillz Kernel

I have a S2 (GT-i9100).
I frequently switch between ROMs, the last rom i flashed was "[ROM][20 Nov][LSJ][4.1.2][V13.0] WanamLite Clean & Fast & Pure Stock Themed ".
The rom was good, fast and stable, but since it was draining the battery too fast, i decided to re-flash my daily driver (super-Nexus).
Unfortunately, when i tried to flash using CWM (phillz kernel), i got the "Status 7" error.
So, this is what i did: (offcourse i wiped cache/data/davlik cache)
1. Re-downlaoded "super-nexus" - That didnt help (the md5 was correct).
2. Downloaded another 4.1.2 "[ROM][23/11/12][JB/CM10&AOKP] Nostromo 1.5 [Tuning utils/TB] " - to my wonder i got the same error again
3. Then i did quite a bit of searching, found that, issue might be because of signature verification in CWM, when i toggled it i got "signature verification - enabled" - so i fig, it was disabled by deafult, i am yet to test by manually making it "disabled".
Could some1 please point me as to why after flashing with Phillz kernel for XXLSJ, m i getting this error, and why m i the only one getting it. I searched quite a lot, couldnt find anything
I am not a complete noob but m stuck here

Ny1 has any idea about this...
At this point any wild guesses wud do...I dont want to reflash via odin, that the last resort...

bhatti1209 said:
Ny1 has any idea about this...
At this point any wild guesses wud do...I dont want to reflash via odin, that the last resort...
Click to expand...
Click to collapse
Finally found a useful post in Phillz CWM thread:
http://forum.xda-developers.com/showthread.php?t=1877270&highlight=status+7&page=46
Since i have less than 10 posts i am not able to post this question directly on that thread, but could some1 please let me know where/how i can remove the assert commands (the ones that are being talked about in the link above).
I am trying to flash a new rom (super-nexus)

I had the same problem. Flashing DorimanX:s kernel first will solve the problem. Remember, this kernel is not compatible with the XXLSJ rom so only reboot the recovery (Advanced - Reboot Recovery). If the reboot freezes, just shut down the phone by long-pressing the power button and boot into recovery by holding Volume Up + Power.

Phone won't boot into ClockworkMod Recovery

Hi,
I currently have ClockworkMod Recovery 6.0.2.3 installed and am using ROM Manager Premium 5.5.1.5 to attempt to install CyanogenMod.
I have the correct rom downloaded for the Verizon version, but every time I try to boot into the ClockworkMod recovery, the standard Android Recovery screen comes up instead.
I have followed about 3 different tutorials, and each ended in the same result.
Any idea what could be going on?
Thanks!

Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.

Edgehood said:
Sounds like user error. If you're rooted, you can use EZ Recovery from the play store to flash your recovery of choice.
Click to expand...
Click to collapse
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..

Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM

CAKELIE said:
Thanks! That worked and got me into ClockworkMod Recovery. Now, the install of CyanogenMod failed. Now to figure out why that happened..
Click to expand...
Click to collapse
How did it fail?
Sent from my LG spectrum (that's right) blazing fast on cm10!

I am having almost the same problem. I rooted my phone using this:
<< 03.06.2013 - PhilZ-cwm6 v5.06.1 with CWM 6.0.3.2 based recovery >>
DDLSC - DXLSE - JPLSB - XXLT6 - ZSLO2 Fixed for bootloop
ZCLSF (no bootloop fix, proper default.prop)
http://d-h.st/users/philz_touch/?fld_id=16061#files
taken from here: http://forum.xda-developers.com/showthread.php?p=31911620#post31911620
as it matches my phone make, build, kernel's date, model, etc. The trouble is when I go to recovery mode from ROM Manager it just stops on its way showing me this green little robot and a progress bar in the middle and it could stay like this for hours without moving anywhere. I have to press my power button and then it moves on and reboots into CWM. I have tried a whole lot of different rootings methods but ROM Manager v5.5.3.7 simply refuses to work with PHILZ-CWM6-DDLSC-ODD-5.06.1-SIGND.ZIP... I am completely lost...
Could anybody suggest / advise anything please? I would highly appreciate it Many thanks in advance!
I am on Android 4.1.2 Jelly Bean, Samsung Galaxy Note GT N7000, build number is JZ054K.N7000DDLSC, baseband version is N7000DDLS6, kernel version is 3.0.31 – 906407 March 6, 2013.

[Q] Issue (Status 7)

Hello everyone, I tried to install two ROMs on my Galaxy (Slim and omni) I had root permission and recovery. However, as soon as I try to install zip from my microSD, after a few lines of code, it's stop process. in the last line there is written:
E:Error in /external_sd/(name of rom).zip
(Status7)
installation aborted.
what can I do?
thanks

Desmojack said:
Hello everyone, I tried to install two ROMs on my Galaxy (Slim and omni) I had root permission and recovery. However, as soon as I try to install zip from my microSD, after a few lines of code, it's stop process. in the last line there is written:
E:Error in /external_sd/(name of rom).zip
(Status7)
installation aborted.
what can I do?
thanks
Click to expand...
Click to collapse
Status 7 means that you need a newer recovery. I just used CWM 6.0.4.7 yesterday to put CM11 on my parents tab2.
Hope this helps

Also try installing zip from " internal " storage.
Pp.

Hi, from CWM download page, the latest version is 6.0.2.7 for the Tab2 10.1 wifi (P5110).
With it installed following Cyanogenmod tutorial, I also have the status 7 error when trying to install both Cyanogenmod 11 latest nightly build, or SlimKat 8 stable.
Device is not rooted, but tried to install ZIP files from internal sd.
Checksums are fine.
I'm interested in the answer if you don't mind me to squat your post?
PS: I'm used to use CWM on my gt-i9100 and gt-i9305 with no problem.
Sent from my GT-I9305 using XDA Free mobile app

Finally solved by updating CWM to unnoficial 6.0.5.0 found on the post here.
http://forum.xda-developers.com/showthread.php?t=2548476
Official 6.0.2.7 can't install kitkat roms and CWM team don't update it anymore for the Galaxy tab 2.
Sent from my GT-I9305 using XDA Free mobile app

If you want a more user friendly touch interface, try TWRP from Android Andi's recovery thread.

[Q&A] [RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.

[Q&A] [RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.
Q&A for [RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.0.3.6
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [RECOVERY][RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.0.3.6. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

I am trying to get the cwm 6.0.3.6 version for my gt-n8013 so I can flash to kit kat but the links aren't working for me. Does anyone have any other links?

Doesn't work on my Note 10.1" N-8010 with Android 4.1 . Everything seems to work fine after installing CWM (green "PASS" message) but after restarting ODIN MODE is present instead of cwm. Tried in different usb ports both usb 2.0 and 3.0 and no luck.

6.0.4.3
Hi, please can you please update CWM for N8010 to 6.0.4.3? Verry thanks
Or please, how can i install .img via odin please?
Thanks and sorry for bad english

Delete please. Post was automatically put here as I'm to new to post in the Gnabo rom thread. Makes no sense here though.....
Great work! My N8010 is new again . I do miss the haptic feedback while typing, but the benefits of the update outweigh the minor loss. Everything else seems smooth so far. Was the loss of haptic feedback an issue with the software update, or is that just the way it works in this version?
Thanks again!

I've got a boot-loop problem...
Specs:
N8013 - WiFi only
It had CW Recovery Touch 6.0.3.6 installed, I don't remember which ROM it was running, but one day it went in to a boot loop, and I cant seem to get it out of the loop. I can't even seem to get it in to recovery anymore.
When I go to download mode, I can flash a new recovery, (ive tried several methods - this one being the latest I've tried: wiki.cyanogenmod.org/w/Install_CM_for_n8013)
When I reboot the device holding Pwr and Vol+, I see a clockworkmod recovery message at the bottom of the screen that says no file_contexts. (not a quote, as it flashes rather quickly, then reboots)
At this point, I am rather certain that i've bricked the thing...
I've tried numerous recovery images, and each time i try and boot recovery, regardless of whether or not it was CWM, the CWM logo and version 6.0.3.6 appears at the bottom of the screen, even when that is not what I just flashed.
Anyone have any ideas?

PhiLz Recovery v6.0.3.6 touch edition
hi, can anybody confirm this custom recovery working fine on
Samsung Galaxy Note N8020 ? Any bugs?
Sorry but I can't download from the links provided on the main thread
" [RootGuide][ALL NOTE 10.1]Official CWM Recovery Touch & Non-Touch 6.0.3.6 "

Same here- What Gives?
sweetja713 said:
I am trying to get the cwm 6.0.3.6 version for my gt-n8013 so I can flash to kit kat but the links aren't working for me. Does anyone have any other links?
Click to expand...
Click to collapse
--> Yeah, I'm having the same download issue. Can see the link, but when you click on it ... it spins and times out! Is there another method of downloading and getting this link or is there a bigger and better build available for the N8013N??

HELP!
Please tell me there is more explanation. I've spent two days trying to find a ROM to install to upgrade past 4.1.2. I have CWM 6.0.1.1 installed and its not working with OMNI or anything else. Please help those of us who spent $600 on a tablet 2 years ago and now can't use apps because Samsung are jerks. The download links you have here are taking me to spam pages. Also, the clockwork page downloads .img files , not .tar or md5. So HELP!!!! I have GT-n8013....
sweetja713 said:
I am trying to get the cwm 6.0.3.6 version for my gt-n8013 so I can flash to kit kat but the links aren't working for me. Does anyone have any other links?
Click to expand...
Click to collapse